--- type: "example" title: "TerminologyCapabilities Example: terminologycapabilities-example" resource: "TerminologyCapabilities" example: "terminologycapabilities-example" --- # TerminologyCapabilities Example: terminologycapabilities-example ## Narrative The EHR Server supports the following transactions for the resource Person: read, vread, update, history, search(name,gender), create and updates. The EHR System supports the following message: admin-notify::Person. The EHR Application has a [general document profile](http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796). ## Example XML ```xml

The EHR Server supports the following transactions for the resource Person: read, vread, update, history, search(name,gender), create and updates.

The EHR System supports the following message: admin-notify::Person.

The EHR Application has a general document profile.

<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="in-compose-or-expansion"/> </TerminologyCapabilities> ```