...
openEHR data types | No. times | FHIR data types | Archetyping | Data Representation | Feedback to FHIR |
---|---|---|---|---|---|
DV_BOOLEAN | 56 | - | Used widely in archetypes. |
| No FHIR subtype of DataType to accommodate booleans? |
|
|
|
|
|
|
DV_ORDERED |
|
|
|
|
|
DV_QUANTIFIED |
| Quantity |
|
|
|
DV_AMOUNT |
|
|
|
|
|
DV_QUANTITY | 189 | Quantity | Used widely in archetypes. | In FHIR, Quantity accommodates both Integer and Real values. | The FHIR choice to represent units as a code or a string seems unnecessarily complicated. A UCUM units string should be adequate. There is an example with unit=mcg/L and code=ug. What can this mean? |
DV_COUNT | 28 | Quantity |
|
| |
DV_PROPORTION | 40 | Ratio |
|
| |
DV_ORDINAL | 50 | Choice |
| The FHIR type does not seem to accommodate values, only symbols. Test for FHIR: how to represent Apgar or Barthel ordinal value lists? | |
DV_INTERVAL<T:DV_QUANTIFIED> | 5 - DV_DATE | Interval |
|
| |
|
|
|
|
|
|
DV_DATE | 25 | xx | xx |
|
|
DV_DATE_TIME | 32 | xx | xx |
|
|
DV_TIME | 0 | xx | xx |
|
|
DV_DURATION | 22 | Quantity | xx |
|
|
|
|
|
|
|
|
DV_TEXT | 521 | CodeableConcept | DV_TEXT mostly used in archetyping to simply indicate the field type. |
| In the FHIR type, the value of the 'text' and the 'displayName' fields will be the same. Given the ubiquity of coded data elements in health data, this seems unfortunate. |
DV_CODED_TEXT | 388 | CodeableConcept | Numerous fields in archetypes are constrained to be local codes, and in templates, to external codes or refsets. |
| '' |
|
|
|
|
|
|
DV_URI | 6 | uri | xx |
|
|
DV_EHR_URI | 2 | uri | xx |
|
|
DV_PARSABLE | 1 | - | xx |
|
|
DV_IDENTIFIER | 2 | HumanId |
| This should be a near perfect bidirectional transform apart from the FHIR HumanId 'period' attribute. | We would consider this a risk, because a validity period might be assigned initially, then be changed; should the data be changed? Can this field be reliably set and reasoned about computationally? |
|
|
|
|
|
|
DV_ENCAPSULATED |
|
|
|
|
|
DV_MULTIMEDIA | 13 | Attachment |
| The FHIR type appears to correspond to allow only base64 ASCII-encoded binary, as is done with MIME attachments in email. This alleviates the need for the 'compression' attribute used in DV_MULTIMEDIA. Any openEHR content should be easy to convert to FHIR format; assuming an openEHR system makes sensible local decisions about binary representation of large multimedia objects, Attachment => DV_MULTIMEDIA should also be trouble-free. |
|
DV_TIME_SPECIFICATION | n/a | Schedule | n/a | These openEHR types are taken from HL7, and so far have limited use in openEHR systems. It would appear reasonable to replace the openEHR type with whatever HL7 decides on for this type in the future, which might be this FHIR type. |
|
DV_GENERAL_TIME_SPECIFICATION | 0 | Schedule |
| '' |
|
DV_PERIODIC_TIME_SPECIFICATION | 0 | Schedule |
| '' |
|
- |
| Money |
|
|
|