Showing:

Annotations
Diagrams
Facets
Source
Used by
Simple Type DataSetValueType
Namespace No namespace
Annotations
 
Data Set Concept Type for the Value Domain
Diagram
DiagramDECOR-datatypes_xsd_Simple_Type_EnumerationToken.tmp#EnumerationToken
Type restriction of EnumerationToken
Type hierarchy
Facets
maxLength 50
enumeration string 
Represents any text item, without visual formatting.
enumeration code 
A system of valid symbols/codes, that substitute for specified concepts e.g. alpha, numeric, symbols and/or combinations, usually defined by a formal reference to a terminology or ontology, but may also be defined by the provision of text. Typically a symbol/code is expressed with a value for code, an identifier for the terminology or ontology it belongs to and at least one textual representation (display name).
enumeration identifier 
Type for representing identifiers of real-world entities. Typical identifiers include drivers licence number, social security number, prescription id, order id, and so on.
enumeration date 
Represents an absolute point in time, as measured on the Gregorian calendar, and specified only to the day. Semantics defined by ISO 8601. Used for recording dates in real world time. The partial form is used for approximate birth dates, dates of death, etc.
enumeration datetime 
Represents an absolute point in time, specified to the second. Semantics defined by ISO 8601. Used for recording a precise point in real world time, e.g. the exact date and time of the birth of a baby, and for approximate time stamps, e.g. the origin of an history observation which is only partially known.
enumeration time 
Represents an point in time on the 24 hour clock without specifying the date, specified to the second. Semantics defined by ISO 8601. Used for recording a point in real world time, e.g. the hours to take medication (08, 12, 18 o'clock), exact time a baby was born, time of stopping CPR.
enumeration quantity 
Quantitified type representing "scientific" quantities, i.e. quantities expressed as a magnitude and units. If not further specified with fractionDigits, a decimal number with optional decimal point (i.e. '3.14159265359'). There are some "special" quantities (used in healthcare), explained later: for time durations duration shall be used; for monetary amounts currency shall be used
enumeration duration 
Is a quantity, represents a period of time with respect to a notional point in time, which is not specified. A sign may be used to indicate the duration is “backwards” in time rather than forwards.
enumeration boolean 
Items which are truly boolean data, such as true/false or yes/no answers.
enumeration count 
Countable (non-monetary) quantities. Used for countable types such as pregnancies, steps (taken by a physiotherapy patient), number of cigarettes smoked in a day.
enumeration ordinal 
Models rankings and scores, e.g. pain, Apgar, reflex, ASA, Tanner values, etc, where there is a) implied ordering, b) no implication that the distance between each value is con- stant, and c) the total number of values is finite. Note that although the term ‘ordinal’ in mathematics means natural numbers only, here any integer is allowed, since negative and zero values are often used by medical professionals for values around a neutral point. 
Examples of sets of ordinal values: -3, -2, -1, 0, 1, 2, 3 (reflex response values); 0, 1, 2 (Apgar score values); 1, 2, 3, 4,... (ASA classification); I, II, III, IV, ... (Tanner scale)
enumeration text 
Represents a text item, which may contain any amount of legal characters arranged as e.g. words, sentences etc. Visual formatting and hyperlinks may be included.
enumeration decimal 
Decimal number (rarely used, in most cases a decimal number is actually a quantity).
enumeration blob 
Things that are typically stored as binary objects in the computer world and need to be rendered appropriately, e.g. images: like X-rays, computertomographic images and scans.
enumeration complex 
Non-atomic datatypes which are not explictly further defined in the dataset itself. Example: 'address' or 'person name'. Usually complex types are assumed to be well-known enough not to warrant further decomposition in the dataset itself.
Used by
Source
 
