Page History
...
SNOMED International creates precoordinated content in accordance with the MRCM. For postcoordinated content, extensions should review the MRCM. If the MRCM does not specify that a particular value is allowed for a given content type (e.g. using an observable entity value for |Component| in a postcoordinated expression), then it must not be used in that content type (e.g. postcoordinated expressions). The MRCM rules for postcoordination must be strictly followed. This is important for interoperability, being able to query the resulting content consistently, etc. However, the MRCM does provide the option for extensions to extend or adapt the rules in a controlled way if required (see the last section of 6. Considerations). This includes expanding the ranges and/or adding new attributes where required. This needs to be done carefully to ensure consistency and data integrity between editions.
There are special cases in the MRCM where an attribute may have two rows. This situation is caused by a new cardinality rule: a row for existing/legacy SNOMED CT content and a row for newly created content. The row that is applicable to new content will be marked by a "[New]" notation.
See MRCM Maintenance ProcessProcess for the maintenance of MRCM rules.
| Warning | ||
|---|---|---|
| ||
SNOMED CT relies on the rules for usefulness to avoid excessive precoordination (see Scope section of Editorial Guide). Approved precoordination patterns have been created and are available at: Pre-coordination Naming Patterns Project. For additional information about the fields used in precoordination, see: What the fields in the Pre-coordination Naming Patterns JIRA Project mean. |
...
Overview
Content Tools
Apps