1 / 14

An Introduction to HL7 Version 2

HL7 and its key role in NPfIT and Existing Systems Integration. An Introduction to HL7 Version 2. Charlie Bishop 9 February 2005. Agenda. History of v2 Scope of v2 Structure of the v2 Standard v2 Message Structure v2 Issues The Future. History of v2. 1987. 1988. Version 2.0. 1990.

gage-pace
Télécharger la présentation

An Introduction to HL7 Version 2

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 and its key role in NPfIT and Existing Systems Integration An Introduction toHL7 Version 2 Charlie Bishop 9 February 2005

  2. Agenda • History of v2 • Scope of v2 • Structure of the v2 Standard • v2 Message Structure • v2 Issues • The Future

  3. History of v2 1987 1988 Version 2.0 1990 Version 2.1 1994 Version 2.2 1996 Version 3 – development starts 1997 Version 2.3 1999 Version 2.3.1 2000 Version 2.4 HL7 UK established HL72UK vA.2 2003 Version 2.5 2005 Version 2.6 – under development / ballot Version 1.0

  4. An International Standard • USA (90% of hospitals) • UK • Canada • Australia • Netherlands • Germany • Japan • Others

  5. Scope • Patient Administration • Registration / MPI • ADT / Inpatients • Scheduling / Outpatients • Waiting List (UK) • Medical Records • Clinical • Orders • Results • Provision of Care • Financial

  6. Structure of the Standard Chapter • Introduction • Control • Patient Administration • Order Entry • Query • Finance • Observation Reporting • Master Files • Medical Records • Scheduling • Patient Referral • Patient Care • Clinical Laboratory Automation • Network Protocols

  7. Message Structure • Triggers • Messages • Segments • Fields • Data Types

  8. Example v2 Message MSH|^~\&|LAB|767543|ADT|767543|20050201130405||ADT^A04|XX3657|P|2.4<CR> EVN||20050201101314||||20050201095000<CR> PID|||1234567891||EXAMPLE^DAVID^S||19590520|M|||23 MAINSTREET^^ANYTOWN^ > ^AN10 8SW||01234 567890<CR> PD1||||DR A WELBY<CR> PV1||0||NEW|||DR K JONES<CR>

  9. XML Representation • Provides compatibility with industry standard tools • Alternative syntax • Data semantic is identical • Simple transform between 2 syntaxes • Segments, Fields and Data Types represented as elements

  10. Example v2 XML Message <!DOCTYPE ADT_A04 SYSTEM "hl7_v231.dtd"> <ADT_A04> <MSH> <MSH.1>|</MSH.1> <MSH.2>^~\&amp;</MSH.2> <MSH.3> <CM.1>LAB</CM.1> </MSH.3> <MSH.4>767543</MSH.4> <MSH.5>ADT</MSH.5> <MSH.6>767543</MSH.6> <MSH.7>20050201130405</MSH.7> <MSH.9> <CM_MSG_TYPE.1>ADT</CM_MSG_TYPE.1> <CM_MSG_TYPE.2>A04</CM_MSG_TYPE.2> </MSH.9> . . .

  11. Delimited vs. XML <!DOCTYPE ADT_A03 SYSTEM "hl7_v231.dtd"> <ADT_A03> <MSH> <MSH.1>|</MSH.1> <MSH.2>^~\&amp;</MSH.2> <MSH.3> <CM.1>LAB</CM.1> </MSH.3> <MSH.4>767543</MSH.4> <MSH.5>ADT</MSH.5> <MSH.6>767543</MSH.6> <MSH.7>20050201130405</MSH.7> <MSH.9> <CM_MSG_TYPE.1>ADT</CM_MSG_TYPE.1> <CM_MSG_TYPE.2>A04</CM_MSG_TYPE.2> </MSH.9> <MSH.10>XX3657</MSH.10> <MSH.11> <ID.1>P</ID.1> </MSH.11> <MSH.12> <ID.1>2.4</ID.1> </MSH.12> </MSH> <EVN> <EVN.2>20050201101314</EVN.2> <EVN.6>20050201095000</EVN.6> </EVN> <PID> <EVN.6>20050201095000</EVN.6> </EVN> <PID> <PID.3.LST> <PID.3> <CX.1>1234567891</CX.1> <CX.4>NHS<CX.4> <CX.5>NH<CX.5> </PID.3> <PID.3> <CX.1>AB12345</CX.1> </PID.3> </PID.3.LST> <PID.4.LST> <PID.5.LST> <PID.5> <XPN.1>EXAMPLE</XPN.1> <XPN.2>DAVID</XPN.2> <XPN.3>S</XPN.3> </PID.5> </PID.5.LST> <PID.7>19590520</PID.7> <PID.8>M</PID.8> <PID.11.LST> <PID.11> <XAD.1>23 MAIN STREET</XAD.1> <XAD.3>ANYTOWN</XAD.3> <XAD.5>AN10 8SW</XAD.5> </PID.11> </PID.11.LST> <PID.13.LST> <PID.13> <XTN.1>01234 567890</XTN.1> </PID.13> </PID.13.LST> <PD1> <PD1.4.LST> <PD1.4> <XCN.1>DR A WELBY</XCN.1> </PD1.4> </PD1.4.LST> </PD1> <PV1> <PV1.2>0</PV1.2> <PV1.4>NEW</PV1.4> <PV1.7.LST> <PV1.7> <XCN.1>DR K JONES</XCN.1> </PV1.7> </PV1.7.LST> </PV1> </ADT_A03> MSH|^~\&|LAB|767543|ADT|767543|20050201130405||ADT^A04|XX3657|P|2.4<CR> EVN||20050201101314||||20050201095000<CR> PID|||1234567891||EXAMPLE^DAVID^S||19590520|M|||23 MAINSTREET^^ANYTOWN^^AN10 8SW||01234 567890<CR> PD1||||DR A WELBY<CR> PV1||0||NEW|||DR K JONES<CR>

  12. Issues • Inconsistent use • Multiple versions • Z-Segments • Interpretation • Localisation Seen one HL7 v2 interface – seen one HL7 v2 interface • Support for clinical data • Communication approach • Broadcast vs. targeted

  13. The Future • HL7 v2 will continue to be developed • HL7 v2 will continue to be widely used in the NHS • Delimited vs. XML • Mapping to v3 • HL7 UK v2 sub-group

  14. Thank you!

More Related