Meeting minutes
ElementDefinition summary flags #133
tim: Summary info is for searching for data and not wanting to provide everything.
… Not in the RDF ont right now, but it's in the element definition. Should it be in the ont?
eric: ShEx schema has a def for StructureDefinition, which means that any StructureDef (in principle) has an RDF representation. We exlude all the metadata when we're building ont.
… I.e., we din't put much in there -- not the metadata.
… We could, or we could write a script that emits the StructureDefs, to have access to everything in them.
tim: It's actually ElementDefinition
eric: Could emit it as an RDF representation of the ElementDef, as an instance of it, e.g., for Patient
structure def for all resources: https://
https://
eric: If this were dumped out as RDF, you'd have the info you need.
… But you'd need to do som estring manipulation.
… Adding a fhir:link would help, but it would have to point back to the shex, because in some resources it will have isSummary true and in some it will be false.
eric: COuld add it to the fhir ont.
https://
eric: Need to talk about the use of "identifier" in the context of the patient resource.
dbooth: Add this meta data to a separate ont file?
eric: It could require the regular fhir ont.
eric: We already have shapes for structure defs. Could have patient.resource.ttl, having some element defs w a string w patient.identifier, and you'd have to know that that is the same as patient.identifier in your resource.
… Will you perform those string operations anyway? if not, and we put in a fhir:link pointing back to the ont, and instead of using bnodes for the property constraints, we could have named nodes.
… Could also point at the shex and use shapepath to identify the spot in shex.
… Other possibility would be do string manip.
tim: Fine w the strcutre def approach, as long as there is something tying it to class patient, that should be enough, if we have the RDF structure def of patient.
ACTION: Tim to come up w concrete proposal
HL7 working group mtgs
https://
dbooth: Some jira tickets marked as reverted, "reconsider for R6".
rob: Need to redisposition it, as completed, currently in R5, mark as preapplied, and ask ITS to approve it.
ACTION: DBooth to ask Paul Knapp about zoom
Playground
houcemeddine: Need the variable for turtle.
… Also, getting 404 for claim URL.
… Wrong URL: http://
… Right URL: https://
rob: Also those URLs are not going to the same release. One is the CI build; the other is the official release.
eric: FHIR use case conventions, but the resource system doeesn't.
… Capital letter things like Observation ...
houcemeddine: If you lowercase the name, then the file is there.
eric: Maybe it's just the way deepak is generating them.
eric: It's a very flat hierarchy. Might be easier to get case sensitive URLs in a subdirectory.
houcemeddine: Also another problem in converting JSON to Turtle. Fails for medication in R5.
eric: There was a skew between the schema and the data.
… Probably need to get the newest examples.
ADJOURNED