Message Profiles are Contracts for Implementation

Transcription

1 Message Profiles are Contracts for Implementation Static Profiles Define structure and content of profile Segment cardinality (m n) No optional fields or sub-fields (R,RE,C,CE,X) All codes defined for fields and sub-fields Dynamic Profiles Define interaction between source and receiver Acknowledgement modes (Accept, Application) Acknowledgement condition (AL, NE, SU, ER)

2 Example of Static Profile Apply profile HL7 Message Structure AWG Message Profile (91 3,' (91 3,' 39 Segments/Segment Groups: - Cardinality (min, max) %; $/ 39 2%; $/ Fields/Components: - Field Usage (Optionality) (R, RE, C, CE, X) - Cardinality (max repeats) - Value Sets/Coding system - Descriptions

3 Progress on Profiles 06+ 3URILOH6SHFLILFDWLRQ (91 3,' 0HVVDJHÃ+HDGH (YHQWÃ7\SH 3DWLHQWÃ'HPRJU 6(4Ã/(1Ã'7Ã52Ã53ÆÃ7%/ÆÃ,7(0Æà ÃÃÃÃÃÃÃÃÃÃÃÃ67ÃÃ5ÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃà ÃÃÃÃÃÃÃÃÃÃÃÃ67ÃÃ5ÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃà ÃÃÃÃÃÃÃÃÃÃ67ÃÃ5(ÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃà 5HY$ 5HY% 5HY& $:* +/ 1 ' - ) 0 $ $ ' - ) 0 $ 3URILOH&RQWHQW +/9HUVLRQ $'7A$ ^LVRÃRUJë` $&.A$ ^«ÃQXOOÃY` 3DWLHQWÃ$GPLQLVWUDWLRQÃ$'7 2UGHUV2EVHUYDWLRQV 5HY$ 5HY% 1 ' - ) 0 $ $ ' - ) 0 $

4 Progress on Profiles 3URILOH7RROV :HE 3URWR :HE 3URWR 5RER+HOS 2ULRQ 3URWR 3URWR $:* +/ $+& 1 ' - ) 0 $ $ ' - ) 0 $ 3URILOH3URFHVV (DFKSURILOHKDVDXQLTXHLGHQWLILHU 2UJDQL]DWLRQVUHJLVWHUSURILOHV$:*$+&+/ 7RROVVXSSRUWHQWU\VHDUFKLQJDQGFRPSDULVRQ 2UJDQL]DWLRQVUHJLVWHUXVHRISURILOHVYHQGRUSURYLGHU«0DUNHWGHWHUPLQHVXWLOLW\RISURILOHV

5 Message Profile Example ADT^A01, ACK^A01 ÄMEDICAL PRODUCTS GROUP 3000 Minuteman Road Andover, MA Message Profile Specification Patient Administration (A/D/T) ADT^AO1 { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) hpmpg(3) profiles(3) awg(1) hl7(1) v2-3(5) static-profile(1) adt(3) a01(1) null(0) null(0) v1(1) } ACK^A01 { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) hpmpg(3) profiles(3) awg(1) hl7(1) v2-3(5) static-profile(1) ack(1) a01(1) null(0) null(0) v1(1) } HP Enterprise Communication Framework April 02, 1999 (DRAFT)

6 Message Profile Example (cont) 1.1 Use Case: Admit/Visit Notification Physician Patient is subject of authorizes triggers Registrar sends notification receives notification Admit/Visit Notification ADT System ADT Notification Recipient $FWRUV 3UHFRQGLWLRQV )ORZRIHYHQWV 3RVWFRQGLWLRQV 'HULYHVHYHQWV Description: A patient is admitted to the healthcare facility. Actors: 1. Patient - is the recipient of healthcare services. It is the subject of the admission to a healthcare facility. 2. Physician is legally responsible for admitting a patient to a healthcare facility. 3. Registrar is responsible for processing an admission request. 4. ADT System is responsible for sending a notification to interested subscribers when a patient is admitted to a healthcare facility. 5. ADT Notification Recipient is responsible for receiving notification of patient admissions. Pre-conditions: 1. A Patient is presented to the healthcare facility. 2. ADT Notification Recipients have subscribed for patient admission/visit event notifications. 3. The Physician authorizes the Patient for admission to the healthcare facility. 4. The Registrar processes the admission request. Flow of events: 1. The ADT System sends notification of the patient admission to all subscribers of this event. 2. Upon receipt of a patient admit/visit notification, the ADT Notification Recipient acknowledges that the event notification was received. 3. The ADT System receives the acknowledgement. If no acknowledgement is received or the acknowledgement indicates that the notification was not received, then the ADT System logs an error. Post-conditions: 1. All ADT Notification Recipients are aware that the Patient has been admitted. Derives events: 1. ADT^A01 - { awg(1) hl7(1) v2-3(5) static-profile(1) adt(3) a01(1) null(0) null(0) v1(1) } 2. ACK^A01 - { awg(1) hl7(1) v2-3(5) static-profile(1) ack(1) a01(1) null(0) null(0) v1(1) }

