Stream: implementers
Topic: Support for ADT A21 and A22 HL7 events in FHIR
nipun garg (Jun 16 2016 at 12:22):
As far as my understanding goes FHIR should support all ADT triggers events from HL7
We have done ADT mapping for some basic triggers but if we wanted to do mapping for A21 and A22 (LOA and return from LOA) what should be the exclusive fields we should map apart from A01 segments.
I suppose we should map EVN-6 which is patient LOA date time and PV2-47 which is expected patient return date/time.
I am currently using Encounter resource for this mapping.
PV2-47----Encounter.period.end
EVN-6- ---???
Please suggest what element I should use here from FHIR
Simone Heckmann (Jun 16 2016 at 15:48):
Hi. I don't think a LOA ends an encounter. I'd suggest to set the Encounter.status to "onleave" once the patient departs and set it back to "in-progress" wht the patient returns. Additionally the LOA could be tracked in Encounter.statusHistory reflecting the period of absence.
Simone Heckmann (Jun 16 2016 at 15:59):
However: Maintaining Encounter.statusHistory might be a tricky beast if you're updating your resources with ADT messages unless you use some sort of patching on the Encounter instead of update.
nipun garg (Jun 17 2016 at 05:44):
Thanks Simone for the response.
If we are reecieving ADT^A21 for LOA and getting EVN-6 as departure time and PV2-47 as expected arrival time, Can I go ahead and add a condition that if "A21 " set Encounter.status to "On-leave" and Encounter.statusHistory.period.starttime = EVN-6
Similarly when I will receive an A22 I will set the condition as if "A22" then Encounter.status to "in-Progress" and Encounter.statusHistory.period.endtime = PV2-47
Will this things would work fine???
Last updated: Apr 12 2022 at 19:14 UTC
