STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

C.1.0 Structured Data Capture Data Element Exchange

C.1.0.1 Scope and Usage

This profile is a placeholder and is not complete. It will eventually set expectations for the capability of data element registry systems as well as systems that create and curate data elements. It expands on the expectations of the base SDC DataElement profile by adding DataElement properties relevant for maintenance of data elements, rather than merely what is sufficient to allow a data element to be referenced within a form. Guidance found within that profile also applies to this one.

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 DataElement. It means that servers SHALL be capable of persisting those elements and returning them in response to requests.

C.1.0.2 Boundaries and Relationships

This profile relies on the use of a number of other profiles, some required, others available for use "when necessary":

  • datalement-11179 which defines extensions for ISO-11179-specific concepts, such as ObjectClass and Property
  • element-extensions which defines extensions describing constraints on the values for data elements. There are used here to constrain the allowed values for questions.
  • iso-21090 provides extensions for strings allowing the conveying of language and translation extensions which may be relevant in some environment

C.1.0.3 Content

Profiles:
SDCDE-DataElementSets expectations for data elements exchanged or maintained within data element registries according to requirements established by the structured data capture project
Examples:
SDC-Gender

Patient gender represented according to SDC rules