This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
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.
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.
Profiles: | |
SDC-ValueSet | Defines how ValueSet 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. |
SDC-ValueSet AHRQ_Medication_Q1 | XML | JSON | The answer list for question 1 on the AHRQ 'Medication or Other Substance' form |
Additional examples of this profile can be found as contained resources within the following examples:
C-CDA-Gender | XML | JSON | FHIR Gender with mapping to C-CDA |
SDC - Combination | XML | JSON | Set of several examples - medication, AHRQ and NCI forms |
SDC-LOINC AHRQ | XML | JSON | LOINC perspective on the AHRQ form found in the SDC - Combination set of questionnaires |
SDC-LOINC USSG Family History | XML | JSON | LOINC US Surgeon General family history including data elements & value sets. Note: This example isn't strictly valid against SDC as data elements do not have definitions and don't include mappings to SDC-approved specificaitons for auto-population |
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.