CapabilityStatement example

ACME EHR capability statement

• Implementation Guide Version: 20130510
• FHIR Version: 6.0.0
• Supported Formats: xml , json
• Supported Patch Formats: application/xml-patch+xml , application/json-patch+json
• Published on: 2012-01-04
• Published by: ACME Corporation

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement instantiates the CapabilityStatement http://ihe.org/fhir/CapabilityStatement/pixm-client

SHALL Support the Following Implementation Guides

• http://example.org/fhir/us/lab

FHIR RESTful Capabilities

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

• The relevant profiles (if any)
• The interactions supported by each resource ( R ead, S earch, U pdate, and C reate, are always shown, while VR ead, P atch, D elete, H istory on I nstance, or H istory on T ype are only present if at least one of the resources has support for them.
• The required, recommended, and some optional search parameters (if any).
• The linked resources enabled for _include
• The other resources enabled for _revinclude
• The operations on the resource (if any)