Stream: implementers
Topic: resources required to transfer a patient
Jayashree Surnar (Aug 30 2017 at 10:43):
what are the resources we need to transfer a patient?
for example in hl7 v2 ADT-A02 has 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
Lloyd McKenzie (Aug 30 2017 at 15:26):
MSH = MessageHeader
SFT = MessageHeader and Device
EVN = MessageHeader
PID, PD1 = Patient
ROL = Practitioner
PV1, PV2 = Encounter (and maybe Account)
DB1 = Condition (or possibly Patient)
OBX = Observation
PDA = Observation and/or DiagnosticReport
Lloyd McKenzie (Aug 30 2017 at 15:26):
Note that you can find v2 mappings for each resource, though we don't have a reverse mapping from v2 to FHIR.
Jayashree Surnar (Aug 31 2017 at 11:57):
thank you @Lloyd McKenzie , in fhir under every resource given fhir to v2 and other mappings. but i didn't fined any message level mappings.for example in v2 there is a message ADT_A02 and has the related segments. but in fhir i didn't fined how many resources are required for a perticular message event.
is there any doc for this?
Lloyd McKenzie (Aug 31 2017 at 14:17):
We have not attempted to map v2 messages to FHIR. FHIR introduces REST and Services, which means there's a whole lot of other ways to get things done than in v2. So something like "update patient demographics" can be handled with a simple RESTful update to Patient. So many of the v2 messages are no longer necessary in a FHIR space. Thus far, those who are implementing FHIR messaging have been content to go off and define their own messages specific to their particular implementation space. That said, if the implementation community wants to start engaging and defining "standard" FHIR messages - whether based on v2 or not - that's certainly possible and something HL7 would support.
Last updated: Apr 12 2022 at 19:14 UTC