<xs:simpleType name="DataSetValueType">
  <xs:annotation>
    <xs:documentation xml:lang="en-US">Data Set Concept Type for the Value Domain</xs:documentation>
  </xs:annotation>
  <xs:restriction base="EnumerationToken">
    <xs:enumeration value="string">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">String</xforms:label>
          <xforms:label xml:lang="en-US">String</xforms:label>
          <xforms:label xml:lang="de-DE">Zeichenkette</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Represents any text item, without visual formatting.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="code">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Code</xforms:label>
          <xforms:label xml:lang="en-US">Code</xforms:label>
          <xforms:label xml:lang="de-DE">Kode</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">A system of valid symbols/codes, that substitute for specified concepts e.g. alpha, numeric, symbols and/or combinations, usually defined by a formal reference to a terminology or ontology, but may also be defined by the provision of text. Typically a symbol/code is expressed with a value for code, an identifier for the terminology or ontology it belongs to and at least one textual representation (display name).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="identifier">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Identificatie</xforms:label>
          <xforms:label xml:lang="en-US">Identifier</xforms:label>
          <xforms:label xml:lang="de-DE">Identifikator</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Type for representing identifiers of real-world entities. Typical identifiers include drivers licence number, social security number, prescription id, order id, and so on.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="date">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Datum</xforms:label>
          <xforms:label xml:lang="en-US">Date</xforms:label>
          <xforms:label xml:lang="de-DE">Datum</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Represents an absolute point in time, as measured on the Gregorian calendar, and specified only to the day. Semantics defined by ISO 8601. Used for recording dates in real world time. The partial form is used for approximate birth dates, dates of death, etc.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="datetime">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Datum/tijd</xforms:label>
          <xforms:label xml:lang="en-US">Date/time</xforms:label>
          <xforms:label xml:lang="de-DE">Datum/Zeit</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Represents an absolute point in time, specified to the second. Semantics defined by ISO 8601. Used for recording a precise point in real world time, e.g. the exact date and time of the birth of a baby, and for approximate time stamps, e.g. the origin of an history observation which is only partially known.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="time">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Tijd</xforms:label>
          <xforms:label xml:lang="en-US">Time</xforms:label>
          <xforms:label xml:lang="de-DE">Zeit</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Represents an point in time on the 24 hour clock without specifying the date, specified to the second. Semantics defined by ISO 8601. Used for recording a point in real world time, e.g. the hours to take medication (08, 12, 18 o'clock), exact time a baby was born, time of stopping CPR.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="quantity">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Hoeveelheid</xforms:label>
          <xforms:label xml:lang="en-US">Quantity</xforms:label>
          <xforms:label xml:lang="de-DE">Quantität</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Quantitified type representing "scientific" quantities, i.e. quantities expressed as a magnitude and units. If not further specified with fractionDigits, a decimal number with optional decimal point (i.e. '3.14159265359'). There are some "special" quantities (used in healthcare), explained later: for time durations duration shall be used; for monetary amounts currency shall be used</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="duration">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Tijdsduur</xforms:label>
          <xforms:label xml:lang="en-US">Duration</xforms:label>
          <xforms:label xml:lang="de-DE">Dauer</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Is a quantity, represents a period of time with respect to a notional point in time, which is not specified. A sign may be used to indicate the duration is “backwards” in time rather than forwards.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="boolean">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Boolean</xforms:label>
          <xforms:label xml:lang="en-US">Boolean</xforms:label>
          <xforms:label xml:lang="de-DE">Boolescher Wert</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Items which are truly boolean data, such as true/false or yes/no answers.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="count">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Aantal</xforms:label>
          <xforms:label xml:lang="en-US">Count</xforms:label>
          <xforms:label xml:lang="de-DE">Zähler</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Countable (non-monetary) quantities. Used for countable types such as pregnancies, steps (taken by a physiotherapy patient), number of cigarettes smoked in a day.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="ordinal">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Ordinaal</xforms:label>
          <xforms:label xml:lang="en-US">Ordinal</xforms:label>
          <xforms:label xml:lang="de-DE">Ordinalzahl</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Models rankings and scores, e.g. pain, Apgar, reflex, ASA, Tanner values, etc, where there is a) implied ordering, b) no implication that the distance between each value is con- stant, and c) the total number of values is finite. Note that although the term ‘ordinal’ in mathematics means natural numbers only, here any integer is allowed, since negative and zero values are often used by medical professionals for values around a neutral point. Examples of sets of ordinal values: -3, -2, -1, 0, 1, 2, 3 (reflex response values); 0, 1, 2 (Apgar score values); 1, 2, 3, 4,... (ASA classification); I, II, III, IV, ... (Tanner scale)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="text">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Tekst</xforms:label>
          <xforms:label xml:lang="en-US">Text</xforms:label>
          <xforms:label xml:lang="de-DE">Text</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Represents a text item, which may contain any amount of legal characters arranged as e.g. words, sentences etc. Visual formatting and hyperlinks may be included.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="decimal">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Decimaal getal</xforms:label>
          <xforms:label xml:lang="en-US">Decimal number</xforms:label>
          <xforms:label xml:lang="de-DE">Dezimalzahl</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Decimal number (rarely used, in most cases a decimal number is actually a quantity).</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="blob">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Binair</xforms:label>
          <xforms:label xml:lang="en-US">Binary</xforms:label>
          <xforms:label xml:lang="de-DE">Binärinformation</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Things that are typically stored as binary objects in the computer world and need to be rendered appropriately, e.g. images: like X-rays, computertomographic images and scans.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="complex">
      <xs:annotation>
        <xs:appinfo>
          <xforms:label xml:lang="nl-NL">Samengestelde gegevens</xforms:label>
          <xforms:label xml:lang="en-US">Collection of data</xforms:label>
          <xforms:label xml:lang="de-DE">Zusammenstellung von Daten</xforms:label>
        </xs:appinfo>
        <xs:documentation xml:lang="en-US">Non-atomic datatypes which are not explictly further defined in the dataset itself. Example: 'address' or 'person name'. Usually complex types are assumed to be well-known enough not to warrant further decomposition in the dataset itself.</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
</xs:simpleType>
XML Schema documentation generated by ® XML Editor.