W3C

- DRAFT -

Semantic Web Health Care and Life Sciences Interest Group Teleconference

10 Oct 2017

See also: IRC log

Attendees

Present
David, Booth, Tony, Mallia, Gopi, EricP, Rob_Hausam
Regrets
Chair
David Booth
Scribe
dbooth

Contents


Semantic MediaWiki for structured healthcare data (Tony Mallia)

tony: This grew out of FHIR RDF work.
... Trying a binding simplification
... Built a small EHR to test it out
... Patient-Patient link (I think) is to say that two patients are the same person.
... We can also find a valueset. Head of SNOMED tree is substance.
... But it is also a subclass of FHIR:AllergyIntolerance.
... I used Semantic MediaWiki to try this out.
... I had used it for other things
... Classess are called Categories in Semantic MediaWiki.
... Nice thing is that the templates include SPARQL-like queries.
... and they define visual presentation.
... Took me less than a week to do this!
... Exceptional productivity.
... It implements some of the OMG MDA concepts.
... Gartner measured productivity gain as 23x with tooling from a Spanish company using Semantic MediaWiki.

(Tony starts demo)

tony: Health record is generated from the query
... Can even do chained properties with inverse properties, in the queries.
... For valueset codes, we can even display the definition when you hover over.
... You can select semantic codes.
... I've shown Clinical Status class as the root, but you can tell it to have no root instead.
... Mouse-over can also be used for explaining various fields.
... The record is categories as a FHIR AllergyIntolerance.
... The platform will list them all.
... I can also add things that are like properties.
... Pages are sort of like blank nodes.

eric: Any idea of scalability? All of snomed?

tony: Some public sites seem to be large. I don't see a scalability problem, because you're on top of MediaWiki.
... It has pages and triples.
... This triplestore is on top of mysql, but you can do other storage underneath.

gopi: Can you query using SPARQL?

tony: It is SPARQL-like, but not SPARQL.

dbooth: How do you see this being used? What would be the best use of it?

tony: I'm trying this out for publishing a paper. There's a cross-over from wiki to 4GL language, and an informatics community can use it. No programming needed.
... I think we are about to have a revolution in software. Anywhere that you use spreadsheets etc for knowledge, it could be done this way.
... I suspect this could be a new platform for developing EHRs.
... Don't know who will pick it up.
... Huge reduction in the dev cost.
... There will be lots of resistance from status quo vendors.
... This can also support inter-wiki communication.
... To pull allergies from other providers.

dbooth: Plan to do more with this?

tony: Submit for publication.
... Then look for sponsorship.

dbooth: You put in some FHIR things manually. If this were done seriously, then all of the FHIR structure definitions, valuesets, etc., could be loaded programmatically.

tony: Yes, though there would be a versioning issue when the FHIR spec changes.
... Currently looking at styles to use for transformations.
... For CRUD on complex graph structures, this is very good.

gopi: Using an RDF triplestore?

tony: It puts them in mysql right now, but can be configured with a real triplestore.

https://www.semantic-mediawiki.org/wiki/Help:SPARQLStore/RepositoryConnector/Generic

dbooth: I could see it being used for data capture similar to Red Cap: https://www.project-redcap.org/ such as surveys.
... Value that I see is in being able to rapidly create new data capture forms, for structured data capture, but have them properly semantically linked to existing records.

gopi: OpenEHR has a collaboration with Marant (in Slovenia), have a platform to create a model in OpenEHR, export to their platform, and it creates the forms.
... This may be able to do something similar.

tony: Once you've built your ont with a language, you're stuck with that language. I suspect there is opportunity for standardizing it.

<inserted> Screenshots and slides from Tony's demo: https://lists.w3.org/Archives/Public/www-archive/2017Oct/0002.html

ADJOURNED

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/10/10 16:51:12 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: i|ADJOURNED|Screenshots and slides from Tony's demo: https://lists.w3.org/Archives/Public/www-archive/2017Oct/0002.html

WARNING: Replacing previous Present list. (Old list: David_Booth, Tony_Mallia, Gopi, EricP, Rob_Hausam)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ David, Booth, Tony, Mallia, Gopi, EricP, Rob_Hausam

Present: David Booth Tony Mallia Gopi EricP Rob_Hausam
No ScribeNick specified.  Guessing ScribeNick: dbooth
Inferring Scribes: dbooth
Found Date: 10 Oct 2017
Guessing minutes URL: http://www.w3.org/2017/10/10-hcls-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]