Structured Data Capture - Data Element Exchange 2.0 (STU2)

This page is part of the Structured Data Capture - Data Element Exchange Specification (v2.0: STU 2) based on FHIR R3. This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

2.1 SDC DE Registry

Format(s):

Narrative view

SDC Data Element Manager

(Requirements Definition)

http://hl7.org/fhir/us/sdcde/CapabilityStatement/sdc-de-registry 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 Manager role when conforming to the S&I Framework's Structured Data Capture FHIR implementation guide. This role is responsible for defining maintaining a repository of data elements used in designing forms, profiles and templates in support of SDC use-cases, including the pre-population and auto-population of forms.

General

FHIR Version: $ver$
Supported formats: xml, json

REST behavior

The primary focus of the repository is the definition of DataElements. However, ValueSets and CodeSystems 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 summary

Resource Search Read Read Version Instance History Resource History Create Update Delete
DataElement (Profile) Yes Yes Yes Yes Yes Yes Yes
ValueSet (Profile) Yes Yes Yes Yes Yes Yes Yes
CodeSystem (Profile) Yes Yes Yes Yes Yes Yes Yes


DataElement

Interactions

Name Description
  search-type

Allows a user to search for existing data elements
  read

Allows retrieval of a specific known data element
  vread

Allows retrieval of a specific version of a data element
  history-instance

Allows review of changes to a data element over time
  create

Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.
  update

Allows maintaining data elements while creating and editing forms. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new data element (and potentially the retiring of the existing data element). Servers may also limit who can change particular data elements.
  delete

Allows removal of an existing data element. Servers may choose to not support deletions or may limit deletions to data elements meeting certain requirements. E.g. only elements with a status of draft or only elements that have been retired for at least two years, etc.

Search

Supported Includes: DataElement.binding.valueSet

Parameter Type Definition & Chaining
code token
context token
date date
description string
identifier token
name string
publisher string
status token
stringency token
url uri
version string
meaning token
objectClass token
property token


ValueSet

Interactions

Name Description
  search-type

Allows discovery of existing value sets for use in authoring data elements
  read

Allows retrieval of a specific value set referenced within a data element
  vread

Allows retrieval of a historical version of a value set as referenced within a data element
  history-instance

Allows review of changes to a value set over time
  create

Allows definition of a new value set used by one or more data elements
  update

Allows existing value sets referenced by one or more data elements to be maintained
  delete

Not all servers will support deletion of value sets. Status change to 'retired' will be more typical, though deletion of draft value sets may keep repositories cleaner.

Search

Supported Includes: ValueSet.compose.import

Parameter Type Definition & Chaining
code token
date date
description string
identifier token
name string
publisher string
reference string
status token
version token


CodeSystem

Interactions

Name Description
  search-type

Allows discovery of existing code systems for use in authoring data elements
  read

Allows retrieval of a specific code system referenced within a data element
  vread

Allows retrieval of a historical version of a code system as referenced within a data element
  history-instance

Allows review of changes to a code system over time
  create

Allows definition of a new code system used by one or more data elements
  update

Allows existing code systems referenced by one or more data element value sets to be maintained
  delete

Not all servers will support deletion of code systems. Status change to 'retired' will be more typical, though deletion of draft code systems may keep repositories cleaner.

Search

Supported Includes: ValueSet.compose.import

Parameter Type Definition & Chaining
code token
context token
date date
description string
identifier token
name string
publisher string
status token
system uri
url uri
version token