Capability Statement

The CapabilityStatement resource is a statement of the kinds of resources and operations provided and/or consumed by an application.


Using GET /metadata you can access FHIR capabilities interaction.
Response is a CapabilityStatement generated from meta resources created in an Aidbox instance. The list of this meta resource types used for the response generation:
  • Operation
  • SearchParameter
  • Entity
Aidbox CapabilityStatement updates automatically after meta resources change. No interaction needed to apply changes to CapabilityStatement.
Read more about conformance rules and the CapabilityStatement resource itself.
Base URL for FHIR compatible API is <server-domain>/fhir/.
The capabilities interaction returns a capability statement describing the server's current operational functionality. The interaction is performed by the HTTP GET command as shown:
GET [base]/metadata{?mode=[mode]}{&_format=[mime-type]}
You can get Capability Statement of your Aidbox with the command:
GET <server-domain>/fhir/metadata
Get metadata
The information returned depends on the value of the mode parameter:
full (or mode not present)
A Capability Statement that specifies which resource types and interactions are supported
As above, but only the normative portions of the Capability Statement
A TerminologyCapabilities resource that provides further information about terminologies are supported by the server
Servers MAY ignore the mode parameter and return a CapabilityStatement resource.

Configure CapabilityStatement

You can reconfigure specific parts of CapabilityStatement by creating AidboxConfig/box resource:
PUT /AidboxConfig/box
# override name and title of CapabilityStatement
name: MyFHIRServer
title: My FHIR server
description: Description of my FHIR server
# override
- coding:
- {system: '', code: SMART-on-FHIR}
text: Very smart!!!
# override
- url:
- {url: token, valueUri: ''}
- {url: authorize, valueUri: ''}
If you want more control over CapabilityStatement, please contact us in the community chat!



The profile property is set when zen profiling is enabled and the following conditions are met:
  • the corresponding resource is defined in zen profile
  • there is exactly one zen schema tagged with base-profile for the corresponding resource

Aidbox native metadata

To get metadata in the internal Aidbox format, use /$metadata?_format=yaml
Get Aidbox native metadata
Capability statements can become quite large; servers are encouraged to support the _summary and _elements parameters on the capabilities interaction, though this is not required. In addition, servers are encouraged to implement the $subset and $implements operations to make it easy for a client to check conformance.
Last modified 5mo ago