Healthcare Standards for Connecting Clinical Applications

663 views

Published on

An introduction to the standards used for connecting clinical applications

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
663
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Healthcare Standards for Connecting Clinical Applications

  1. 1. © 2012 IBM CorporationIBM Integration BusIntroduction to Healthcare StandardsAnt Phillipsantphill@uk.ibm.com
  2. 2. © 2012 IBM CorporationHL7 Introduction Messaging standard for the exchange of healthcare information– Health Level-7 refers to the application (top) layer in the ISO OSI Reference Model– Version 2.2 of the standard was ANSI accredited in 1996– Standards compliance is variable between the main vendors– HL7 is the key connectivity standard in the provider space HL7 covers a range of standards areas:– Conceptual standards – HL7 Reference Implementation Model (RIM)– Document standards – HL7 Clinical Document Architecture (CDA)– Messaging standards – HL7 v2.x (including XML variant) and v3.x Deployment specific message segments are supported (Z-segments) Supports variety of character encodings (ASCII, ISO-8859 and Unicode) Latest version (v2.6) was approved by ANSI in October 2007– Compliance as always lags behind the standardisation process– HL7 sample in Message Broker is up to date for v2.5 of the standard2
  3. 3. © 2012 IBM CorporationScope There are quite a few things that the HL7 v.2x standard does not cover! The standard is not a complete systems integration solution– Lack of process conformity within healthcare delivery environments– This effectively leads to a unique use of the standard at each site– Standard is really a common framework for integrating systems Standard is largely silent about authentication and confidentiality of data!– No standard way to encrypt the data flowing down TCP/IP connections– Likewise there are no audit trails, security controls and/or access procedures– No controlled disclosure or notification of disclosed information No inter-system database locking or transaction coordination Standard builds on other coding systems such as LOINC and SNOMED3
  4. 4. © 2012 IBM CorporationHL7 v2.x Chapters4
  5. 5. © 2012 IBM CorporationMSH      Message Header SegmentEVN      Event type segmentPID      Patient Identification segment  [PD1]  Patient Additional Demographic segment[{NK1}]  Next of Kin / Associated Parties[PV1]    Patient Visit segmentMSH|^~&|HNAM|CAPIOUK|JDE|JDE|20030821153359||ADT^A04|Q590076T590056X77||2.3EVN|A04|20030822172800|||1PID|1|151^^^CD:678893^CD:1079^""|151^^^CD:678893^CD:10^""||ZZTEST^selfpayGT^^^^^CD:766||20030820000000|CD:363||""|1^test^chester^""^ch11ab^CD:312726^CD:756^^cheshire||01234567890^CD:170||""|CD:309239|""|166^^^CD:678894^CD:1077^""||||""|||0|""|""|""||""PD1|""|""||589824^Waller^Dave^Jones|""||""|""HL7 v2.x Message Example (ADT)Code DescriptionADT^A01 Admit a patientADT^A02 Transfer a patientADT^A03 Discharge a patientADT^A04 Register a patientADT^A05 Pre-admit a patient5
  6. 6. © 2012 IBM CorporationHL7 v2.x Commonly-Used Segments6
  7. 7. © 2012 IBM CorporationObservation Results Example (ORU) Abstract syntax for an ORU HL7 v2.x message:MSH Message headerPID Patient Identification DetailsPV1 Patient VisitOBR Results header{OBX} Results detail (repeats) Example message conforming to this definition:MSH|^~&||^123457^Labs|||200808141530||ORU^R01|123456789|P|2.4PID|||123456^^^SMH^PI||MOUSE^MICKEY||19620114|M|||14 DisneyRd^Disneyland^^^MM1 9DLPV1|||5N|||||G123456^DR SMITHOBR|||54321|666777^CULTURE^LN|||20080802||||||||SW^^^FOOT^RT|C987654OBX||CE|0^ORG|01|STAU||||||FOBX||CE|500152^AMP|01||||R|||FOBX||CE|500155^SXT|01||||S|||FOBX||CE|500162^CIP|01||||S|||FReport from Lab123457, 15:30 14 Aug 2008,‐ ‐Ref 123456789Patient: MICKEY MOUSE, DoB: 14 Jan 1962, M‐ ‐Address: 14 Disney Rd, Disneyland, MM1 9DLSpecimen: Swab, FOOT, Right, Requested By: C987654,Location: 5NPatients GP: Dr Smith (G123456)Organism: STAUSusceptibility: AMP RSXT SCIP S7
  8. 8. © 2012 IBM CorporationClinical Terminology
  9. 9. © 2012 IBM CorporationClinical Terminology - Introduction9 Most scientific fields of endeavour have a well defined terminology– Healthcare covers a huge breadth of scientific levels – radiologists work with subatomicparticles, haematologists study blood cells, physicians are concerned with abnormalbody functions, and public health doctors study the spread of disease in populations
  10. 10. © 2012 IBM CorporationCoding vs Classification Classification collects things into groups or classes– It is the basis for the majority of statistical analysis, accountancy and much more– By its very nature, the process of classifying things loses accuracy Coding is the allocation of identifiers to things – an alternative name– No more interest to end users than a bar code on a cereal packet! Here is a skiing accident described by the trauma surgeon as a closedspiral fracture of the shaft of the right tibia with fractured fibula:In ICD-10 this injury is described by the following classification:Chapter XIX: Injury, poisoning, and certain other consequences of external cause (S00-T98)S82: Fracture of lower leg, including ankleS82.2: Fracture of shaft of tibia (with or without mention of fracture of fibula)S82.2.1: Closed fracture of shaft of tibia Note that ICD-10 does not specify whether the leg or left or right, whetherthe fracture is simple, spiral or compound or if the fibula is also fractured10
  11. 11. © 2012 IBM CorporationICD-10 International Statistical Classification of Diseases and Health Problems Enables the recording, analysis and interpretation for patient mortality– ICD-10 contains more than 140K codes (ICD-9 contains 17K codes) In practice, it has become the standard classification for all generalepidemiological and many health management purposes ICD-10 is not suitable for coding distinct clinical entities Format XXX.XXX X [category.etiology/site/severity extension]:K50.013 Crohn’s disease of small intestine with fistulaK71.51 Toxic liver disease with chronic active hepatitis with ascitesH02.835 Dermatochalasis of left lower eyelidT81.530 Perforation due to foreign body accidently left in body following surgical operation ICD-10 widely used for medical reimbursements in the US (HIPPA)11Epidemiology is the study of patterns of health and illness and associated factors at the populationlevel
  12. 12. © 2012 IBM CorporationRead Codes Read Codes are widely used by GPs in the UK NHS and New Zealand– Used by clinicians to record patient findings and procedures– Read codes come in two versions – v2 and v3 (Clinical Terms v3)– Codes are organised into chapters identified by the first character Codes are five characters long with missing letters replaced by a dot– Letters are 0-9, A-Z and a-z (omitting O and I to reduce coding errors)– Results in a very large potential code space > 750M codes (605)H Respiratory disease (H33zz Asthma NOS)J Digestive system diseases (J20.. Acute appendicitis)G Circulatory system diseases (G3z.. Ischaemic heart disease NOS) Framework is broken down into subchapters to give more precise detailH.... Respiratory system diseaseH3... Chronic Obstructive Pulmonary DiseaseH33.. AsthmaH331. Intrinsic asthmaH3311 Intrinsic asthma with status asthmaticus Problems stem from the single hierachy provided by the codes– Consider the clinically accurate code 8H2P (emergency admission asthma)12
  13. 13. © 2012 IBM CorporationSNOMED CT - Overview SNOMED has a long history dating back more than 40 years Comprehensive (multi-lingual) clinical terminology for recording the healthand care of individual patients– Codes can be indexed and retrieved for use at the clinical point-of-care– SNOMED codes can also be re-used for management and research Latest evolution of the standard (SNOMED CT) was formed in 1999– Merger of SNOMED with NHS Clinical Terms v3– Every Read Code and existing SNOMED code is represented In 2007 the International Health Terminology Standards DevelopmentOrganisation (IHTSDO) acquired the SNOMED IPR SNOMED CT is sufficiently complex to only be useful in an IT context– By January 2009, it contained over 350K active concepts, ~1M descriptions and 1.38Mrelationships – the sheer size of the standard is an on-going maintenance issue13
  14. 14. © 2012 IBM CorporationSNOMED CT – Building Blocks14 Building blocks of SNOMED are concepts, descriptions and relationships– Each concept represents a single specific clinical meaning– Concepts have a fully specified name (FSN) which may not be the preferred term Every concept, relationship and description has an identifier (SCTID)– SCTID contains the unique identifier, partition identifier and a trailing check digit
  15. 15. © 2012 IBM CorporationSNOMED CT – Expressions and Grammar Expressions are usually presented using a composition grammar87628006 | bacterial infectious disease | Concepts can be combined in post-coordinated expressions to create amore accurate clinical meaning87628006 | bacterial infectious disease |:246075003 | causative agent |= 9861002 | streptococcus pneumoniae | Nested expressions supported through the use of parenthesis:87628006 | bacterial infectious disease |:246075003 | causative agent |= 9861002 | streptococcus pneumoniae |,363698007 | finding site |= (45653009 | structure of upper lobe of lung |:272741003 | laterality |= 7771999 | left |) Concepts can be combined using the plus sign:87628006 | bacterial infectious disease | + 50043002 | disorder of respiratory system |15
  16. 16. © 2012 IBM CorporationSNOMED CT and HL7 SNOMED CT and HL7 do not always sit easily together– Not surprising when message structure and terminology have evolved separately For example consider the transport of Taurine deficiency– No pre-coordinated term exists in SNOMED CT for this disorder Transmit the data as a post coordinated term in OBX.5:70241007 | Nutritional deficiency |: 47429007 | Associated with |= 10944007 | Taurine | Alternatively use observation sub IDs in HL7 messages:OBX|1|CE|29308-4|1|70241007^Nutritional deficiency^SCT|...OBX|2|CE|29308-4|1.1|47429007 ^Associated with^SCT|...OBX|3|CE|29308-4|1.1.1| 10944007^Taurine^SCT|... Impossible to draw a clean dividing line between the two!– Guidelines exist to provide some clarity – for example use HL7 message structure totransmit dates, times, people and places - use SNOMED CT for semantic relationshipssuch as laterality and other post coordinated information16
  17. 17. © 2012 IBM CorporationLOINC Logical Observation Identifiers Names and Codes (LOINC)– Coding system for medical and laboratory observations– Relatively new standard (inception dates back to 1994)– Identified by HL7 as the preferred code set for laboratory test names Each test or observation has a unique six digit code containing:– Component - what is measured, evaluated, or observed (for example, urea)– Property - characteristics of what is measured, such as length, mass and volume– Time - interval of time over which the observation or measurement was made– System - specimen type within which the observation was made (for example, blood)– Scale - the scale of measure for the measurement or observation– Method - procedure used to make the measurement or observation Observation code and value transmitted in OBX-3 and OBX-5 (ORU)17

×