ADT_A28
3.2.28 ADT/ACK - add person information (event A28)
21 segments
The purpose of this and the three following messages is to allow sites with multiple systems and respective master patient databases to communicate activity related to a person regardless of whether that person is currently a patient on each system. Each system has an interest in the database activity of the others in order to maintain data integrity across an institution. Though they are defined within the ADT message set, these messages differ in that they are not patient-specific. To a certain registry, the person may be a person of interest, a potential future patient, or a potential guarantor. For example, these events can be used to maintain an MPI (master patient index), a cancer registry, members of a managed care plan, an HIV database, etc.
These events should not replace the use of the A01 (admit/visit notification, A03 (discharge/end visit), A04 (register a patient), A08 (update patient information), etc., events. They are not intended to be used for notification of real-time Patient Administration events. Visit information may be included but is not required. These events are primarily for demographic data, but optional historical non-demographic data may be sent as well.
Message Structure
21 segments
R RequiredO Optional Choice
MSH
R1EVN
R1PID
R1PD1
O1NK1
O*PV1
R1PV2
O1DB1
O*OBX
O*AL1
O*DG1
O*DRG
O1PROCEDURE
O*PR1
R1ROL
O*GT1
O*INSURANCE
O*IN1
R1IN2
O1IN3
O1ACC
O1UB1
O1UB2
O1