Page History
In some cases, an implementer may need to add additional information about each member of a subset. This information may be additional textual information or additional coded values.
Annotating each member of a subset with additional information can facilitate the processing of subset members and assist in meeting the functional requirements of a system.
| Requirement | Description | Example Use | Reference Set |
|---|---|---|---|
A set of components with free text annotations | A set of concepts, descriptions or relationships each annotated with a free text note | Displaying a textual note for each concept in a list. For example, displaying an advisory note on how to request a particular procedure. | 5.5. Annotation Reference Set |
| A set of components with coded annotations
| A set of concepts, descriptions or relationships each annotated with a reference to another component | Marking each concept with a specific coded value to support automated processing of a list. For example, marking each inactive concept with a code that indicates the reason they were inactivated | 5.6. Attribute Value Reference Set
|
| Specifying whether descriptions are preferred or acceptable in a given dialect, care setting or clinical context. | 5.7. Language Reference Set |
For more detailed use case examples, please refer to the following sections:
- 3.2.2.1. Linking Concepts to Web Resources
- 3.2.6.3.1. Representing Reasons for Component Inactivation
- 3.2.5.1. Indications of Acceptability of Descriptions
Overview
Content Tools
Apps