FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-definition-resource-types-for-R4 | Version: 0.0.1-snapshot-2 | |||
Standards status: Informative | Maturity Level: 5 | Computable Name: R5_definition_resource_types_for_R4 |
This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/definition-resource-types | 5.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/fhir-types
version 5.0.0
Code | Display | Definition |
ChargeItemDefinition | ChargeItemDefinition | The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. |
ClinicalUseDefinition | ClinicalUseDefinition | A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure. |
EventDefinition | EventDefinition | The EventDefinition resource provides a reusable description of when a particular event can occur. |
MessageDefinition | MessageDefinition | Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. |
ObservationDefinition | ObservationDefinition | Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. |
OperationDefinition | OperationDefinition | A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). |
Questionnaire | Questionnaire | A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. |
Requirements | Requirements | The Requirements resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays. |
SubscriptionTopic | SubscriptionTopic | Describes a stream of resource state changes identified by trigger criteria and annotated with labels useful to filter projections from this topic. |
TestPlan | TestPlan | A plan for executing testing on an artifact or specifications |
TestScript | TestScript | A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. |
This value set expansion contains 11 concepts.
Code | System | Display | Definition |
ChargeItemDefinition | http://hl7.org/fhir/fhir-types | ChargeItemDefinition | The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. |
ClinicalUseDefinition | http://hl7.org/fhir/fhir-types | ClinicalUseDefinition | A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure. |
EventDefinition | http://hl7.org/fhir/fhir-types | EventDefinition | The EventDefinition resource provides a reusable description of when a particular event can occur. |
MessageDefinition | http://hl7.org/fhir/fhir-types | MessageDefinition | Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. |
ObservationDefinition | http://hl7.org/fhir/fhir-types | ObservationDefinition | Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. |
OperationDefinition | http://hl7.org/fhir/fhir-types | OperationDefinition | A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). |
Questionnaire | http://hl7.org/fhir/fhir-types | Questionnaire | A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. |
Requirements | http://hl7.org/fhir/fhir-types | Requirements | The Requirements resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays. |
SubscriptionTopic | http://hl7.org/fhir/fhir-types | SubscriptionTopic | Describes a stream of resource state changes identified by trigger criteria and annotated with labels useful to filter projections from this topic. |
TestPlan | http://hl7.org/fhir/fhir-types | TestPlan | A plan for executing testing on an artifact or specifications |
TestScript | http://hl7.org/fhir/fhir-types | TestScript | A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. |
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 |