Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-defined-types-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 5 | Computable Name: R3DefinedTypesForR4 | ||
| This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/defined-types | 3.0.2 for use in FHIR R4 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/defined-types|4.0.1. |
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/defined-types|3.0.2 as defined in FHIR STU3
in FHIR R4.
The source value set is bound to the following FHIR STU3 elements:
ElementDefinition.type.codeStructureDefinition.typeTestScript.setup.action.assert.resourceTestScript.setup.action.operation.resourceNote that there are 200 concepts not included in this cross-version definition because they have valid representations.
Following are the generation technical comments: One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. The source value set has fewer active concepts (173) than the target (211), so the source is narrower than the target.
References
http://hl7.org/fhir/resource-types version 📍3.0.2| Code | Display | Definition |
| DataElement | DataElement | The formal description of a single piece of information that can be gathered and reported. |
| ExpansionProfile | ExpansionProfile | Resource to define constraints on the Expansion of a FHIR ValueSet. |
| ProcedureRequest | ProcedureRequest | A record of a request for diagnostic investigations, treatments, or operations to be performed. |
| ProcessRequest | ProcessRequest | This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources. |
| ProcessResponse | ProcessResponse | This resource provides processing status, errors and notes from the processing of a resource. |
| ReferralRequest | ReferralRequest | Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. |
This value set expansion contains 6 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/resource-types | 3.0.2 | DataElement | DataElement | The formal description of a single piece of information that can be gathered and reported. | ||
http://hl7.org/fhir/resource-types | 3.0.2 | ExpansionProfile | ExpansionProfile | Resource to define constraints on the Expansion of a FHIR ValueSet. | ||
http://hl7.org/fhir/resource-types | 3.0.2 | ProcedureRequest | ProcedureRequest | A record of a request for diagnostic investigations, treatments, or operations to be performed. | ||
http://hl7.org/fhir/resource-types | 3.0.2 | ProcessRequest | ProcessRequest | This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources. | ||
http://hl7.org/fhir/resource-types | 3.0.2 | ProcessResponse | ProcessResponse | This resource provides processing status, errors and notes from the processing of a resource. | ||
http://hl7.org/fhir/resource-types | 3.0.2 | ReferralRequest | ReferralRequest | Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. |
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 |