16:01:15 RRSAgent has joined #hcls 16:01:15 logging to https://www.w3.org/2022/01/13-hcls-irc 16:01:24 rrsagent, make logs public 16:01:31 Meeting: FHIR RDF 16:01:35 Chair: David Booth 16:06:29 Topic: Concept URIs for codeableconcepts 16:06:30 https://github.com/w3c/hcls-fhir-rdf/issues/94 16:09:07 gaurav: Investigating adding prefixes to the FHIR spec, for use in generating FHIR RDF URIs for codeableconcepts. 16:09:41 https://terminology.hl7.org/ 16:10:18 gaurav: This website is cool, it has all the info in it. 16:10:38 ... E.g., to learn about the national drug codes. 16:10:59 https://terminology.hl7.org/CodeSystem-v3-ndc.html 16:11:34 gaurav: For CodeSystem there' an Identifier field. 16:11:35 bmc has joined #hcls 16:12:01 https://terminology.hl7.org/NamingSystem-v3-ndc.html 16:12:14 gaurav: The idea is to have a third value for prefix. 16:12:26 eric: SNOMED is a good example, because it already has a URL. 16:13:06 eric: Before deploying that, we'll need to ask orgs to honor the URL space that we're proposing for them. 16:13:16 ... Outreach effort. 16:14:35 gaurav: Now I know which repo this info comes from. But there's also a node.js package, with a JSON version for all of this: https://simplifier.net/packages/hl7.terminology.r4/1.0.0/~files 16:14:59 ... OIDs and URIs also show up there. You can view it as JSON, XML or Turtle. 16:15:40 gaurav: Still trying to determine if a change to this repo is reflected in the spec, or if anything else needs to be changed. 16:16:10 ... I raised an issue and got an immediate response from Grahame: https://github.com/HL7/UTG/issues/7#issuecomment-1000173095 16:16:52 gaurav: If we fix it here, it should propagate everywhere. 16:17:24 ... Grahame said to discuss it on chat.fhir.org #terminology and expect lots of arguments. 16:18:15 ... Think we should finish determining exactly what needs to be changed, then launch the outreach effort. 16:18:46 ... NamingSystem says that someone somewhere has a system for codes, and CodeSystem says what the codes are. 16:19:18 eric: They don't want to invent terms in a valueset. They put it into a codesystem instead. 16:20:26 eric: Also suggest that when we invent a mapping (if an org has not done it), we do it in the HL7 space, and make clear that it may be superseded by that org. 16:21:27 gaurav: This page suggests a particular convention for "temporary" URIs: https://build.fhir.org/terminologies.html#system 16:22:36 brad: Want to be sure we don't jeopardize what's going on with US Core stuff. They define various systems in codings. 16:22:55 http://www.hl7.org/fhir/us/core/terminology.html 16:23:18 includes the text: 16:23:19 [[ 16:23:21 terminology.hl7.org/temporary/CodeSystem/xxxxx (where xxxx is a meaningful text string) 16:23:27 ]] 16:23:29 brad: They talk about various codings and require certain URLs. 16:23:48 ... so coordinate with US-Core 16:24:33 s/includes the text/includes the template/ 16:26:08 eric: Pick a couple like disease ont and BFO, and try to get others on board. 16:27:41 ACTION: David to find who at Regenstrief might be a contact 16:30:44 eric: Kent Spackman wrote a perl script to convert SNOMED terms to URLs, but the org does not provide a website supporting them. 16:32:42 eric: 1. whether that's the official URL vs 2. whether you can HTTP GET that URL. 16:33:23 ... When Kent picked purl.org, that was the trend at the time. But it's out of favor now, and it has limited server capacity. 16:36:14 david: Could this mapping from system+code to URL be inferred using OWL? 16:36:31 eric: Cannot do literal inference in OWL. 16:36:37 ... I tried it. :( 16:37:08 gaurav: Could also provide a mapping server, but maintaining it would too much work. 16:38:15 eric: Wonder how hard it would be to set up a CTS-2 server to do that. https://www.omg.org/spec/CTS2/ 16:40:57 david: But not really needed if we get it into the FHIR spec. 16:41:18 ben: NHS are running an instance and I believe Germany set up an instance 16:41:25 ben: eg https://www.healthterminologies.gov.au/access/ backed by ontoserver 16:41:31 ben: and NHS instance https://digital.nhs.uk/services/terminology-servers 16:42:19 ben: SNOMED has different regions and additions. 16:43:02 ... ontoserver also has federation capabilities. 16:44:47 ... Different health systems have different requirements 16:48:43 ... If those URIs are put into the FHIR terminology server, then hopefully they'll be picked up by various terminology servers. 16:50:04 ben: regional editions are both subsets and extensions (terms that they want to get in sooner). 16:52:05 topic: Adding third pane to FHIR JSON-LD playground 16:52:23 james: Functionally finished. Testing now. 16:52:45 ... Option to choose between two versions of JSON-LD. Which to use? 16:52:54 eric: We need 1.1. 16:54:26 ACTION: James to give a demo next week of FHIR JSON-LD playground 16:54:37 Topic: Turtle serializer 16:54:58 eric: I put turtle serializer into my FHIR JSOn-LD playground. 16:55:03 (gives demo) 16:57:17 james: How is nquads used? Does anyone use it? 16:57:44 eric: nquads is a subset of turtle. 16:58:31 james: Can i get this code? 17:02:36 eric: Yes, it's checked in. 17:02:41 david: Call that tab Canonicalized NQuads? 17:03:40 https://github.com/ericprud/fhircat-playground/blob/ericP-variant/fhirlib/test/FhirTurtleSerializer.test.js 17:06:14 ADJOURNED 17:08:47 Present: Brad Simons, David Booth, EricP, James Champion, Gaurav Vaidya, Dagmar, Ben McAlister 17:09:16 rrsagent, draft minutes 17:09:16 I have made the request to generate https://www.w3.org/2022/01/13-hcls-minutes.html dbooth_ 17:27:14 dbooth has joined #hcls 17:27:31 rrsagent, make logs public 17:31:53 i/Kent Spackman wrote a perl/david: [FOLLOWUP] In Sept 2020 Swapna Abhyankar from Regenstrief was very helpful in responding to LOINC licensing questions. He might be a good contact. 17:32:15 rrsagent, draft minutes 17:32:15 I have made the request to generate https://www.w3.org/2022/01/13-hcls-minutes.html dbooth