Stream: V2
Topic: ADT Cancel Transfer (Event A12)
Richard Kavanagh (May 12 2020 at 12:50):
I'm passing a question on from a colleague..
If a patient is admitted as a patient (ADT^A01^ADT_A01) and then undergoes a series of transfers (ADT^A02^ADT_A02) - is it possible to cancel (ADT^A12^ADT_A09) any of the previous transfers or just the latest one?
Does the processing of a (ADT^A12^ADT_A09) re-establish the bed state (via PV1-3)?
Hopefully, this makes sense...
René Spronk (May 13 2020 at 06:19):
A12 (as a trigger event) only cancels the latest transfer. A12 itself lists the correct location in PV1. As such if you were to send a single A12 to cancel multiple subsequent transfers it would probably still work, but AFAIK it's not the intent of an A12.
Richard Kavanagh (May 13 2020 at 07:10):
@René Spronk thanks for the info - after wading through the V2.4 spec then I see that now. That's good news as it makes it easier at our end.
Frank Oemig (May 13 2020 at 07:58):
v2 is designed to communicate the newest information. Therefore, all events update the status quo of the patient.
Frank Oemig (May 13 2020 at 08:01):
But we do have the same problem. There is a history flag, that indicates an update of old data. But one cannot assume a correct interpretation of events if this flag is ignored. Consequently, one can only update old data by using new events. IIHE ITI has done that within the PAM profile. This new event is called Z99. You will find usage of it in the German National Extension (Vol.4).
Frank Oemig (May 13 2020 at 08:02):
(In Germany we have tried to make use of this flag on normal messages, but this is not safe and will certainly lead to modifying the latest data which is not the intend and falsifying the wrong data.)
Last updated: Apr 12 2022 at 19:14 UTC
