An introduction to HL7 version 3 and the NPfIT Message Implementation Manual

1. An introduction to HL7 version 3 and the NPfIT Message Implementation Manual (c) 2005, Blue Wave Informatics LLP

2. Explosion in number of Interfaces • Information for Health proposes using IT to better share patient record • Must interface different systems together • How many interfaces do we need? • 2 Systems = 1 Interface • 3 Systems = 3 Interfaces • 4 Systems = 6 Interfaces • n Systems = n*(n-1)/2 Interfaces • 15 GP Pharmacy Systems = 105 Interfaces • 250 Trusts = 31,125 Interfaces • x Systems in each trust = xxxxx • Something has to be done!

3. Database Model Real World HL7 Model HL7 is an Information model not Database Model

4. 3 Core Concepts to Cover • Static Models • Dynamic Models • Implementation Technology Specification

5. HL7 Model Classes (6 core + 1) Role Partici-pation Act Role Relation Role Act Relation Entity Non core Act

6. Static Model Underlying Structures • Reference Information Model • Vocabulary • Data Types Specification • Communications Infrastructure

7. Dynamic Model – An Outline ReceiverResponsi-bilities Application Roles Payload Trigger Events

8. Implementation Technology Specification • Models are not tied to a method of implementation BUT • Currently models become XML schemas

9. Use of XML for HL7 Messaging

10. What makes HL7 a Standard? • HL7 is an accredited ANSI standards body • Recognised by CEN and ISO as the leading body in healthcare messaging • HL7 Standards become ISO standards • To become an HL7 Standard must be balloted • Three ballots per year • RIM and Datatypes are normative

11. The Ballot Pack …

12. Localisation • Can refine models by restricting specification • Can replace vocabulary with local vocabulary • Leads to NPfIT Message Implementation Manual - The MIM !

13. The MIM

14. MIM Contents • Domains • A&E … • Diagnostic Imaging • eBooking … • GP2GP • Infrastructure … • Medication Management … • PDS • Provision of Care • PSIS Query • Data Types • Vocabulary

15. Using The MIM • The MIM is accessible from the repository on the HL7 UK web site • It documents the models and schemas used for NPfIT messaging • It documents the localised content compared to HL7.ORG Ballot 6 • You need to look at the Ballot 6 content as well as the MIM

16. An example message fragment for eBS from the MIM … <subject typeCode="SBJ"> <patientRole classCode="PAT"> <!-- NHS number --> <id root="2.16.840.1.113883.2.1.4.1" extension="9999999484"/> <patientPerson classCode="PSN" determinerCode="INSTANCE"> <!-- (Current) Usual name --> <name use="L"> <prefix>Ms</prefix> <given>Three</given> <given>Zoe</given> <family>Editestpatient</family> <validTime> <low value="20030930"/> </validTime> <id root="2.16.840.1.113883.2.1.3.2.4.18.1" extension="P000000021"/> </name> <!-- Administrative gender of "Female" --> <administrativeGenderCode code="2"/> <!-- Full date of birth --> <birthTime value="19780719"/> <!-- Full date and time of death --> <deceasedTime value="200312020635"/> </patientPerson>

17. eBS Activity Diagram from W5

18. Lessons to learn • How to do implementations • How to test conformance