A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server or Client for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.

CapabilityStatement
url
Canonical identifier for this capability statement, represented as a URI (globally unique)
identifier
Additional identifier for the CapabilityStatement (business identifier)
version
Business version of the capability statement
versionAlgorithm[x]
How to compare versions
name
Name for this capability statement (computer friendly)
title
Name for this capability statement (human friendly)
status
draft | active | retired | unknown
experimental
For testing purposes, not real usage
date
Date last changed
publisher
Name of the publisher/steward (organization or individual)
contact
Contact details for the publisher
description
Natural language description of the capability statement
useContext
The context that the content is intended to support
jurisdiction
Intended jurisdiction for capability statement (if applicable)
purpose
Why this capability statement is defined
copyrightLabel
Copyright holder and year(s)
kind
instance | capability | requirements
instantiates
Canonical URL of another capability statement this implements
imports
Canonical URL of another capability statement this adds to
software
Software that is covered by this capability statement
name
A name the software is known by
version
Version covered by this statement
releaseDate
Date this version was released
implementation
If this describes a specific instance
description
Describes this specific instance
url
Base URL for the installation
custodian
Organization that manages the data
fhirVersion
FHIR Version the system supports
format
formats supported (xml | json | ttl | mime type)
patchFormat
Patch formats supported
acceptLanguage
Languages supported
implementationGuide
Implementation guides supported
rest
If the endpoint is a RESTful one
mode
client | server
documentation
General description of implementation
security
Information about security of implementation
cors
Adds CORS Headers (http://enable-cors.org/)
service
OAuth | SMART-on-FHIR | NTLM | Basic | Kerberos | Certificates
description
General description of how security works
resource
Resource served on the REST interface
type
A resource type that is supported
profile
System-wide profile
supportedProfile
Use-case specific profiles
documentation
Additional information about the use of the resource type
interaction
What operations are supported?
code
read | vread | update | patch | delete | history-instance | history-type | create | search-type
documentation
Anything special about operation behavior
versioning
no-version | versioned | versioned-update
readHistory
Whether vRead can return past versions
updateCreate
If update can commit to a new identity
conditionalCreate
If allows/uses conditional create
conditionalRead
not-supported | modified-since | not-match | full-support
conditionalUpdate
If allows/uses conditional update
conditionalPatch
If allows/uses conditional patch
conditionalDelete
not-supported | single | multiple - how conditional delete is supported
referencePolicy
literal | logical | resolves | enforced | local
searchInclude
_include values supported by the server
searchRevInclude
_revinclude values supported by the server
searchParam
Search parameters supported by implementation
name
Name for parameter in search url
definition
Source of definition for parameter
type
number | date | string | token | reference | composite | quantity | uri | special
documentation
Server-specific usage
operation
Definition of a resource operation
name
Name by which the operation/query is invoked
definition
The defined operation/query
documentation
Specific details about operation behavior
interaction
What operations are supported?
code
transaction | batch | search-system | history-system
documentation
Anything special about operation behavior
searchParam
Search parameters for searching all resources
operation
Definition of a system level operation
compartment
Compartments served/used by system
messaging
If messaging is supported
endpoint
Where messages should be sent
protocol
http | ftp | mllp +
address
Network address or identifier of the end-point
reliableCache
Reliable Message Cache Length (min)
documentation
Messaging interface behavior details
supportedMessage
Messages supported by this system
mode
sender | receiver
definition
Message supported by this system
document
Document definition
mode
producer | consumer
documentation
Description of document support
profile
Constraint on the resources used in the document