W3C

– DRAFT –
FHIR RDF

16 June 2022

Attendees

Present
Brad Simons, David Booth, EricP, Gaurav Vaidya
Regrets
-
Chair
David Booth
Scribe
dbooth

Meeting minutes

FHIR RDF Playground

eric: Still need to do the value type simplification.
… Need to update shex library first though.

eric: Revelations: if we want to hoist scalars -- scalars have deep XML representation, but in JSON they're hoisted -- but in RDF we need to come up w the analog to the extension point. That means that we need to use RDF Collections.
… If there's a CodeableCOncept w n codings, the fhir:index goes into each of the codings. But if I have two status, it isn't a bnode, so I can attach the fhir:index. That means that if we want to use hoisting, that pushes us to also use RDF Collections.

Issue 95: References lack a type arc

https://github.com/w3c/hcls-fhir-rdf/issues/95

dbooth: More to be done on this issue?

eric: Preprocessor job.. Needs to infer type from ref URL.
… That will work for FHIR URLs, but not other URLs.

dbooth: i wonder if the broader FHIR community has raised this issue

gaurav: <<reference attribute, a "Literal reference, Relative, internal or absolute URL">> (from the issue)

eric: Right now, there's a small set of types that are allowed, which comes from the resource definition.
… In the shex I was saying "it has to be one of these types". If we cannot validate that it is one of those things, then we need explicit code in the shex to relax that.

eric: OWL property constraint.
… i.e., the owl analog to range.

ACTION: DBooth to find out if the broader FHIR community is looking at this issue.

eric: Preprocessor already does the microparsing of the relative URL to determine the type.

dbooth: If the broader community doesn't address this, do we close this issue with a WONTFIX tag?

eric: yes.

Concept IRIs

gaurav: Fixed the final issue (UTF16 encoding issue).
… but want Eric to review my code.

eric: You should never see a surrogate pair when you are expecting a unicode char.
… In JS, python, etc, you get the string and then should never see any BOMs.

https://github.com/w3c/hcls-fhir-rdf/issues/94

ACTION: Eric to review gaurav's code

dbooth: A couple of slides here: https://docs.google.com/presentation/d/19Xd8i6mK-fhgoCPF3q9BvUu1RFmUxrGCOzWKbfVN5J4/edit#slide=id.g1280217e6c0_0_19

ACTION: gaurav to reach out to Terminology group.

ADJOURNED

<dbooth> s/needs to implement it. Also need/job. Needs/

Summary of action items

  1. DBooth to find out if the broader FHIR community is looking at this issue.
  2. Eric to review gaurav's code
  3. gaurav to reach out to Terminology group.
Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).

Diagnostics

Failed: s/needs to implement it. Also need/job. Needs/

Succeeded: i/More to be done /https://github.com/w3c/hcls-fhir-rdf/issues/95

Succeeded: s/Preprocessor needs to implement it/Preprocessor job.

Succeeded: s/Also need to infer/Needs to infer/

No scribenick or scribe found. Guessed: dbooth

Maybe present: dbooth, eric, gaurav