This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Example CodeSystem/submit-data-update-type (XML)
Raw XML (canonical form + also see XML Format Specification)
Definition for Code SystemSubmitDataUpdateType
<?xml version="1.0" encoding="UTF-8"?>
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="submit-data-update-type"/>
<meta>
<lastUpdated value="2024-11-15T18:37:49.495+00:00"/>
<profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
</meta>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<p class="res-header-id">
<b> Generated Narrative: CodeSystem submit-data-update-type</b>
</p>
<a name="submit-data-update-type"> </a>
<a name="hcsubmit-data-update-type"> </a>
<a name="submit-data-update-type-en-US"> </a>
<p> This case-sensitive code system
<code> http://hl7.org/fhir/CodeSystem/submit-data-update-type</code> defines the following codes:
</p>
<table class="codes">
<tr>
<td style="white-space:nowrap">
<b> Code</b>
</td>
<td>
<b> Display</b>
</td>
<td>
<b> Definition</b>
</td>
</tr>
<tr>
<td style="white-space:nowrap">incremental
<a name="submit-data-update-type-incremental"> </a>
</td>
<td> Incremental</td>
<td> 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.</td>
</tr>
<tr>
<td style="white-space:nowrap">snapshot
<a name="submit-data-update-type-snapshot"> </a>
</td>
<td> Snapshot</td>
<td> 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</td>
</tr>
</table>
</div>
</text>
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="cqi"/>
</extension>
<url value="http://hl7.org/fhir/CodeSystem/submit-data-update-type"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.4.1948"/>
</identifier>
<version value="6.0.0-ballot2"/>
<name value="SubmitDataUpdateType"/>
<title value="Submit Data Update Type"/>
<status value="active"/>
<experimental value="true"/>
<date value="2021-04-06T19:00:36+00:00"/>
<publisher value="HL7 International - Clinical Quality Information Work Group"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/cqi/index.cfm"/>
</telecom>
</contact>
<description value="Concepts for how a measure report consumer and receiver coordinate data exchange
updates. The choices are snapshot or incremental updates"/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<caseSensitive value="true"/>
<valueSet value="http://hl7.org/fhir/ValueSet/submit-data-update-type"/>
<content value="complete"/>
<count value="2"/>
<concept>
<code value="incremental"/>
<display value="Incremental"/>
<definition value="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."/>
</concept>
<concept>
<code value="snapshot"/>
<display value="Snapshot"/>
<definition value="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"/>
</concept>
</CodeSystem>
Usage note: every effort has been made to ensure that the
examples are correct and useful, but they are not a normative part
of the specification.