100 likes | 230 Views
HL7 EHR SIG New Projects- Tentative. Gary Dickinson 5 May 2004. Potential EHR SIG Projects. EHR-S Functional Model Profiles Interoperability Service Oriented Architecture EHR Record Interchange. EHR-S Functional Model Trial Use Period. Develop Profile Toolkit
E N D
HL7 EHR SIGNew Projects- Tentative Gary Dickinson 5 May 2004
Potential EHR SIG Projects • EHR-S Functional Model • Profiles • Interoperability • Service Oriented Architecture • EHR Record Interchange
EHR-S Functional ModelTrial Use Period • Develop Profile Toolkit • Promote Development of EHR-S Profiles • Care Setting Profiles: Generic • Use Profiles: Specific • Providers, Payers, Vendors, Professional Societies... • Realms (Countries) • Encourage Feedback to SIG
EHR-S Functional ModelFull Normative Standard • At Conclusion of “Trial Use” Period • Committee Ballot(s): 2005 • Membership Ballot: 2006 • Publication Target: Early 2007 • Gather Input and Feedback • From DSTU balloters • From Industry Sources, including Profiling Organizations and Realms • Incorporate into Proposal Database
EHR-S Functional ModelFull Normative Standard (con’t) • Update EHR-S Functional Model • From Proposal Database and Other Input • Revise Functional Statements, Descriptions • Revise Rationales • Develop Explicit Conformance Criteria • Per EHR-S Function
Health Record InteroperabilityWhat Is It? • What Does “Interoperability” Mean in the Context of Health Record Interchange? • Perspectives • Clinical • Technical • Define Interoperability Characteristics, Criteria
Health Record InteroperabilityMeasurable • Health Record Interchange • Lossless: Received HR = Original HR • Subset: Received HR is Subset of Original HR • Define Methodology for Measurement • Completeness Flag • If Subset, Pointer to Originating Application and/or Original Record
Health Record Interchange • “Dr Yasnoff” Project • Collaborators: Dr. Ed Hammond, Dr. Helga Rippen, Dr. Bill Braithwaite, et al. • Define Record Content • Record • Element • Define Record Interchange Methodology
Service Oriented Architecturefor EHR Systems • Next Generation • Beyond Messaging • Tightly Coupled Applications • Example(s) • n Tier: Presentation, Business Logic, Persistent DataStore
“Demand Side” Liaisons • Patient Care • Community Based Care • Pediatric Data Standards