16:00:19 <RRSAgent> RRSAgent has joined #hcls
16:00:19 <RRSAgent> logging to https://www.w3.org/2022/01/27-hcls-irc
16:00:25 <dbooth> rrsagent, make logs public
16:00:30 <dbooth> Meeting: FHIR RDF
16:00:33 <dbooth> Chair: David Booth
16:03:43 <dbooth> Topic: Concept URIs
16:04:08 <dbooth> Issue 94
16:05:04 <dbooth> gaurav: Playing with the HL7 UTG repo.  There are XML files that seem to be the source of truth.
16:05:50 <dbooth> ... I added another identifier, with use "prefix", but that caused a validation error.  I tried type "prefix", but and it accepts it but does not pass it downstream.
16:07:35 <dbooth> ... It gets converted into HTML docs, which don't contain the type field, but the JSON has it.
16:08:35 <dbooth> ... The type field is supposed to be extensible, which is why we thought that would be a good field for it.  If we can convince the FHIR group to accept this, then we can figure out how to do it.
16:09:18 <dbooth> ... I also confirmed that if I modify the XML file, it shows up in the generated XML and JSON on the website and the downloads of the master package.
16:09:54 <dbooth> ... Next step is to incorporate this into FHIR examples, and for all the SNOMED concepts attach the prefixes.
16:11:25 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/94#issuecomment-1023370141
16:11:46 <dbooth> https://github.com/gaurav/UTG/blob/d51fb82feae5cc328bcf871776124fcca53900eb/input/sourceOfTruth/external/v3/codeSystems/cs-v3-snomed-CT.xml#L30-L35
16:11:53 <dbooth> https://github.com/gaurav/UTG/blob/d51fb82feae5cc328bcf871776124fcca53900eb/input/sourceOfTruth/external/v3/namingSystems/v3-snomed-CT.xml
16:12:01 <dbooth> https://github.com/gaurav/UTG/blob/d51fb82feae5cc328bcf871776124fcca53900eb/input/sourceOfTruth/external/v3/namingSystems/v3-snomed-CT.xml#L38-L42
16:12:40 <dbooth> gaurav: NamingSystems and CodingSystems are weirdly inconsistent.
16:13:46 <dbooth> david: Should file an issue on that.
16:14:12 <dbooth> gaurav: I'll file an issue in the UTG repo.
16:15:28 <dbooth> david: What else would be needed to make a full proposal for this change?
16:15:43 <dbooth> gaurav: Writing a google doc description.
16:16:15 <dbooth> ... Grahame suggested we bring this to the FHIR chat.
16:17:44 <dbooth> eric: We're trying to figure out how to add URLs to terminologies that don't have their own URLs, and replicate those that do.  Is "prefix" sufficient for both cases?
16:18:17 <dbooth> ... And of the existing URLs, is a simple prefix sufficient?  Or might we need to do something different for two different code systems?
16:19:00 <dbooth> david: Such as a URL template?
16:19:16 <dbooth> eric: Yes, and maybe some codes munging needed first.
16:19:59 <dbooth> gaurav: 1. Is it still worth trying to get just a prefix in?  2. Is there an egregious thing that would need a special case?  There might already be one.
16:20:29 <dbooth> gaurav: Found this in a SNOMED code: 128045006:{363698007=56459004}
16:21:09 <dbooth> ... For anything in the FHIR examples, we can make sure that every SNOMED code converts to an RDF URL.
16:21:41 <dbooth> eric: We can solve this easily by URL encoding.
16:22:10 <dbooth> david: Also need some canonicalization, eg, for spaces.
16:24:50 <dbooth> eric: Do we care about compositional syntax?   If someone wrote it in that syntax, they're using it to say this is a fracture of the right clavicle.
16:25:34 <dbooth> ... But you don't need to write the SNOMED code that way, because you can express it in FHIR anyway.
16:26:16 <dbooth> s/that way/that way for this example/
16:26:38 <dbooth> ... But other cases might not.
16:26:47 <dbooth> ... Bu t we could use URL encoding.
16:27:29 <dbooth> s/Bu t/But/
16:31:14 <dbooth> eric: I suspect that most uses of compositional codes are expressible in FHIR in other ways.
16:31:49 <dbooth> gaurav: I'll focus on FHIR examples.  Other example FHIR data, to find codes that cannot just be prefixed?
16:32:23 <dbooth> ACTION: Eric to ask folks at NHS about use of compositional codes other than SNOMED
16:32:54 <dbooth> gaurav: I have 8 candidates that we can just prefix, including SNOMED and LOINC.
16:33:24 <dbooth> eric: We should do this as early as possible, becuase it impacts tooling.
16:35:02 <dbooth> david: I'm comfortable with only the prefix solution.
16:36:19 <dbooth> eric: Could imagine something hierarchical that contains slashes and you don't want those slashes URL encoded.
16:38:44 <dbooth> david: Should do a survey of code systems.
16:39:45 <dbooth> ACTION: Gaurav to get the list of terminologies and mark which ones are covered by prefix solution.
16:40:33 <dbooth> Topic: Preprocessing
16:40:58 <dbooth> eric: Preprocessing step did not cover the conversion of union types to specific types.
16:41:56 <dbooth> ... E.g., FHIR datetype is a union of four different XSD types.  But we want them specifically typed in the RDF, so the preprocessing needs to do that.
16:43:06 <dbooth> ... To fix that I had to microparse to match one of the four types.  But to parse it, I had to know that it is a FHIR datetype (not an int, for example).
16:44:08 <dbooth> ... So I had to pass the content model to the preprocessing.
16:58:51 <dbooth> david: Should be able to know from the FHIR property name, whether it needs special union preprocessing.
17:01:47 <dbooth> ADJOURNED
17:01:54 <dbooth> rrsagent, draft minutes
17:01:54 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/27-hcls-minutes.html dbooth
17:37:21 <dbooth> Present: David Booth, EricP, Dagmar, Gaurav Vaidya, Gopi, Jim Balhoff
17:37:24 <dbooth> rrsagent, draft minutes
17:37:24 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/27-hcls-minutes.html dbooth
18:16:11 <TallTed> TallTed has joined #hcls