70 likes | 103 Views
The EHR Simulator. Objective: To show that an EHR can be derived and maintained as a consequence of messages and transactions. Clinical Support Systems. EPR. Patient data repository. EHR Publication System. Work-flow Negotiation & Auditing. EHR workflows. EHR Portal/Hub. Audit trails.
E N D
The EHR Simulator Objective: To show that an EHR can be derived and maintained as a consequence of messages and transactions.
Clinical Support Systems EPR Patient data repository EHR Publication System Work-flow Negotiation & Auditing EHR workflows EHR Portal/Hub Audit trails Clinical register Registration System EHR Gateway Patient consent EPR system register EHR Management Domain EHR Access Systems Tokens EHR Service Domain EHR resource distribution
Clinical Service System Call Handling & Triage User (E) G G EPR Hospital Clinical System User (H) G Bookings G User (P) EHR Publication System G G EHR Publication System EHR Portal EHR Portal G ConsentRegister Rules Gateway services G UserRegister Practice System Trusted Third Party Server User (GP) EPR Pharmacy System PCT System
Registrations Prescription 1 Consent registration GP Publication GP eczema Referral to Cardiologist Radiology Referral Lab Orders Cardio Appointment Radiology Appointment Lab Results ECG Result CXR Result Ambulance Call Ambulance Results A&E Triage A&E Orders A&E Radiology A&E Rad Results A&E Lab Results Hospital Discharge Referral for Exercise Test Simulator Messages and transactions Each message has an XML schema and a publication rule which defines what data will be recorded, where it will be recorded and how the root publication server will be notified.