Overview
| User | Use Case | |
|---|---|---|
| Authors | ||
Editors of the International Edition | The requirement to consistently apply historical relationships to inactivated components in the International Edition |
The requirement to consistently apply historical relationships to reactivated components in the International Edition |
Reactivation of a previously inactivated component
Assess impact on International Refsets and update as required
Editors of Extensions (This includes Consultant Terminologists) | Management of historical associations from International release and possible impact on local inactivations/reactivations The requirement to consistently apply historical relationships to inactivated components in the Local Edition The requirement to consistently apply historical relationships to reactivated components in the Local Edition | |
| Release Management Team | SNOMED International Management of inactivation | Assess the need for retrospective assessment of inactivated/reactivated components in the International Release of SNOMED CT Develop a process for retrospective correction of inactivation historical relationships |
Provision of appropriate Editorial guidance |
for |
SNOMED International and Local |
NRC editors on inactivation/reactivation Consideration of the impact on Language editions Development of quality assurance routines/algorithms Assess impact of inactivated/reactivated components on International Refsets and mappings and update as required Process for notifying the community of practice about upcoming inactivation/reactivation |
Authors of Extensions
Management of historical associations from International release and possible impact on local inactivations
Inactivation of local extension components
Reactivation of local extensioncomponents |
| Local management of inactivation | Development of quality assurance routines/algorithms Assess impact of inactivated/reactivated components on national Refsets, mappings and data sets Process for notifying the community of practice about upcoming inactivation/reactivation |
Management of component inactivation with new releases of SNOMED CT
- Identifying impacts of components which have been activated
- Resolving inactivation issues (e.g. identifying replacements)
| Developers | Terminology server producers | Development of services to identify inactivated/reactivated concepts and how to manage their replacements Development of services to manage the impact of inactivated/reactivated Refsets , mappings and Datasets where these services form a part of the terminology server services |
| Producers of clinical systems | Development of queries over historical data to identify inactivated components and their replacements which can be presented to end users and systems in real time Development of robust audit trails which ensure a complete concept history which may include textual supporting information Development of appropriate notification to end users of clinical records where concept inactivation may impact the meaning of existing records | |
| End Users | Clinical end users | How to manage the apparent loss of frequently used concepts How to manage the impact of component inactivation/reactivation on personal/local audit |
| Data analysts/Information managers | How to manage component inactivation/reactivation to ensure a robust history mechanism for traceability and data healing How to manage changes to component status as a result of inactivation/reactivation in current live data collection and discovery activities How to manage the impact of component inactivation/reactivation on mappings |
Component Inactivation
When components of SNOMED CT are deemed out of scope or inappropriate for a particular SNOMED CT Edition, it is the responsibility of SNOMED CT authors to inactivate the component, specify an appropriate reason for inactivation and in some cases, identify proper replacements.
...