This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Clinical Quality Information Work Group | Maturity Level: 4 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/submit-data-update-type
|
Version: 6.0.0-ballot2 | |||
active as of 2021-04-06 | Computable Name: SubmitDataUpdateType | |||
Flags: | OID: 2.16.840.1.113883.4.642.3.3055 |
This value set is used in the following places:
Concepts for how a measure report consumer and receiver coordinate data exchange updates. The choices are snapshot or incremental updates
Generated Narrative: ValueSet submit-data-update-type
Last updated: 2024-11-04T22:22:12.906Z
Profile: Shareable ValueSet
http://hl7.org/fhir/CodeSystem/submit-data-update-type
This expansion generated 04 Nov 2024
Generated Narrative: ValueSet
Last updated: 2024-11-04T22:22:12.906Z
Profile: Shareable ValueSet
Expansion based on codesystem Submit Data Update Type v6.0.0-ballot2 (CodeSystem)
This value set contains 2 concepts
Code | System | Display | Definition |
incremental | http://hl7.org/fhir/CodeSystem/submit-data-update-type | 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 | http://hl7.org/fhir/CodeSystem/submit-data-update-type | 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 |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | 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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |