Message ADT_A17 to Bundle Map
| V2 Segment | Display | FHIR Target | Equivalence |
|---|---|---|---|
ADT_A17.MSH | Message Header | BundleMessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource. Provenance[1]If the FHIR transformation does not yield a FHIR message, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Proviance resource instance to the relevant FHIR resources generated. If there is a source in MSH-4, or known based on the configuration. Provenance[2]If the FHIR transformation does not yield a FHIR Bunlde, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. | equivalentequivalentequivalentequivalent |
ADT_A17.SFT | Software Segment | Provenance[1].entity.what(Device)If the software does represent not the original source system Provenance[1].entity.what(Device)If the software represents the original source system | equivalentequivalent |
ADT_A17.EVN | Event Type | Provenance[3]Provenance[3]If EVN-5 is not valued, then the MSH may have either the sending responsible organization (MSH-22) or the sending facility (MSH-4) to reasonable approximate the agent relevant for this Provenance instance. | equivalentequivalent |
ADT_A17.PID | Patient Identification | Patient[1]Processing of the PID segment results in the creation of a new Patient resource Account[1]Provenance[4]One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date. Patient[2]Processing of the PID segment results in the creation of a new Patient resource Account[2]Provenance[5]One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date. | equivalentequivalentequivalentequivalentequivalentequivalent |
ADT_A17.PD1 | Additional Demographics | Patient[1]Incorporate PD1 content into the Patient created from the PID segment. Patient[2]Incorporate PD1 content into the Patient created from the PID segment. | equivalentequivalent |
ADT_A01.PD1 | Additional Demographics | Observation[3] | equivalent |
ADT_A17.PV1 | Patient Visit | Encounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource Patient[1]Encounter[2]Processing of the PV1 segment results in the creation of a new Encounter resource BasicPatient[1]Coverage[1] | equivalentequivalentequivalentequivalentequivalentequivalent |
ADT_A17.PV2 | Patient Visit - Additional Info. | Encounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment. Encounter[2]Incorporate PV2 content into the Encounter created from the PV1 segment. | equivalentequivalent |
ADT_A17.OBSERVATION.OBX | Observation/Result | Observation[1]One cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1]. Observation[1]One cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1]. Observation[2]One cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1]. Based on profiles, such as Vital Signs, certain observations are represented on the Observation, while others on its components. No computable guidance available yet. Observation[2]One cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1]. Based on profiles, such as Vital Signs, certain observations are represented on the Observation, while others on its components. No computable guidance available yet. | equivalentequivalentequivalentequivalent |