Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-transport-code-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 1 | Responsible: Orders and Observations | Computable Name: R5TransportCodeForR4 | |
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/transport-code|5.0.0 for use in FHIR R4.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/transport-code|5.0.0 as defined in FHIR R5
in FHIR R4.
The source value set is bound to the following FHIR R5 elements:
Transport.codeNote 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-code|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4
References
http://hl7.org/fhir/CodeSystem/transport-code version 📍5.0.0| Code | Display | Definition |
| abort | Mark the focal resource as no longer active | Abort, cancel or withdraw the focal resource, as appropriate for the type of resource. |
| approve | Activate/approve the focal resource | Take what actions are needed to transition the focus resource from 'draft' to 'active' or 'in-progress', as appropriate for the resource type. This may involve additing additional content, approval, validation, etc. |
| change | Change the focal resource | Update the focal resource of the owning system to reflect the content specified as the Task.focus |
| fulfill | Fulfill the focal request | Act to perform the actions described in the focus request. This might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events. The degree of fulfillment requested might be limited by Task.restriction. |
| instantiate | Instantiate the focal definition | Act to perform the actions defined in the focus definition resource (ActivityDefinition, PlanDefinition, Questionnaire, etc.) For PlanDefinition or ActivityDefinition, this might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events. For Questionnaire, this would result in a QuestionnaireResponse - and possibly resources constructed using data extracted from the response. The degree of fulfillment requested might be limited by Task.restriction. |
| replace | Replace the focal resource with the input resource | Replace the focal resource with the specified input resource |
| resume | Re-activate the focal resource | Transition the focal resource from 'suspended' to 'active' or 'in-progress' as appropriate for the resource type. |
| suspend | Suspend the focal resource | Transition the focal resource from 'active' or 'in-progress' to 'suspended' |
This value set expansion contains 8 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | abort | Mark the focal resource as no longer active | Abort, cancel or withdraw the focal resource, as appropriate for the type of resource. | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | approve | Activate/approve the focal resource | Take what actions are needed to transition the focus resource from 'draft' to 'active' or 'in-progress', as appropriate for the resource type. This may involve additing additional content, approval, validation, etc. | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | change | Change the focal resource | Update the focal resource of the owning system to reflect the content specified as the Task.focus | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | fulfill | Fulfill the focal request | Act to perform the actions described in the focus request. This might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events. The degree of fulfillment requested might be limited by Task.restriction. | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | instantiate | Instantiate the focal definition | Act to perform the actions defined in the focus definition resource (ActivityDefinition, PlanDefinition, Questionnaire, etc.) For PlanDefinition or ActivityDefinition, this might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events. For Questionnaire, this would result in a QuestionnaireResponse - and possibly resources constructed using data extracted from the response. The degree of fulfillment requested might be limited by Task.restriction. | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | replace | Replace the focal resource with the input resource | Replace the focal resource with the specified input resource | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | resume | Re-activate the focal resource | Transition the focal resource from 'suspended' to 'active' or 'in-progress' as appropriate for the resource type. | ||
http://hl7.org/fhir/CodeSystem/transport-code | 5.0.0 | suspend | Suspend the focal resource | Transition the focal resource from 'active' or 'in-progress' to 'suspended' |
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 |