1 / 25

HL7 V2 and V3 – where next?

HL7 V2 and V3 – where next?. Charlie McCay HL7UK Chair-elect Charlie@RamseySystems.co.uk. Charlie McCay. Interest in Clear and Testable specifications Chair Elect HL7UK Co-chair XML and Implementation groups in HL7.org Consult for NPfIT and others Speaking as myself (and for HL7UK).

etta
Download Presentation

HL7 V2 and V3 – where next?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HL7 V2 and V3 – where next? Charlie McCay HL7UK Chair-elect Charlie@RamseySystems.co.uk

  2. Charlie McCay • Interest in Clear and Testable specifications • Chair Elect HL7UK • Co-chair XML and Implementation groups in HL7.org • Consult for NPfIT and others • Speaking as myself (and for HL7UK) 2/25

  3. Topics • HL7 • Data Items and Technology • V2 • V3 • What to do now 3/25

  4. How HL7 works • HL7.org and HL7UK… • Products… • Organisation… • Meetings… • Ballots… 4/25

  5. HL7.org and HL7UK • Membership organisations • Both aim to provide standards that support Clinical Information System Interoperability • HL7UK does this in a UK context 5/25

  6. HL7 Products • Specifications • V2, V3, CDA, Arden, CCOW, … • Informative, Normative or Reference • Methods for developing specifications • MDF, HDF, … 6/25

  7. HL7 Organisation • ANSI, ISO, CEN • TCs, SIGs and others • Technical Committees • Special Interest Groups • HL7.org, and the affiliates 7/25

  8. HL7 Meetings • Working Group Meetings • Three meetings a year, 4-500 attendees • Committee work and tutorials • Harmonisation • Three times a year, 40 attendees • Conference calls, Mailing lists 8/25

  9. HL7 Ballots • Central and Affiliate • Committee and Membership • Joining ballot pools, and meaning of votes • Resolution of negatives 9/25

  10. Topics • HL7 • Data Items and Technology • V2 • V3 • What to do now 10/25

  11. Data items and Technology • “Semantics” is the definition of the data items that are permitted in the message • this is HL7 core business • “Technology” is what is used to transmit that meaning between systems • HL7 is a convenient place to share best practice 11/25

  12. Topics • HL7 • Data Items and Technology • V2 • V3 • What to do now 12/25

  13. V2 – what it looks like MSH|^&~\|HIS|HSP1|BEDMGMT|HSP1|200105311136||RSP^Znn^RSP_Q11|1|P|2.4| MSA|AA|8699| QAK|1022|OK| Znn^Find Location^HL70471|1|1|0 QPD|Znn^Find Location^HL70471|1022|LOC^Location Master^HL70175|HSP1|2N^101^^HSP1 MFE|MAD|||2N^101^^HSP1|PL LOC|2N^101^^HSP1|Station 2 North, room 101|R||(407)804-5000||IVP|P LCH|2N^101^^HSP1|||PRL^Privacy level^HL70324|S^Semi-private room^HL70262 LCH|2N^101^^HSP1|||SMK^Smoking^HL70324|Y^^HL70136 13/25

  14. V2 • Widely used in secondary care • Implementation-specific profiles • Used for “within institution” messaging • Messaging workbench for profiles • |^ and XML representations 14/25

  15. History revisited • V2 messages defined “as needed” • Limited depth because of the encoding • Implicit groupings • Ugly datatypes • “Z” segments 15/25

  16. Topics • HL7 • Data Items and Technology • V2 • V3 • What to do now 16/25

  17. HL7 V3 • What it looks like… • Background… • Cascade of Models… • Implementation Technology Specification… 17/25

  18. V3 – what it looks like <product contextControlCode="OP" typeCode="PRD" type="Participation"> <manufacturedProduct classCode="MANU" type="RoleHeir"> <manufacturedRequestedMaterial determinerCode="KIND" classCode="MMAT" type="ManufacturedMaterial"> <code codeSystem="2.16.840.1.113883.2.1.3.2.4.15" code="1084011000001108" displayName="Betamethasone valerate 0.1% cream 30 gram"> </code> </manufacturedRequestedMaterial> </manufacturedProduct> </product> 18/25

  19. Background to V3 • Moving out of the hospital • Too many committees • Richer data structures - Models • Changing technology • Not just messaging 19/25

  20. Cascade of Models RIM Medical Records Lab Pharmacy 20/25

  21. Implementation Technology Specification • Abstract definitions as XML (MIF) • XML first ITS off the block … • Java SIG for internal application interfaces • Other possibilities • HOM – HL7 Object Model ? • ??? 21/25

  22. XML Defined and Validated • ITS defines the set of valid instances • Schemas and other tools test conformance • Validation tools will improve • Schemas generated using XSLT • Different flavours of Schema could be done • Other validation tools 22/25

  23. Topics • HL7 • Data Items and Technology • V2 • V3 • What to do now 23/25

  24. Where Next? • National and local communications • Maintain semantic mappings (expensive) • Semantic migration harder than technical migration • Collaboration for semantic mappings • Sharing best practice • Feedback on what helps and what does not 24/25

  25. Products • Implementation Resource Kit • Evolution of UK HL7 (V2 and V3) standards • Frequently asked Questions • What else do you need? 25/25

More Related