Generated Narrative: StructureDefinition profile-Transport Name Flags Card. Type Description & Constraints Basic 0..* Basic Resource for non-supported content #xD; Slices for extension 3..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:instantiatesCanonical 0..1 uri R5: Formal definition of transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.instantiatesCanonical #xD; extension:instantiatesUri 0..1 uri R5: Formal definition of transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.instantiatesUri #xD; extension:basedOn 0..* Reference(Cross-version Profile for R5.Resource for use in FHIR STU3(0.1.0) | Resource) R5: Request fulfilled by this transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.basedOn #xD; extension:groupIdentifier 0..1 Identifier R5: Requisition or grouper id (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.groupIdentifier #xD; extension:partOf 0..* Reference(Cross-version Profile for R5.Transport for use in FHIR STU3(0.1.0) | Basic) R5: Part of referenced event (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.partOf #xD; extension:statusReason 0..1 CodeableConcept R5: Reason for current status (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.statusReason Binding: R5TransportStatusReasonForR3 (0.1.0) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. #xD; extension:intent 1..1 code R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.intent Binding: R5TransportIntentForR3 (0.1.0) (required): Distinguishes whether the transport is a proposal, plan or full order. #xD; extension:priority 0..1 code R5: routine | urgent | asap | stat (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.priority Binding: MedicationRequestPriority (required): The priority of a transport (may affect service level applied to the transport). #xD; extension:code 0..1 CodeableConcept R5: Transport Type (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.code Binding: R5TransportCodeForR3 (0.1.0) (example): Codes to identify what the transport involves. These will typically be specific to a particular workflow. #xD; extension:description 0..1 string R5: Human-readable explanation of transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.description #xD; extension:focus 0..1 Reference(Cross-version Profile for R5.Resource for use in FHIR STU3(0.1.0) | Resource) R5: What transport is acting on (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.focus #xD; extension:for 0..1 Reference(Cross-version Profile for R5.Resource for use in FHIR STU3(0.1.0) | Resource) R5: Beneficiary of the Transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.for #xD; extension:encounter 0..1 Reference(Cross-version Profile for R5.Encounter for use in FHIR STU3(0.1.0) | Encounter) R5: Healthcare event during which this transport originated (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.encounter #xD; extension:completionTime 0..1 dateTime R5: Completion time of the event (the occurrence) (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.completionTime #xD; extension:authoredOn 0..1 dateTime R5: Transport Creation Date (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.authoredOn #xD; extension:lastModified 0..1 dateTime R5: Transport Last Modified Date (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.lastModified #xD; extension:requester 0..1 Reference(Cross-version Profile for R5.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R5.Organization for use in FHIR STU3(0.1.0) | Organization | Cross-version Profile for R5.Patient for use in FHIR STU3(0.1.0) | Patient | Cross-version Profile for R5.Practitioner for use in FHIR STU3(0.1.0) | Practitioner | Cross-version Profile for R5.PractitionerRole for use in FHIR STU3(0.1.0) | PractitionerRole | Cross-version Profile for R5.RelatedPerson for use in FHIR STU3(0.1.0) | RelatedPerson) R5: Who is asking for transport to be done (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.requester #xD; extension:performerType 0..* CodeableConcept R5: Requested performer (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.performerType #xD; extension:owner 0..1 Reference(Cross-version Profile for R5.Practitioner for use in FHIR STU3(0.1.0) | Practitioner | Cross-version Profile for R5.PractitionerRole for use in FHIR STU3(0.1.0) | PractitionerRole | Cross-version Profile for R5.Organization for use in FHIR STU3(0.1.0) | Organization | Cross-version Profile for R5.CareTeam for use in FHIR STU3(0.1.0) | CareTeam | Cross-version Profile for R5.HealthcareService for use in FHIR STU3(0.1.0) | HealthcareService | Cross-version Profile for R5.Patient for use in FHIR STU3(0.1.0) | Patient | Cross-version Profile for R5.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R5.RelatedPerson for use in FHIR STU3(0.1.0) | RelatedPerson) R5: Responsible individual (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.owner #xD; extension:location 0..1 Reference(Cross-version Profile for R5.Location for use in FHIR STU3(0.1.0) | Location) R5: Where transport occurs (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.location #xD; extension:insurance 0..* Reference(Cross-version Profile for R5.Coverage for use in FHIR STU3(0.1.0) | Coverage | Cross-version Profile for R5.ClaimResponse for use in FHIR STU3(0.1.0) | ClaimResponse) R5: Associated insurance coverage (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.insurance #xD; extension:note 0..* Annotation R5: Comments made about the transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.note #xD; extension:relevantHistory 0..* Reference(Cross-version Profile for R5.Provenance for use in FHIR STU3(0.1.0) | Provenance) R5: Key events in history of the Transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.relevantHistory #xD; extension:restriction 0..1 (Complex) R5: Constraints on fulfillment transports (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.restriction #xD; extension:input 0..* (Complex) R5: Information used to perform transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.input #xD; extension:output 0..* (Complex) R5: Information produced as part of transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.output #xD; extension:requestedLocation 1..1 Reference(Cross-version Profile for R5.Location for use in FHIR STU3(0.1.0) | Location) R5: The desired location (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.requestedLocation #xD; extension:currentLocation 1..1 Reference(Cross-version Profile for R5.Location for use in FHIR STU3(0.1.0) | Location) R5: The entity current location (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.currentLocation #xD; extension:reason 0..1 (Complex) R5: Why transport is needed (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.reason #xD; extension:history 0..1 Reference(Cross-version Profile for R5.Transport for use in FHIR STU3(0.1.0) | Basic) R5: Parent (or preceding) transport (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.history #xD; Slices for modifierExtension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; modifierExtension:status 0..1 code R5: in-progress | completed | abandoned | cancelled | planned | entered-in-error (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.status Binding: R5TransportStatusForR3 (0.1.0) (required): Status of the transport. #xD; Documentation for this format
Cross-version Profile for R5.Transport for use in FHIR STU3
This cross-version profile allows R5 Transport content to be represented via FHIR STU3 Basic resources.
Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
R5: Formal definition of transport (new)
R5: `Transport.instantiatesCanonical` (new:canonical(ActivityDefinition))
Element `Transport.instantiatesCanonical` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.instantiatesCanonical` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
R5: `Transport.instantiatesUri` (new:uri)
Element `Transport.instantiatesUri` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.instantiatesUri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Request fulfilled by this transport (new)
R5: `Transport.basedOn` (new:Reference(Resource))
Element `Transport.basedOn` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.basedOn` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.groupIdentifier` (new:Identifier)
Element `Transport.groupIdentifier` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.groupIdentifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.partOf` (new:Reference(Transport))
Element `Transport.partOf` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.partOf` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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].
R5: `Transport.statusReason` (new:CodeableConcept)
Element `Transport.statusReason` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.statusReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This applies to the current status. Look at the history of the transport to see reasons for past statuses.
R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option (new)
Element `Transport.intent` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.intent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This element is immutable. Proposed transports, planned transports, etc. must be distinct instances. In most cases, Transports will have an intent of "order".
R5: routine | urgent | asap | stat (new)
Element `Transport.priority` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.priority` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.code` (new:CodeableConcept)
Element `Transport.code` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The title (eg "My Transports", "Outstanding Transports for Patient X") should go into the code.
R5: Human-readable explanation of transport (new)
R5: `Transport.description` (new:string)
Element `Transport.description` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.focus` (new:Reference(Resource))
Element `Transport.focus` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.focus` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If multiple resources need to be manipulated, use sub-transports. (This ensures that status can be tracked independently for each referenced resource.).
R5: `Transport.for` (new:Reference(Resource))
Element `Transport.for` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.for` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Healthcare event during which this transport originated (new)
R5: `Transport.encounter` (new:Reference(Encounter))
Element `Transport.encounter` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.encounter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Completion time of the event (the occurrence) (new)
R5: `Transport.completionTime` (new:dateTime)
Element `Transport.completionTime` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.completionTime` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.authoredOn` (new:dateTime)
Element `Transport.authoredOn` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.authoredOn` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.lastModified` (new:dateTime)
Element `Transport.lastModified` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.lastModified` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Who is asking for transport to be done (new)
R5: `Transport.requester` (new:Reference(Device,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))
Element `Transport.requester` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.requester` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.performerType` (new:CodeableConcept)
Element `Transport.performerType` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.performerType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.owner` (new:Reference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson))
Element `Transport.owner` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.owner` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Transports may be created with an owner not yet identified.
R5: `Transport.location` (new:Reference(Location))
Element `Transport.location` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.insurance` (new:Reference(Coverage,ClaimResponse))
Element `Transport.insurance` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.insurance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Comments made about the transport (new)
Element `Transport.note` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Key events in history of the Transport (new)
R5: `Transport.relevantHistory` (new:Reference(Provenance))
Element `Transport.relevantHistory` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.relevantHistory` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.
R5: Constraints on fulfillment transports (new)
R5: `Transport.restriction` (new:BackboneElement)
Element `Transport.restriction` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.restriction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Information used to perform transport (new)
R5: `Transport.input` (new:BackboneElement)
Element `Transport.input` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.input` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Information produced as part of transport (new)
R5: `Transport.output` (new:BackboneElement)
Element `Transport.output` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.output` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.requestedLocation` (new:Reference(Location))
Element `Transport.requestedLocation` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.requestedLocation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.currentLocation` (new:Reference(Location))
Element `Transport.currentLocation` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.currentLocation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: `Transport.reason` (new:CodeableReference(Resource))
Element `Transport.reason` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.reason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.
R5: Parent (or preceding) transport (new)
R5: `Transport.history` (new:Reference(Transport))
Element `Transport.history` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.history` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: in-progress | completed | abandoned | cancelled | planned | entered-in-error (new)
Element `Transport.status` is not mapped to FHIR STU3, since FHIR R5 `Transport` is not mapped. Element `Transport.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Identifier assigned to the resource for business purposes, outside the context of FHIR.
Identifies the 'type' of resource - equivalent to the resource name for other resources.
Because resource references will only be able to indicate 'Basic', the type of reference will need to be specified in a Profile identified as part of the resource. Refer to the resource notes section for information on appropriate terminologies for this code. This element is labeled as a modifier because the it defines the meaning of the resource and cannot be ignored.
Must be able to distinguish different types of Basic resources.
Codes for identifying types of resources not yet defined by FHIR
Identifies the patient, practitioner, device or any other resource that is the "focus" of this resource.
Optional as not all potential resources will have subjects. Resources associated with multiple subjects can handle this via extension.
Needed for partitioning the resource by Patient.
./participation[typeCode='SBJ'] (possibly through a ControlAct and Role)
Identifies when the resource was first created.
Allows ordering resource instances by time.
./participation[typeCode='AUT']/time (possibly through a ControlAct and Role)
Indicates who was responsible for creating the resource instance.
./participation[typeCode='SUB'] (possibly through a ControlAct and Role)