Release 4B R5 Final QA

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-draft-final: Final QA Preview for R5 - STU see ballot notes ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Operation-capabilitystatement-conforms

Example OperationDefinition/CapabilityStatement-conforms (Narrative)

FHIR Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : Not linked to any defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format.

Conforms OPERATION: Conforms The official URL for this operation definition is: http://hl7.org/fhir/OperationDefinition/CapabilityStatement-conforms This operation asks the server to check that it implements all the resources, interactions, search parameters, and operations

Note that this is the client provides in its capability statement. The client provides both capability statements by reference, and must ensure that all formal definition for the referenced resources are available to conforms operation as an OperationDefinition on CapabilityStatement. See the conformance server Operation documentation

URL: [base]/CapabilityStatement/$conforms

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN left 0..1 canonical

A canonical reference to the left-hand system's capability statement

IN right 0..1 canonical

A canonical reference to the right-hand system's capability statement

IN mode 0..1 code

What kind of comparison to perform - server to server, or client to server (use the codes 'server/server' or 'client/server')

OUT issues 1..1 OperationOutcome

Outcome of the CapabilityStatement test

OUT union 0..1 CapabilityStatement

The intersection of the functionality described by the CapabilityStatement resources

OUT intersection 0..1 CapabilityStatement

The union of the functionality described by the CapabilityStatement resources

The operation performs a full comparison of the functionality described by the two capability statements, including the profiles and value sets they reference, and also including concept maps and structure maps.

The full execution of this operation is still a matter of research, but it is intended to support comparison of systems to see if they will interoperate

If the capability statements can be successfully compared, then the return value is a 200 OK with an OperationOutcome along with intersection and union capability statements. The operation outcome can contain errors relating to differences between the capability statements. If the capability statements cannot be compared, because dependencies cannot be located, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity >= error

 

 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.