This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4
This is the narrative for the resource. See also the XML, JSON or Turtle format.
Note that this is the formal definition for the find-matches operation as an OperationDefinition on CodeSystem. See the Operation documentation
URL: [base]/CodeSystem/$find-matches
URL: [base]/CodeSystem/[id]/$find-matches
Parameters
The system in which composition is to be performed. This must be provided unless the operation is invoked on a code system instance
The version of the system for the inferencing to be performed
One or more properties that contain information to be composed into the code
Identifies the property provided
The value of the property provided
Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)
Identifies the sub-property provided
The value of the sub-property provided
Whether the operation is being used by a human ('false'), or a machine ('true'). If the operation is being used by a human, the terminology server can return a list of possible matches, with commentary. For a machine, the server returns complete or partial matches, not possible matches. The default value is 'false'
Post-coordinated expressions are allowed to be returned in the matching codes (mainly for SNOMED CT). Default = false
Concepts returned by the server as a result of the inferencing operation
A code that matches the properties provided
One or more properties that contain properties that could not be matched into the code
Identifies the property provided
The value of the property provided
Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)
Identifies the sub-property provided
The value of the sub-property provided
Information about the quality of the match, if operation is for a human
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.