Overview

In this chaptersection, we present the key requirements of the SNOMED CT MRCM. These requirements are grouped into 'constraint requirements' and 'design requirements'.

...

Requirement D.2: Human readable
The MRCM must be computationally transformable into a representation that is human readable, to support human review, validation, education and understanding of the rules. Additional text explaining the rules further should be able to be added to each rule to further aid its understanding.

...

Requirement D.4: Support specified use cases
The MRCM must be useful in supporting the use cases described in Chapter 2, including the authoring and validation of SNOMED CT concepts, expressions, constraints and queries, Natural Language Processing natural language processing (NLP) and terminology binding.

Requirement D.5: Version history
The SNOMED CT concept model rules must be able to be changed between releases to fix identified issues and enhance future releases (in conjunction with clear editorial guidelines). As such, the MRCM must be versioned to retain a history of changes, and to enable the concept model to evolve gracefully over time.

...

• • Leverage the work that has already been performed to support common requirements, such as versioning and intensional constraint definition,
  • Make it easier for the SNOMED CT community to understand the design and correctly interpret the meaning of the MRCM rules,
  • Facilitate the easier adoption of the MRCM rules by existing SNOMED CT implementers, and
  • Allow common terminology services to be reused to support the implementation of the MRCM.

...