This page is part of the FHIR Specification (v1.1.0: STU 3 Ballot 1). 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 is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.
This is the narrative for the resource. See also the XML or JSON format.
(Requirements Definition)
Published: 2014-07-06 (draft)
Published by: U.S. Office of the National Coordinator (ONC)
This profile defines the expected capabilities of the SDC Data Element Curator role when conforming to the S&I Framework's Structured Data Capture FHIR Data Element Exchange implementation guide. This role is responsible for defining and updating data elements stored in a repository.
FHIR Version: | 1.1.0 |
---|---|
Supported formats: | xml, json |
The primary focus of the curator is the definition and maintenance of DataElements. However, ValueSets must also be supported to allow definition of coded data elements. Some data elements will choose to maintain value sets as 'contained' resources, meaning the value set exists only in the context of the data element and cannot be referenced or maintained without also updating the data element. However, systems should support value set re-use across data elements. (Version-specific referencing can be used to avoid value sets from changing independent of the referencing Questionnaire.)
Security:
Implementations must meet the general security requirements documented in the SDC implementation guide.
Resource | Search | Read | Read Version | Instance History | Resource History | Create | Update | Delete |
---|---|---|---|---|---|---|---|---|
DataElement (Profile) | SHALL | SHALL | SHALL | SHALL | SHALL | SHALL | MAY | |
ValueSet (Profile) | SHALL | SHALL | SHALL | SHALL | SHALL | SHALL | MAY |
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.