Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Conformance-base2.xml

Raw XML (canonical form)

Basic Conformance Statement

<Conformance xmlns="http://hl7.org/fhir">
  <id value="base2"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>Base FHIR Conformance Statement (Empty)</h2>
      <p>This is the base conformance statement for FHIR. It represents a server that provides
         the none of the functionality defined by FHIR. It is provided to use as a template for
         system designers to build their own conformance statements from. A conformance profile
         has to contain something, so this contains a read of a Conformance Statement</p>
      <table>
        <tr>
          <td>Mode</td>
          <td>SERVER</td>
        </tr>
        <tr>
          <td>Description</td>
          <td>An empty conformance statement</td>
        </tr>
        <tr>
          <td>Transaction</td>
          <td/>
        </tr>
        <tr>
          <td>System History</td>
          <td/>
        </tr>
        <tr>
          <td>System Search</td>
          <td/>
        </tr>
      </table>
      <table>
        <tr>
          <th>
            <b>Resource Type</b>
          </th>
          <th>
            <b>Profile</b>
          </th>
          <th>
            <b>Read</b>
          </th>
          <th>
            <b>V-Read</b>
          </th>
          <th>
            <b>Search</b>
          </th>
          <th>
            <b>Update</b>
          </th>
          <th>
            <b>Updates</b>
          </th>
          <th>
            <b>Create</b>
          </th>
          <th>
            <b>Delete</b>
          </th>
          <th>
            <b>History</b>
          </th>
        </tr>
        <tr>
          <td>Conformance</td>
          <td>y</td>
          <td/>
          <td/>
          <td/>
          <td/>
          <td/>
          <td/>
          <td/>
        </tr>
      </table>
    </div>
  </text>
  <url value="http://hl7.org/fhir/Conformance/base2"/>
  <version value="1.2.0-7447"/>
  <name value="Base FHIR Conformance Statement (Empty)"/>
  <status value="draft"/>
  <experimental value="true"/>
  <publisher value="FHIR Project Team"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <date value="2015-12-11T17:38:40+11:00"/>
  <description value="This is the base conformance statement for FHIR. It represents a server that provides
   the none of the functionality defined by FHIR. It is provided to use as a template for
   system designers to build their own conformance statements from. A conformance profile
   has to contain something, so this contains a read of a Conformance Statement"/>
  <kind value="capability"/>
  <software>
    <name value="Insert your softwware name here..."/>
  </software>
  <fhirVersion value="1.2.0"/>
  <acceptUnknown value="no"/>
  <format value="xml"/>
  <format value="json"/>
  <rest>
    <mode value="server"/>
    <documentation value="An empty conformance statement"/>
    <security>
      <cors value="true"/>
      <service>
        <coding>
          <system value="http://hl7.org/fhir/restful-security-service"/>
          <code value="SMART-on-FHIR"/>
          <display value="SMART-on-FHIR"/>
        </coding>
        <text value="See http://docs.smarthealthit.org/"/>
      </service>
      <description value="This is the conformance statement to declare that the server supports SMART-on-FHIR. See
       the SMART-on-FHIR docs for the extension that would go with such a server"/>
    </security>
    <resource>
      <type value="Conformance"/>
      <interaction>
        <code value="read"/>
        <documentation value="Read Conformance Resource"/>
      </interaction>
    </resource>
  </rest>
</Conformance>

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.