Changes between Version 1 and Version 2 of NextforHMS

01/28/10 06:18:48 (14 years ago)
Mark Prutsalis

Add additional requirements


  • NextforHMS

    v1 v2  
    1717These requirements were shared with us after review of the system's current functionality (on current vita branch currently being pushed eventually up to the EC2 instance).  SOUTHCOM was explicitly told that we would NOT be adding these features on/by 27 January - but that we would get them into the queue of things to work on for the next release. If you have time to begin to work on these on dev and get them in the queue for the next prod push, that would be good, but this is nothing to lose any sleep over.
     20== Additional Requirements based on 280110T0400Z review of notes from the day: ==
     23* '''Security''' - enable role management - this is an urgent requirement assigned to sysadmin team: Praneeth (lead), Tim & Dan.  Need written recommendation sent to mark by e-mail by 1600Z on 28 January 2010; meeting in #sahana-py at 1700Z on 28 January.  Background: security for personnel on ground makes it inadvisable to publish publicly the needs and fulfillment information that might be embedded in the HMS - i.e. publishing that medical supplies are to be delivered to this place at this time might put the shipment and relief workers lives at risk.  We need a plan to implement role-based access to different Sahana libraries.  I need the sysadmin team to advise which of the following requirements is possible to do through front-end configuration of SahanaPy security settings (preferred) and which will require coding changes (not preferred).  Alternatives are welcome.  The team should also evaluate and advise on the impact shutting down read-only public access to parts of sahana will have on our feeds of data on hospital locations and hospital management data.  Requirements:
     24  * Public/anonymous access:  Read only access to OR, RMS Twitter and 4636 Messages. 
     25     * Option to make HMS hospitals feed with location and general information - but not the shortages table - publicly available
     26     * Can we hide individual fields (like beds available, security status, facility status) from public view without code changes?
     27  * Registered users:  Read only access to entire system (adding PR and HMS / HMS shortages)
     28  * Entry users: Registered users who are given add/edit/update/delete access to OR, PR, HMS
     29  * Options to create additional groups that have add/edit/update/delete access to each individual registry - and bundle people that way.  e.g. Tim has write privileges to OR and PR but not HMS or RMS; Praneeth has write privileges to RMS but nothing else; Dan has write privileges to RMS, OR, and PR but not HMS. [[BR]]
     31* '''Provenance of data''' - without adding any fields (at this time), we need to display the last time data records were updated and by whom - we should be able to pull from the last modified column and the registered user who made the modification.  This is especially important to allow for evaluation of how old data is and how often it is being updated.  Maybe a big bold splash on upper right when viewing a hospital record would say "Last modified on DDMMYY at HH:MM UTC by <Registered User>".  Or just show the data as additional field in form view or column in table view.  [[BR]]
     33* '''Operating Room Status''' - add to list of services on Hospital entry/edit form - similar to Emergency Room, Clinical, Facility, Security fields now.[[BR]]
     35* Add Link to Bed Capacity, Services, Shortages, Contacts to main ADD Hospital form @ /hms/hospital/create[[BR]]
     37* Add Register for new account and Login Links prominent on home/splash page