...
Requirement # | Description |
1.3.1 | The System shall have access to relevant patient medical data including diagnoses, medications, adverse events, radiology, labs, appointments, etc. |
1.3.2 | The System shall have access to relevant authoritative medical reference knowledge bases. |
1.3.3 | The System shall have access to other relevant authoritative decision support systems that have public, well-defined APIs. |
1.3.4 | The System shall have the ability to respond to data requests from relevant authoritative decision support systems that have been approved for system integration. |
1.3.5 | The System shall optionally limit its responses for data requests from authorized third party decision support systems according to local policy. |
1.3.6 | The System shall have the ability to present providers with questions and manually respond to data requests from decision support systems if automated access to such data is either not available or not desirable. Assumption: should define the data elements that would be accepted by the system for response. |
1.3.7 | The System shall provide a method of documenting decision support interactions(will new clinical data captured in interactive mode be send for storage to EMR?). |
1.3.8 | The System shall allow providers to override recommendations by the clinical decision support system. |
1.3.9 | KMR / DDSS shall provide information for auditable events and shall be configurable. |
1.3.10 | The system shall provide audit logs that include all inputs and outputs from inference engine (be conservative). |
1.3.11 | The system shall provide other authorized requesters, such as an EMR system, with audit responses/logs. |