This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Example TerminologyCapabilities/example (XML)
Raw XML (canonical form + also see XML Format Specification)
Jump past Narrative
General Terminology Capability Example (id = "example")
<?xml version="1.0" encoding="UTF-8"?>
<TerminologyCapabilities xmlns="http://hl7.org/fhir">
<id value="example"/>
<text>
<status value="generated"/> <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/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4
ea1-911a-721a60663796">general document profile</a> .
</p>
</div>
</text>
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="vocab"/>
</extension>
<url value="urn:uuid:68d043b5-9ecf-4559-a57a-396e0d452311"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.6.2"/>
</identifier>
<version value="20130510"/>
<name value="ACMEEHR"/>
<title value="ACME EHR capability statement"/>
<status value="draft"/>
<experimental value="true"/>
<date value="2012-01-04"/>
<publisher value="HL7 International / Terminology Infrastructure"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/Vocab"/>
</telecom>
</contact>
<description value="This is the FHIR capability statement for the main EHR at ACME for the private
interface - it does not describe the public interface"/>
<kind value="instance"/>
<software>
<name value="TxServer"/>
<version value="0.1.2"/>
</software>
<implementation>
<description value="Acme Terminology Server"/>
<url value="http://example.org/tx"/>
</implementation>
<codeSearch value="in-compose-or-expansion"/>
</TerminologyCapabilities>
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.