2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 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

Conformance-sdc-de-curator

This is the narrative for the resource. See also the XML or JSON format.

SDC Data Element Curator

(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.

General

FHIR Version: 0.2
Supported formats: xml, json

REST behavior

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.

Summary

Resource Search Read Read Version Instance History Resource History Validate Create Update Delete
DataElement Yes Yes Yes Yes Yes Yes Yes Yes
ValueSet Yes 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, such as adding additional mappings, display names, etc. 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.
  validate

Allows a client to verify whether a particular new data element or revision of an existing data element would be accepted based on validation and other business rules. Useful for some workflows
  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.


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
  validate

Allows verification that a value set is valid prior to submission - useful for some workflows.
  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.

 

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.