Terminologycapabilities-example.xml

General Condition 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-4ea1-911
        a-721a60663796">general document profile</a> .
      </p> 
    </div> 
  </text> 
  <!--     the identifier for this capability statement. 
    The identifier and version establish identifiers that other specifications etc.may
   use to 
    refer to the capability statement that this resource represents in a logical manner
   
    rather than in a literal (URL) fashion 

    The identifier should be globally unique - a UUID, an OID, or a URL/URI
      -->
  <url value="urn:uuid:68D043B5-9ECF-4559-A57A-396E0D452311"/> 
  <version value="20130510"/> 
  <name value="ACME-EHR"/> 
  <title value="ACME EHR capability statement"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2012-01-04"/> 
  <publisher value="ACME Corporation"/> 
  <contact> 
    <name value="System Administrator"/> 
    <telecom> 
      <system value="email"/> 
      <value value="wile@acme.org"/> 
    </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="explicit"/> 
</TerminologyCapabilities>