70 likes | 225 Views
Clinical Work Process Architecture. Business Architecture. CONTEXT. Potential Applications. Clinical Work Process Architecture. System Architecture. Integration & Deployment Models. Information Architecture. 1. EHRS Work Process Architecture.
E N D
Clinical Work Process Architecture BusinessArchitecture CONTEXT PotentialApplications ClinicalWork ProcessArchitecture SystemArchitecture Integration &DeploymentModels InformationArchitecture 1
EHRS Work Process Architecture • The EHR Clinical Reference Framework: Life of the Lamberts • Depiction of the use of an EHR Solution in different contexts of health service delivery • 14 different storyboards created • Extensible by adding new use cases • System or security administration use cases not represented • Life of the Lamberts • Patient centric framework • Focused on different members of a family and their health status evolution • Focused on health related events • Represented with UML use case notation • Developed under Magic Draw case tool • Published as artefacts under the Artefact Repository • Available in HTML and PDF format • Available in Magic Draw format and XMI for upload to other case tools
Public HealthServices PharmacySystem RadiologyCenterPACS/RIS Lab System(LIS) Hospital, LTC,CCC, EPR PhysicianOffice EMR EHR Viewer EHR IP EHR IP EHR IP EHR IP EHR IP EHR IP EHR IP Public Health Provider Pharmacist Radiologist Lab Clinician Physician/Provider Physician/Provider Physician/Provider EHRS Reference Architecture HIAL Comm Step Put New Patient POS APPLICATION Life OfThe Lamberts SIGNIFICANT REUSEHERE Encounter COPDStoryboard EHR IP Add New Patient Clinical Events Encounter Clinical Activity Clinic VisitAdmission NewFamily PhysicianActivity NewFamily PhysicianActivity Storyboard EHR IP Storyboard EHR IP Clinical Events Clinical Activity EHR IP Clinical Events POINT OF SERVICE EHRS Reference Architecture 3
Longitudinal Record Services Common Services Communication Bus Documenting EHRi Services Requirements JURISDICTIONAL INFOSTRUCTURE Ancillary Data& Services EHR Data& Services DataWarehouse Registries Data& Services ImmunizationManagement PHSReporting SharedHealth Record DrugInformation DiagnosticImaging Laboratory HealthInformation ClientRegistry HIAL ProviderRegistry HIAL HIAL HIAL HIAL HIAL HIAL HIAL LocationRegistry BusinessRules EHRIndex MessageStructures NormalizationRules Terminology Repository HIAL HIAL Security MgmtData Privacy Data Configuration HIAL HIAL HIAL IP “Put” IP “List” IP “Get” IP “List” IP “Get” EHR IPData EHR IPData EHR IPData EHR IPData EHR IPData EHR IP EHR IP EHR IP EHR IP EHR IP Hospital, LTC,CCC, EPR PhysicianOffice EMR PhysicianOffice EMR EHR Viewer EHR Viewer Radiologist Lab Clinician Physician/Provider Physician/Provider Physician/Provider POINT OF SERVICE EHRS Reference Architecture
Common Services Communication Bus Security MgmtData Privacy Data Configuration HIAL EHR INTERFACE REQUIREMENTS DOCUMENTATION Life of theLamberts Storyboards Encounters ClinicalActivities People Use Cases: Caregiver Perspective JURISDICTIONAL INFOSTRUCTURE Ancillary Data& Services EHR Data& Services DataWarehouse Registries Data& Services • First class of deliverables are contextual & informational • They describe the end-user functional requirements and assumptions for use of an EHR Solution • Establish when POS applications expected to interact with an EHRi in the context of daily work activities for caregivers • Infoway not attempting to document all forms of potential uses of an EHR • Scope is broad enough to cover large spectrum of healthcare and public health service delivery to achieve representative set Public HealthServices PharmacySystem RadiologyCenterPACS/RIS Lab System(LIS) Hospital, LTC,CCC, EPR PhysicianOffice EMR EHR Viewer Public Health Provider Pharmacist Radiologist Lab Clinician Physician/Provider Physician/Provider Physician/Provider POINT OF SERVICE
EHR INTEROPERABILITY PROFILE Public HealthServices PharmacySystem RadiologyCenterPACS/RIS Lab System(LIS) Hospital, LTC,CCC, EPR PhysicianOffice EMR EHR Viewer EHR IP CommunicationSteps Public Health Provider Pharmacist Radiologist Lab Clinician Physician/Provider Physician/Provider Physician/Provider POINT OF SERVICE EHR Interoperability Profile (EHR IP) JURISDICTIONAL INFOSTRUCTURE Ancillary Data& Services EHR Data& Services DataWarehouse Registries Data& Services • Second class of deliverables normative; specify the interfaces between POS applications and EHR • Establishes a language to describe types of service requests made to an EHRi • Positions which data to be exchanged by referring to data views of the data model • Assumes SOAP-based web services calls where XML encoded HL7 V3 message requests and responses are carried between POS applications and the EHRi HIAL
Longitudinal Record Services JURISDICTIONAL INFOSTRUCTURE INFOSTRUCTURE INTEROPERABILITY PROFILE Ancillary Data& Services EHR Data& Services DataWarehouse Registries Data& Services ImmunizationManagement PHSReporting SharedHealth Record DrugInformation DiagnosticImaging Laboratory HealthInformation ClientRegistry ProviderRegistry BusinessRules EHRIndex MessageStructures NormalizationRules LocationRegistry InfostructureIP InfostructureServices Catalogue Generic InterfaceSpecification TerminologyRegistry POINT OF SERVICE Common Services EHR Infostructure IP (EHR I-IP) Communication Bus Security MgmtData Privacy Data Configuration HIAL • Third class of deliverables normative; specify inner workings within EHR Infostructure to orchestrate and process transactions • Express sequencing of activities to process transactions • Express expected capabilities of services within an EHRi to process transactions