This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Clinical Quality Information Work Group | Maturity Level: 3 | Trial Use | Use Context: Any |
This is a value set defined at http://www.hl7.org/Special/committees/cqi/index.cfm .
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/submit-data-update-type |
Version: | 4.6.0 |
Name: | SubmitDataUpdateType |
Title: | Submit Data Update Type |
Definition: | Concepts for how a measure report consumer and receiver coordinate data exchange updates. The choices are snapshot or incremental updates |
Committee: | Clinical Quality Information Work Group |
OID: | 2.16.840.1.113883.4.642.3.0 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/CodeSystem/submit-data-update-type
This expansion generated 15 Apr 2021
This value set contains 2 concepts
Expansion based on Submit Data Update Type v4.6.0 (CodeSystem)
All codes from system http://hl7.org/fhir/CodeSystem/submit-data-update-type
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 |
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 |