W3C

- DRAFT -

FHIR/RDF

02 Apr 2019

Attendees

Present
Ken_Cottrell, EricP, Pawel, David_Booth
Regrets
Chair
David Booth
Scribe
dbooth

Contents


Introductions

Ken: Interested in CDISC / FHIR

Paper on ShEx / IPSM comparison

pawel: No updates from others. Deadline tomorrow Hawaii time, for abstract. Still a week for the paper, for ISWC.
... Paper deadline Apr 10.
... If we don't make that, next deadline is for Semantics Conference Apr 23.
... ISWC is in Aukland. Have funding to go.

https://github.com/szmejap/ShEx-IPSM-Article

eric: Suggest not saying that SW is growing, but use cases are growing.

CDISC and FHIR

ken: Talking to a company about a project on clinical trial metadata. They are looking at FHIR as an integration mechanism. They pointed me to the CDISC website. Ref had something to do with the FDA. Helps track drugs.

Some links from search: https://www.google.com/search?client=ubuntu&channel=fs&q=cdisc+site%3Ahttp%3A%2F%2Fbuild.fhir.org%2F&ie=utf-8&oe=utf-8

ken: Previously worked with RDF and ont.

david: Two angles. Previous work on representing CDISC in RDF, independently of FHIR.
... Second is separate effort of connecting FHIR to CDISC.

https://build.fhir.org/mappings.html

https://www.cdisc.org/standards/data-exchange/define-xml

ken: For bus dev, vendors are getting into FHIR. Clinical trials companies also working on it. Uptake of FHIR?

eric: Clinical research orgs are oriented around SDTM and XML, but FDA is steering away from that. FDA is modeling clinical events that are not captured by SDTM. People are trying to put it into STDM. FDA wants to combine clinical studies to get safety signals, etc.
... Cool thing to do would be to model therapeutic areas in FHIR, and give roll-ups of that for submission.
... The win is to detect or categorize or stratify the clinical events to find the people you actually want in your study.
... That's hard because studies are done before the fact. Data goes to EMR and into the repo that eventually gets submitted to FDA. Typically in trials people don't try to dredge clinical pathways back out of EMRs. They do it for one-off studies, but no std way to do that.

ken: Most people using EMRs for billing -- not evaluating pathways or which drugs work?

eric: right.

ken: Part of the interest in FHIR is that there will be an opportunity to harvest info from EMR in systems.

eric: Also OMOP standard.
... ohdsi.org
... Also PCORNET.
... I2B2 people are also in this space, though more chaotically.
... https://www.w3.org/2013/12/FDA-TA/

FDA Therapeutic Areas modeled as RDF

<scribe> ACTION: Eric to spell out "Therapeutic Areas"

ken: Previously working on a project at Siemans on architecture using Elk and Jena, but never could handle the semantic mapping problem.
... Medical code mapping
... Wanted to use ont engine for semantic mapping.

david: Look at the webinar and tutorial from Harold Solbrig: http://yosemiteproject.org/recorded-webinars/

ADJOURNED

Summary of Action Items

[NEW] ACTION: Eric to spell out "Therapeutic Areas"
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/04/02 16:06:45 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Ken_Cottrell EricP Pawel David_Booth
No ScribeNick specified.  Guessing ScribeNick: dbooth
Inferring Scribes: dbooth

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: eric

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]