This page is part of the Structured Data Capture FHIR IG (v1.6: STU 2 Ballot 1) based on FHIR v1.6.0. . For a full list of available versions, see the Directory of published versions

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

12 Code System

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

12.0.1 Scope and Usage

This profile sets expectations for use of the CodeSystem 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 CodeSystem. 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.

12.0.2 Boundaries and Relationships

This profile relies on the use of the codesystem-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 r rendering-extensions which defines rendering information for display names and labels of codes.

12.0.3 Content

Profiles:
SDC-CodeSystem Defines how CodeSystem is used to reflect code lists found in data element defintions and form definitions to be used within the ONC's Structured Data Capture standard.

12.0.4 Example List

This profile can be found as contained resources within the following examples:

SDC - Combination XML JSON Set of several examples - medication, AHRQ and NCI forms

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.