Meeting minutes
FHIR RDF Playground
(James does demo)
james: problem w some structure defs causing pre-processing errors
eric: For any version you should be able to get both the structure def and matching examples -- they're paired.
… Look at 4.2 and 5-something.
rob: There's an R5 snapshot release that's more stable.
eric: Diff from snapshot vs CI build probably won't be much difference.
rob: Agreed.
james: I hid the Bundle example, but will add it back in.
eric: In manifest, Suggest making the version be an array
eric: You could group the examples under R4 vs R5.
dbooth: Request moving the R5 and Advanced buttons up, away from the example tabs.
dbooth: Houcemeddine, anything to ask James?
houcemeddine: Talk w James later this week.
eric: Suggest working out some workflow. We have input from FHIR JSON and from FHIR RDF, and the validator should operator on both of them. Somebody will want to figure out which input buttons to use.
dbooth: How about making the Turtle window be editable, and add a button below to validate.
james: I can do that
… how about like this? https://
houcemeddine: Need two types of validation: extensive vs not. Patient schema.
dbooth: It should be in the generated shex.
https://
ACTION: James to send invite to houcemeddine to discuss playground
HAPI
eric: Done part of the job of converting HAPI back to use R5 RDF.
… Did fhir:v, haven't yet done value[x], lists, or shortening property names.
FHIR build and FHIR RDF validation
dbooth: Turns out the special turtle parser is needed for FHIR validator.
jim: I'll work on that.
… When does the validator run? In the build?
rob: Runs standalone. I thought it was run in the build.
… On separate issue, someone posted an invalid code sys, but Grahame had disabled the validation so it wasn't caught.
ACTION: DBooth to create a jira ticket for FHIR RDF validator
Ontology generation
daniel: Need to know what we want to do in the code. Lots of edge cases. Some easy, some hard.
daniel: How are properties defined?
jim: whatever's after the last period is the shortened property name.
rob: Just take the tail. Are they the same property?
dbooth: They're the same property by fiat.
eric: Some look wrong, but they reflect things that the pub process plans to address, to make them more consistent.
… Any remaining that look wrong will be addressed eventually.
dbooth: They can always be distinguish by context in the resource.
daniel: Second issues is value[x] types, e.g., author[x]
… Property becomes fhir:author
dbooth: And add a type arc also.
daniel: What about modified property names?
dbooth: Don't try to make disjointness statements about modified properties.
eric: Don't confuse semantics w datatypes. Looks weird to use the same property w all these different datatypes. But in good reusaalbe properties, they're separated.
… Good that we're not giving range constraints.
… Might not even want to include range constraints on any properties.
daniel: Intend to not include any range constraints.
AGREED: Not include range constraints.
Concept IRIs and IRI stems
gaurav: Everything remaining is not needed for R5 deadline.
… Re LOINC proposal, we're up to 8 positive points and need 15.
… Reached out to Reuben. Who is Family requirement?
rob: Somebody doing v2 or v3 group.
… Suggest Jean Detau(sp?)
… One other thing: adding IRIs to known ID systems. The list was voted and approved, but then moved to IDs in THO.
… Now a NamingSystem in terminology.hl7.org
… I created an HTA ticket. SHould I create a third UTG ticket, to make the code change?
rob: Yes. Would be pro forma.
ITS meeting
dbooth: ITS Meeting 3pm Eastern US Feb 22 Wednesday
… Who else can join?
Rob: i probably can
daniel: I can.
ADJOURNED