R6 Ballot (2nd Draft)

Publish-box (todo)

Example CodeSystem/submit-data-update-type (JSON)

Clinical Quality Information Work GroupMaturity Level: N/AStandards Status: Informative

Raw JSON (canonical form + also see JSON Format Specification)

Definition for Code SystemSubmitDataUpdateType

{
  "resourceType" : "CodeSystem",
  "id" : "submit-data-update-type",
  "meta" : {
    "lastUpdated" : "2024-08-12T16:52:12.437+08:00",
    "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablecodesystem"]
  },
  "text" : {
    "status" : "generated",
    "div" : "<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-AU\"> </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>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "cqi"
  }],
  "url" : "http://hl7.org/fhir/CodeSystem/submit-data-update-type",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.4.1948"
  }],
  "version" : "6.0.0-ballot2",
  "name" : "SubmitDataUpdateType",
  "title" : "Submit Data Update Type",
  "status" : "active",
  "experimental" : true,
  "date" : "2021-04-06T19:00:36+00:00",
  "publisher" : "HL7 International - Clinical Quality Information Work Group",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://www.hl7.org/Special/committees/cqi/index.cfm"
    }]
  }],
  "description" : "Concepts for how a measure report consumer and receiver coordinate data exchange updates. The choices are snapshot or incremental updates",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001",
      "display" : "World"
    }]
  }],
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/submit-data-update-type",
  "content" : "complete",
  "count" : 2,
  "concept" : [{
    "code" : "incremental",
    "display" : "Incremental",
    "definition" : "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."
  },
  {
    "code" : "snapshot",
    "display" : "Snapshot",
    "definition" : "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"
  }]
}

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.