Publish-box (todo)
FHIR Infrastructure Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: No defined compartments |
This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile CapabilityStatement.
Generated Narrative: CapabilityStatement example-terminology-server
json
, xml
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.
server
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include
_revinclude
Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
---|---|---|---|---|---|---|---|---|---|
CodeSystem | http://hl7.org/fhir/StructureDefinition/CodeSystem | y | y | url, version, name, title, status | $expand , $expand , $expand | ||||
ValueSet | http://hl7.org/fhir/StructureDefinition/ValueSet | y | y | url, version, name, title, status | $expand , $expand | ||||
ConceptMap | http://hl7.org/fhir/StructureDefinition/ConceptMap | y | y | url, version, name, title, status | $expand |
read
, search-type
.Conformance | Parameter | Type | Documentation |
---|---|---|---|
SHALL | url | uri | |
SHALL | version | token | |
SHALL | name | string | |
SHALL | title | string | |
SHALL | status | token |
read
, search-type
.Conformance | Parameter | Type | Documentation |
---|---|---|---|
SHALL | url | uri | |
SHALL | version | token | |
SHALL | name | string | |
SHALL | title | string | |
SHALL | status | token |
read
, search-type
.Conformance | Parameter | Type | Documentation |
---|---|---|---|
SHALL | url | uri | |
SHALL | version | token | |
SHALL | name | string | |
SHALL | title | string | |
SHALL | status | token |
Conformance | Operation | Documentation |
---|---|---|
SHALL | $expand |
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.