xml, hl7 messaging and the clinical document architecture
Post on 13-Jan-2016
43 Views
Preview:
DESCRIPTION
TRANSCRIPT
XML, HL7 Messagingand the Clinical Document Architecture
Contents
• Introduction to XML
• Introduction to Heath Level 7 (HL7)
• HL7 messaging, current and future
• HL7 Clinical Document Architecture (CDA)
Generalized Markup Languages
• Markup identifies structural elements of a document rather than specific formatting features
• Markup is expressed as standard text sequences (markup "tags")
• Formatting instructions are applied separately to the specified document elements
• Markup tags can be human-readable
Markup Expresses Metadata
• Documents naturally have content and metadata• Metadata may help specify:
> Meaning of data (e.g., standard coding)
> Arrangement of data (display)
> Correct use of the data (business rules)
> Context and relationships between data elements
• Example of display markup:
Documents contain <emph>metadata</emph> and "primary" data
Embedded "tag" Tag content
Heritage of Generalized Markup Languages
SGML
Internal workat IBM
TeX, nroff, troff
Many special-purpose markup
languages
HTML
XML
Many special-purpose markup
languages
1984
~1990
1998
XHTML
Frameworks
Implementations
Tag formatsDTD formatProcessing rules
Extensable Markup Language (XML)
• HTML originally specified structural components of documents> HTML has evolved to become a presentation syntax
• SGML is complex and requires complex processing software• XML is a simplified version of SGML designed for electronic
document archiving and exchange> Allows creation of special-purpose markup languages> Can represent a variety of data structures and semi-structured data as well
as metadata> Arbitrary tag nesting, recursion and granularity> Human-readable and machine readable> Expected to be useful for creation of special purpose data-interchange
standards as well as document structuring
XML Document Detail
<procedure cpt="1234"><pat_phys pnum="abcd">
<firstName>Elmer</firstName><lastName>Fudd</lastName><degree>M.D.</degree>
</pat_phys><proc_name>Upper endoscopy of gizzard</proc_name><proc_date>09/09/1999</proc_date><location name="ER"/>
</procedure>
Element name AttributeOpening tag
Closing tagSingleton tag
Content
HL7Health Level 7
• Founded by healthcare providers in 1987
• Version 1.0 late in 1987
• Version 2.0 late in 1988
• Versions 2.1, 2.2 and 2.3 published in 1990, 1994 and 1997; ANSI standards
• Pragmatic approach
• Work on Version 3 (XML-based) is ongoing
Organized to create standards for the exchange, management and integration of data that supports clinical patient care and the management, delivery and evaluation of healthcare services
"Level Seven"
A protocol for the exchange of health care information
ISO-OSI Layered Protocol Model
1 Physical 1 Physical 2 Data Link 2 Data Link 3 Network 3 Network 4 Transport 4 Transport
Communication
5 Session 5 Session 6 Presentation 6 Presentation 7 Application 7 Application
Function
HL7 Transactional Model
(external) admitevent
trigger event
network
sendHL7 A01 msg
receive HL7 ACK msg
ADT system
Lab system
Receive A01,send ACK
EXTER N A L H O S PITALS
U PM C M ESSAG E R O U TER
SUNQ UESTLAB
EPICPHYSICIAN
PRACT ICE PLAN
PHARM AKO NPHARM ACY
ST ARBRADDO CK,
MCKEESPO RT ,ST . M ARG ARET
HO RIZO N
CO PAT HPAT HO LO G Y
CLIN IPAC MEDIPACHDX INSURANCE
VERIF ICAT IO N
IDXRAD RADIO LO G Y
Q UESTREFERENCE
LABO RAT O RY
AMBULAT O RY
EMT EKCRIT ICAL
CARERING MED
PAG ING
APACHECRIT ICAL
CARE
DERO YALO R
CBO RDDIET ARY
DO LBEYT RANSCRIPT IO N
INT ELLUSMEDICAL
RECO RDS
SUMM ITCARDIO LO G YABACUS
MARQ UET T EEKG
PAT HO LO G Y
CLEM
MCDO DG E
DECEDI
SHADYSIDET DS
VAHO SPIT AL
MAG EESMS
CHILDRENSHO SPIT AL
SMS
NO RT HERNHEALT H
SU
NQ
UE
ST
RE
SU
LT
S/IN
Q
IDX
RA
D R
ES
UL
TS
SU
NQ
UE
ST
AD
T/O
E
IDX
RA
D A
DT
/OE
CB
OR
D O
RD
ER
S
AD
T
INS
UR
AN
CE
EL
IGIB
ILIT
Y
RE
SP
ON
SE
INS
. EL
IGIB
ILIT
Y
RE
SU
LT
S
CP
AC
AD
T/O
E
MP
AC
AD
T
CP
AC
RE
S / IN
Q
CH
P S
MS
AD
T
QU
ES
T R
ES
UL
TS
OR
DE
RS
TO
QU
ES
T
EP
IC O
RD
ER
S
MP
AC
INQ
EP
IC IN
Q
EP
IC R
SP
MP
AC
RS
P
SH
AD
YS
IDE
TD
S A
DT
MP
AC
AD
T
IMA
GE
LO
CA
TIO
N
DE
MO
G
PA
TH
OL
OG
Y R
EP
OR
TS
HD
X R
ES
PO
NS
E
HD
X IN
Q
MP
AC
AD
T
SU
NQ
UE
ST
RE
SU
LT
S
MA
GE
E A
DT
OR
DE
RS
MP
AC
AD
T
OR
DE
RS
RE
PO
RT
S
CP
AC
AD
T/O
E
CH
P S
MS
AD
T
MP
AC
AD
T
PH
YS
. RE
PO
RT
S
QU
ES
T R
ES
UL
TS
SU
NQ
UE
ST
OR
DE
RS
CL
INIC
AL
DA
TA
MP
AC
AD
T
CH
P S
MS
AD
T
PU
LM
ON
AR
Y R
ES
UL
TS
MP
AC
AD
T
CP
AC
OR
DE
RS
AD
T / S
MS
LA
B/ M
ED
ITE
CH
TR
AN
SC
RIP
TIO
N/ M
ED
WR
ITE
R
IDX
RA
D R
EP
OR
TS
AB
AC
US
AD
T
MP
AC
AD
T
O.R
. SU
MM
AR
Y
RE
PO
RT
S
AD
T
MP
AC
AD
T
AB
AC
US
AD
T
MP
AC
AD
T
RE
SU
LT
S
IDX
RA
D R
ES
UL
TS
AD
T
CL
INIC
AL
NO
TE
S
MP
AC
AD
T
EK
G R
EP
OR
TSS
UN
QU
ES
T R
ES
UL
TS
EM
TE
K C
LIN
ICA
L
SU
NQ
UE
ST
RE
SU
LT
S
IDX
RA
D R
ES
UL
TS
CO
PA
TH
RE
PO
RT
S
AD
T
PU
RC
HA
SE
OR
DE
RS
OR
DE
R S
TA
TU
S
PU
RC
HA
SE
OR
DE
RS
OR
DE
R S
TA
TU
S
AD
T
MP
AC
AD
T
RE
SU
LT
S
O.R
. SU
MM
AR
Y
OR
DE
RS
AD
T/O
E
SU
NQ
UE
ST
RE
SU
LT
ST
AT
US
ST
AR
RE
SU
LT
ST
AT
US
ST
AR
AD
T/ O
E
ST
AR
OR
DE
RS
PRO DUCT IO N FILES FT P'D IN DEVELO PM ENT
BE
D C
EN
SU
S
IDX
RA
D R
ES
UL
T S
TA
TU
S
INQ
UIE
RIE
S
ST
AR
OR
DE
RS
ST
AR
RE
SU
LT
ST
AT
US
ST
AR
INQ
UIE
RIE
S
DA
TA
RE
PO
SIT
OR
Y
CERNERCLIN ICAL INFO RMAT IO N SYST EM
OM
S R
ES
UL
TS
MARS
C O R PO R ATE S YSTE M S
LAN VISIO NIMAG ING
MP
AC
AD
T
IMA
GE
LO
CA
TIO
N
CO
PA
TH
DE
MO
G
MP
AC
AD
T
CIS
OR
DE
RS
MP
AC
AD
T
PH
AR
MA
CY
OR
DE
RS
MP
AC
AD
T
EP
IC M
PI#
IDX
RA
D S
TA
TU
S/ R
ES
UL
TS
SU
NQ
UE
ST
ST
AT
US
/ RE
SU
LT
S
CO
PA
TH
ST
AT
US
/ RE
SU
LT
S
QU
ES
T S
TA
TU
S/ R
ES
UL
TS
PH
AR
MA
KO
N R
ES
UL
TS
SH
AD
YS
IDE
TD
S P
HA
RM
AC
Y O
RD
ER
S
ME
DIT
EK
LA
B S
TA
TU
S/R
ES
UL
TS
SH
AD
YS
IDE
SM
S R
AD
IOL
OG
Y
SH
AD
YS
IDE
TD
S A
DT
CL
INIP
AC
OR
DE
RS
DO
LB
EY
TR
AN
SC
RIP
TIO
N
MA
RQ
UE
TT
E E
KG
WP
IC C
LIN
ICA
L N
OT
ES
SH
AD
YS
IDE
TD
S/P
AT
IEN
T C
AR
E
SH
AD
YS
IDE
MR
C T
RA
NS
CR
IPT
ION
SH
AD
YS
IDE
SM
S R
AD
IOL
OG
Y
SU
MM
IT R
ES
UL
TS
AM
BU
LA
TO
RY
RE
SU
LT
S
DE
RO
YA
L O
R S
UM
MA
RY
/NO
TE
S
MP
I #
ST
AT
US
CIS
RE
SU
LT
S
SH
AD
YS
IDE
MU
SE
CA
RD
IOL
OG
Y
SH
AD
YS
IDE
OR
BIT
/OR
SY
ST
EM
MU
SE
CA
RD
IOL
OG
Y
OR
BIT
OR
SY
ST
EM
RA
DIO
LO
GY
/ SM
S
AS O F 10/9/98LDG
CO
PA
TH
RE
PO
RT
S
MP
AC
AD
T
Current Message-Router-Based Interfaces
HL7 Abstract Messages
• Identifies data fields
• Describes error conditions
• DOES NOT describe the byte string contained in the message.
Admit Message
MSH|^~\&|ADT1|MCM|LABADT|MCM|198808181126|SECURITY|ADT^A01|MSG00001|P|2.3|<cr>
EVN|A01|198808181123||<cr>
PID|||PATID1234^5^M11||JONES^WILLIAM^A^III||19610615|M||C|1200 N ELM
STREET^^GREENSBORO^NC^27401-1020|GL|(919)379-1212|(919)271-3434||S||
PATID12345001^2^M10|123456789|987654^NC|<cr>
NK1|JONES^BARBARA^K|WIFE||||||NK^NEXT OF KIN<cr>
PV1|1|I|2000^2012^01||||004777^LEBAUER^SIDNEY^J.|||SUR||||ADM|A0|<cr>
segments, fields, components & subcomponents
Variability in HL7 Interfaces
• Site 1:OBX|1|CE|ABO^ABO GROUP||O^Type O|
• Site 2:OBX|1|CE|BLDTYP^ABO GROUP||TYPEO^Type O|
• Site 3:OBX|1|CE|ABOTYPE^ABO GROUP||OPOS^Type O|
"when you've seen one HL7 interface you've seen one HL7 interface"
HL7 v2.x is not Plug and Play
• Cost of installing an HL7 interface: 2-4 weeks of analyst time
• Issues> Different implicit information models
> Misunderstanding of specifications
> No vocabulary to describe conformance except by detailed specs
> Significant local demands on vendors
Goals for Version 3
• Substantially reduce interface development time> Clarify spec for messages
> Create a specified information model
• Method for conformance specification• Support modern communications infrastructures• Reference Information Model (RIM)
> Coherent shared information model
> Includes all content of HL7 messages
> Provides consistency to messages across usage settings
Reference Information Model (RIM)
Observation_intent_or_orderpatient_hazard_codereason_for_study_cdrelevant_clinical_information_txtreporting_priority_cdspecimen_action_cd
Clinical_observation
abnormal_result_ind : IDlast_observed_normal_values_dttm : DTMnature_of_abnormal_test ing_cd : CEclinically_relevant_begin_dttm : DTMclinically_relevant_end_dttm : DTMobservation_value_txt : NMprobability_number : NMreferences_range_text : STvalue_units_code : CE
Assessment
Healthcare_service_providerspecialty_cd : CNE
Stakeholder_identifierid : STidentif ier_type_cd : ID
Organizationorganization_name_type_cd : CNEorganization_nm : STstandard_industry_class_cd 0..*
0..1 is_a_subdivision_of
0..*
has_as_a_subdivision
0..1
Person
birth_dttm : DTMgender_cd : CNEmarital_status_cd : CNEprimary_name_representation_cd : CNEprimary_name_type_cd : CNEprimary_prsnm : PNrace_cd : CNE
Individual_healthcare_practitionerdesc : TXpractitioner_type_cd : CNE
1
0..1
takes_on_role_of1
is_a_role_of0..1
Stakeholderaddr : XADphon : XTN
0..*
1
is_assigned_to0..*
is_assigned1
Healthcare_provider_organization
0..1
1
is_a_role_of0..1
takes_on_role_of
1
Collected_specimen_samplebody_site_cd : CEcollection_end_dttm : DTMcollection_start_dttm : DTMcollection_volume_amt : CQhandling_cd : IDid : IIDmethod_of_collection_desc : TXspecimen_addit ive_txt : STspecimen_danger_cd : IDspecimen_source_cd : CE
0..*1
is_collected_by
0..*
collects
1
Patient
ambulatory_status_cdbirth_order_numberliving_arrangement_cdliving_dependency_cdmultiple_birth_indnewborn_baby_indorgan_donor_indpreferred_pharmacy_id
0..1
1
is_a_role_of
0..1takes_on_role_of
1
0..*
0..1
has_a_primary_provider
0..*is_the_primary_provider_for
0..1
0..*
0..1
is_sourced_from0..*
is_source_for0..1
Active_participation
participation_type_cd : ID
0..1
0..*
participates_in0..1
has_as_participant0..*
Master_patient_service_location
addr : XADemail_address : XTNid : IDnm : STphon : XTN
1..*
0..*provides_patient_services_at
1..*
provides_services_on_behalf_of0..*
0..*
0..1
is_included_in
0..*
includes 0..1
0..1
0..*
is_primary_facility_for0..1
has_as_primary_facility
0..*
Target_participationparticipation_type_cd : CE
0..1
0..*
is_target_of
0..1
has_as_target0..*
0..1
0..*
is_target_of
0..1
has_as_target
0..*
0..1
0..*
is_target_for0..1
has_as_target
0..*
Service_intent_or_orderfiller_order_id : IIDfiller_txt : TXorder_idorder_placed_dttm : DTMorder_quantitytiming_qt : TQplacer_order_id : IIDplacer_txt : TXreport_results_to_phone : XTNintent_or_order_cd : ID
0..* 0..1
participates_in
0..*
has_as_participant
0..1
1..*
0..1
is_target_of
1..*
has_as_target
0..1
1
0..*
is_entry_location_for
1
is_entered_at
0..*
Master_service
method_cd : CEmethod_desc : TXservice_desc : TXtarget_anatomic_site_cd : CEuniversal_service_id : CE
0..*
1
is_an_instance_of
0..*
is_instantiated_as
1
Service_event
service_desc : STservice_event_descspecimen_received_dttm : DTMname : CE
0..*
0..1
participates_in0..*
has_as_active_participant
0..1
0..*
0..1
is_performed_at
0..*
is_location_for
0..1
0..*
0..1
is_target_of
0..*
has_as_target
0..1
0..1
0..*
is_fulfilled_by0..1
fulfills0..*
1
0..*
is_delivered_during1
delivers
0..*
Advantages of XML for Message Formatting
• The syntax handles recursion and nesting> Variably nested structures to arbitrary depth
> More flexible than segments, fields, components & subcomponents
> Objects (including contained objects) can be represented
> Relational structures can be represented
• Simple syntax, easy to debug (human readable)• Software tools (parsers, etc.) are generally available• Language- and platform-independent• Compatibility with other industries
HL7 2.3 Message Format
HL7 v3 Message Format
HL7 Clinical Document Architecture (CDA)
• Level 1: XML-coded header> Contents may be flat or tagged text
• Level 2: Coded document sections> Generic architectural DTD with multiple derived DTDs
• Level 3: Coded content> Text tagging based on RIM
> Generic architectural DTD with multiple derived DTDs
• Initial focus is documents used directly in clinical care
A multilevel representation of medical documents that can be passed as messages and which make up the medical record.
Definition of a Document
• Persistence> Defined by local and regulatory requirements
• Stewardship> Maintained by an organization or person
• Authentication> A collection of information that is to be legally authenticated
• Wholeness> Legal authentication applies to the document as a whole and not to
parts of the document out of context. The document also establishes a context for use of the contained information.
• Human readability
Advantages of XML for Document Management
• Adaptable to unstructured and semi-structured data• Tagging does not destroy the document or its text
flow> The text of the document can be recovered by ignoring
the tags
• Tagged document are human readable• If tagging is well-documented and/or tags are
logically named, XML documents will remain readable over the long term
CDA Level 1 Markup
Header & "wrapper"
Clinical Documentas text
CDA Level 2 Markup
Header & "wrapper"
Clinical Documentwith structural markup(main sections)
CDA Level 3 Markup
Header & "wrapper"
Clinical Documentwith detailed markupincluding local extensions
Why Not Standardize DTDs?
• DTDs support local processes• Single documents may use multiple DTDs• Achieving consensus on details is lengthy• DTDs evolve with local needs• Strategy:
> Create generic architectural DTDs
> Allow local extension
> Local extensions can be ignored when necessary
Key Header Elements
• ID, set ID, version, addendum vs. replacement• Fulfills order• Document type (LOINC)• Origination time• Confidentiality level• Patient encounter• Service actors (care providers; individuals and organizations)
> Authenticator, legal authenticator, originator, intended recipient, originating organization, provider, transcriptionist
• Service target (living or inanimate)> If patient, one and only one
Structural Markup
• HTML-like (captions/headings, paragraphs, lists, tables)
• Recursive relationships• Content tag: generic identifier and target for text
sequences• Coded entry: standard vocabulary entry, can be
targeted to a text span defined by content tags• Generic design yields limited ability to specify
structure of particular document types (schemas?)• Complex style sheets for particular documents?
Summary
• XML is a flexible framework for creating tag vocabularies that add metadata to textual documents
• HL7 is a core standard in healthcare systems communications that has strengths and also specific weaknesses
• A new version of the HL7 messaging standard attempts to address those weaknesses through definition of a reference information model and XML message formatting
• HL7 has also defined a generic XML standard for clinical documents that is intended to improve the structure, accessibility and longevity of the electronic medical record.
top related