Example of conformance (id = "example")

<Conformance xmlns="http://hl7.org/fhir">
  <date>2012-01-04</date>
  <publisher>
    <name>ACME Corporation</name>
    <contact>
      <system>email</system>
      <value>wile@acme.org</value>
    </contact>
  </publisher>
  <software>
    <name>EHR</name>
    <version>0.00.020.2134</version>
  </software>

  <!--   while the FHIR infrastructure is turning over prior to development, a version is 
    required. Note that this may be rescinded later?   -->
  <version>0.02</version>
  <acceptUnknown>true</acceptUnknown>
  
  <!--   in a real conformance statement, it's unlikely that a single conformance statement 
    would declare conformance for REST, messaging, and documents, though it is legal. 
    This example does so in order to show all the parts of a conformance statement   -->
  <rest>
    <!--   this is a server conformance statement. Note that servers are required to provide 
      one of these. It can easily be edited by hand - copy this, replace the metadata above, 
      delete the messaging and document stuff below, and then replace the details appropriately.   -->
    <mode>server</mode>
    <!--   zero or more of these - declaration of support for a resource   -->
    <resource>
      <type>Person</type>
      <!--   let's assume that HL7 has stood up a profile registry at http://fhir.hl7.org/fhir 
        - it's likely to have a registry, though this is not decided, nor is a URL decided. 
        This application simply uses a profile registered directly with HL7. For the simplest 
        case of a FHIR REST Server, just delete this profile reference. Profile references do 
        not need to be a UUID, though a profile registry could insist that they are   -->
      <profile>http://fhir.hl7.org/base/profile/@7896271d-57f6-4231-89dc-dcc91eab2416</profile>
      <operation>
        <code>read</code>
      </operation>
      <operation>
        <code>vread</code>
      </operation>
      <operation>
        <code>update</code>
      </operation>
      <operation>
        <code>history</code>
      </operation>
      <operation>
        <code>create</code>
      </operation>
      <operation>
        <code>updates</code>
      </operation>
    </resource>
  </rest>

  <!--   a messaging conformance statement. Applications are not required to make a conformance 
    statement with regard to messaging, though there is active argument that they should.    -->
  <messaging>
    <!--   how to tell whether this llp is a server or a client?   -->
    <event>
      <code>admin-notify</code>
      <mode>receiver</mode> <!--   this a receiver - i.e. answers. Not neccessariy a server   -->
      <focus>Person</focus>
      <!--   specify a profile for the request person. Very often there's no point profiling 
        the response, it's not interesting   -->
      <request>http://fhir.hl7.org/base/profile/@7896271d-57f6-4231-89dc-dcc91eab2416</request>
    </event>
  </messaging>
  
  <!--   a document conformance statement   -->
  <document>
    <mode>consumer</mode>
    <documentation>Basic rules for all documents in the EHR system</documentation>
    <!--   this is the important element: a reference to a published document profile 
       note that this is a version specific reference.  -->
    <profile>http://fhir.hl7.org/base/profile/@bc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/@b5fdd9fc-b021-4ea1-911a-721a60663796</profile>
  </document>  
  <text>
  
    <status>generated</status>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>The EHR Server supports the following transactions for the resource Person: read, vread, 
        update, history, search(name,gender), create, and updates.</p>
      <p>The EHR System supports the following message: admin-notify::Person.</p>
      <p>The EHR Application has a <a href="http://fhir.hl7.org/base/profile/@bc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/@b5fdd9fc-b021-4ea1-911a-721a60663796">general document profile</a>.</p>
    </div>
  </text>
</Conformance>

Example of conformance

{"Conformance": {
  "acceptUnknown": {"value": "org.hl7.fhir.instance.model.Boolean@1300271a"},
  "text": {
    "status": "generated",
    "div": "<div>\n      <p>The EHR Server supports the following transactions for the resource Person: read, vread, \n        update, history, search(name,gender), create, and updates.<\/p>\n      <p>The EHR System supports the following message: admin-notify::Person.<\/p>\n      <p>The EHR Application has a <a href=\"http://fhir.hl7.org/base/profile/@bc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/@b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile<\/a>.<\/p>\n    <\/div>"
  },
  "document": [{
    "documentation": {"value": "Basic rules for all documents in the EHR system"},
    "profile": {"value": "http://fhir.hl7.org/base/profile/@bc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/@b5fdd9fc-b021-4ea1-911a-721a60663796"},
    "mode": "consumer"
  }],
  "software": {
    "name": {"value": "EHR"},
    "version": {"value": "0.00.020.2134"}
  },
  "messaging": [{"event": [{
    "request": {"value": "http://fhir.hl7.org/base/profile/@7896271d-57f6-4231-89dc-dcc91eab2416"},
    "focus": {"value": "Person"},
    "code": {"value": "admin-notify"},
    "mode": "receiver"
  }]}],
  "rest": [{
    "resource": [{
      "operation": [
        {"code": "read"},
        {"code": "vread"},
        {"code": "update"},
        {"code": "history"},
        {"code": "create"},
        {"code": "updates"}
      ],
      "type": {"value": "Person"},
      "profile": {"value": "http://fhir.hl7.org/base/profile/@7896271d-57f6-4231-89dc-dcc91eab2416"}
    }],
    "mode": "server"
  }],
  "date": {"value": "2012-01-04"},
  "version": {"value": "0.02"},
  "publisher": {
    "name": {"value": "ACME Corporation"},
    "contact": [{
      "system": "email",
      "value": {"value": "wile@acme.org"}
    }]
  }
}}