The formal description of a single piece of information that can be gathered and reported.

Often called a clinical template.

An absolute uri that is used to identify this element when it is referenced in a specification, model, design or an instance (should be globally unique URI, and an be urn:uuid: or urn:oid:).

Formal identifier that is used to identify this data element when it is represented in other formats, or referenced in a specification, model, design or an instance.

Typically, this is used for values that can go in a v3 II data type.

The identifier that is used to identify this version of the data element when it is referenced in a StructureDefinition, Questionnaire or instance. This is an arbitrary value managed by the definition author manually.

There may be multiple resource versions of the data element that have this same identifier. The resource version id will change for technical reasons, whereas the stated version number needs to be under the author's control.

N/A.

The term used by humans to refer to the data element. Should ideally be unique within the context in which the data element is expected to be used.

This may be similar to the question used to prompt someone for a data element value, but the purpose is communicating about the data element, not asking the question. (Refer to the 'question' element for the latter.).

The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of data element definitions.

A flag to indicate that this search data elemnt definition is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.

Allows filtering of search data element definitions that are appropriate for use vs. not.

The status of the data element.

Allows filtering of data elements that are appropriate for use vs. not.

The date that the status for this business version of the data element became effective. (I.e. Date the draft was created, date element became active or date element became retired).

This refers to the "business" version - the DataElement.version which changes based on business processes. It does not refer to the date of the RESTful version which is part of the resource metadata.

A copyright statement relating to the definition of the data element. Copyright statements are generally legal restrictions on the use and publishing of the details of the definition of the data element.

The copyright statement does not apply to values for the data element, only to its definition.

The name of the individual or organization that published the data element.

Helps establish the "authority/credibility" of the data element. May also allow for contact.

Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.

Contacts to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number (tel:), etc.

The name of an individual to contact regarding the data element.

If there is no named individual, the telecom is for the organization as a whole.

Contact details for individual (if a name was provided) or the publisher.

Identifies how precise the data element is in its definition.

Allows determining whether the degree of comparability of data element instances - less granular data elements result in data that is less comparable (or at least requires more work to compare).

Identifies a specification (other than a terminology) that the elements that make up the DataElement hav some correspondance with.

An Internal id that is used to identify this mapping set when specific mappings are made on a per-element basis.

The specification is described once, with general comments, and then specific mappings are made that reference this declaration.

An absolute URI that identifies the specification that this mapping is expressed to.

A formal identity for the specification being mapped to helps with identifying maps consistently.

A name for the specification that is being mapped to.

Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usage.

Defines the structure, type, allowed values and other constraining characteristics of the data element.

For simple data types there will only be one repetion. For complex data types, multiple repetitions will be present defining a nested structure using the "path" element.