...
Disallow conflicting representations by disallowing use of information model elements, i.e. cardinality 0..0.
Example:
Impact: would require post-coordination or likely extensive local, national, or international pre-coordination.
Meaning is provided by a mutually constrained combination of multiple SNOMED CT encoded information model elements
Impact: all these options would require software implementing run-time constraint checking between multiple information model elements
Option 2
Allow use of information model element only if there is no "corresponding" (how?) SNOMED CT attribute in a concept definition of a concept used as a value in another information model element.
...
This pattern does e.g. not allow concepts which are primitive children of concepts with non-IsA relationships and thus seems overly restrictive.
Option X+
There are other options for guaranteeing consistency between multiple SNOMED CT-valued information model elements, and hence interoperability:
- the value of one information model element, if it does not exist, is assigned by extracting a value from a SNOMED CT attribute from a concept which is a value of another information model element.
- the value of one information model element, if it does not exist, is assigned or asserted to be equal to or subsumed by an expression which is a templated combination of multiple other information model elemetn values, .
Meaning is provided by a mutually unconstrained combination of multiple SNOMED CT encoded information model elements
...