SlideShare a Scribd company logo
Name: Carmen Alcivar
Week 3 Homework Assignment
Decode the following HL7 Version 2.5.1 Message
MSH|^~&|REGADT|MCM|IFENG||200301061000||ADT^A05^ADT_A05|000001|P|2.5.1|||
 MSH: Message header, must begin every message, segment identifier
 |- Field Separator
 ^~&|Encoding characters, component separator, repetition separator, escape character,
subcomponent separator
 REGADT: Sending application. preadmit notification – non admitted patient. The REGADT system
supports entry of two insurance plans, one guarantor, and one diagnosis.
 MCM: Sending facility. this notification was recorded in the MCM system
 IFENG: Receiving application. This was sent to the interface engine on the date and time below
 Skip 1, receiving facility
 200301061000: date and time of message
 |Skip 1, security
 ADT^A05^ADT_A05: Message type, Admit discharge transfer:
o ADT: Readmit notification
o A05: Event A05= non-admitted patient.
o ADT_A05: Admit discharge transfer
 000001: - message control ID.
 P: Processing ID,
 2.5.1 : version
 |||Skip 2: Sequence number and Continuation pointer
EVN|A05|200301061000|200301101400|01||200301061000
 EVN: event type segment
 A05: pre-admit a patient
 200301061000: recorded date and time
 200301101400: Date/Time Planned Event
 01: event reason, Patient request
 ||Skip 1 operator ID
 200301061000:date and time event occurred
PID|1||191919^^^GENHOS||MASSIE^JAMES^A||19560129|M|||171
ZOBERLEIN^^ISHPEMING^MI^49849^""^||(900)485-5344|(900)485-
5344||S||10199925^^^GENHOS^AN|371-66-9256||
 PID| Set Id- Patient Identification segment
 1|: This field contains the number that identifies this transaction. For the first occurrence of the
segment, the sequence number shall be one, for the second occurrence, the sequence number shall
be two, etc.
 Skip 1 : patient ID
 191919^^^GENHOS : Patient Identifier list
o 191919: patient ID number
o Skip 2: heck Digit (ST) , Check Digit Scheme (ID)
o GENHOS : Assigning authority
 Skip 1 : Alternate Patient ID-PID
 MASSIE^JAMES^A: Patie t’s a e
o MASSIE: Family name
o JAMES: Given name
o A: Second and Further Given Names or Initials Thereof
 Skip 1: Mothert’s a e aide a e
 19560129: date/time of birth
 M: Administrative sex- Male
 Skip 2: alias and race
 171 ZOBERLEIN ^^ISHPEMING^MI^49849^""^ : Patient Address :
o 171 ZOBERLEIN : street address
o Skip 2 : Other Designation and City
o ISHPEMING^MI^49849^""^ St
o ISHPEMING: city
o MI, state or province
o 49849 Zip or postal code
o "":country Id
 Skip 1: Country code
 (900)485-5344 : Phone number home
 (900)485-5344 : Phone number business
 Skip1
 S: Marital Status – Single
 Skip 1: Religion
 10199925^^^GENHOS^AN: Patient Account number
