Decision Support Module Goals
...
Decision Support OpenMRS Module Architecture
| Gliffy | ||
|---|---|---|
|
...
- At the REST layer, scraping calls for all resources (Preferred)
- At the service layer, hooking into other service calls
- At the database layer as SQL constraints
...
https://wiki.openmrs.org/display/docs/Clinical+Decision+Support
Where Does the Arden Rule Run? – triggered by any user call.
Responses to an Arden Rule Invalidation
The alerts should be as in-obtrusive as possible and not interrupt patient flow (unless Arden finds the rule breaking to be very severe/life threatening). In general, the alerts should show up in a small corner in the Outpatient module rather than a popup that requires the provider to click 'OK'.
Types of alerts:
--Informative: most rule invalidations should send this alert back. Appears as a small text field
--Overrideable: a more serious rule break incurs overrideable. Requires click from doctor (should avoid this as much as possible)
--Stop: does not allow data to be saved in the database. Only for life threatening rule breaks (should avoid this nearly always)
Note that this can be implemented by alertType member in the RaxaAlert data model.
Example Cases that Require Decision Support
The system should deal correctly with the following cases:
...
Proposed Timeline
September 3: DSS module working in OpenMRS 1.7.x
...