View Source

Section 4.2.3 Data Entry Context, noted that the environment or use case in which data is entered may:

Determine the range of that can rationally be entered
- For example, limiting the range of concepts that can be used for diagnoses to subtypes of 64572001 |Disease (disorder)|.
Significantly affect the interpretation of concepts and other data entered
- For example, entry of a subtype of 64572001 |Disease (disorder)| in a "Family History" section should be interpreted as a family history of that disorder, rather than a diagnosis suffered by the subject of the record.

are links between terminology components and information model artifacts, such as EHR structures and data entry contexts. There are two types of terminology bindings, and . summarizes the characteristics of these two types of terminology binding.

Summary of the Characteristics of Different Types of Terminology Binding

Value Set Binding

Meaning Binding

Definition

Practical use when applied to a

To constrain the range of (or ) that can be entered in a particular data entry context.

To specify how the meaning of a or is affected by the data entry context in which it is entered.

Example

To constrain the values entered in a field labeled "Surgical operation" to concepts that represent subtypes of surgical procedures.

To specify that when a "disorder" concept is entered in a family history data entry form, this represents a "family history" of this disorder.

Representation

Each SNOMED CT should be represented using an as specified in the Expression Constraint Language - Specification and Guide.

Each SNOMED CT could be represented using a single SNOMED concept.

Example

The expression constraint below only matches concepts that are subtypes of ..

<387713003 |Surgical procedure (procedure)|

A data entry context to which this constraint is applied would only permit the entry of concepts representing surgical procedures. If a user searches for terms matching "append" surgical procedure concepts such as , , and

should be available for selection. However, other concepts with matching terms such as

,

, and

should not be available in this data entry context.

The expression template below indicates that when a subtype of the concept is entered used in the family history data entry context, it should be treated as the value of the attribute.

If the concept is entered in this data entry context, that concept becomes the value of the associated finding attribute as shown in the following expression. The resulting expression is equivalent to the definition of the concept.

416342005 |Procedure related observable (observable entity)|

The following subsections describe ways in which each of these types of terminology binding can be used to represent data entry contexts.