– DRAFT –
FHIR RDF

DICOM

dbooth: There are two cases: things that are not known -- someone's birthday -- versus something that will never be known, like a probe was broken and we didn't get a measurement at this point in time, and therefore we will never have a value for that thing.

gaurav: Would this be useful in specifying that e.g. a fhir:Observation is missing because it was not permitted/not permitted/not applicable? https://build.fhir.org/valueset-data-absent-reason.html

gaurav: There is also “IND” (indeterminate) in https://build.fhir.org/valueset-observation-interpretation.html

gaurav: FHIR provides a limited way to indicate that something is missing in an observation.

rob: representation of null values is important. Two distinct cases. Not sure whether we need separate syntaxes for them.

erich: I shared null flavors info about DICOM with EricP

erich: What if you don't yet know which use case it is? What should you put there? rdf:empty ?

ACTION: Erich to add option 6 for a single blank node

erich: https://dicom.nema.org/MEDICAL/Dicom/current/output/chtml/part20/sect_5.3.2.html

erich: Might also want to handle null flavors

FHIR RDF update at HL7 WG Meetings: May 21, 11am Dallas TX time.

dbooth: I will report our progress.

detlef: Out next week.

rob: out next two weeks.

IRI Stems

gaurav: No updates yet. Updated PR for review.
… Radlex is thinking about it.

ADJOURNED