Changes between Version 3 and Version 4 of Deployments/Ebola
- Timestamp:
- 10/15/14 08:33:17 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Deployments/Ebola
v3 v4 26 26 27 27 == Solution == 28 * Template ('Disease'? I see this as more widely applicable than Ebola, although Ebola is clearly the most pressing) 28 === Template === 29 Action: Fran 30 31 'Disease' I see this as more widely applicable than Ebola, although Ebola is clearly the most pressing 29 32 - enable only relevant modules 30 33 - customise menus … … 32 35 - customise modules 33 36 34 * Data Model 37 === Data Model === 35 38 - a link table between pr_person <> pr_person: pr_person_contact 36 39 - hms_person_status (lowest degree of separation from an infected person, tested (None, Positive, Negative), last-monitored datetime, last-monitored result, in-treatment-centre (hospital_id?)) 37 40 - hms_person_monitor: component of pr_person to record the monitoring results (if we need to keep historical) 38 41 42 === UI === 39 43 * Simplification of PR to minimum required for the usecase 40 44 - pr_contact … … 43 47 * Simplification of HMS to minimum required for the usecase (which could start as zero with all referrals happening off-system) 44 48 49 === Workflow === 45 50 * onaccept routine (run async where possible, even if unlikely on the older hardware we're talking) to flag record of contacts that need to go into enhanced monitoring...and provide a summarised list to the relevant person (email?) Do we notify the contact themselves via SMS? 46 51 52 === Reporting === 47 53 * Simple reporting to see a list (& totals) of contacts that we should be monitoring and their status 48 54 55 === Translation === 56 If it is to be used in Guinea, we should ensure the relevant strings are translated into French 57 58 === Testing === 59 60 === Installer === 49 61 * Build Installer 50 62 63 === Sync === 51 64 * Do we need Sync with a central server? 52 65