STU 2 Ballot

This page is part of the Structured Data Capture - Data Element Exchange Specification (v1.6: STU 2 Ballot 1) based on FHIR v1.6.0. The current version which supercedes this version is 2.0. For a full list of available versions, see the Directory of published versions

4 Value Set

This is a pre-release of a future version of SDC-DE (expected to be STU 2). The current version is STU 2.
For a full list of available versions, see the Directory of published versions .

4.0.1 Scope and Usage

This profile sets expectations for use of the ValueSet resource within the Structured Data Capture implementation guide. This includes identifying which core elements and extensions must be supported.

For the purposes of this profile, Supported means that clients SHALL be capable of processing the element/extension and use the information to control the display and information capture associated with the ValueSet. It means that servers SHALL be capable of persisting those elements and returning them in response to requests. For systems rendering Questionnaires, these Supported elements and extensions must be supported in the rendering of allowed choices associated with questions.

4.0.2 Boundaries and Relationships

This profile relies on the use of the valueset-extensions profile which defines a number of less common properties for value sets, several of which are mandated for this profile. It also makes use of the rendering-extensions which defines rendering information for display names and labels of codes.

4.0.3 Content

Profiles:
SDCDE-ValueSet Defines how ValueSet is used to reflect code lists found in data element defintions for exchange and maintenance between data element registries according to requirements established by the ONC's Structured Data Capture standard.

4.0.4 Example List

Examples of this profile can be found as contained resources within the following examples:

SDC-Gender XML JSON Patient gender represented according to SDC rules

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.