18.4.11 ADT/ACK - Pending Discharge (Event A16) (3.3.16)

An A16 event notifies other systems of a plan to discharge a patient when the patient has not yet left the healthcare facility. It is used when advanced notification of a discharge is required in order to prepare for the patient's change in location. For example, it is used to notify the pharmacy of the possible need for discharge drugs or to notify psychotherapy of the possible need for post-discharge appointments or to notify the extended care or home health system that the patient will be discharged and that the new extended care and home health admission assessment can be scheduled.

The fields included when this message is sent should be the fields pertinent to communicate this event. When other important fields change, it is recommended that the A08 (update patient information) event be used in addition.

The ROL segment has been deprecated and retained for backwards compatiblity purposes only as of v 2.9. The reader is referred to the PRT segment instead.

The PRT - Participation Information Segment is used in this message to communicate providers not specified elsewhere. Person level providers with an ongoing relationship are reported in the PRT segment following the PID/PD1 segments. Providers corresponding to the PV1 data are reported in the PRT segment following the PV1/PV2 segments. Providers related to a specific procedure are reported in the PRT segment following the PR1 segment. Providers related to a specific insurance are reported in the PRT segment following the IN1/IN2/IN3 segments. To communicate the begin- and end-date of the provider, use the PRT-11 - Begin Date/Time and the PRT-12 - End Date/Time in the PRT, with the applicable PRT-4 - Role of Participation. Refer to Chapter 7 for the definition of the PRT segment.

• Message
• ACK Choreography
• FHIR Structure Definition
• v2.xml XSD
• ER7 Example
• XML Example

Segment	Cardinality	Implement	Status
ADT^A16^ADT_A16
MSH Message Header	[1..1]	SHALL
ARV Access Restriction
SFT Software Segment
UAC User Authentication Credential Segment	[0..1]
EVN Event Type	[1..1]	SHALL
PID Patient Identification	[1..1]	SHALL
PD1 Patient Additional Demographic	[0..1]
OH1 Person Employment Status
OH2 Past or Present Job
OH3 Usual Work	[0..1]
OH4 Combat Zone Work
ARV Access Restriction			B
ROL Role			B
PRT Participation Information
NEXT_OF_KIN
NK1 Next of Kin / Associated Parties	[1..1]	SHALL
OH2 Past or Present Job
OH3 Usual Work	[0..1]
PV1 Patient Visit	[1..1]	SHALL
PV2 Patient Visit - Additional Information	[0..1]
ARV Access Restriction			B
ROL Role			B
PRT Participation Information
DB1 Disability
OBSERVATION
OBX Observation/Result	[1..1]	SHALL
PRT Participation Information
AL1 Patient Allergy Information
IAM Patient Adverse Reaction Information
DG1 Diagnosis
DRG Diagnosis Related Group	[0..1]
PROCEDURE
PR1 Procedures	[1..1]	SHALL
ROL Role			B
PRT Participation Information
GT1 Guarantor
INSURANCE
IN1 Insurance	[1..1]	SHALL
IN2 Insurance Additional Information	[0..1]
IN3 Insurance Additional Information, Certification
ROL Role			B
PRT Participation Information
AUTHORIZATION
AUT Authorization Information	[1..1]	SHALL
PRT Participation Information
REFERRAL
RF1 Referral Information	[1..1]	SHALL
PRT Participation Information
ACC Accident	[0..1]

 

ADT_A16

MSH-15	MSH-16	Immediate ACK	Application Ack
Blank	Blank	-	ADT^A16^ADT_A16
NE	NE	-	-
AL, SU, ER	NE	ACK^A16^ACK	-
NE	AL, SU, ER	-	ACK^A16^ACK
AL, SU, ER	AL, SU, ER	ACK^A16^ACK	ACK^A16^ACK

We need some ER7 examples...

We need some XML examples...