Conformance-sdc-de-registry

Allows a user to search for existing data elements

Allows retrieval of a specific known data element

Allows retrieval of a specific version of a data element

Allows review of changes to a data element over time

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

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.

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

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.

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

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

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

Allows review of changes to a value set over time

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

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

Allows verification that a value set is valid prior to submission - useful for some workflows.

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.