When defining the set of codes allowed for a given element there's actually more to do than just referencing the set of codes. There's also a question of defining the conformance expectations for how the referenced set of codes are expected to be used. I.e. Are implementations restricted to the set of codes specified, must they support all of the codes, etc.
| Requirement
|
When identifying the set of codes associated with an element, there's a need to identify the total set of codes that are potentially allowed to be sent, regardless of whether all implementations will support all codes.
|
| Rationale
|
- The 'allowed' set of codes defines the interoperability space for communicating. If you don't know what set of codes can potentially be sent, you can't interoperate
|
| MIF
|
mif-core-base.xsd/VocabularyValueSetBinding/baseValueSet
|
| Requirement
|
When identifying the set of codes associated with an element, there's a need to know what subset of those must be fully supported by implementations.
|
| Rationale
|
- When defining interoperability specifications, it's not always necessary for all implementations to support the complete set of codes. For example, pharmacists may capture procedures for things like smoking cessation training, but they're not likely to capture an appendectomy. There may however be a subset of codes that all implementers are expected to handle. This needs to be communicated in the specification
|
| MIF
|
mif-core-base.xsd/VocabularyValueSetBinding/minimumValueSet
|
| Requirement
|
When defining a constraint on an existing set of vocabulary, there's a need to differentiate between codes that are not supported (those outside the base value set) and will likely raise an error if transmitted and those that simply won't be processed but will not result in an error.
|
| Rationale
|
- Receiving a non-supported code is sometimes cause for an error while in other circumstances it might be safely ignored. It's essential for implementers to know the expected behavior.
|
| MIF
|
mif-core-base.xsd/VocabularyValueSetBinding/ignoredValueSet
|
| Requirement
|
When defining a set of codes for use in a specification, there's a need to differentiate whether the set of codes is considered exhaustive (i.e. all codes must come from the specified value set) or as the base preferred set that must be used if an appropriate code is available.
|
| Rationale
|
- Not all code systems or sets of code systems will necessarily fully encompass a domain space
- New concepts can arise that need to be communicated before a code is available in a standardized code system
|
| Methodology
|
Coding Strength
|
