Stream: v2 to FHIR
Topic: (no topic)
Kevin Mayfield (Aug 02 2017 at 18:28):
thanks, that makes sense.
Jayashree Surnar (Aug 30 2017 at 10:40):
hello,
- ADT A02: (Transfer a patient)
contains 12 segments
MSH - Message Header
SFT - Software Segment
EVN - Event Type
PID - Patient Identification
PD1 - Patient Additional Demographic
ROL - Role
PV1 - Patient Visit
PV2 - Patient Visit - Additional Information
ROL - Role
DB1 - Disability
OBX - Observation/Result
PDA - Patient Death and Autopsy
like that in fhir what are the resources we need to transfer a patient?
Tom Pick (Sep 01 2017 at 08:43):
Hello all. I'm trying to map some V2 appointment data into FHIR model, and I'm confused by the difference between reason and type. I need to find a home for both SCH-7 and SCH-8 data. The FHIR Appointment resource description seems to me to suggest SCH-7 should go in appointmentType, but the mappings show it allocated to reason. In addition, there is no mapping at all for SCH-8, and whilst AIS-3 also maps to reason, ARQ-7 (which I thought was similar) maps to appointmentType. Is there any standard guidance for this? Any help much appreciated!
Grahame Grieve (Sep 01 2017 at 18:54):
@Brian Postlethwaite
Eric Haas (Sep 02 2017 at 02:30):
After reviewing V210.2.3.3 and 10.2.3.4 in version 2.8.2 I can see cause for confusion, because in IMO the listed examples for reasons are in fact appointment types ...
-
SCH-7 Appointment Reason also uses 0276 which based on the description seems inappropriate as it is the 'Reason codes to describe the reason that the service is occurring or the resource is being used' and I think is more aligned with concepts like 'suture out' or 'recheck ear'
-
SCH -8 Appointment Type uses 0277 which seems to overlap with 0276 - it describes the kind of appointment for administrative reason. ( and I think of these as new patient, recheck, discharge, walk in, emergency) andin V2 it suggested values in table 0277 which seems to overlap with 0276 this element is aligned with the AppointmentType element which uses table 0276.
in Summary:
- .appointmentType --> SCH-8 and ARQ-8
- .reason --> SCH-7 and ARQ-7
So I think the existing FHIR --> V2 mappings are incorrect and moreover the definitions in V2 do not align with the codes which can be misleading. Having said that in the real world these fields may be conflated into one. (new patient/check ear)
Tom Pick (Sep 07 2017 at 07:19):
Thanks so much for your helpful reply @Eric Haas (and sorry for the lateness of mine). If I've understood you correctly, you're suggesting mapping v2 type to FHIR type, and v2 reason to FHIR reason, which is definitely appealing for its simplicity. As such, I think I'll go with that. I do think these fields are used flexibly in the real world, but I have to pick something I suppose! I'm new to how these things work - is there anything I can do to help get this corrected in the docs? Is there some process that requires that to go to wider discussion? Please let me know if you'd like me to raise this elsewhere.
Eric Haas (Sep 07 2017 at 18:16):
You can create a tracker for the responsible group to update the mappings. just click on the link 'Propose a Change' at the bottom of the page in the spec to raise an issue.
Tom Pick (Sep 08 2017 at 07:30):
Ah top tip! Thanks.
Prince Melvin (Sep 06 2018 at 05:57):
Hi,
I am new to FHIR. Can you tell me what are the resources in FHIR is needed for ADT A04 message?
Simone Heckmann (Sep 06 2018 at 09:03):
What are you trying to accomplish? Create a ADT A04 message from FHIR data or vice versa? What is the ultimate goal? Is it enough to create the outpatient Encounter or are you aiming to transfer the complete (potential) content of an ADT_A04 message (including coverage, diagnosis and whatnot)?
Brendan Keeler (May 05 2019 at 14:17):
We have Montreal bagels at table 21 for those interested in trying the local cuisine. Denser and sweeter than New York bagels, some say you don't even need cream cheese (but we have that too)
Brendan Keeler (May 05 2019 at 14:17):
First come first serve
Last updated: Apr 12 2022 at 19:14 UTC
