This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Requirements-Value Set Content

From HL7Wiki
Revision as of 05:20, 27 November 2009 by Lmckenzi (talk | contribs) (New page: {{V3 Methodology Requirements}} Value set content defines an enumeration or expression that resolves to a set of codes from one or more code systems. ==Content== ==Filters== ==Qualifier...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Value set content defines an enumeration or expression that resolves to a set of codes from one or more code systems.

Content

Filters

Qualifiers

Requirement Valueset content that draws from code systems that support post-coordination needs to be able to indicate what types of qualifier relationships are allowed.
Rationale Post-coordination is complex and few systems can support (or want) all of the expressivity that post-coordination might allow. Therefore it is important to define what types of relationships can be used.
MIF mif-vocabulary-model.xsd/ValueSetVersion/allowedQualifiers


Requirement When identifying qualifiers, there's a need to identify what types of concepts are allowed as the target for a particular relationship.
Rationale When allowing qualifiers, it's not always sufficient to say "qualifier relationships of this type". For example, limiting which types of body sites can be communicated.
MIF mif-vocabulary-model.xsd/ValueSetVersion/allowedQualifiers/targetConcepts


Requirement When defining support for qualifier relationships, the value set must be able to assert conformance and cardinality constraints.
Rationale Concepts can have multiple qualifiers of the same type. However, systems may not be designed to handle multiple repetitions or may have limits on how many repetitions they can manage. In some cases, there might be a need for a certain minimum number of repetitions to be present. Similarly, the expectation for support of a particular qualifier might be optional, required, or even not permitted. And some systems might declare that they'll tolerate the presence of a given qualifier but will ignore it if present.
MIF
  • mif-vocabulary-model.xsd/ValueSetVersion/allowedQualifiers/@conformance
  • mif-vocabulary-model.xsd/ValueSetVersion/allowedQualifiers/@minimumMultiplicity
  • mif-vocabulary-model.xsd/ValueSetVersion/allowedQualifiers/@maximumMultiplicity


Requirement Valueset content that draws from code systems that support post-coordination needs to indicate whether the default assumption is that qualifiers not specifically referenced are allowed or not permitted.
Rationale It is not always convenient to explicitly list every qualifier association that is possible for a particular code system, but it is not safe to assume that non-mentioned qualifiers are allowed.
MIF mif-vocabulary-model.xsd/ValueSetVersion/@areBaseQualifiersUnlimited


Requirement Valueset content that draws from code systems that support post-coordination and where concepts can be represented in both post-coordinated and pre-coordinated form need to indicate whether the preference for representing a concept is using the pre-coordinated or the post-coordinated form.
Rationale While some systems might easily support both types of representations, for other types of communications it will be easier if there is only a single way a particular concept is represented in an exchange.
MIF mif-vocabulary-model.xsd/ValueSetVersion/@postCoordinationPreference