FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

12.2 Resource Transport - Content

Orders and Observations icon Work GroupMaturity Level: 1 Trial UseSecurity Category: Patient Compartments: No defined compartments

Record of transport of item.

12.2.1 Scope and Usage

This resource is an event resource from a FHIR workflow perspective - see Workflow. It is the intent of the Orders and Observation Workgroup to align this resource with the workflow pattern for event resources.

The Transport resource captures the requested movement and movement history of persons and items in the healthcare spectrum. The Transport resource documents the movement of a person or item. Since it follows the event pattern, it can be used in the request of a transport event, but it can be used in conjunction with the Task resource to operationalize a movement event in a workflow. While the current use cases are focused on the lab and the movement of patients, this resource will be easily extensible to handle the movement of anything in healthcare. Sample use cases for the laboratory are as follows:

  • Movement of a specimen between distinct healthcare locations (clinic to lab, lab to lab, lab to biorepository) without the use of a third-party transport system (e.g. a courier)
  • Movement of a specimen between distinct healthcare locations (clinic to lab, lab to lab, lab to biorepository) with the use of a third-party transport system (e.g. a courier)
  • Accessing the current location (tracking) and the complete location history (audit) for a given specimen.
Sample use cases involving patients include
  • Movement of a patient within a healthcare setting (changing floors of the hospital)
  • Movement of a patient between healthcare settings (moving a patient from one hospital to another)

12.2.2 Background and Context

With the emergence of IHE profiles on the movement of laboratory specimens (SET icon) and the growing needs around the movement of patients (documentation, scheduling, real-time updates), there is a need to capture the data around the movement of a patient or item in the healthcare setting. While the Task resource captures some of the data generated around an event, the Transport resource is built to capture the documentation along with the request/fulfillment of a transport event.

12.2.3 Boundaries and Relationships

The Transport resource can be requested by a ServiceRequest or by a Task, as shown in the diagram below. Also, this resource is only for the documentation of the physical movement of material items (people, animals, things). To operationalize the movement of people and things, Task should be used. Provenance can be used to document the steps but that is for the resource aspect, not the actual movement history of the item. During the movement of a patient, the business status (change in the level of care/patient class) might change. To allow for the capture of the current business status of the patient, the reason element should be used.

Diagram showing Transport resource event flow

12.2.4 References to this Resource

  • Resource References: itself

12.2.5 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Transport TU DomainResource Delivery of item

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier 0..* Identifier External identifier

... instantiates Σ 0..1 canonical(ActivityDefinition) Formal definition of transport
... basedOn Σ 0..* Reference(Task | ServiceRequest | DeviceRequest | MedicationRequest | RequestOrchestration | SupplyRequest | VisionPrescription) Request fulfilled by this transport

... groupIdentifier Σ 0..1 Identifier Requisition or grouper id
... partOf Σ 0..* Reference(Transport) Part of referenced event

... status ?!Σ 0..1 code preparation | in-progress | not-done | suspended | stopped | on-hold | completed | entered-in-error | unknown
Binding: Transport Status (Required)
... statusReason Σ 0..1 CodeableConcept Reason for current status
Binding: Transport Status Reason (Example)
... code Σ 0..1 CodeableConcept Transport Type
Binding: Transport Codes (Example)
... description Σ 0..1 string Human-readable explanation of transport
... focus Σ 0..1 Reference(Any) What transport is acting on
... for Σ 0..1 Reference(Any) Beneficiary of the Transport
... encounter Σ 0..1 Reference(Encounter) Healthcare event during which this transport originated
... completionTime Σ 0..1 dateTime Completion time of the event (the occurrence)
... authoredOn 0..1 dateTime Transport Creation Date
... lastModified Σ 0..1 dateTime Transport Last Modified Date
... requester Σ 0..1 Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) Who is asking for transport to be done
... performerType 0..* CodeableConcept Requested performer
Binding: Procedure Performer Role Codes (Preferred)

... owner Σ 0..1 Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Responsible individual
... location Σ 0..1 Reference(Location) Where transport occurs
... insurance 0..* Reference(Coverage | ClaimResponse) Associated insurance coverage

... note 0..* Annotation Comments made about the transport

... relevantHistory 0..* Reference(Provenance) Key events in history of the Transport

... restriction 0..1 BackboneElement Constraints on fulfillment transports
.... repetitions 0..1 positiveInt How many times to repeat
.... period 0..1 Period When fulfillment sought
.... recipient 0..* Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) For whom is fulfillment sought?

... input 0..* BackboneElement Information used to perform transport

.... type 1..1 CodeableConcept Label for the input
Binding: TransportInputParameterType (Example)
.... value[x] 1..1 * Content to use in performing the transport
... output 0..* BackboneElement Information produced as part of transport

.... type 1..1 CodeableConcept Label for output
Binding: TransportOutputParameterType (Example)
.... value[x] 1..1 * Result of output
... requestedLocation Σ 1..1 Reference(Location) The desired location
... currentLocation Σ 1..1 Reference(Location) The entity current location
... reason 0..1 CodeableReference(Any) Why transport is needed
Binding: TransportReason (Example)
... history 0..1 Reference(Transport) Parent (or preceding) transport

doco Documentation for this format icon

See the Extensions for this resource

 

Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis

12.2.5.1 Terminology Bindings

Path ValueSet Type Documentation
Transport.status TransportStatus Required

Status of the transport
Transport.statusReason TransportStatusReason (a valid code from Transport Status) Example

Status reason of the transport.
Transport.code TransportCode (a valid code from Transport Codes) Example

Codes indicating the type of action that is expected to be performed
Transport.performerType ProcedurePerformerRoleCodes Preferred

This example value set defines the set of codes that can be used to indicate a role of a procedure performer.
Transport.input.type Example
Transport.output.type Example
Transport.reason Example

12.2.6 Search Parameters

Search parameters for this resource. See also the full list of search parameters for this resource, and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
identifier token External identifier Transport.identifier
status token in-progress | completed | entered-in-error Transport.status