Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Example CapabilityStatement/base2 (XML)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

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

Base Capability Statement

<?xml version="1.0" encoding="UTF-8"?>

<CapabilityStatement xmlns="http://hl7.org/fhir">
  <id value="base2"/> 
  <text> 
    <status value="extensions"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> Base FHIR Capability Statement (Empty)</h2> 
      <div> 
        <p> This is the base Capability 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 Capability Statements from. A capability
           statement has to contain something, so this contains a read of a Capability Statement</p> 

      </div> 
      <table> 
        <tr> 
          <td> Mode</td> 
          <td> SERVER</td> 
        </tr> 
        <tr> 
          <td> Description</td> 
          <td> 
            <div> 
              <p> An empty Capability Statement</p> 

            </div> 
          </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 title="GET a resource (read interaction)">Read</b> 
          </th> 
          <th> 
            <b title="GET all set of resources of the type (search interaction)">Search</b> 
          </th> 
          <th> 
            <b title="PUT a new resource version (update interaction)">Update</b> 
          </th> 
          <th> 
            <b title="POST a new resource (create interaction)">Create</b> 
          </th> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <url value="http://hl7.org/fhir/CapabilityStatement/base2"/> 
  <version value="5.0.0"/> 
  <name value="Base FHIR Capability Statement (Empty)"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2023-03-26T15:21:02+11:00"/> 
  <publisher value="FHIR Project Team"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="This is the base Capability 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 Capability Statements from. A capability
   statement has to contain something, so this contains a read of a Capability Statement"/> 
  <kind value="capability"/> 
  <software> 
    <name value="Insert your software name here..."/> 
  </software> 
  <fhirVersion value="5.0.0"/> 
  <format value="xml"/> 
  <format value="json"/> 
  <rest> 
    <mode value="server"/> 
    <documentation value="An empty Capability Statement"/> 
    <security> 
      <cors value="true"/> 
      <service> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/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 Capability 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> 
  </rest> 
</CapabilityStatement> 

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.