Message ADT_A06 to Bundle Map

Processing of the MSH segment results in the creation of a new MessageHeader resource.

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 Provenance resource instance to the relevant FHIR resources generated.

If there is a source in MSH-4, or known based on the configuration.

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.

If the software does represent not the original source system

If the software represents the original source system

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.

Processing of the PID segment results in the creation of a new Patient resource

One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date.

Incorporate PD1 content into the Patient created from the PID segment.

When the ROL includes entries with roles in Table HL70443 other than "PP", then they may be candidates for CareTeam, but not all. That is implementation specific.

It will be left to implementation negotiation to determine whether disparate systems merely change the patient class, or close and open a new account. The current active account number should appear in field PID-18 - Patient Account Number; the prior account number can be included optionally in MRG-3 - Prior Patient Account Number. Depending on the relationship between the old and new account, the implementer should consider whether Account.partOf should be used as well to link the two accounts appropriately.\

Typically, each NK1 will be translated to either a new RelatedPerson resource or added as a new occurrence of Patient.contact, but it's possible to insert the NK1 data into both structures.

Processing of the PV1 segment results in the creation of a new Encounter resource. Note also that per A06 and A07 trigger event definitions PV1-19 - Visit Number may also be changed during this event.

Incorporate PV2 content into the Encounter created from the PV1 segment.

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].

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].

Processing of the AL1 segment results in the creation of a new AllergyIntolerance resource

Processing of the DG1 segment results in the creation of a new Condition resource

If in context of the patient

If in context of an encounter

If in context of a episode of care

Processing of the IN1 segment results in the creation of a new Coverage resource

Incorporate IN3 content into the Coverage created from the IN1 segment.