Page tree
Skip to end of metadata
Go to start of metadata

This page describes the segment layout of the ADT messages that are sent to Amadeus.

Amadeus accepts messages containing segments that are not defined here, as long as the order and structure of those segments conform to the HL7 2.5.1 standard. However, it only processes and stores data from these segments.

A01, A03, A04, A08

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
ZMSHMessage header - customONBy default, the absence of a ZMSH segment indicates that you are using version 1 of the Amadeus message specification.
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
ZPD1

Patient additional demographic – custom

ONOnly supported in version 2 and later of the Amadeus message specification. See also ZMSH.
NK1Next of kin or associated partiesOY
  • Multiple NK1 segments may be included, but only one will be stored.
  • To identify which NK1 segment is used as the emergency contact, the segments are scanned sequentially to check the value of NK1.7.1 Contact Role Identifier. The first segment with NK1.7.1 = ER is selected as the Emergency Contact and the name and relationship are stored. If this process does not identify an emergency contact, the first NK1 segment is used by default.
PV1Patient visit RN

For sites that send A04 and A08 messages with empty PV1 segments, see Mapping A04 and A08 Messages.

ZPV1Patient visit - customON
PV2Patient visit additional informationON
AL1Allergy informationOYThe AL1 segment is ignored in A03 messages.
DG1DiagnosisOY
ZDG1Diagnosis - customON
PROCEDURE
O Y  

PR1

ProceduresRN

ZPR1

Procedures - customON
INSURANCE
O Y

IN1

InsuranceRNRequires the Insurance module.

IN2

Insurance additional informationOYRequires the Insurance module.
PDAPatient death and autopsyIN

Mapping A04 and A08 Messages

A04 (Patient Registration) and A08 (Patient Information Update) messages require a PV1 segment. However, in some cases, participants send them with an empty PV1 segment. For these participants, the site-specific configuration must map the:

  • A04 to an A28 message
  • A08 to an A31 message

The only difference between these messages is that an A04 and A08 require a PV1 segment, while it is optional for an A28 and A31 message.


A02

Segment  Name


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
PV1Patient visitRN
ZPV1Patient visit - customON
PV2Patient visit additional informationON
PDAPatient death and autopsyIN

A05, A28, A31

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
ZMSHMessage header - customONBy default, the absence of a ZMSH segment indicates that you are using version 1 of the Amadeus message specification.
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
ZPD1Additional demographics - customON

Only supported in version 2 and later of the Amadeus message specification. See also ZMSH .

NK1Next of kin or associated partiesOY
  • Multiple NK1 segments may be included, but only one will be stored.
  • To identify which NK1 segment is used as the emergency contact, the segments are scanned sequentially to check the value of NK1.7.1 Contact Role Identifier. The first segment with NK1.7.1 = ER is selected as the Emergency Contact and the name and relationship are stored. If this process does not identify an emergency contact, the first NK1 segment is used by default.
PV1Patient visitRN

Not required for A28 and A31. 

ZPV1Patient visit - customON
PV2Patient visit additional informationON
AL1Allergy informationOY
DG1DiagnosisOY
ZDG1Diagnosis - customON
PROCEDURE
O Y  

PR1

ProceduresRN

ZPR1

Procedures - customON
INSURANCE
O Y  

IN1

InsuranceRNRequires the Insurance module.

IN2

Insurance additional informationONRequires the Insurance module.

A06, A07

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
NK1Next of kin or associated partiesOY
  • Multiple NK1 segments may be included, but only one will be stored.
  • To identify which NK1 segment is used as the emergency contact, the segments are scanned sequentially to check the value of NK1.7.1 Contact Role Identifier. The first segment with NK1.7.1 = ER is selected as the Emergency Contact and the name and relationship are stored. If this process does not identify an emergency contact, the first NK1 segment is used by default.
PV1Patient visitRN

 

ZPV1Patient visit - customON
PV2Patient visit additional informationON
AL1Allergy informationOY
DG1DiagnosisOY
ZDG1Diagnosis - customON
PROCEDURE
O Y  

PR1

ProceduresRN

ZPR1

Procedures - customON
INSURANCE
O Y  

IN1

InsuranceRNRequires the Insurance module.

IN2

Insurance additional informationONRequires the Insurance module.

A11, A38

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
PV1Patient visitRN
ZPV1Patient visit - customON
PV2Patient visit additional informationON
DG1DiagnosisOY
ZDG1Diagnosis - customON

A12

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
SFTSoftwareIN
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
PV1Patient visitRN
ZPV1Patient visit - customON
PV2Patient visit additional informationON
DG1DiagnosisOY
ZDG1Diagnosis - customON

A13

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
EVN  Event informationRN
PIDPatient identificationRN
PD1Additional demographicsON
NK1Next of kin or associated partiesOY
  • Multiple NK1 segments may be included, but only one will be stored.
  • To identify which NK1 segment is used as the emergency contact, the segments are scanned sequentially to check the value of NK1.7.1 Contact Role Identifier. The first segment with NK1.7.1 = ER is selected as the Emergency Contact and the name and relationship are stored. If this process does not identify an emergency contact, the first NK1 segment is used by default.
PV1Patient visit RN
ZPV1Patient visit - customON
PV2Patient visit additional informationON
AL1Allergy informationOY
DG1DiagnosisOY
ZDG1Diagnosis - customON
PROCEDURE
O Y  

PR1

ProceduresRN

ZPR1

Procedures - customON
INSURANCE
O Y  

IN1

InsuranceRNRequires the Insurance module.

IN2

Insurance additional informationOYRequires the Insurance module.
PDAPatient death and autopsyIN

A40

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
EVN  Event informationRN
PATIENT
R Y  

PID

Patient identification

R

N

PD1

Additional demographicsON

MRG

Merge informationRN

PV1

Patient visitON

ZPV1

Patient visit - customON

A45, A50

ADT^A50 message processing is only supported in Orion Health solutions that are deployed with CDR. In solutions deployed with CDS, these messages are sent to the error queue.

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
SFTSoftwareIY
EVNEvent informationRN
PIDPatient identificationRN
PD1Additional demographicsON
MERGE_INFO
R N  

MRG

Merge informationRN

PV1

Patient visitRN

MERGE_INFO Segment Group

MERGE_INFO is an ordered group that contains the MRG and PV1 segments. The following are some key differences from the HL7 specification:

  • The HL7 ADT specification permits repeating MERGE_INFO groups. This means that there can be multiple Move Encounter requests for a patient in a PID segment. However, the ADT definition in Orion Health solutions only permits one MERGE_INFO group, as CDR8 does not support multiple groups. If the source message has multiple MERGE_INFO groups, it will fail validation.
  • Both patients must exist in EMPI before their information in the ADT^A45 message is sent. If one of the patients is not in EMPI, CDR will accept the ADT^A45 message and move the Encounter information to or from a non-existent patient but Clinical Portal will not reflect this information move.

How CDS processes an ADT^A45

The Mutation Subscription mappers are used for ingesting ADT^A45 messages in an Orion Health solution deployed with CDS. The Log Type (FTV values) for ADT^A45 is:

HL7:ADTA45:1


A60

ADT^A60 message processing is only supported in Orion Health solutions that are deployed with CDS. In solutions deployed with CDR, these messages are sent to the error queue.

SegmentName


Usage ?



Can Repeat ?


Guidance
MSHMessage headerRN
SFTSoftwareIY
EVNEvent informationRN
PIDPatient identificationRN
PV1Patient visitON
PV2Patient visit additional informationON
IAMPatient adverse reaction informationOY
IN THIS SECTION


  • No labels