ADTs

1. What is the format of the ADT message?

ADT messages are delivered as Base64-encoded JSON containing the raw HL7 V2 message. Messages are encoded in Base64 to ensure HL7 V2 standard encoding characters (| & ^ ~) are transmitted without corruption.

2. Do you support ADT messages in FHIR or FLAT?

At this time ADT messages are not available in the FHIR or FLAT formats. However, we are exploring offering this feature in the future, if there's sufficient demand.

3. What ADT event types are available?

The following ADT events are supported:

Message Type	Action
A01	Admit Patient
A02	Transfer Patient
A03	Discharge Patient
A04	Register Patient
A08	Update Patient
A11	Cancel Admit
A12	Cancel Transfer
A13	Cancel Discharge
A21	Start of medical leave of absence (MLOA)
A22	Return from MLOA
A52	Cancel start of MLOA
A53	Cancel return from MLOA

Note:

Update Patient (A08)

Applies to the preceding event. When patient information is updated, such as insurance, that update should link to the previous admission or discharge event.

Register Patient (A04)

Creates a presented event for ED presentations. This means for an A04 message with a patient class of emergency, the event will be mapped to CREATE_PRESENTED in the EVN.4. Additionally, Registration events do not precede an admit event unless the patient is returning to the ED.