7 Patient ADT System is subject of Message Profile Example (cont) Physician authorizes triggers Registrar sends notification receives notification Admit/Visit Notification 8VHÃ&DVH 0RGHO ADT Notification Recipient ADT Cardinality Description MSH 1..1 Message Header EVN 1..1 Event Type PID 1..1 Patient Identification [PD1] 0..3 Additional Demographics [ { NK1 } ] 1..1 Next of Kin /Associated Parties PV Patient Visit [ PV2 ] 0..0 Patient Visit - Additional Info. [ { DB1 } ] 0..0 Disability Information [ { OBX } ] 0..0 Observation/Result [ { AL1 } ] 0..* Allergy Information [ { DG1 } ] 0..0 Diagnosis Information [ DRG ] 0..0 Diagnosis Related Group [ { 0..0 PR Procedures [{ROL}] 0..0 Role }] [ { GT1 } ] 0..0 Guarantor [ { 0..0 IN Insurance [ IN2 ] 0..0 Insurance Additional Info. [ IN3 ] 0..0 Insurance Add l Info - Cert. } ] [ ACC ] 0..0 Accident Information [ UB1 ] 0..0 Universal Bill Information [ UB2 ] 0..0 Universal Bill 92 Information 6WDWLFÃ3URILOH Type Table Name Value Description Source Used AWG 0007 Admission HL7 2.3, PV1-4 Type AWG, UB92 suggested 0007 A Accident HL E Emergency HL L Labor and Delivery HL R Routine HL ACC Accident 0007 EMR Emergency 0007 LAD Labor and Delivery 0007 NEB Newborn 0007 ROU Routine 0007 OBS Observation 0007 URG Urgent 0007 ELE Elective 0007 REH Rehabilitation 0007 HEL Helicopter 0007 NEP Newborn Premature 0007 NSP Newborn Sick Premature 0007 OCH Occupational Heath 0007 OTI Outpatient to Inpatient 7DEOHVÃ 1. USE CASE MODEL USE CASE: ADMIT/VISIT NOTIFICATION DYNAMIC INTERACTION MODEL STATIC PROFILE: ADT/ACK (EVENT A01) ADT^A ACK^A DYNAMIC PROFILE: ADT/ACK (EVENT A01) ADT^A ACK^A SEGMENT PROFILES MSH MESSAGE HEADER SEGMENT DEFINITION EVN - EVENT TYPE SEGMENT DEFINITION PID (Y) - PATIENT DEMOGRAPHICS SEGMENT DEFINITION PD1 PATIENT ADDITIONAL DEMOGRAPHIC SEGMENT DEFINITION NK1 - NEXT OF KIN SEGMENT DEFINITION PV1 (2) - ADMIT VISIT INFO SEGMENT DEFINITION AL1 - ALLERGY SEGMENT DEFINITION MSA - MESSAGE ACKNOWLEDGMENT SEGMENT DEFINITION ERR - ERROR SEGMENT DEFINITION TABLES TABLE 0001 SEX TABLE 0002 MARITAL STATUS TABLE 0003 EVENT TYPE CODE TABLE 0004 PATIENT CLASS TABLE 0005 RACE TABLE 006 RELIGION TABLE 0007 ADMISSION TYPE TABLE 0008 ACKNOWLEDGEMENT CODE TABLE 0009 AMBULATORY STATUS TABLE 0010 ADMITTING/ATTENDING/REFERRING/CONSULTING DOCTOR TABLE 0018 PATIENT TYPE TABLE 0023 ADMIT SOURCE TABLE 0062 EVENT REASON CODE TABLE 0063 RELATIONSHIP TABLE 0069 HOSPITAL SERVICE TABLE 0087 PREADMIT TEST INDICATOR TABLE 0092 READMISSION INDICATOR TABLE 0099 VIP INDICATOR TABLE 0104 VERSION ID TABLE 0127 ALLERGY TYPE TABLE 0128 ALLERGY SEVERITY TABLE 0131 CONTACT ROLE TABLE 0155 ACCEPT/APPLICATION ACKNOWLEDGEMENT CONDITIONS TABLE CITIZENSHIP TABLE 0172 VETERANS MILITARY STATUS TABLE 0189 ETHNIC GROUP TABLE 0296 PRIMARY LANGUAGE...39 : ADT System : ADT Notification Recipient ADT^A01 ACK^A01,QWHUDFWLRQ 0RGHO 1.1 ADT^A01 The dynamic profile of the ADT^A01 event notification requires that an HL7 Accept Acknowledgement be sent but that no HL7 Application Acknowledgement is sent in response to this ADT^A01 message. Dynamic Profile Identifier: { awg(1) hl7(1) v2-3(5) dynamic-profile(2) accal-appne(5) } 1.2 ACK^A01 The dynamic profile of the ACK^A01 acknowledgement requires that neither an HL7 Accept Acknowledgement or an HL7 Application Acknowledgement is sent in response to this ACK^A01 message. Dynamic Profile Identifier: { awg(1) hl7(1) v2-3(5) dynamic-profile(2) accne-appne(6) } '\QDPLFÃ3URILOHÃ SEQ LEN DT OPT RP/# TBL# ITEM # ELEMENT NAME 1 ST R Field Separator ST R Encoding Characters HD R Sending Application HD X Sending Facility HD RE Receiving Application HD X Receiving Facility 7 26 TS RE Date/Time Of Message 8 40 ST X Security 9 7 CM R Message Type ST R Message Control ID 11 3 PT R Processing ID 12 8 ID R Version ID NM X Sequence Number ST X Continuation Pointer 15 2 ID R Accept Acknowledgment Type 16 2 ID R Application Acknowledgment Type 17 2 ID RE Country Code 18 6 ID X Y/ Character Set CE X Principal Language Of Message 6HJPHQWÃ3URILOHVÃ

8 Profile Registry Supports Integration Registry Supports Yellow Pages and White Pages Lookup Each profile has a unique identifier Organizations register profiles (AWG, AHC, HL7 ) Organizations register use of profiles (vendor, provider ) Integrator uses tools for searching, and comparison Market determines utility of profiles Example of Profile Identifier (ASN.1) { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) hpmpg(3) profiles(3) awg(1) hl7(1) v2-3(5) static-profile(1) adt(3) a01(1) null(0) null(0) v1(1) } { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) hpmpg(3) profiles(3) awg(1) hl7(1) v2-3(5) dynamic-profile(2) accal-appne(5) }