...
The analysis below is structured according to the question: for every aspect of each openEHR data type that appears in openEHR archetypes, how would the same thing be done with FHIR data types? Accordingly the analysis has the openEHR types on the left.
Primitive types
openEHR data types | FHIR data types | Comments |
|---|---|---|
Octet | xx | xx |
Character | xx | xx |
Boolean | xx | xx |
Integer | xx | xx |
Real | xx | xx |
Double | xx | xx |
String | xx | xx |
Array<T> | xx | xx |
List<T> | xx | xx |
Set<T> | xx | xx |
Hash<T,U> | xx | xx |
Interval<T> | xx | xx |
ISO8601_DATE | xx | xx |
ISO8601_DATE_TIME | xx | xx |
ISO8601_TIME | xx | xx |
ISO8601_DURATION | xx | xx |
ISO8601_TIMEZONRE | xx | xx |
Complex Types
openEHR data types | FHIR data types | |
|---|---|---|
DV_BOOLEAN | xx | xx |
DV_QUANTITY | xx | xx |
DV_COUNT | xx | xx |
DV_PROPORTION | xx | xx |
DV_ORDINAL | xx | xx |
DV_INTERVAL<T:DV_QUANTIFIED> | xx | xx |
DV_DATE | xx | xx |
DV_DATE_TIME | xx | xx |
DV_TIME | xx | xx |
DV_DURATION | xx | xx |
DV_TEXT | xx | xx |
DV_CODED_TEXT | xx | xx |
CODE_PHRASE | xx | xx |
DV_URI | xx | xx |
DV_EHR_URI | xx | xx |
DV_PARSABLE | xx | xx |
DV_IDENTIFIER | xx | xx |