The Transport resource represents the movement or transportation of individuals and items (such materials and equipment) within a healthcare setting. It encompasses both planned and completed transport events.

Identifier for the transport event that is used to identify it across multiple disparate systems.

This identifier is typically assigned by the dispenser, and may be used to reference the delivery when exchanging information about it with other systems.

The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Transport.

Enables a formal definition of how the transport is to be performed, enabling automation.

BasedOn refers to a higher-level authorization that triggered the creation of the transport. It references a "request" resource such as a ServiceRequest or Transport, which is distinct from the "request" resource the Transport is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a transport is created to fulfill a procedureRequest ( = FocusOn ) to transport a specimen to the lab.

A larger event of which this particular event is a component or step.

E.g. Drug administration as part of a procedure, procedure as part of observation, etc.

Not to be used to link an event to an Encounter - use Event.context for that.

[The allowed reference resources may be adjusted as appropriate for the event resource].

A code specifying the state of the transport event.

An explanation as to why this transport is held, failed, was refused, etc.

This applies to the current status. Look at the history of the transport to see reasons for past statuses.

A name or code (or both) briefly describing what the transport involves.

The title (eg "My Transports", "Outstanding Transports for Patient X") should go into the code.

A free-text description of what is to be performed.

The resource representing the physical entity being transported.

Used to identify the thing to be done.

If multiple resources need to be manipulated, use sub-transports. (This ensures that status can be tracked independently for each referenced resource.). When the transport is a device for a patient this would be the device.

The entity who benefits from the performance of the service specified in the transport (such as patient or subject).

Used to track transports outstanding for a beneficiary. Do not use to track the transport owner or creator (see owner and creator respectively). This can also affect access control.

When the transport is a device for a patient this would be the Patient.

The healthcare event (e.g. a patient and healthcare provider interaction) during which this transport was created.

For some transports it may be important to know the link between the encounter the transport originated within.

The period when the transport event is occurring or did occur.

The status code allows differentiation of whether the timing reflects an ongoing event or historic one. Ongoing transports should not include an end in the Period.

The date and time this transport was created.

Most often used along with lastUpdated to track duration of the transport to supporting monitoring and management.

The date and time of last modification to this transport.

Used along with history to track transport activity and time in a particular transport state. This enables monitoring and management.

Identifies the entity expected to perform the transport.

Identifies who is expected to perform this transport.

Transports may be created with an owner not yet identified.

Principal physical location where this transport is performed.

Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Transport.

Free-text information captured about the transport as it progresses.

Links to Provenance records for past versions of this Transport that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the transport.

This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.

The target location for the transport event.

The starting location for the transport event.

A resource reference indicating why this transport needs to be performed.

Transports might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in Transport.reasonCode if the data is free (uncoded) text.

The immediately preceding Transport event.