o 10199925: patient ID number
o Skip 2 : heck Digit (ST)> ^ <Check Digit Scheme (ID
o GENHOS: Assigning authority
o AN: Identifier Type Code (ID)
 371-66-9256: Social Security Number Patient
 Skip 1 Driver's License Number - Patient
NK1|1|MASSIE^ELLEN|SPOUSE|171 ZOBERLEIN^^ISHPEMING^MI^49849^""^|(900)485-
5344|(900)545-1234~(900)545-1200|EC^EMERGENCY CONTACT
 NK1: Next of Kin/Associated Parties
 1: Set Id-NK1
 MASSIE^ELLEN: Name
o MASSIE : Family name (FN)
o ELLEN: Given name (ST)
 SPOUSE: Relationship
 171 ZOBERLEIN^^ISHPEMING^MI^49849^""^|: Address
o 171 ZOBERLEIN : Street Address
o Skip 1: Other Designation (ST)
o ISHPEMING: City (ST)
o MI (State or Province (ST)
o 49849: Zip of Postal Code
o "" : Country ID
 (900)485-5344: Phone Number
 (900)545-1234~ 900)545-1200:Business Phone Number
 EC^EMERGENCY CONTACT : Contact Role
o EC : Identifier (ST), Employer Emergency contact
o EMERGENCY CONTACT : Text (ST)
PV1||O|||||0148^ADDISON^JAMES|0148^ADDISON^JAMES|0148^ADDISON^JAMES|AMB|||||||0
148^ADDISON^JAMES||1|
 PV1: Patient visit segment-first occurrence
 Skip 1: Set ID
 O: Patient Class: Outpatient
 Skip4: Assigned Patient Location, Admission type, Preadmit Number, Prior Patient Location
 0148^ADDISON^JAMES:Attending Doctor
o 0148: Id Number (ST)
o ADDISON: Family Name (FN)
o JAMES: Given Name (ST)
 0148^ADDISON^JAMES: Referring Doctor
o 0148: Id Number (ST)
o ADDISON: Family Name (FN)
o JAMES: Given Name (ST)
 0148^ADDISON^JAMES Referring Doctor
o 0148: Id Number (ST)
o ADDISON: Family Name (FN)
o JAMES: Given Name (ST)
 AMB: Hospital Service
 ||||||| Skip 6 : Temporary Location, Preadmit Test Indicator, Re-Admission Indicator, Admit Source,
Ambulatory Status, VIP Indicator
 0148^ADDISON^JAMES: Admitting Doctor
o 0148: Id Number (ST)
o ADDISON: Family Name (FN)
o JAMES: Given Name (ST)
 Skip 1: Patient Type
 1: visit number
OBX|1|ST|1010.1^BODY WEIGHT||62|kg|||||F
 OBX: Observation/Result Segment
 1: set ID, This field contains the sequence number so in this case this is the number of the sequence.
 ST: Value Type String Data
 1010.1^BODY WEIGHT: Observation Identifier
o 1010.1:Identifier ST
o BODY WEIGHT: Text ST
 Skip 1: Observation subID
 62: Observation value
 Kg: Units
 ||||| skip 4:References Range, Abnormal Flags, Probability, Nature of Abnormal Test,
 F : Observation Result Status: Final results; Can only be changed with a corrected result.
OBX|2|ST|1010.1^HEIGHT||190|cm|||||F
 OBX: Set ID, Observation/Result Segment
 2: Sequence number. Observation 2
 ST: Value Type String Data
 1010.1^HEIGHT: Observation Identifier
o 1010.1: Identifier ST
o HEIGHT: Text ST

 Skip 1: Observation Sub-ID
 190: Observation value
 Cm: units
 ||||| skip 4: References Range, Abnormal Flags, Probability, Nature of Abnormal Test,
 F: Observation Result Status: Final results; Can only be changed with a corrected result.

More Related Content

What's hot

2009 12 07 - LOINC Introduction and Overview
2009 12 07 - LOINC Introduction and Overview2009 12 07 - LOINC Introduction and Overview
2009 12 07 - LOINC Introduction and Overviewdvreeman
 
Patient matching in FHIR
Patient matching in FHIRPatient matching in FHIR
Patient matching in FHIRGrahame Grieve
 
Authoring Profiles in FHIR
Authoring Profiles in FHIRAuthoring Profiles in FHIR
Authoring Profiles in FHIREwout Kramer
 
IHE on FHIR and DICOMweb 2017
IHE on FHIR and DICOMweb 2017IHE on FHIR and DICOMweb 2017
IHE on FHIR and DICOMweb 2017Brad Genereaux
 
Understanding Resources in FHIR - Session 3 of FHIR basics training series
Understanding Resources in FHIR - Session 3 of FHIR basics training seriesUnderstanding Resources in FHIR - Session 3 of FHIR basics training series
Understanding Resources in FHIR - Session 3 of FHIR basics training seriesKumar Satyam
 
Fhir basics session 1 Introduction to Interoperabilty & Principles of FHIR
Fhir basics session 1 Introduction to Interoperabilty & Principles of FHIRFhir basics session 1 Introduction to Interoperabilty & Principles of FHIR
Fhir basics session 1 Introduction to Interoperabilty & Principles of FHIRKumar Satyam
 
Introduction to cda may 2019 montreal
Introduction to cda may 2019 montrealIntroduction to cda may 2019 montreal
Introduction to cda may 2019 montrealAbdul-Malik Shakir
 
FHIR Tutorial - Morning
FHIR Tutorial - MorningFHIR Tutorial - Morning
FHIR Tutorial - MorningEwout Kramer
 
Hospital Readmissions Reduction Program: Keys to Success
Hospital Readmissions Reduction Program: Keys to SuccessHospital Readmissions Reduction Program: Keys to Success
Hospital Readmissions Reduction Program: Keys to SuccessHealth Catalyst
 
FHIR Documents by Lloyd McKenzie
FHIR Documents by Lloyd McKenzieFHIR Documents by Lloyd McKenzie
FHIR Documents by Lloyd McKenzieFHIR Developer Days
 
Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...
Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...
Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...Tobias Schimmer
 
Hl7 standard
Hl7 standardHl7 standard
Hl7 standardMarina462
 
Precise Patient Registries: The Foundation for Clinical Research & Population...
Precise Patient Registries: The Foundation for Clinical Research & Population...Precise Patient Registries: The Foundation for Clinical Research & Population...
Precise Patient Registries: The Foundation for Clinical Research & Population...Health Catalyst
 
FHIR architecture overview for non-programmers by René Spronk
FHIR architecture overview for non-programmers by René SpronkFHIR architecture overview for non-programmers by René Spronk
FHIR architecture overview for non-programmers by René SpronkFHIR Developer Days
 

What's hot (20)

Healthcare HIPAA Edi x12 basics 1
Healthcare HIPAA Edi x12 basics 1Healthcare HIPAA Edi x12 basics 1
Healthcare HIPAA Edi x12 basics 1
 
Hl7 & FHIR
Hl7 & FHIRHl7 & FHIR
Hl7 & FHIR
 
2009 12 07 - LOINC Introduction and Overview
2009 12 07 - LOINC Introduction and Overview2009 12 07 - LOINC Introduction and Overview
2009 12 07 - LOINC Introduction and Overview
 
Patient matching in FHIR
Patient matching in FHIRPatient matching in FHIR
Patient matching in FHIR
 
Authoring Profiles in FHIR
Authoring Profiles in FHIRAuthoring Profiles in FHIR
Authoring Profiles in FHIR
 
IHE on FHIR and DICOMweb 2017
IHE on FHIR and DICOMweb 2017IHE on FHIR and DICOMweb 2017
IHE on FHIR and DICOMweb 2017
 
Understanding Resources in FHIR - Session 3 of FHIR basics training series
Understanding Resources in FHIR - Session 3 of FHIR basics training seriesUnderstanding Resources in FHIR - Session 3 of FHIR basics training series
Understanding Resources in FHIR - Session 3 of FHIR basics training series
 
Hl7 overview
Hl7 overviewHl7 overview
Hl7 overview
 
Fhir basics session 1 Introduction to Interoperabilty & Principles of FHIR
Fhir basics session 1 Introduction to Interoperabilty & Principles of FHIRFhir basics session 1 Introduction to Interoperabilty & Principles of FHIR
Fhir basics session 1 Introduction to Interoperabilty & Principles of FHIR
 
FHIR & Ice
FHIR & IceFHIR & Ice
FHIR & Ice
 
Introduction to cda may 2019 montreal
Introduction to cda may 2019 montrealIntroduction to cda may 2019 montreal
Introduction to cda may 2019 montreal
 
FHIR Tutorial - Morning
FHIR Tutorial - MorningFHIR Tutorial - Morning
FHIR Tutorial - Morning
 
Hospital Readmissions Reduction Program: Keys to Success
Hospital Readmissions Reduction Program: Keys to SuccessHospital Readmissions Reduction Program: Keys to Success
Hospital Readmissions Reduction Program: Keys to Success
 
FHIR Documents by Lloyd McKenzie
FHIR Documents by Lloyd McKenzieFHIR Documents by Lloyd McKenzie
FHIR Documents by Lloyd McKenzie
 
Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...
Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...
Design Thinking and Business Model Innovation at SAP - From Efficiency to Inn...
 
Hl7 standard
Hl7 standardHl7 standard
Hl7 standard
 
Precise Patient Registries: The Foundation for Clinical Research & Population...
Precise Patient Registries: The Foundation for Clinical Research & Population...Precise Patient Registries: The Foundation for Clinical Research & Population...
Precise Patient Registries: The Foundation for Clinical Research & Population...
 
Introduction to hl7 v2
Introduction to hl7 v2Introduction to hl7 v2
Introduction to hl7 v2
 
FHIR and DICOM by Marten Smits
FHIR and DICOM by Marten SmitsFHIR and DICOM by Marten Smits
FHIR and DICOM by Marten Smits
 
FHIR architecture overview for non-programmers by René Spronk
FHIR architecture overview for non-programmers by René SpronkFHIR architecture overview for non-programmers by René Spronk
FHIR architecture overview for non-programmers by René Spronk
 

More from CARMEN ALCIVAR

Population Health - HEDIS - Health Plan
Population Health - HEDIS - Health PlanPopulation Health - HEDIS - Health Plan
Population Health - HEDIS - Health PlanCARMEN ALCIVAR
 
Packet capture and network traffic analysis
Packet capture and network traffic analysisPacket capture and network traffic analysis
Packet capture and network traffic analysisCARMEN ALCIVAR
 
example of sql injection
example of sql injectionexample of sql injection
example of sql injectionCARMEN ALCIVAR
 
encryption and hash algorithms
encryption and hash algorithmsencryption and hash algorithms
encryption and hash algorithmsCARMEN ALCIVAR
 
Auditing a Wireless Network and Planning for a Secure WLAN Implementation
Auditing a Wireless Network and Planning for a Secure WLAN ImplementationAuditing a Wireless Network and Planning for a Secure WLAN Implementation
Auditing a Wireless Network and Planning for a Secure WLAN ImplementationCARMEN ALCIVAR
 
Utilization Management
Utilization ManagementUtilization Management
Utilization ManagementCARMEN ALCIVAR
 

More from CARMEN ALCIVAR (6)

Population Health - HEDIS - Health Plan
Population Health - HEDIS - Health PlanPopulation Health - HEDIS - Health Plan
Population Health - HEDIS - Health Plan
 
Packet capture and network traffic analysis
Packet capture and network traffic analysisPacket capture and network traffic analysis
Packet capture and network traffic analysis
 
example of sql injection
example of sql injectionexample of sql injection
example of sql injection
 
encryption and hash algorithms
encryption and hash algorithmsencryption and hash algorithms
encryption and hash algorithms
 
Auditing a Wireless Network and Planning for a Secure WLAN Implementation
Auditing a Wireless Network and Planning for a Secure WLAN ImplementationAuditing a Wireless Network and Planning for a Secure WLAN Implementation
Auditing a Wireless Network and Planning for a Secure WLAN Implementation
 
Utilization Management
Utilization ManagementUtilization Management
Utilization Management
 

HL7 decoding _Alcivar_C

  • 1. Name: Carmen Alcivar Week 3 Homework Assignment Decode the following HL7 Version 2.5.1 Message MSH|^~&|REGADT|MCM|IFENG||200301061000||ADT^A05^ADT_A05|000001|P|2.5.1|||  MSH: Message header, must begin every message, segment identifier  |- Field Separator  ^~&|Encoding characters, component separator, repetition separator, escape character, subcomponent separator  REGADT: Sending application. preadmit notification – non admitted patient. The REGADT system supports entry of two insurance plans, one guarantor, and one diagnosis.  MCM: Sending facility. this notification was recorded in the MCM system  IFENG: Receiving application. This was sent to the interface engine on the date and time below  Skip 1, receiving facility  200301061000: date and time of message  |Skip 1, security  ADT^A05^ADT_A05: Message type, Admit discharge transfer: o ADT: Readmit notification o A05: Event A05= non-admitted patient. o ADT_A05: Admit discharge transfer  000001: - message control ID.  P: Processing ID,  2.5.1 : version  |||Skip 2: Sequence number and Continuation pointer EVN|A05|200301061000|200301101400|01||200301061000  EVN: event type segment  A05: pre-admit a patient  200301061000: recorded date and time  200301101400: Date/Time Planned Event  01: event reason, Patient request  ||Skip 1 operator ID  200301061000:date and time event occurred
  • 2. PID|1||191919^^^GENHOS||MASSIE^JAMES^A||19560129|M|||171 ZOBERLEIN^^ISHPEMING^MI^49849^""^||(900)485-5344|(900)485- 5344||S||10199925^^^GENHOS^AN|371-66-9256||  PID| Set Id- Patient Identification segment  1|: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.  Skip 1 : patient ID  191919^^^GENHOS : Patient Identifier list o 191919: patient ID number o Skip 2: heck Digit (ST) , Check Digit Scheme (ID) o GENHOS : Assigning authority  Skip 1 : Alternate Patient ID-PID  MASSIE^JAMES^A: Patie t’s a e o MASSIE: Family name o JAMES: Given name o A: Second and Further Given Names or Initials Thereof  Skip 1: Mothert’s a e aide a e  19560129: date/time of birth  M: Administrative sex- Male  Skip 2: alias and race  171 ZOBERLEIN ^^ISHPEMING^MI^49849^""^ : Patient Address : o 171 ZOBERLEIN : street address o Skip 2 : Other Designation and City o ISHPEMING^MI^49849^""^ St o ISHPEMING: city o MI, state or province o 49849 Zip or postal code o "":country Id  Skip 1: Country code  (900)485-5344 : Phone number home  (900)485-5344 : Phone number business  Skip1  S: Marital Status – Single  Skip 1: Religion  10199925^^^GENHOS^AN: Patient Account number o 10199925: patient ID number o Skip 2 : heck Digit (ST)> ^ <Check Digit Scheme (ID
  • 3. o GENHOS: Assigning authority o AN: Identifier Type Code (ID)  371-66-9256: Social Security Number Patient  Skip 1 Driver's License Number - Patient NK1|1|MASSIE^ELLEN|SPOUSE|171 ZOBERLEIN^^ISHPEMING^MI^49849^""^|(900)485- 5344|(900)545-1234~(900)545-1200|EC^EMERGENCY CONTACT  NK1: Next of Kin/Associated Parties  1: Set Id-NK1  MASSIE^ELLEN: Name o MASSIE : Family name (FN) o ELLEN: Given name (ST)  SPOUSE: Relationship  171 ZOBERLEIN^^ISHPEMING^MI^49849^""^|: Address o 171 ZOBERLEIN : Street Address o Skip 1: Other Designation (ST) o ISHPEMING: City (ST) o MI (State or Province (ST) o 49849: Zip of Postal Code o "" : Country ID  (900)485-5344: Phone Number  (900)545-1234~ 900)545-1200:Business Phone Number  EC^EMERGENCY CONTACT : Contact Role o EC : Identifier (ST), Employer Emergency contact o EMERGENCY CONTACT : Text (ST) PV1||O|||||0148^ADDISON^JAMES|0148^ADDISON^JAMES|0148^ADDISON^JAMES|AMB|||||||0 148^ADDISON^JAMES||1|  PV1: Patient visit segment-first occurrence  Skip 1: Set ID  O: Patient Class: Outpatient  Skip4: Assigned Patient Location, Admission type, Preadmit Number, Prior Patient Location  0148^ADDISON^JAMES:Attending Doctor o 0148: Id Number (ST) o ADDISON: Family Name (FN) o JAMES: Given Name (ST)  0148^ADDISON^JAMES: Referring Doctor o 0148: Id Number (ST) o ADDISON: Family Name (FN) o JAMES: Given Name (ST)
  • 4.  0148^ADDISON^JAMES Referring Doctor o 0148: Id Number (ST) o ADDISON: Family Name (FN) o JAMES: Given Name (ST)  AMB: Hospital Service  ||||||| Skip 6 : Temporary Location, Preadmit Test Indicator, Re-Admission Indicator, Admit Source, Ambulatory Status, VIP Indicator  0148^ADDISON^JAMES: Admitting Doctor o 0148: Id Number (ST) o ADDISON: Family Name (FN) o JAMES: Given Name (ST)  Skip 1: Patient Type  1: visit number OBX|1|ST|1010.1^BODY WEIGHT||62|kg|||||F  OBX: Observation/Result Segment  1: set ID, This field contains the sequence number so in this case this is the number of the sequence.  ST: Value Type String Data  1010.1^BODY WEIGHT: Observation Identifier o 1010.1:Identifier ST o BODY WEIGHT: Text ST  Skip 1: Observation subID  62: Observation value  Kg: Units  ||||| skip 4:References Range, Abnormal Flags, Probability, Nature of Abnormal Test,  F : Observation Result Status: Final results; Can only be changed with a corrected result. OBX|2|ST|1010.1^HEIGHT||190|cm|||||F  OBX: Set ID, Observation/Result Segment  2: Sequence number. Observation 2  ST: Value Type String Data  1010.1^HEIGHT: Observation Identifier o 1010.1: Identifier ST o HEIGHT: Text ST   Skip 1: Observation Sub-ID  190: Observation value  Cm: units  ||||| skip 4: References Range, Abnormal Flags, Probability, Nature of Abnormal Test,  F: Observation Result Status: Final results; Can only be changed with a corrected result.