NULL_FLAVOUR Data absent Element null_flavour to Data Absent reason Element contains a field NULL_FLAVOUR to represent missing information. FHIR does this as extension data absent reason. Hereby the null_flavour codes of openEHR has to be mapped to the data-absent-reason-valueset. FHIR code openEHR openEHR code Comment unknown unknown 271 Default for openEHR→FHIR asked-unknown unknown 253 temp-unknown unknown 253 not-asked unknown 253 asked-declined unknown 253 masked masked 272 Default for openEHR→FHIR not-applicable not applicable 273 Default for openEHR→FHIR unsupported unknown 253 as-text unknown 253 error unknown 253 not-a-number unknown 253 negative-infinity unknown 253 positive-infinity unknown 253 not-performed unknown 253 not-permitted unknown 253 unknown no information 253 Default for openEHR→FHIR The null_reason is to mapped from code along with the null_flavour. If the null_reason contains a string that matches the codings of the valueset, use if for openEHR→FHIR. FHIRpath Cardinality Comment openEHR Cardinality Comment code 0..1 null_flavour 0..1 code 0..1 FHIR→openEHR null_reason 0..1 if exists and matches fhir code, use for openEHR→FHIR PARTY_IDENTIFIER EVENT