Current Build

Переводит команда Health Samurai. Приглашаем поучаствовать в русификации стандарта FHIR: GitHub, Email.

Operation-codesystem-lookup

Vocabulary Work GroupMaturity Level: N/ABallot Status: InformativeCompartments: Not linked to any defined compartments

Это описательная часть ресурса. См. также в формате XML, JSON или Turtle.


Concept Look Up & Decomposition

OPERATION: Concept Look Up & Decomposition

The official URL for this operation definition is:

http://hl7.org/fhir/OperationDefinition/CodeSystem-lookup

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

URL: [base]/CodeSystem/$lookup

Parameters

UseNameCardinalityTypeBindingDocumentation
INcode0..1code

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

INsystem0..1uri

The system for the code that is to be located

INversion0..1string

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

INcoding0..1Coding

A coding to look up

INdate0..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.

INdisplayLanguage0..1code

The requested language for display (see $expand.displayLanguage)

INproperty0..*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: url, name, version (code system info) and code information: display, definition, designation, parent and child, and for designations, lang.X where X is a designation language code. Some of the properties are returned explicit in named parameters (when the names match), and the rest (except for lang.X) in the property parameter group

OUTname1..1string

A display name for the code system

OUTversion0..1string

The version that these details are based on

OUTdisplay1..1string

The preferred display for this concept

OUTdesignation0..*

Additional representations for this concept

OUTdesignation.language0..1code

The language this designation is defined for

OUTdesignation.use0..1Coding

Код, описывающий, каким образом будет использоваться это обозначение

OUTdesignation.value1..1string

The text value for this designation

OUTproperty0..*

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

OUTproperty.code1..1code

Identifies the property returned

OUTproperty.value0..1code

The value of the property returned

OUTproperty.description0..1string

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

OUTproperty.subproperty0..*

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

OUTproperty.subproperty.code1..1code

Identifies the sub-property returned

OUTproperty.subproperty.value1..1code

The value of the sub-property returned

OUTproperty.subproperty.description0..1string

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

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.


 

 

Примечание к использованию: мы очень стараемся приводить корректные и полезные примеры, но нормативно они не являются частью спецификации.