W3C

– DRAFT –
FHIR RDF

02 October 2025

Attendees

Present
David Booth, Detlef Gritner, Eric Jahn, Erich Bremer, EricP, Jim Balhoff, Ken Lord, Tim Prudhomme
Regrets
-
Chair
David Booth
Scribe
dbooth

Meeting minutes

R6 triage

dbooth: I think #172 (Issues with using FHIR R5 ShEx) can be done after R6, because it does not affect the validity of any FHIR RDF data. It only affects ShEx usability and precision.

w3c/hcls-fhir-rdf#172

AGREED

dbooth: Similarly, I think #177 (OWL polymorphic types + references), #178 (OWL punning issues) and #179 (OWL hierarchy fixes) can be done after R6, because they do not affect the validity of any FHIR RDF data. They only affects OWL usability and precision.

w3c/hcls-fhir-rdf#177

w3c/hcls-fhir-rdf#178

w3c/hcls-fhir-rdf#179

tim: It includes both bug fix and improvement
… already implemented fixes for these.

tim: These changes also implement the fhir:link --> fhir:l

dbooth: Can we approve #177 for inclusion in R6?

dbooth: the fhir:l change needs to be in R6

AGREED: the fhir:l change needs to be in R6

AGREED: Other than the fhir:l change, 177, 178 and 179 could wait until after R6

AGREED: 167 and 168 can be done after R6

dbooth: Also #171 (Add a documentation page for all the IRI prefixes currently on THO) after R6? I think it can be an "informative" addition, rather than normative/authoritative.

w3c/hcls-fhir-rdf#171

jim: There are some hard-coded URIs for LOINC and MeSH, but they don't use the IRI stems in THO

dbooth: I think THO repo can update independently of the FHIR core versioning

ken: Yes, that's the intent.

AGREED: #171 can be after R6

Issue 120: Syntax of added fhir:l links

dbooth: At

w3c/hcls-fhir-rdf#120 (comment) Tim replied: "Yes and we should recommend here that they SHOULD be generated, but not specify how."

dbooth: Should we specify the URI syntax in the rdf.html page?

tim: For References, they should be constrained by the Reference types, e.g., for Patient, "Patient" should be in the link.
… But for URIs the literals should just be turned links directly.

dbooth: We'll specify the location of where the fhir:l links go, but what about the syntax of those links?

AGREED: Yes, specify what the syntax SHALL be

dbooth: And that will include the special case for canonical, from pipe to query string,

Scheduling extra calls

dbooth: Nov 1 R6 deadline is rapidly approaching. Should we schedule more FHIR RDF calls? Add Mondays at 11am Boston time?

AGREED: Add Tuesdays 11am Boston time

Issue 120

tim: Might be able to do HAPI changes after R6 deadline

FHIR Ontology

ken: This work on the FHIR ont could be helpful to us, because the FHIR data model has been critical in our ont.
… Would be really helpful to have a powerpoint presentation on it.
… What are the objectives and mission of this work?

ericp: Slides I did for SWAT4LS might be helpful?

ACTION: DBooth to send Ken previous status slides

tim: Also copy me

Yellow schemas

ACTION: Dbooth to create an issue to add Turtle to XML column on datatypes page

AGREED: Add fhir:l to Reference yellow schema

ADJOURNED

Summary of action items

  1. DBooth to send Ken previous status slides
  2. Dbooth to create an issue to add Turtle to XML column on datatypes page
Minutes manually created (not a transcript), formatted by scribe.perl version 246 (Wed Oct 1 15:02:24 2025 UTC).

Diagnostics

No scribenick or scribe found. Guessed: dbooth

Maybe present: AGREED, dbooth, jim, ken, tim

All speakers: AGREED, dbooth, ericp, jim, ken, tim

Active on IRC: dbooth