Embedded Files
ADT A08: Update an encounter
ADT A08: Update an encounter
Overview
Overview
Records an update to Encounter information.
Relevant entities
Relevant entities
Encounter information is used to populate [[Encounter]] and [[Encounter Event]] entities
Please click through to the Data Model to explore the presentation of these entities in the web interface.
Updated behaviour
Updated behaviour
[[Encounter]]
Matched on: [[Encounter.External Encounter ID]] as derived from PV1-19.1
When matched: The [[Encounter Event]] will be handled as indicated below.
When not matched: No action.
[[Encounter Event]]: Admission Event
Matched on: An Encounter can contain zero or one admission [[Encounter Event]]s. If the [[Encounter]] has been matched, then there will be at most one admission [[Encounter Event]], so no other IDs are required for matching.
When matched: The timestamp of the existing admission [[Encounter Event]] will be updated to the admit timestamp provided on this update [[Encounter Event]], if one was provided and which differs.
When not matched: No action.
[[Encounter Event]]: Discharge Event
Matched on: An Encounter can contain zero or one discharge [[Encounter Event]]s. If the [[Encounter]] has been matched, then there will be at most one discharge [[Encounter Event]], so no other IDs are required for matching.
When matched: The timestamp of the existing discharge [[Encounter Event]] will be updated to the discharge timestamp provided on this update [[Encounter Event]], if one was provided and which differs.
When not matched: No action.
[[Encounter Event]]: Update Event
Matched on: Update [[Encounter Event]]s are not uniquely identifiable.
When matched: N/A
When not matched: The update event [[Encounter Event]] will be added to the [[Encounter]].
Definition
Definition
This is identical in format to the ADT A01, except that timestamp of the update [[Encounter Event]] will be taken from EVN-6, and PV1-44 and PV1-45 will be checked only for updates to the timestamp of admission and/or discharge [[Encounter Event]]s, where they exist. This is shown below:
Examples
Examples
MSH|^~\&|SendingApp|SendingFacility|HL7API|PKB|20160102101112||ADT^A08|ABC0000000001|P|2.4
PID|||9999999999^^^NHS^NH||Smith^John^Joe^^Mr||19700101|M|||Flat name^1, The Road^London^London^SW1A 1AA^GBR||01234567890^PRN~07123456789^PRS|^NET^^john.smith@company.com~01234098765^WPN||||||||||||||||N|
PV1|1|I|^^^^^^^^My Ward||||^Jones^Stuart^James^^Dr^|^Smith^William^^^Dr^|^Foster^Terry^^^Mr^||||||||||V00001|||||||||||||||||||||||||201508011000|201508011200
Response
Response
PKB will respond with a standard HL7 acknowledgement.
Page updated
Report abuse