Release 4 Snapshot 3: Connectathon 32 Base

This page is part of the Snapshot #3 for FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0 R5 , released to support Connectathon 32 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4

Example OperationDefinition/CapabilityStatement-implements (Narrative)

Using Codes Code Systems
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 4.3.14.379 or Turtle format.

Note that this is the formal definition for the implements operation as an OperationDefinition on CapabilityStatement. See the Operation documentation Code System http://terminology.hl7.org/CodeSystem/communication-topic

URL: [base]/CapabilityStatement/$implements

URL: [base]/CapabilityStatement/[id]/$implements

Parameters

This is a code system defined by the FHIR project. This Code system is used in the following value sets: ValueSet: CommunicationTopic (Codes describing the purpose or content of the communication.) ValueSet: CommunicationTopic (Codes describing the purpose or content of the communication.) 4.3.14.379.1 Content 4.3.14.379.2 CommunicationTopic prescription-refill-request Report Labs phone-consult Summary Report Source
Patient Care Work Group Use   Maturity Level : 1 Draft Name Use Context : Any Cardinality Summary Type Defining URL: http://terminology.hl7.org/CodeSystem/communication-topic Binding Version: 4.0.1 Documentation
Name: IN CommunicationTopic server Title: 0..1 CommunicationTopic canonical Definition:

Codes describing A canonical reference to the purpose or content of server capability statement - use this if the communication. implements is not invoked on an instance (or on the /metadata end-point)

Committee: Patient Care
Work Group
OID: IN 2.16.840.1.113883.4.642.4.1078 (for OID based terminology systems) client Source Resource 0..1 XML / JSON canonical

Codes describing A canonical reference to the purpose or content of client capability statement - use this if the communication. This code system http://terminology.hl7.org/CodeSystem/communication-topic defines implements is not invoked on an instance (or on the following codes: /metadata end-point)

Code Display Definition
Prescription Refill Request IN The purpose or content of the communication is a prescription refill request. progress-update resource Progress Update 0..1 The purpose or content of the communication is a progress update. report-labs CapabilityStatement The purpose or content of the communication is to report labs. appointment-reminder Appointment Reminder

The purpose or content of the communication is an appointment reminder. client capability statement, provided inline

OUT Phone Consult return The purpose or content of the communication is a phone consult. 1..1 summary-report OperationOutcome The purpose or content of the communication is a summary report.
  See the full registry of code systems defined as part of FHIR.

Explanation Outcome of the columns that may appear on this page: CapabilityStatement test

Level
A few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.

The source of operation does not perform a full conformance check; in particular it does not check that the definition of profiles align. It merely checks that the code (when behaviors the value set draws in codes defined elsewhere) Code The code (used client wishes to use are provided Technically, this operation is implemented as the code follows:

  • The server's capability statement must have an entry for each resource in the client's capability statement
  • The server's resource instance). If the code is support must have matching flags for updateCreate, conditionalCreate, conditionalRead, conditionalUpdate, conditionalPatch, conditionalDelete, searchInclude, searchRevInclude
  • The server's capability statement must have a matching interaction for each interaction in italics, this indicates that the code is client capability statement (whether or not selectable ('Abstract') Display it is on a resource)
  • The display (used server's capability statement must have a search parameter with matching name and definition for any search parameters in the display element of client capability statement
  • The server must have an operation definition with a Coding ). matching reference for any operations in the client capability statement

If there the capability statements match by these rules, then the return value is a 200 OK with an operation outcome that contains no display, implementers should not simply display issues with severity >= error. If the code, but map capability statement doesn't match, the concept into their application Definition return value is a 4xx error, with an OperationOutcome with at least one issue with severity >= error

An explanation of

 

 

Usage note: every effort has been made to ensure that the meaning examples are correct and useful, but they are not a normative part of the concept Comments Additional notes about how to use the code specification.