Concept Look Up & Decomposition

$lookupoperation

Given a code/system, or a Coding, get additional details about the concept, including definition, status, designations, and properties. One of the products of this operation is a full decomposition of a code from a structured terminology. When invoking this operation, a client SHALL provide both a system and a code, either using the system+code parameters, or in the coding parameter. Other parameters are optional

TypeInstance

Implementation Notes

Note that the $lookup operation is more than just a code system search - the server finds the concept, and gathers the return information from the underlying code system definitions.

Metadata

ID
CodeSystem-lookup
Applies to Resources
CodeSystem

Input Parameters (8)

code0..1code

The code that is to be located. If a code is provided, a system must be provided

system0..1uri

The system for the code that is to be located

version0..1string

The version of the system, if one was provided in the source data

coding0..1Coding

A coding to look up

date0..1dateTime

The date for which the information should be returned. Normally, this is the current conditions (which is the default value) but under some circumstances, systems need to acccess this information as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.

displayLanguage0..1code

The requested language for display (see CodeSystem.concept.designation.language)

property0..*code

A property that the client wishes to be returned in the output. If no properties are specified, the server chooses what to return. The following properties are defined for all code systems: name, version (code system info) and code information: display, designation, and lang.X where X is a designation language code. These properties are returned explicitly in named out parameters with matching names, or in designations. In addition, any property codes defined by [this specification](codesystem.html#defined-props) or by the CodeSystem ([CodeSystem.property.code](codesystem-definitions.html#CodeSystem.property)) are allowed, and these are returned in the out parameter ```property```

useSupplement0..*canonical

Supplements to take into account when performing the $lookup operation. The supplements must be for the same CodeSystem. By default, supplements for the code system are not automatically included except where they provide additional designations that may be indicated by, for example, the displayLanguage parameter

Output Parameters (6)

name1..1stringrequired

A display name for the code system

version0..1string

The version that these details are based on

display1..1stringrequired

The preferred display for this concept

definition0..1string

A statement of the meaning of the concept from the code system

designation0..*

Additional representations for this concept

language0..1code

The language this designation is defined for

use0..1Coding

A code that details how this designation would be used

additionalUse0..*Coding

Additional codes that detail how this designation would be used (if there is more than one)

value1..1stringrequired

The text value for this designation

property0..*

One or more properties that contain additional information about the code, including status. For complex terminologies (e.g. SNOMED CT, LOINC, medications), these properties serve to decompose the code

code1..1coderequired

Identifies the property returned

value0..1Element

The value of the property returned

description0..1string

Human Readable representation of the property value (e.g. display for a code)

source0..1canonical

If information from a supplement is included as a property (e.g. any additional property or property value), then this parameter must assert the url of the supplement.

subproperty0..*

Nested Properties (mainly used for SNOMED CT decomposition, for relationship Groups)

code1..1coderequired

Identifies the sub-property returned

value1..1Elementrequired

The value of the sub-property returned

description0..1string

Human Readable representation of the sub-property value (e.g. display for a code)

source0..1canonical

If information from a supplement is included as a subproperty (e.g. any additional subproperty or subproperty value), then this parameter must assert the url of the supplement.