See also: IRC log
<scribe> scribe: ericP
Susie: would like updates from the task forces
-> http://www.w3.org/2008/07/MappingRules/ SPASQL rule mapping paper (using COI data)
vipul: we need the mapping from RxNorm to NDC code
... we'll meet on monday to search for candidate patients
kei: have been on sabatical
... next BioRDF call will be 8Sept
... agenda: work on the hcls kb, including deri's hosting of the kb
<JohnMadden> eric,could you move your phone receiver away from your keyboard -- your keyclicks are coming through phone
<JohnMadden> much, thanks
<JohnMadden> fine noe
<JohnMadden> now
Susie: linking open drug data:
... have a call with mohammad uldrin, who will share his drug target paper with us
... expect to drill down and look for interesting questions
... expect to map peoples' data ourselves to convince people to host sparql endpoints themselves
chimezie: terminology task force in early stages, but lots of interest
... have asked JohnMadden if he's interested in leading
JohnMadden: happy to take it on, need to schedule regular meeting
<Susie> http://esw.w3.org/topic/HCLSIG/Meetings/2008-08-07_Conference_Call
-> http://esw.w3.org/topic/HCLSIG/Meetings/2008-08-07_Conference_Call?action=AttachFile&do=get&target=EHRCR.pdf EHRCR paper
<Susie> http://esw.w3.org/topic/HCLSIG/Meetings/2008-08-07_Conference_Call
linda: am representing e-clinical forum and the CDC clinical task force today
... have presented at hands 2008 (SP?)
... have large vendors and niche providers
... been working with hl7
[slide 11]
linda: tool their EHR profile to see where we need to extend it for clinical research
[slide 12]
[slide 13]
[slide 14]
linda: most research is global, needs to translate to EuroRec
[slide 15]
linda: hope for HL7 and ANSI standard in jan 09
[slide 16]
linda: release 1: make sure it had the req'd data for research
[slide 17,20]
linda: our EHR-CR is under Tier0
... Tier0 is RFD
[slide 21]
linda: current state is very separate worlds with duplicate data entry
[slide 22]
linda: next state will still require the investigator to enter some research data
[slide 23]
linda: will need separate entry system even at Teir1
[slide 24-26]
linda: Tier3 gets real reuse of the data
... we talked about the requirements for a clinic to participate in research
... we talked about what was needed, but have not prescribed any tech
[slide 29]
[slide 32]
linda: all of these workflow participants are documented in IHE
... we started with C-DASH, to populate forms
... a lot of the data is collected in a running record format
... to facilitate that, we had the sponsor site (quintiles) send the data to a holding area for the form filler to interrogate
[next slide: Cerner EHR System]
linda: this does not introduce new reqs on the user
... the blanks indicate the data that the study corrdinator needs to supply
... we want to capture transient events (reported nausea)
... have option for mod'ing current other medication
[slide Submitted to Form Receiver Successfully]
linda: no ids supplied apart from the sponsor's unique id
... demographics are preserved if they appear in the body of the case report
[slide IPL Data Archive]
[slide 44, tabular report]
vipul: what's the relationship between OHM and SDTM?
linda: [some folks] have been working on that connection
vipul: Braun kissler suggested that all the clinical models will be harmonnized with the SDTM
[slide Data Reciever]
linda: populates based on patient data passed from EHR system
[sldie 47, Next Steps]
linda: nuts and bolts stuff, like "how do you data-lock this?"
... actively looking for a trial site to compare RFD systems and conventional system
... hope to remove humans from the RFD process
... would give secondary uses (e.g. epidemiology research) that much more credibility
vipul: have talked with kathrine about this
... see COI as a complement to your work
... [ref slide low 20s]
... trying to avoid hard coding the mapping
... a declarative mapping would allow us to just push a button
... there is a big push on the HC world to follow C-CHT recommendations
... would be great to take any EMR system, and a clinical trial system (e.g. face forward) and plug them in together
linda: are you in contact with IET? have hundreds of participants in trials
vipul: picked a trial from clinicaltrial.gov
... challenges include structures and vocabularies
... in HC world, use many, e.g. RxNorm
linda: timeframe
vipul: 2 months
[proliferation of TLAs and ETLAs]
Carl_Tasswell: is there some part of what you presented today that is already hooked into semantic technologies, i.e. ontologies?
... or is it all say, XML, but not semantic yet?
linda: Braun Kissler is C-DISC's ontologist
... if you can't share meanings for "adverse event", you get soup
... can invite Braun
Susie: would like another update on the terminology/ontology work
Carl: AMIA working on ... Barry Smith et al trying to build semantic tech for clinical trials
linda: AMIA interested in RFD [was it RFD?]
vipul: one prob with ontology work is that folks are rolling new onts instead of re-using current onts
<vipul> http://esw.w3.org/topic/HCLS/ClinicalObservationsInteroperability
[Discuss Clinical Decision Support Project postponed 'till next meeting]
Carl: difficult to address competing/conflicting demands of working with standards with established software infrstructure and addressing fundamental flaws coming from non-semantic origins
vipul: avg. worker in the health care delivery system not following the academic work
... need to show how the new work provides added value
chimezie: there are legitimate concearns with existing tech
... at the same time, also legitamate critisims with building pure onts with no domain expertise
... ample space for a middle ground to work
[ADJOURNED]