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-submit-data-update-type-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 4 | Responsible: Clinical Quality Information | Computable Name: R5SubmitDataUpdateTypeForR4 | |
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/submit-data-update-type|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/submit-data-update-type|5.0.0 as defined in FHIR R5
in FHIR R4.
The source value set is bound to the following FHIR R5 elements:
MeasureReport.dataUpdateTypeNote 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/submit-data-update-type|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4
References
http://hl7.org/fhir/CodeSystem/submit-data-update-type version 📍5.0.0| Code | Display | Definition |
| incremental | Incremental | In contrast to the Snapshot Update, the FHIR Parameters resource used in a Submit Data or the Collect Data scenario contains only the new and updated DEQM and QI Core Profiles since the last transaction. If the Consumer supports incremental updates, the contents of the updated payload updates the previous payload data. |
| snapshot | Snapshot | In contrast to the Incremental Update, the FHIR Parameters resource used in a Submit Data or the Collect Data scenario contains all the DEQM and QI Core Profiles for each transaction. If the Consumer supports snapshot updates, the contents of the updated payload entirely replaces the previous payload |
This value set expansion contains 2 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/CodeSystem/submit-data-update-type | 5.0.0 | incremental | Incremental | In contrast to the Snapshot Update, the FHIR Parameters resource used in a Submit Data or the Collect Data scenario contains only the new and updated DEQM and QI Core Profiles since the last transaction. If the Consumer supports incremental updates, the contents of the updated payload updates the previous payload data. | ||
http://hl7.org/fhir/CodeSystem/submit-data-update-type | 5.0.0 | snapshot | Snapshot | In contrast to the Incremental Update, the FHIR Parameters resource used in a Submit Data or the Collect Data scenario contains all the DEQM and QI Core Profiles for each transaction. If the Consumer supports snapshot updates, the contents of the updated payload entirely replaces the previous payload |
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 |