NHSDigital-CapabilityStatement
Conformance url | FHIR Module | Maturity Level |
---|---|---|
https://fhir.nhs.uk/StructureDefinition/NHSDigital-CapabilityStatement | Implementation Support | draft |
Conformance Rules
with CapabilityStatement
CapabilityStatement | I | CapabilityStatement | There are no (further) constraints on this element Element IdCapabilityStatement A statement of system capabilities DefinitionA 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. Applications may implement multiple versions (see Managing Multiple Versions, and the $versions 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.
| |
extension | I | 0..* | Extension | Element IdCapabilityStatement.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
Package | S I | 0..1 | Extension(Complex) | Element IdCapabilityStatement.extension:Package Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-CapabilityStatement-Package Constraints
|
url | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdCapabilityStatement.url Canonical identifier for this capability statement, represented as a URI (globally unique) DefinitionAn absolute URI that is used to identify this capability statement when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this capability statement is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the capability statement is stored on different servers. Allows the capability statement to be referenced by a single globally unique identifier. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions. In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.version Business version of the capability statement DefinitionThe identifier that is used to identify this version of the capability statement when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the capability statement author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different capability statement instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the capability statement with the format [url]|[version].
|
name | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.name Name for this capability statement (computer friendly) DefinitionA natural language name identifying the capability statement. This name should be usable as an identifier for the module by machine processing applications such as code generation. Support human navigation and code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
|
title | Σ | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.title Name for this capability statement (human friendly) DefinitionA short, descriptive, user-friendly title for the capability statement. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
|
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.status draft | active | retired | unknown DefinitionThe status of this capability statement. Enables tracking the life-cycle of the content. Allows filtering of capability statements that are appropriate for use versus not.This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems. The lifecycle status of an artifact. PublicationStatus (required)Constraints
|
experimental | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.experimental For testing purposes, not real usage DefinitionA Boolean value to indicate that this capability statement is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Enables experimental content to be developed following the same lifecycle that would be used for a production-level capability statement. Allows filtering of capability statements that are appropriate for use versus not.
|
date | Σ | 1..1 | dateTime | There are no (further) constraints on this element Element IdCapabilityStatement.date Date last changed Alternate namesRevision Date DefinitionThe date (and optionally time) when the capability statement was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the capability statement changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the capability statement. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
|
publisher | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.publisher Name of the publisher (organization or individual) DefinitionThe name of the organization or individual that published the capability statement. Helps establish the "authority/credibility" of the capability statement. May also allow for contact. Usually an organization but may be an individual. The publisher (or steward) of the capability statement is the organization or individual primarily responsible for the maintenance and upkeep of the capability statement. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the capability statement. This item SHOULD be populated unless the information is available from context.
|
contact | Σ | 0..* | ContactDetail | There are no (further) constraints on this element Element IdCapabilityStatement.contact Contact details for the publisher DefinitionContact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.
|
description | I | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.description Natural language description of the capability statement DefinitionA free text natural language description of the capability statement from a consumer's perspective. Typically, this is used when the capability statement describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP. This description can be used to capture details such as why the capability statement was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the capability statement as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the capability statement is presumed to be the predominant language in the place the capability statement was created).This does not need to be populated if the description is adequately implied by the software or implementation details.
|
useContext | Σ | 0..* | UsageContext | There are no (further) constraints on this element Element IdCapabilityStatement.useContext The context that the content is intended to support DefinitionThe content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances. Assist in searching for appropriate content. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
|
jurisdiction | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdCapabilityStatement.jurisdiction Intended jurisdiction for capability statement (if applicable) DefinitionA legal or geographic region in which the capability statement is intended to be used. It may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended. Countries and regions within which this artifact is targeted for use. Jurisdiction ValueSet (extensible)Constraints
|
purpose | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.purpose Why this capability statement is defined DefinitionExplanation of why this capability statement is needed and why it has been designed as it has. This element does not describe the usage of the capability statement. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this capability statement.
| |
copyright | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.copyright Use and/or publishing restrictions Alternate namesLicense, Restrictions DefinitionA copyright statement relating to the capability statement and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the capability statement. Consumers must be able to determine any legal restrictions on the use of the capability statement and/or its content. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
kind | S Σ I | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.kind instance | capability | requirements DefinitionThe way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase). Allow searching the 3 modes. Note that FHIR strings SHALL NOT exceed 1MB in size How a capability statement is intended to be used. CapabilityStatementKind (required)Constraints
|
instantiates | Σ | 0..* | canonical(CapabilityStatement) | There are no (further) constraints on this element Element IdCapabilityStatement.instantiates Canonical URL of another capability statement this implements DefinitionReference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details. HL7 defines the following Services: Terminology Service. Many Implementation Guides define additional services. canonical(CapabilityStatement) Constraints
|
imports | Σ | 0..* | canonical(CapabilityStatement) | There are no (further) constraints on this element Element IdCapabilityStatement.imports Canonical URL of another capability statement this adds to DefinitionReference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them. the contents of any directly or indirectly imported CapabilityStatements SHALL NOT overlap, i.e. they cannot refer to the same rest/resource, operations/name, searchparam/name, interaction/code, messaging/endpoint, document/mode pair. A capability statement that imports another CapabilityStatement automatically instantiates it too (though this is often not a very useful statement for the kinds of CapabilityStatements that are suitable for importing). canonical(CapabilityStatement) Constraints
|
software | S Σ I | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.software Software that is covered by this capability statement DefinitionSoftware that is covered by this capability statement. It is used when the capability statement describes the capabilities of a particular software version, independent of an installation.
|
name | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.software.name A name the software is known by DefinitionName the software is known by. Note that FHIR strings SHALL NOT exceed 1MB in size
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.software.version Version covered by this statement DefinitionThe version identifier for the software covered by this statement. If possible, a version should be specified, as statements are likely to be different for different versions of software.
|
releaseDate | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdCapabilityStatement.software.releaseDate Date this version was released DefinitionDate this version of the software was released.
|
implementation | Σ I | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.implementation If this describes a specific instance DefinitionIdentifies a specific implementation instance that is described by the capability statement - i.e. a particular installation, rather than the capabilities of a software program.
|
description | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.implementation.description Describes this specific instance DefinitionInformation about the specific installation that this capability statement relates to. Note that FHIR strings SHALL NOT exceed 1MB in size
|
url | Σ | 0..1 | url | There are no (further) constraints on this element Element IdCapabilityStatement.implementation.url Base URL for the installation DefinitionAn absolute base URL for the implementation. This forms the base for REST interfaces as well as the mailbox and document interfaces. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
custodian | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdCapabilityStatement.implementation.custodian Organization that manages the data DefinitionThe organization responsible for the management of the instance and oversight of the data on the server at the specified URL. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
fhirVersion | S Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.fhirVersion FHIR Version the system supports DefinitionThe version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value. Servers may implement multiple versions (see Managing Multiple Versions, and the $versions operation). If they do, and the CapabilityStatement is requested from the server, then this fhirVersion will be either the version requested, or the server's default version. All published FHIR Versions. FHIRVersion (required)Constraints
|
format | Σ | 1..* | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.format formats supported (xml | json | ttl | mime type) DefinitionA list of the formats supported by this implementation using their content types. "xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here. The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
|
patchFormat | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.patchFormat Patch formats supported DefinitionA list of the patch formats supported by this implementation using their content types. At present, the patch mime types application/json-patch+json and application/xml-patch+xml are legal. Generally, if a server supports PATCH, it would be expected to support the patch formats and match the formats it supports, but this is not always possible or necessary. The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
|
implementationGuide | S Σ | 0..* | canonical(ImplementationGuide) | There are no (further) constraints on this element Element IdCapabilityStatement.implementationGuide Implementation guides supported DefinitionA list of implementation guides that the server does (or should) support in their entirety. canonical(ImplementationGuide) Constraints
|
rest | S Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest If the endpoint is a RESTful one DefinitionA definition of the restful capabilities of the solution, if any. Multiple repetitions allow definition of both client and/or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements).
|
mode | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.mode client | server DefinitionIdentifies whether this portion of the statement is describing the ability to initiate or receive restful operations. Note that FHIR strings SHALL NOT exceed 1MB in size The mode of a RESTful capability statement. RestfulCapabilityMode (required)Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.documentation General description of implementation DefinitionInformation about the system's restful capabilities that apply across all applications, such as security. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
security | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security Information about security of implementation DefinitionInformation about security implementation from an interface perspective - what a client needs to know.
|
extension | I | 0..* | Extension | Element IdCapabilityStatement.rest.security.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
oauthUris | S I | 0..1 | Extension(Complex) | Element IdCapabilityStatement.rest.security.extension:oauthUris Automated discovery of OAuth2 endpoints Alternate namesextensions, user content DefinitionSupports automated discovery of OAuth2 endpoints. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris Constraints
|
cors | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security.cors Adds CORS Headers (http://enable-cors.org/) DefinitionServer adds CORS headers when responding to requests - this enables Javascript applications to use the server. The easiest CORS headers to add are Access-Control-Allow-Origin: * & Access-Control-Request-Method: GET, POST, PUT, DELETE. All servers SHOULD support CORS.
|
service | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security.service OAuth | SMART-on-FHIR | NTLM | Basic | Kerberos | Certificates DefinitionTypes of security services that are supported/required by the system. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Types of security services used with FHIR. RestfulSecurityService (extensible)Constraints
|
description | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security.description General description of how security works DefinitionGeneral description of how security works. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
resource | S Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource Resource served on the REST interface DefinitionA specification of the restful capabilities of the solution for a specific resource type. Max of one repetition per resource type.
|
extension | I | 0..* | Extension | Element IdCapabilityStatement.rest.resource.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
searchParameterCombination | I | 0..* | Extension(Complex) | Element IdCapabilityStatement.rest.resource.extension:searchParameterCombination An allowable parameter combination Alternate namesextensions, user content DefinitionThis extension defines a possible search parameter combination, by listing a set of search parameters and indicating whether they are required or optional. If a search combination is specified, clients should expect that they must submit a search that meets one of the required combinations or the search will be unsuccessful. If multiple search parameter combinations are specified, a client may pick between them, and supply the minimal required parameters for any of the combinations. For example, on the Patient Resource you could use this to state support for searching by Patient.name and Patient.gender is required. Extension(Complex) Extension URLhttp://hl7.org/fhir/StructureDefinition/capabilitystatement-search-parameter-combination Constraints
|
type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.type A resource type that is supported DefinitionA type of resource exposed via the restful interface. Note that FHIR strings SHALL NOT exceed 1MB in size One of the resource types defined as part of this version of FHIR. ResourceType (required)Constraints
|
profile | Σ | 1..1 | canonical(StructureDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.profile Base System profile for all uses of resource DefinitionA specification of the profile that describes the solution's overall support for the resource, including any constraints on cardinality, bindings, lengths or other limitations. See further discussion in Using Profiles. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system. canonical(StructureDefinition) Constraints
|
supportedProfile | Σ | 0..* | canonical(StructureDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.supportedProfile Profiles for use cases supported DefinitionA list of profiles that represent different use cases supported by the system. For a server, "supported by the system" means the system hosts/produces a set of resources that are conformant to a particular profile, and allows clients that use its services to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile. See further discussion in Using Profiles. Supported profiles are different than the profile that applies to a particular resource in .rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that do? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile). canonical(StructureDefinition) Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.documentation Additional information about the use of the resource type DefinitionAdditional information about the resource type used by the system. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
interaction | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.interaction What operations are supported? DefinitionIdentifies a restful operation supported by the solution. In general, a Resource will only appear in a CapabilityStatement if the server actually has some capabilities - e.g. there is at least one interaction supported. However interactions can be omitted to support summarization (_summary = true).
| |
extension | I | 0..* | Extension | Element IdCapabilityStatement.rest.resource.interaction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
Examples | I | 0..1 | Extension(Complex) | Element IdCapabilityStatement.rest.resource.interaction.extension:Examples Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-CapabilityStatement-Examples Constraints
|
code | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.interaction.code read | vread | update | patch | delete | history-instance | history-type | create | search-type DefinitionCoded identifier of the operation, supported by the system resource. Note that FHIR strings SHALL NOT exceed 1MB in size Operations supported by REST at the type or instance level. TypeRestfulInteraction (required)Constraints
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.interaction.documentation Anything special about operation behavior DefinitionGuidance specific to the implementation of this operation, such as 'delete is a logical delete' or 'updates are only allowed with version id' or 'creates permitted from pre-authorized certificates only'. REST allows a degree of variability in the implementation of RESTful solutions that is useful for exchange partners to be aware of. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
versioning | 0..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.versioning no-version | versioned | versioned-update DefinitionThis field is set to no-version to specify that the system does not support (server) or use (client) versioning for this resource type. If this has some other value, the server must at least correctly track and populate the versionId meta-property on resources. If the value is 'versioned-update', then the server supports all the versioning features, including using e-tags for version integrity in the API. If a server supports versionIds correctly, it SHOULD support vread too, but is not required to do so. How the system supports versioning for a resource. ResourceVersionPolicy (required)Constraints
| |
readHistory | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.readHistory Whether vRead can return past versions DefinitionA flag for whether the server is able to return past versions as part of the vRead operation. It is useful to support the vRead operation for current operations, even if past versions aren't available.
| |
updateCreate | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.updateCreate If update can commit to a new identity DefinitionA flag to indicate that the server allows or needs to allow the client to create new identities on the server (that is, the client PUTs to a location where there is no existing resource). Allowing this operation means that the server allows the client to create new identities on the server. Allowing the clients to create new identities on the server means that the system administrator needs to have confidence that the clients do not create clashing identities between them. Obviously, if there is only one client, this won't happen. While creating identities on the client means that the clients need to be managed, it's much more convenient for many scenarios if such management can be put in place.
| |
conditionalCreate | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalCreate If allows/uses conditional create DefinitionA flag that indicates that the server supports conditional create. Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.
| |
conditionalRead | 0..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalRead not-supported | modified-since | not-match | full-support DefinitionA code that indicates how the server supports conditional read. Conditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2. A code that indicates how the server supports conditional read. ConditionalReadStatus (required)Constraints
| |
conditionalUpdate | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalUpdate If allows/uses conditional update DefinitionA flag that indicates that the server supports conditional update. Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.
| |
conditionalDelete | 0..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalDelete not-supported | single | multiple - how conditional delete is supported DefinitionA code that indicates how the server supports conditional delete. Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2. A code that indicates how the server supports conditional delete. ConditionalDeleteStatus (required)Constraints
| |
referencePolicy | 0..* | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.referencePolicy literal | logical | resolves | enforced | local DefinitionA set of flags that defines how references are supported. Note that FHIR strings SHALL NOT exceed 1MB in size A set of flags that defines how references are supported. ReferenceHandlingPolicy (required)Constraints
| |
searchInclude | 0..* | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchInclude _include values supported by the server DefinitionA list of _include values supported by the server. If this list is empty, the server does not support includes.
| |
searchRevInclude | 0..* | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchRevInclude _revinclude values supported by the server DefinitionA list of _revinclude (reverse include) values supported by the server. If this list is empty, the server does not support reverse includes.
| |
searchParam | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam Search parameters supported by implementation DefinitionSearch parameters for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation. The search parameters should include the control search parameters such as _sort, _count, etc. that also apply to this resource (though many will be listed at CapabilityStatement.rest.searchParam). The behavior of some search parameters may be further described by other code or extension elements, or narrative within the capability statement or linked SearchParameter definitions.
| |
name | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.name Name of search parameter DefinitionThe name of the search parameter used in the interface. Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.
| |
definition | 0..1 | canonical(SearchParameter) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.definition Source of definition for parameter DefinitionAn absolute URI that is a formal reference to where this parameter was first defined, so that a client can be confident of the meaning of the search parameter (a reference to SearchParameter.url). This element SHALL be populated if the search parameter refers to a SearchParameter defined by the FHIR core specification or externally defined IGs. This SHOULD be present, and matches refers to a SearchParameter by its canonical URL. If systems wish to document their support for modifiers, comparators, target resource types, and chained parameters, they should do using a search parameter resource. This element SHALL be populated if the search parameter refers to a SearchParameter defined by the FHIR core specification or externally defined IGs.
| |
type | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.type number | date | string | token | reference | composite | quantity | uri | special DefinitionThe type of value a search parameter refers to, and how the content is interpreted. While this can be looked up from the definition, it is included here as a convenience for systems that autogenerate a query interface based on the server capability statement. It SHALL be the same as the type in the search parameter definition. Data types allowed to be used for search parameters. SearchParamType (required)Constraints
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.documentation Server-specific usage DefinitionThis allows documentation of any distinct behaviors about how the search parameter is used. For example, text matching algorithms. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
operation | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation Definition of a resource operation DefinitionDefinition of an operation or a named query together with its parameters and their meaning and type. Consult the definition of the operation for details about how to invoke the operation, and the parameters. Operations linked from CapabilityStatement.rest.resource.operation must have OperationDefinition.type = true or OperationDefinition.instance = true. If an operation that is listed in multiple CapabilityStatement.rest.resource.operation (e.g. for different resource types), then clients should understand that the operation is only supported on the specified resource types, and that may be a subset of those listed in OperationDefinition.resource.
|
name | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation.name Name by which the operation/query is invoked DefinitionThe name of the operation or query. For an operation, this is the name prefixed with $ and used in the URL. For a query, this is the name used in the _query parameter when the query is called. The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used. The name does not include the "$" portion that is always included in the URL.
|
definition | Σ | 1..1 | canonical(OperationDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation.definition The defined operation/query DefinitionWhere the formal definition can be found. If a server references the base definition of an Operation (i.e. from the specification itself such as This can be used to build an HTML form to invoke the operation, for instance. canonical(OperationDefinition) Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation.documentation Specific details about operation behavior DefinitionDocumentation that describes anything special about the operation behavior, possibly detailing different behavior for system, type and instance-level invocation of the operation. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
interaction | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.interaction What operations are supported? DefinitionA specification of restful operations supported by the system.
| |
code | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.interaction.code transaction | batch | search-system | history-system DefinitionA coded identifier of the operation, supported by the system. Note that FHIR strings SHALL NOT exceed 1MB in size Operations supported by REST at the system level. SystemRestfulInteraction (required)Constraints
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.interaction.documentation Anything special about operation behavior DefinitionGuidance specific to the implementation of this operation, such as limitations on the kind of transactions allowed, or information about system wide search is implemented. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
searchParam | 0..* | see (searchParam) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.searchParam Search parameters for searching all resources DefinitionSearch parameters that are supported for searching all resources for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation. Typically, the only search parameters supported for all searches are those that apply to all resources - tags, profiles, text search etc. These search parameters should include the control search parameters such as _sort, _count, etc. that also apply to this resource (though many will be listed at CapabilityStatement.rest.searchParam). The behavior of some search parameters may be further described by other code or extension elements, or narrative within the capability statement or linked SearchParameter definitions. | |
operation | Σ | 0..* | see (operation) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.operation Definition of a system level operation DefinitionDefinition of an operation or a named query together with its parameters and their meaning and type. CapabilityStatement.rest.operation is for operations invoked at the system level, or for operations that are supported across multiple resource types. Operations linked from CapabilityStatement.rest.operation must have OperationDefinition.system = true, or more than one Operation.resource. |
compartment | 0..* | canonical(CompartmentDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.compartment Compartments served/used by system DefinitionAn absolute URI which is a reference to the definition of a compartment that the system supports. The reference is to a CompartmentDefinition resource by its canonical URL . At present, the only defined compartments are at CompartmentDefinition. canonical(CompartmentDefinition) Constraints
| |
messaging | S Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.messaging If messaging is supported DefinitionA description of the messaging capabilities of the solution. Multiple repetitions allow the documentation of multiple endpoints per solution.
|
endpoint | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.endpoint Where messages should be sent Alternate names3 DefinitionAn endpoint (network accessible address) to which messages and/or replies are to be sent.
| |
protocol | 1..1 | CodingBinding | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.endpoint.protocol http | ftp | mllp + DefinitionA list of the messaging transport protocol(s) identifiers, supported by this endpoint. Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. The protocol used for message transport. MessageTransport (extensible)Constraints
| |
address | 1..1 | url | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.endpoint.address Network address or identifier of the end-point DefinitionThe network address of the endpoint. For solutions that do not use network addresses for routing, it can be just an identifier. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |
reliableCache | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.reliableCache Reliable Message Cache Length (min) DefinitionLength if the receiver's reliable messaging cache in minutes (if a receiver) or how long the cache length on the receiver should be (if a sender). If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.documentation Messaging interface behavior details DefinitionDocumentation about the system's messaging capabilities for this endpoint not otherwise documented by the capability statement. For example, the process for becoming an authorized messaging exchange partner. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
supportedMessage | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.supportedMessage Messages supported by this system DefinitionReferences to message definitions for messages this system can send or receive. This is a proposed alternative to the messaging.event structure.
|
extension | I | 0..* | Extension | Element IdCapabilityStatement.messaging.supportedMessage.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
Examples | I | 0..* | Extension(Complex) | Element IdCapabilityStatement.messaging.supportedMessage.extension:Examples Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-CapabilityStatement-Examples Constraints
|
mode | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.supportedMessage.mode sender | receiver DefinitionThe mode of this event declaration - whether application is sender or receiver. Note that FHIR strings SHALL NOT exceed 1MB in size The mode of a message capability statement. EventCapabilityMode (required)Constraints
|
definition | Σ | 1..1 | canonical(MessageDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.supportedMessage.definition Message supported by this system DefinitionPoints to a message definition that identifies the messaging event, message structure, allowed responses, etc.
|
document | Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.document Document definition DefinitionA document definition.
|
mode | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.document.mode producer | consumer DefinitionMode of this document declaration - whether an application is a producer or consumer. Note that FHIR strings SHALL NOT exceed 1MB in size Whether the application produces or consumes documents. DocumentMode (required)Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.document.documentation Description of document support DefinitionA description of how the application supports or uses the specified document profile. For example, when documents are created, what action is taken with consumed documents, etc. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
profile | Σ | 1..1 | canonical(StructureDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.document.profile Constraint on the resources used in the document DefinitionA profile on the document Bundle that constrains which resources are present, and their contents. The profile is actually on the Bundle. canonical(StructureDefinition) Constraints
|
from CapabilityStatement
CapabilityStatement | I | CapabilityStatement | There are no (further) constraints on this element Element IdCapabilityStatement A statement of system capabilities DefinitionA 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. Applications may implement multiple versions (see Managing Multiple Versions, and the $versions 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.
| |
extension | I | 0..* | Extension | Element IdCapabilityStatement.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
Package | S I | 0..1 | Extension(Complex) | Element IdCapabilityStatement.extension:Package Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-CapabilityStatement-Package Constraints
|
url | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdCapabilityStatement.url Canonical identifier for this capability statement, represented as a URI (globally unique) DefinitionAn absolute URI that is used to identify this capability statement when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this capability statement is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the capability statement is stored on different servers. Allows the capability statement to be referenced by a single globally unique identifier. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions. In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.version Business version of the capability statement DefinitionThe identifier that is used to identify this version of the capability statement when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the capability statement author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different capability statement instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the capability statement with the format [url]|[version].
|
name | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.name Name for this capability statement (computer friendly) DefinitionA natural language name identifying the capability statement. This name should be usable as an identifier for the module by machine processing applications such as code generation. Support human navigation and code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
|
title | Σ | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.title Name for this capability statement (human friendly) DefinitionA short, descriptive, user-friendly title for the capability statement. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
|
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.status draft | active | retired | unknown DefinitionThe status of this capability statement. Enables tracking the life-cycle of the content. Allows filtering of capability statements that are appropriate for use versus not.This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems. The lifecycle status of an artifact. PublicationStatus (required)Constraints
|
experimental | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.experimental For testing purposes, not real usage DefinitionA Boolean value to indicate that this capability statement is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Enables experimental content to be developed following the same lifecycle that would be used for a production-level capability statement. Allows filtering of capability statements that are appropriate for use versus not.
|
date | Σ | 1..1 | dateTime | There are no (further) constraints on this element Element IdCapabilityStatement.date Date last changed Alternate namesRevision Date DefinitionThe date (and optionally time) when the capability statement was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the capability statement changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the capability statement. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
|
publisher | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.publisher Name of the publisher (organization or individual) DefinitionThe name of the organization or individual that published the capability statement. Helps establish the "authority/credibility" of the capability statement. May also allow for contact. Usually an organization but may be an individual. The publisher (or steward) of the capability statement is the organization or individual primarily responsible for the maintenance and upkeep of the capability statement. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the capability statement. This item SHOULD be populated unless the information is available from context.
|
contact | Σ | 0..* | ContactDetail | There are no (further) constraints on this element Element IdCapabilityStatement.contact Contact details for the publisher DefinitionContact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.
|
description | I | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.description Natural language description of the capability statement DefinitionA free text natural language description of the capability statement from a consumer's perspective. Typically, this is used when the capability statement describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP. This description can be used to capture details such as why the capability statement was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the capability statement as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the capability statement is presumed to be the predominant language in the place the capability statement was created).This does not need to be populated if the description is adequately implied by the software or implementation details.
|
useContext | Σ | 0..* | UsageContext | There are no (further) constraints on this element Element IdCapabilityStatement.useContext The context that the content is intended to support DefinitionThe content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances. Assist in searching for appropriate content. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
|
jurisdiction | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdCapabilityStatement.jurisdiction Intended jurisdiction for capability statement (if applicable) DefinitionA legal or geographic region in which the capability statement is intended to be used. It may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended. Countries and regions within which this artifact is targeted for use. Jurisdiction ValueSet (extensible)Constraints
|
purpose | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.purpose Why this capability statement is defined DefinitionExplanation of why this capability statement is needed and why it has been designed as it has. This element does not describe the usage of the capability statement. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this capability statement.
| |
copyright | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.copyright Use and/or publishing restrictions Alternate namesLicense, Restrictions DefinitionA copyright statement relating to the capability statement and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the capability statement. Consumers must be able to determine any legal restrictions on the use of the capability statement and/or its content. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
kind | S Σ I | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.kind instance | capability | requirements DefinitionThe way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase). Allow searching the 3 modes. Note that FHIR strings SHALL NOT exceed 1MB in size How a capability statement is intended to be used. CapabilityStatementKind (required)Constraints
|
instantiates | Σ | 0..* | canonical(CapabilityStatement) | There are no (further) constraints on this element Element IdCapabilityStatement.instantiates Canonical URL of another capability statement this implements DefinitionReference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details. HL7 defines the following Services: Terminology Service. Many Implementation Guides define additional services. canonical(CapabilityStatement) Constraints
|
imports | Σ | 0..* | canonical(CapabilityStatement) | There are no (further) constraints on this element Element IdCapabilityStatement.imports Canonical URL of another capability statement this adds to DefinitionReference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them. the contents of any directly or indirectly imported CapabilityStatements SHALL NOT overlap, i.e. they cannot refer to the same rest/resource, operations/name, searchparam/name, interaction/code, messaging/endpoint, document/mode pair. A capability statement that imports another CapabilityStatement automatically instantiates it too (though this is often not a very useful statement for the kinds of CapabilityStatements that are suitable for importing). canonical(CapabilityStatement) Constraints
|
software | S Σ I | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.software Software that is covered by this capability statement DefinitionSoftware that is covered by this capability statement. It is used when the capability statement describes the capabilities of a particular software version, independent of an installation.
|
name | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.software.name A name the software is known by DefinitionName the software is known by. Note that FHIR strings SHALL NOT exceed 1MB in size
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.software.version Version covered by this statement DefinitionThe version identifier for the software covered by this statement. If possible, a version should be specified, as statements are likely to be different for different versions of software.
|
releaseDate | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdCapabilityStatement.software.releaseDate Date this version was released DefinitionDate this version of the software was released.
|
implementation | Σ I | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.implementation If this describes a specific instance DefinitionIdentifies a specific implementation instance that is described by the capability statement - i.e. a particular installation, rather than the capabilities of a software program.
|
description | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.implementation.description Describes this specific instance DefinitionInformation about the specific installation that this capability statement relates to. Note that FHIR strings SHALL NOT exceed 1MB in size
|
url | Σ | 0..1 | url | There are no (further) constraints on this element Element IdCapabilityStatement.implementation.url Base URL for the installation DefinitionAn absolute base URL for the implementation. This forms the base for REST interfaces as well as the mailbox and document interfaces. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
custodian | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdCapabilityStatement.implementation.custodian Organization that manages the data DefinitionThe organization responsible for the management of the instance and oversight of the data on the server at the specified URL. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
fhirVersion | S Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.fhirVersion FHIR Version the system supports DefinitionThe version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value. Servers may implement multiple versions (see Managing Multiple Versions, and the $versions operation). If they do, and the CapabilityStatement is requested from the server, then this fhirVersion will be either the version requested, or the server's default version. All published FHIR Versions. FHIRVersion (required)Constraints
|
format | Σ | 1..* | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.format formats supported (xml | json | ttl | mime type) DefinitionA list of the formats supported by this implementation using their content types. "xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here. The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
|
patchFormat | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.patchFormat Patch formats supported DefinitionA list of the patch formats supported by this implementation using their content types. At present, the patch mime types application/json-patch+json and application/xml-patch+xml are legal. Generally, if a server supports PATCH, it would be expected to support the patch formats and match the formats it supports, but this is not always possible or necessary. The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
|
implementationGuide | S Σ | 0..* | canonical(ImplementationGuide) | There are no (further) constraints on this element Element IdCapabilityStatement.implementationGuide Implementation guides supported DefinitionA list of implementation guides that the server does (or should) support in their entirety. canonical(ImplementationGuide) Constraints
|
rest | S Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest If the endpoint is a RESTful one DefinitionA definition of the restful capabilities of the solution, if any. Multiple repetitions allow definition of both client and/or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements).
|
mode | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.mode client | server DefinitionIdentifies whether this portion of the statement is describing the ability to initiate or receive restful operations. Note that FHIR strings SHALL NOT exceed 1MB in size The mode of a RESTful capability statement. RestfulCapabilityMode (required)Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.documentation General description of implementation DefinitionInformation about the system's restful capabilities that apply across all applications, such as security. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
security | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security Information about security of implementation DefinitionInformation about security implementation from an interface perspective - what a client needs to know.
|
extension | I | 0..* | Extension | Element IdCapabilityStatement.rest.security.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
oauthUris | S I | 0..1 | Extension(Complex) | Element IdCapabilityStatement.rest.security.extension:oauthUris Automated discovery of OAuth2 endpoints Alternate namesextensions, user content DefinitionSupports automated discovery of OAuth2 endpoints. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris Constraints
|
cors | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security.cors Adds CORS Headers (http://enable-cors.org/) DefinitionServer adds CORS headers when responding to requests - this enables Javascript applications to use the server. The easiest CORS headers to add are Access-Control-Allow-Origin: * & Access-Control-Request-Method: GET, POST, PUT, DELETE. All servers SHOULD support CORS.
|
service | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security.service OAuth | SMART-on-FHIR | NTLM | Basic | Kerberos | Certificates DefinitionTypes of security services that are supported/required by the system. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Types of security services used with FHIR. RestfulSecurityService (extensible)Constraints
|
description | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.security.description General description of how security works DefinitionGeneral description of how security works. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
resource | S Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource Resource served on the REST interface DefinitionA specification of the restful capabilities of the solution for a specific resource type. Max of one repetition per resource type.
|
extension | I | 0..* | Extension | Element IdCapabilityStatement.rest.resource.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
searchParameterCombination | I | 0..* | Extension(Complex) | Element IdCapabilityStatement.rest.resource.extension:searchParameterCombination An allowable parameter combination Alternate namesextensions, user content DefinitionThis extension defines a possible search parameter combination, by listing a set of search parameters and indicating whether they are required or optional. If a search combination is specified, clients should expect that they must submit a search that meets one of the required combinations or the search will be unsuccessful. If multiple search parameter combinations are specified, a client may pick between them, and supply the minimal required parameters for any of the combinations. For example, on the Patient Resource you could use this to state support for searching by Patient.name and Patient.gender is required. Extension(Complex) Extension URLhttp://hl7.org/fhir/StructureDefinition/capabilitystatement-search-parameter-combination Constraints
|
type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.type A resource type that is supported DefinitionA type of resource exposed via the restful interface. Note that FHIR strings SHALL NOT exceed 1MB in size One of the resource types defined as part of this version of FHIR. ResourceType (required)Constraints
|
profile | Σ | 1..1 | canonical(StructureDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.profile Base System profile for all uses of resource DefinitionA specification of the profile that describes the solution's overall support for the resource, including any constraints on cardinality, bindings, lengths or other limitations. See further discussion in Using Profiles. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system. canonical(StructureDefinition) Constraints
|
supportedProfile | Σ | 0..* | canonical(StructureDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.supportedProfile Profiles for use cases supported DefinitionA list of profiles that represent different use cases supported by the system. For a server, "supported by the system" means the system hosts/produces a set of resources that are conformant to a particular profile, and allows clients that use its services to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile. See further discussion in Using Profiles. Supported profiles are different than the profile that applies to a particular resource in .rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that do? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile). canonical(StructureDefinition) Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.documentation Additional information about the use of the resource type DefinitionAdditional information about the resource type used by the system. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
interaction | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.interaction What operations are supported? DefinitionIdentifies a restful operation supported by the solution. In general, a Resource will only appear in a CapabilityStatement if the server actually has some capabilities - e.g. there is at least one interaction supported. However interactions can be omitted to support summarization (_summary = true).
| |
extension | I | 0..* | Extension | Element IdCapabilityStatement.rest.resource.interaction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
Examples | I | 0..1 | Extension(Complex) | Element IdCapabilityStatement.rest.resource.interaction.extension:Examples Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-CapabilityStatement-Examples Constraints
|
code | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.interaction.code read | vread | update | patch | delete | history-instance | history-type | create | search-type DefinitionCoded identifier of the operation, supported by the system resource. Note that FHIR strings SHALL NOT exceed 1MB in size Operations supported by REST at the type or instance level. TypeRestfulInteraction (required)Constraints
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.interaction.documentation Anything special about operation behavior DefinitionGuidance specific to the implementation of this operation, such as 'delete is a logical delete' or 'updates are only allowed with version id' or 'creates permitted from pre-authorized certificates only'. REST allows a degree of variability in the implementation of RESTful solutions that is useful for exchange partners to be aware of. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
versioning | 0..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.versioning no-version | versioned | versioned-update DefinitionThis field is set to no-version to specify that the system does not support (server) or use (client) versioning for this resource type. If this has some other value, the server must at least correctly track and populate the versionId meta-property on resources. If the value is 'versioned-update', then the server supports all the versioning features, including using e-tags for version integrity in the API. If a server supports versionIds correctly, it SHOULD support vread too, but is not required to do so. How the system supports versioning for a resource. ResourceVersionPolicy (required)Constraints
| |
readHistory | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.readHistory Whether vRead can return past versions DefinitionA flag for whether the server is able to return past versions as part of the vRead operation. It is useful to support the vRead operation for current operations, even if past versions aren't available.
| |
updateCreate | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.updateCreate If update can commit to a new identity DefinitionA flag to indicate that the server allows or needs to allow the client to create new identities on the server (that is, the client PUTs to a location where there is no existing resource). Allowing this operation means that the server allows the client to create new identities on the server. Allowing the clients to create new identities on the server means that the system administrator needs to have confidence that the clients do not create clashing identities between them. Obviously, if there is only one client, this won't happen. While creating identities on the client means that the clients need to be managed, it's much more convenient for many scenarios if such management can be put in place.
| |
conditionalCreate | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalCreate If allows/uses conditional create DefinitionA flag that indicates that the server supports conditional create. Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.
| |
conditionalRead | 0..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalRead not-supported | modified-since | not-match | full-support DefinitionA code that indicates how the server supports conditional read. Conditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2. A code that indicates how the server supports conditional read. ConditionalReadStatus (required)Constraints
| |
conditionalUpdate | 0..1 | boolean | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalUpdate If allows/uses conditional update DefinitionA flag that indicates that the server supports conditional update. Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.
| |
conditionalDelete | 0..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.conditionalDelete not-supported | single | multiple - how conditional delete is supported DefinitionA code that indicates how the server supports conditional delete. Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2. A code that indicates how the server supports conditional delete. ConditionalDeleteStatus (required)Constraints
| |
referencePolicy | 0..* | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.referencePolicy literal | logical | resolves | enforced | local DefinitionA set of flags that defines how references are supported. Note that FHIR strings SHALL NOT exceed 1MB in size A set of flags that defines how references are supported. ReferenceHandlingPolicy (required)Constraints
| |
searchInclude | 0..* | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchInclude _include values supported by the server DefinitionA list of _include values supported by the server. If this list is empty, the server does not support includes.
| |
searchRevInclude | 0..* | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchRevInclude _revinclude values supported by the server DefinitionA list of _revinclude (reverse include) values supported by the server. If this list is empty, the server does not support reverse includes.
| |
searchParam | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam Search parameters supported by implementation DefinitionSearch parameters for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation. The search parameters should include the control search parameters such as _sort, _count, etc. that also apply to this resource (though many will be listed at CapabilityStatement.rest.searchParam). The behavior of some search parameters may be further described by other code or extension elements, or narrative within the capability statement or linked SearchParameter definitions.
| |
name | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.name Name of search parameter DefinitionThe name of the search parameter used in the interface. Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.
| |
definition | 0..1 | canonical(SearchParameter) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.definition Source of definition for parameter DefinitionAn absolute URI that is a formal reference to where this parameter was first defined, so that a client can be confident of the meaning of the search parameter (a reference to SearchParameter.url). This element SHALL be populated if the search parameter refers to a SearchParameter defined by the FHIR core specification or externally defined IGs. This SHOULD be present, and matches refers to a SearchParameter by its canonical URL. If systems wish to document their support for modifiers, comparators, target resource types, and chained parameters, they should do using a search parameter resource. This element SHALL be populated if the search parameter refers to a SearchParameter defined by the FHIR core specification or externally defined IGs.
| |
type | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.type number | date | string | token | reference | composite | quantity | uri | special DefinitionThe type of value a search parameter refers to, and how the content is interpreted. While this can be looked up from the definition, it is included here as a convenience for systems that autogenerate a query interface based on the server capability statement. It SHALL be the same as the type in the search parameter definition. Data types allowed to be used for search parameters. SearchParamType (required)Constraints
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.searchParam.documentation Server-specific usage DefinitionThis allows documentation of any distinct behaviors about how the search parameter is used. For example, text matching algorithms. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
operation | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation Definition of a resource operation DefinitionDefinition of an operation or a named query together with its parameters and their meaning and type. Consult the definition of the operation for details about how to invoke the operation, and the parameters. Operations linked from CapabilityStatement.rest.resource.operation must have OperationDefinition.type = true or OperationDefinition.instance = true. If an operation that is listed in multiple CapabilityStatement.rest.resource.operation (e.g. for different resource types), then clients should understand that the operation is only supported on the specified resource types, and that may be a subset of those listed in OperationDefinition.resource.
|
name | Σ | 1..1 | string | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation.name Name by which the operation/query is invoked DefinitionThe name of the operation or query. For an operation, this is the name prefixed with $ and used in the URL. For a query, this is the name used in the _query parameter when the query is called. The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used. The name does not include the "$" portion that is always included in the URL.
|
definition | Σ | 1..1 | canonical(OperationDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation.definition The defined operation/query DefinitionWhere the formal definition can be found. If a server references the base definition of an Operation (i.e. from the specification itself such as This can be used to build an HTML form to invoke the operation, for instance. canonical(OperationDefinition) Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.resource.operation.documentation Specific details about operation behavior DefinitionDocumentation that describes anything special about the operation behavior, possibly detailing different behavior for system, type and instance-level invocation of the operation. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
interaction | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.rest.interaction What operations are supported? DefinitionA specification of restful operations supported by the system.
| |
code | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.rest.interaction.code transaction | batch | search-system | history-system DefinitionA coded identifier of the operation, supported by the system. Note that FHIR strings SHALL NOT exceed 1MB in size Operations supported by REST at the system level. SystemRestfulInteraction (required)Constraints
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.rest.interaction.documentation Anything special about operation behavior DefinitionGuidance specific to the implementation of this operation, such as limitations on the kind of transactions allowed, or information about system wide search is implemented. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
searchParam | 0..* | see (searchParam) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.searchParam Search parameters for searching all resources DefinitionSearch parameters that are supported for searching all resources for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation. Typically, the only search parameters supported for all searches are those that apply to all resources - tags, profiles, text search etc. These search parameters should include the control search parameters such as _sort, _count, etc. that also apply to this resource (though many will be listed at CapabilityStatement.rest.searchParam). The behavior of some search parameters may be further described by other code or extension elements, or narrative within the capability statement or linked SearchParameter definitions. | |
operation | Σ | 0..* | see (operation) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.operation Definition of a system level operation DefinitionDefinition of an operation or a named query together with its parameters and their meaning and type. CapabilityStatement.rest.operation is for operations invoked at the system level, or for operations that are supported across multiple resource types. Operations linked from CapabilityStatement.rest.operation must have OperationDefinition.system = true, or more than one Operation.resource. |
compartment | 0..* | canonical(CompartmentDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.rest.compartment Compartments served/used by system DefinitionAn absolute URI which is a reference to the definition of a compartment that the system supports. The reference is to a CompartmentDefinition resource by its canonical URL . At present, the only defined compartments are at CompartmentDefinition. canonical(CompartmentDefinition) Constraints
| |
messaging | S Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.messaging If messaging is supported DefinitionA description of the messaging capabilities of the solution. Multiple repetitions allow the documentation of multiple endpoints per solution.
|
endpoint | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.endpoint Where messages should be sent Alternate names3 DefinitionAn endpoint (network accessible address) to which messages and/or replies are to be sent.
| |
protocol | 1..1 | CodingBinding | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.endpoint.protocol http | ftp | mllp + DefinitionA list of the messaging transport protocol(s) identifiers, supported by this endpoint. Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. The protocol used for message transport. MessageTransport (extensible)Constraints
| |
address | 1..1 | url | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.endpoint.address Network address or identifier of the end-point DefinitionThe network address of the endpoint. For solutions that do not use network addresses for routing, it can be just an identifier. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |
reliableCache | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.reliableCache Reliable Message Cache Length (min) DefinitionLength if the receiver's reliable messaging cache in minutes (if a receiver) or how long the cache length on the receiver should be (if a sender). If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.
| |
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.documentation Messaging interface behavior details DefinitionDocumentation about the system's messaging capabilities for this endpoint not otherwise documented by the capability statement. For example, the process for becoming an authorized messaging exchange partner. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
supportedMessage | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.supportedMessage Messages supported by this system DefinitionReferences to message definitions for messages this system can send or receive. This is a proposed alternative to the messaging.event structure.
|
extension | I | 0..* | Extension | Element IdCapabilityStatement.messaging.supportedMessage.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
Examples | I | 0..* | Extension(Complex) | Element IdCapabilityStatement.messaging.supportedMessage.extension:Examples Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-CapabilityStatement-Examples Constraints
|
mode | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.supportedMessage.mode sender | receiver DefinitionThe mode of this event declaration - whether application is sender or receiver. Note that FHIR strings SHALL NOT exceed 1MB in size The mode of a message capability statement. EventCapabilityMode (required)Constraints
|
definition | Σ | 1..1 | canonical(MessageDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.messaging.supportedMessage.definition Message supported by this system DefinitionPoints to a message definition that identifies the messaging event, message structure, allowed responses, etc.
|
document | Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element IdCapabilityStatement.document Document definition DefinitionA document definition.
|
mode | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdCapabilityStatement.document.mode producer | consumer DefinitionMode of this document declaration - whether an application is a producer or consumer. Note that FHIR strings SHALL NOT exceed 1MB in size Whether the application produces or consumes documents. DocumentMode (required)Constraints
|
documentation | 0..1 | markdown | There are no (further) constraints on this element Element IdCapabilityStatement.document.documentation Description of document support DefinitionA description of how the application supports or uses the specified document profile. For example, when documents are created, what action is taken with consumed documents, etc. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
profile | Σ | 1..1 | canonical(StructureDefinition) | There are no (further) constraints on this element Element IdCapabilityStatement.document.profile Constraint on the resources used in the document DefinitionA profile on the document Bundle that constrains which resources are present, and their contents. The profile is actually on the Bundle. canonical(StructureDefinition) Constraints
|
apiDefinition (extension)
Links to the API documentation MUST be provided.
{ "url": "https://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-APIDefinition", "extension": [ { "url": "openApi", "extension": [ { "url": "documentation", "valueUri": "https://digital.nhs.uk/developer/api-catalogue/electronic-prescription-service-fhir" },{ "url": "description", "valueString": "Access the Electronic Prescription Service (EPS) - the national service used to send electronic prescriptions from GP surgeries to pharmacies." }, } ] }
A list of Implementation Guide packages used with this API MUST be provided.
Although the UKCore.R4
version can be derived from the uk.nhsdigital.r4
package information, it MUST be provided. This applies to all derived or supplemental packages.
{ "url": "https://fhir.nhs.uk/StructureDefinition/Extension-NHSDigital-APIDefinition", "extension": [ { "url": "implementationGuide", "extension": [ { "url": "name", "valueString": "uk.nhsdigital.r4" },{ "url": "version", "valueString": "2.1.34-discovery" } ] }, { "url": "implementationGuide", "extension": [ { "url": "name", "valueString": "UKCore.R4.02.00.00" },{ "url": "version", "valueString": "2.0.0" } ] } ] }
status
"status": "active"
kind
For APIM FHIR endpoints this MUST be instance
"kind": "instance"
software
For APIM FHIR endpoints this is the API Name and verson of the API.
"software": { "name": "EPS NextGen", "version": "1.2.4-alpha", "releaseDate": "2021-07-21T00:00:00+00:00" }
fhirVersion
For APIM FHIR R4 endpoints this MUST be 4.0.1
"fhirVersion": "4.0.1"
format
MUST be provided. This is populated according to serialisation policies. Serialisation
"format": [ "application/fhir+json", "application/fhir+xml" ]
implementationGuide
List of FHIR Implementation Guides followed by the API. For NHS Digital APIM endpoints this MUST include:
"implementationGuide": [ "https://simplifier.net/guide/nhsdigital" ],
rest
This is required for all APIM FHIR endpoints.
rest.security
Only populated if the endpoint is secured using APIM Apigee security.
SHOULD include the url of the OAuth2/Apigee endpoint. Add extension http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris to profile.
"security": { "extension": [ { "url": "http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris", "extension": [{ "url": "token", "valueUri": "https://oauth2.nhs.uk/token" },{ "url": "authorize", "valueUri": "https://oauth2.nhs.uk/authorize" },{ "url": "manage", "valueUri": "https://oauth2.nhs.uk/authorizations/manage" }] } ] }
For APIM FHIR endpoints this should be populated as follows:
"security": { "service": [ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/restful-security-service", "code": "OAuth", "display": "OAuth2 Token" } ] } ] }
rest.resource
All the resources supported by the endpoint MUST be listed together with the FHIR profile they conform to. This applies to all FHIR Exchange methods.
"resource": [ { "type": "CommunicationRequest", "profile": "https://fhir.nhs.uk/StructureDefinition/NHSDigital-CommunicationRequest" } ]
messaging
MUST be populated if FHIR Messaging is used. This MUST list all the FHIR MessageDefinitions the endpoint supports.
"messaging": [ { "supportedMessage": [ { "mode": "receiver", "definition": "https://fhir.nhs.uk/MessageDefinition/prescription-order" }, { "mode": "receiver", "definition": "https://fhir.nhs.uk/MessageDefinition/dispense-notification" } ] } ]