Meeting minutes
Concept IRIs
gaurav: Working on this ticket: https://
… Need to email committee leads to get a vote scheduled.
… We made a change to the FHIR spec for version 5. Added a dash to the names in the naming system fields, but didn't in the code system fields.
https://
https://
gaurav: Fix this? We could add a hyphen into the code system. Or if we want to standardize to no hyphen, that would require a change to FHIR.
rob: v2 code system follows that pattern. Why do we need to update a v2 code system?
gaurav: I think there's a LOINC code system.
rob: To match the style of that code system, then without hyphen seems okay.
… It matches the typical convention of that.
… None of the others have a hyphen, so I could see removing the hyphen.
… Codes often use hyphens.
… I'd leave it alone.
dbooth: Benefit in having them both have the hyphen or both without the hyphen.
gaurav: Removing the dash is a change to FHIR, adding the change would be a change to THO.
… Easy thing would be to add the hyphen to THO.
rob: That would be the worst thing.
… Another precedent, style convention, in V2 and V3 codes never have dashes and always upper case, but in FHIR they may have them and may have different case.
… Dashes are common in FHIR.
erich: Agree w consistency.
… Would opt for consistency.
rob: naming system must be lower case. FOr code system, must have upper case.
jim: I like consistency. Sounds like most aligned w convention would be to remove the dash, but don't know how much turmoil that causes.
jim: Changing FIHR spec would cause confusion.
dbooth; Could treat it as an erratum until R6.
rob: Bug fixes to R5 are likely to be scoped to critical changes.
dbooth: How are people leaning?
gaurav: Don't care.
jim: Leaning to leaving it along.
tim: neutral.
rob: on the fence. okay w change proposal.
erich: leave it alone.
dbooth: Anyone opposed to leaving it as is.
AGREED: Leave it as is.
gaurav: Next issue: want to create a PR for next concept IRIs, i think MESH and something else.
Fixes to Turtle examples.
jim: I'll nudge them in zulip. Also made an issue on unit tests.
dbooth: I thought that there were round trip tests, but they got disabled in the build because they took too long.
tim: In R5 we switched to a different parser/generator. The tests are duplicated across FHIR version.
jim: Would be a waste of time to do a custom FHIR RDF parser, given that we have Jena.
dbooth: Need to check w EricP about HAPI FHIR.
tim: Could add some turtle unit test for R5.
dbooth: How many?
tim: WOuld be nice to do the ones that currently have bugs
… I can take this on.
HAPI server
tim: The app I showed you I hooked to a FHIR server, and the HAPI fhir server can give RDF, but it needs to be updated to give R5.
… It says it is giving R5, but it's actually giving R4.
ADJOURNED