Meeting minutes
Update on FHIR build process
jim: No progress on the build code. no update from Grahame yet.
SPARQL list updater
jim: I updated the SPARQL code. Seems to work. Also added another one, with a different filter. This one looks for predicates that are in the fhir: namespace, and only changes object of those predicates.
dbooth: For performance test, you only need a bunch of data that uses RDF lists, then add in a little FHIR data with lists.
eric: If someone is using this in anger, they'll probably be using an API.
… GO has lots of things that use lists in OWL.
dbooth: Where should we store these scripts?
… Could be rdf.html page. Or github, or a wiki.
rob: Or the THO site
… THO is the same a FHIR IG -- Implementation Guide.
rob: Anything you can do in the FHIR spec you can do in THO, in terms of formatting.
AGREED: Keep in on github
eric: Propose to change the page name to owlSafeLists
AGREED: Change page name to owlSafeLists
ACTION: Eric to make these changes
ACTION: DBooth to finish edits on that page.
Concept IRIs
gaurav: Should we add some text to rdf.html to say what restrictions should be on IRI stems?
dbooth: Make sense.
… E.g., don't put in a partial domain name.
eric: Agreed.
rob: Should we add an IRI type?
… But not (yet) as a FHIR datatype?
dbooth: Sounds good to me.
gaurav: Do we need to worry about NamingSystem at all? Or should we view this as only being a CodeSystem thing?
rob: Policy is that for every CodeSystem, there is a NamingSystem.
dbooth: And in point 2 we need to add an iri-stem code to NamingSystemIdentifierType
rob: But if we're adding iri-stem, shouldn't we also add an iri code?
dbooth: If there isn't yet a use for it, I generally think it should not be added.
rob: Okay to leave it out, and see if it comes up in discussion.
jim: I don't think we should require the IRI stem to end with a hash or slash.
dbooth: Agreed.
jim: Wonder how people put HPO codes into FHIR.
ACTION: Gaurav to draft text on IRI stems for rdf.html
gaurav: Next step is make a PR for proposing the changes to THO.
dbooth: Next step on updating rdf.html?
rob: Put the proposed changes into the jira ticket, and get it approved.
… For approval by ITS.
Implementation Guidelines
eric: What are IGs doing now? What made CDA super successful was the IG that told you everything you need to write in the health record that did not have a defined structure. E.g., how to write when someone quit smoking. Will FHIR IG do that also?
rob: Yes, depends on how far you take it. Some constraints may be loose, some may be very locked down. Might take more than one layer to get there.
eric: CDA had one set. Would every FHIR profile define their own?
rob: Reverse of that. CDA also had realm specific guides. CDA also had CCDA for USA, etc. But Europoe has different ones.
… In FHIR you can do universal, or a particular realm, etc.
… But the IG is a container that included profiles, which are almost alwasy part of an IG.
… An IG typically includes multiple profiles.
… Profiles are computable constraints.
eric: The point is that if you are going beyond the specificity of what's in a terminology, then you give guidance.
ADJOURNED