Path
CapabilityStatement
Id
CapabilityStatement
Cardinality
0 - *
Definition
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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.
Comment
Applications may implement multiple versions (see [Managing Multiple Versions](versioning.html), and the [$versions](capabilitystatement-operation-versions.html) operation). If they do, then a CapabilityStatement describes the system's support for a particular version of FHIR, and the server will have multiple statements, one for each version.
Constraint
Name should be usable as an identifier for the module by machine processing applications such as code generation
A Capability Statement SHALL have at least one of REST, messaging or document element.
A Capability Statement SHALL have at least one of description, software, or implementation element.
Messaging end-point is required (and is only permitted) when a statement is for an implementation.
The set of documents must be unique by the combination of profile and mode.
If kind = instance, implementation must be present and software may be present
If kind = capability, implementation must be absent, software must be present
If kind = requirements, implementation and software must be absent
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
If a resource is contained in another resource, it SHALL NOT have a security label
A resource should have narrative for robust management