Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - 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

Example OperationDefinition/CapabilityStatement-conforms (Narrative)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

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

Note that this is the formal definition for the conforms operation as an OperationDefinition on CapabilityStatement. See the Operation documentation

URL: [base]/CapabilityStatement/$conforms

Parameters

UseNameCardinalityTypeBindingDocumentation
INleft0..1canonical

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

INright0..1canonical

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

INmode0..1code

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

OUTissues1..1OperationOutcome

Outcome of the CapabilityStatement test

OUTunion0..1CapabilityStatement

The intersection of the functionality described by the CapabilityStatement resources

OUTintersection0..1CapabilityStatement

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.