Conformance-sdc-de-curator.xml

SDC Data Elements author/maintenance system (id = "sdc-de-curator")

Raw XML

<Conformance xmlns="http://hl7.org/fhir">
  <id value="sdc-de-curator"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <name value="SDC Data Element Curator"/>
  <publisher value="U.S. Office of the National Coordinator (ONC)"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://wiki.siframework.org/Structured+Data+Capture+Initiative"/>
    </telecom>
  </contact>
  <description value="This profile defines the expected capabilities of the ''SDC Data Element Curator'' role
   when conforming to the S&amp;I Framework's [[sdc|Structured Data Capture FHIR Data Element
   Exchange implementation guide]].  This role is responsible for defining and updating data
   elements stored in a repository."/>
  <status value="draft"/>
  <date value="2014-07-06"/>
  <fhirVersion value="0.2"/>
  <acceptUnknown value="false"/>
  <format value="xml"/>
  <format value="json"/>
  <rest>
    <mode value="server"/>
    <documentation value="The primary focus of the curator is the definition and maintenance of [[DataElement]]s.
      However, [[ValueSet]]s must also be supported to allow definition of coded data elements.
      Some data elements will choose to maintain value sets as 'contained' resources, meaning
     the value set exists only in the context of the data element and cannot be referenced
     or maintained without also updating the data element.  However, systems should support
     value set re-use across data elements.  (Version-specific referencing can be used to avoid
     value sets from changing independent of the referencing [[Questionnaire]].)"/>
    <security>
      <description value="Implementations must meet the general security requirements documented in the [[sdc-security|SDC
       implementation guide]]."/>
    </security>
    <resource>
      <type value="DataElement"/>
      <profile>
        <reference value="http://hl7.org/fhir/Profile/dataelement-sdc-de"/>
      </profile>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows a user to search for existing data elements"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific known data element"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a specific version of a data element"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to a data element over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="create"/>
        <documentation value="Allows defining a new data element.  Repositories requiring curation of submitted data
         elements may require all new data elements to have a status of 'draft'."/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="update"/>
        <documentation value="Allows maintaining data elements, such as adding additional mappings, display names, etc.
          Servers may choose to prohibit certain types of edits, instead requiring the creation
         of a new data element (and potentially the retiring of the existing data element).  Servers
         may also limit who can change particular data elements."/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="validate"/>
        <documentation value="Allows a client to verify whether a particular new data element or revision of an existing
         data element would be accepted based on validation and other business rules.  Useful for
         some workflows"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="delete"/>
        <documentation value="Allows removal of an existing data element.  Servers may choose to not support deletions
         or may limit deletions to data elements meeting certain requirements.  E.g. only elements
         with a status of draft or only elements that have been retired for at least two years,
         etc."/>
      </interaction>
    </resource>
    <resource>
      <type value="ValueSet"/>
      <profile>
        <reference value="http://hl7.org/fhir/Profile/valueset-sdc-de"/>
      </profile>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing value sets for use in authoring data elements"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific value set referenced within a data element"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a value set as referenced within a data element"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to a value set over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="create"/>
        <documentation value="Allows definition of a new value set used by one or more data elements"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="update"/>
        <documentation value="Allows existing value sets referenced by one or more data elements to be maintained"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="validate"/>
        <documentation value="Allows verification that a value set is valid prior to submission - useful for some workflows."/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/ExtensionDefinition/conformance-common-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="delete"/>
        <documentation value="Not all servers will support deletion of value sets.  Status change to 'retired' will
         be more typical, though deletion of draft value sets may keep repositories cleaner."/>
      </interaction>
    </resource>
  </rest>
</Conformance>