Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-transport-intent-for-R3 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 2 | Responsible: Orders and Observations | Computable Name: R5TransportIntentForR3 | |
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/transport-intent|5.0.0 for use in FHIR STU3.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/transport-intent|5.0.0 as defined in FHIR R5
in FHIR STU3.
The source value set is bound to the following FHIR R5 elements:
Transport.intentNote that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://hl7.org/fhir/ValueSet/transport-intent|5.0.0, defined in FHIR R5 does not have any mapping to FHIR STU3
References
This value set includes codes based on the following rules:
http://hl7.org/fhir/request-intent version 📍5.0.0| Code | Display | Definition |
| filler-order | Filler Order | The request represents the view of an authorization instantiated by a fulfilling system representing the details of the fulfiller's intention to act upon a submitted order. |
| instance-order | Instance Order | An order created in fulfillment of a broader order that represents the authorization for a single activity occurrence. E.g. The administration of a single dose of a drug. |
| option | Option | The request represents a component or option for a RequestOrchestration that establishes timing, conditionality and/or other constraints among a set of requests. Refer to [RequestOrchestration](https://hl7.org/fhir/R5/RequestOrchestration.html) for additional information on how this status is used. |
| order | Order | The request represents a request/demand and authorization for action by the requestor. |
| original-order | Original Order | The request represents an original authorization for action. |
| plan | Plan | The request represents an intention to ensure something occurs without providing an authorization for others to act. |
| proposal | Proposal | The request is a suggestion made by someone/something that does not have an intention to ensure it occurs and without providing an authorization to act. |
| reflex-order | Reflex Order | The request represents an automatically generated supplemental authorization for action based on a parent authorization together with initial results of the action taken against that parent authorization. |
http://hl7.org/fhir/transport-intent version 📍5.0.0
| Code | Display | Definition |
| unknown | Unknown | The intent is not known. When dealing with Transport, it's not always known (or relevant) how the transport was initiated - i.e. whether it was proposed, planned, ordered or just done spontaneously. |
This value set expansion contains 9 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/request-intent | 5.0.0 | filler-order | Filler Order | The request represents the view of an authorization instantiated by a fulfilling system representing the details of the fulfiller's intention to act upon a submitted order. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | instance-order | Instance Order | An order created in fulfillment of a broader order that represents the authorization for a single activity occurrence. E.g. The administration of a single dose of a drug. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | option | Option | The request represents a component or option for a RequestOrchestration that establishes timing, conditionality and/or other constraints among a set of requests. Refer to RequestOrchestration for additional information on how this status is used. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | order | Order | The request represents a request/demand and authorization for action by the requestor. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | original-order | Original Order | The request represents an original authorization for action. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | plan | Plan | The request represents an intention to ensure something occurs without providing an authorization for others to act. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | proposal | Proposal | The request is a suggestion made by someone/something that does not have an intention to ensure it occurs and without providing an authorization to act. | ||
http://hl7.org/fhir/request-intent | 5.0.0 | reflex-order | Reflex Order | The request represents an automatically generated supplemental authorization for action based on a parent authorization together with initial results of the action taken against that parent authorization. | ||
http://hl7.org/fhir/transport-intent | 5.0.0 | unknown | Unknown | The intent is not known. When dealing with Transport, it's not always known (or relevant) how the transport was initiated - i.e. whether it was proposed, planned, ordered or just done spontaneously. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |