Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

dummy

...

DATS

schemas

context (vocabularies)

...

Name (Working term)

...

Area of coverage

...

DATS

schemas

context (vocabularies)

...

Spatial and geographic

...

Information required for describing geographic information and services (e.g. ISO 19115)

...

EX_Extent element: generic GML coordinate geometry (includes SRS), WGS84 bounding box, or location identifier; multiple locations can be specified. Bounding box is most commonly used.  MD_SpatialRepresentation for documenting raster geometries.

...

Location.position (WGS-84 latitude / longitude / altitude)

Location.address

location

...

Place

(reusing GeoJSON)

...

Temporal

...

Information required for describing time-based characteristics of the data (e.g. the date of publication, a time stamp)

...

Datatypes date, time, datetime and instant (instantdatetimedatatime)

(references XML Schema)

...

DateInfo

...

Contributors

...

People, organisations, agents, ...

...

...

Person

Organization

...

Process

...

Description of processes, workflows, transformations, ...

...

Healthcare Specific:

...

Activity

Study

DataAcquisition

DataAnalysis

...

Provenance

...

(Related to process) Descriptions of the process used to create/produce/transform/publish data

...

Versioning is via protocol

Transformations using Reference resource

...

Activity

Study

DataAcquisition

DataAnalysis

...

Vocabularies / lists / classifications

...

Enumerated lists of terms that may be applied to content being described.

...

(Can) cover a broad range of code systems, from internal enumerations to SNOMED CT, LOINC, RxNorm, ICD-10, etc.

RDF supports Concept URI's.  JSON and XML support the ISO 21090 CD datatype

...

Annotation

...

Resources

...

Objects being described or referenced. May include datasets, but also publications, software, code, other metadata, ...

...

...

Specific for biomedical datasets:

...

Datasets

...

Specific descriptions of datasets as primary objects

...

Group will be enhanced in the R4/R5 path

...

Observation / Capture

...

Classes/objects that describe the processes by which data is created, generated, captured, transformed. (QUESTION: Is this the same as Provenance/Process?)

...

Data

...

The logical structure of the data being described - variables, units of measurement, concepts, sample units and populations, records, datum(s), cells. (May or may not be a subset of datasets)

...

clinical care artifacts, some pre-defined aggregations

See: Resource List

...

Storage

...

The physical representation of the data (files, formats, locations, ...)

...

Formats:  XML, JSON, RDF

Media resource

Attachment resource

(Use Mime Type)

Specification does notprescribe storage formats, names, etc 

...

DataDistribution

DataRepository

...

Access

...

Who can access the data and how

...

Access

ConsentInfo

...

Administrative / core / ...

...

Foundational classes for use in building the specification - e.g. identification, versioning, primitives

...

IdentifierInfo

AlternateIdentifierInfo

...

FHIR supports both a constraint mechanism – subsetting possible values and a tag/value extension mechanism for adding new elements. See: https://www.hl7.org/fhir/STU3/profiling.html

These fall under the general rubric of "Profile"

...

The entries below trash can probably be removed.