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 . Page versions: R3 R2

ISO 11179 Data Element Profile (Conformance Package)

Scope and Usage

This profile defines extensions that may be useful in exposing data elements from ISO 11179-conformant registries. The list of extensions is not currently complete - additional extensions would be required to support all required and optional 11179 elements. The set of define extensions will increase over time based on implementer interest. At some point, a full profile for 11179-conformant systems may be developed.

The list of defined extensions is as follows:

  • objectClass - specifies the Object_Class for a Concept_Element or the meaning of a Data_Element
  • property - specifies the Object_Class Property for a Concept_Element or the meaning of a Data_Element
Extensions:
11179-objectClassObject Class :

A concept that represents a set of ideas, abstractions, or things in the real world that can be identified with explicit boundaries and meaning and whose properties and behavior follow the same rules. It may be either a single or a group of associated concepts, abstractions, or things.

11179-propertyObject Class Property :

A quality common to all members of an object class. A property may be any feature that humans naturally use to distinguish one individual object from another. It is the human perception of a single quality of an object class in the real world. It is conceptual and thus has no particular associated means of representation by which the property can be communicated.

11179-permitted-value-valuesetPermitted values :

Allows expressing the value set that must be stored internally by the system (as distinct from the base value set which defines values for exchange).

11179-permitted-value-conceptmapMapping from permitted to transmitted :

Expresses the linkage between the internal codes used for storage and the codes used for exchange.

11179-effective-periodWhen data element is "valid" :

Identifies the date on which the element became (or is expected to become) active and the date on which the element became (or is expected to become) retired.