Minor fixes needed for the results of terminology.hl7.org merges

[gaurav]

UP-364 Request to add IRI stems to LOINC:

• LOINC CodeSystem: looks good!
• LOINC NamingSystem
  • Specifically mentions "This uniqueId should have a type of 'iri-stem', which we will change once https://jira.hl7.org/browse/FHIR-39604 has been merged." -- that should be fixed, and the type updated.
• IdentifierType
  • Type IRISTEM looks correct, but refers to https://build.fhir.org/rdf.html#iri-stem, which should be changed to https://hl7.org/fhir/rdf.html#iri-stem

Action: draft proposed as https://jira.hl7.org/browse/UP-464

UP-406 Add IRIs to the External Known Identifier Systems:

• Add IRI as a NamingSystem: not yet implemented; this might be queued for the next release (https://jira.hl7.org/browse/UPSM-191) IRI as NamingSystem now up at https://terminology.hl7.org/NamingSystem-iri.html (or https://terminology.hl7.org/5.2.0/NamingSystem-iri.html) as per https://jira.hl7.org/browse/UP-406?focusedCommentId=221291; looks good.

FHIR-39604 Add "iri-stem" as a NamingSystem identifier type:

• NamingSystem Identifier Type:
  • Mentions "See rdf.html#iri-stem for details on how this value may be used." -- this link should be fixed.
  • Action: submitted as https://jira.hl7.org/browse/FHIR-42696

[gaurav]

• https://jira.hl7.org/browse/UP-464 will need to be voted on by ITS. @gaurav to e-mail ITS co-chairs and see if they want to do this as an in-person meeting.
• @gaurav to create a proposal for UP-464 for changes: https://confluence.hl7.org/display/VMAH/Create+a+Proposal
• Note that we've currently set up the identifier type as IRISTEM but the naming system type as iri-stem, because I thought the former would be more readable (especially in lowercase) but the former seemed closer with what the other values are doing. Standards stability suggests we shouldn't change this, but since nobody is likely to be using this yet apart from us, now might be our only change to harmonize the two values. @dbooth-boston Could you please put this on a future FHIR-RDF meeting agenda to discuss? UPDATE 1/29/24 from DBooth: Done. We discussed this on the 05 Oct 2023 call, and though the minutes are not very clear, Gaurav reported: "we decided that the former should probably be iristem to standardize things a bit more, but that we weren’t going to align things perfectly (the former is consistently lowercased while the latter is consistently uppercased) and so we should leave things as they are".

[gaurav]

• Get in touch with Jess Bota (@gaurav)

[dbooth-boston]

Gaurav: This is currently waiting in 'content check'. https://www.w3.org/2024/03/07-hcls-minutes.html

[gaurav]

Marc Duteau has explained that the reason for this is that THO still uses R4, so it doesn't have the "iri-stem" type from R5. So I think this issue will blocked until that happens. Marc is chatting with Grahame to figure out if this is something they can work around.

[dbooth-boston]

Gaurav: THO is still using R4, so we might need to wait for them to go to R5 to make this change.

[dbooth-boston]

@gaurav to review

[gaurav]

This appears to be completely done except for the last piece (https://jira.hl7.org/browse/FHIR-42696). I created a PR against FHIR to implement this (HL7/fhir#3205) -- not sure if that's the right move at this point, but at worse they can only reject it.