Difference between revisions of "ValueSet FHIR Resource Proposal"
| Line 2: | Line 2: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents | + | This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
Latest revision as of 05:51, 22 May 2014
This page documents an Approved FHIR Resource Proposal
Contents
- 1 ValueSet
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Examples
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
ValueSet
Owning committee name
Vocabulary (Temporarily owned by FHIR Core)
Contributing or Reviewing Work Groups
- None
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
Value set allows definition of an allowed set of values for any coded element. It also supports the on-the-fly definition of code systems from which the content of those allowed values can be drawn. Finally, it supports operations converting expression-based definitions of sets of codes into enumerated lists. It includes support for all types of code systems - local and "standard", pre and post-coordinated, finite and infinite.
RIM scope
ValueSet is outside the RIM's scope, though the elements for a given code partially map to the ISO CD data type. Value Sets are more appropriately mapped to the MIF.
Resource appropriateness
Shared value sets are essential to healthcare interoperability. They have been in use within HL7 since v2 (though known as tables) and are a key part of HL7 v3. Each value set is maintained indepenendently and has its own id which applies whether dealing with the expanded or unexpanded version of the value set.
Expected implementations
Content sources
- HL7 v3 MIF
- CTS 2
- CDISC code lists
Examples
All the value sets defined for the resources themselves should provide a sufficient set.
Resource Relationships
Value Sets can include other ValueSet instances. ValueSets are referenced by Profiles. On occasion, a Coding might choose to reference the ValueSet (or expanded value set) it was drawn from via an extension.
Timelines
First DSTU
gForge Users
N/A
