This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v4.0.0: STU4 (v4.0.0)) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/davinci-deqm/ValueSet/update-type | Version: 4.0.0 | |||
Active as of 2020-08-15 | Computable Name: DEQMUpdateTypeValueSet |
Concepts for how a DEQM Consumer supports data exchange updates. The choices are snapshot or incremental updates
References
http://hl7.org/fhir/us/davinci-deqm/CodeSystem/update-type
This value set contains 2 concepts
Expansion based on codesystem DEQM Update Type Code System v4.0.0 (CodeSystem)
Code | System | Display | Definition |
incremental | http://hl7.org/fhir/us/davinci-deqm/CodeSystem/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/us/davinci-deqm/CodeSystem/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 |
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 |