COI Functional Requirements - ways to implement them

Hi Vipul -

Your functional requirements spreadsheet for a "recruitment" use
case seems to be developing fine in its center rows.  To make a
real impact, however, such mappings must migrate to executables
that can actually suggest real patients as profile candidates.

I've been exploring designs that can implement your spreadsheet
rows as a web service of "predicates" helpful to achieving this.
The simplest design [1] just wraps a shell of customized JSPs
that can make such mappings around any working EMR system.

To support patient-matching for any protocol of interest, a user
must also describe that protocol's goals.  A browser-based web app
[2] can help input parameters to automate a recurring EMR search,
which seems to me about what is optimal in practice.

   [1] see "EMR Wrappers" under BIONTDSEDCM Use Case Scenarios
   [2] see "Search Agents" under BIONTDSEDCM Use Case Scenarios

I'd like to discuss both in Tuesday's telcon, as proposals for
the F2F brainstorming session about next steps.  Questions and
feedback coming first by email from the group would be welcome.

best regards,
Dan Corwin



Kashyap, Vipul wrote:
> Hi,
> 
>  
> 
> As discussed in the last telcon, I have refined the spreadsheet and 
> identified clear examples of how we would represent
> 
> the various mappings across the DCM and SDTM standards. In particular, 
> have tried to illustrate (in red font)
> 
>  
> 
> -          Mapping between Blood Pressure related classes between the 
> DCM and SDTM
> 
> -          Mapping between Blood Pressure related terminological 
> concepts between relevant terminologies
> 
> -          Mappings between data types and units across HL7 and SDTM
> 
>  
> 
> Look forward to further feedback and discussion at the next telcon on 
> the coming Tuesday.
> 
>  
> 
> Thanks and Regards,
> 
>  
> 
> ---Vipul
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* public-hcls-dse-request@w3.org 
> [mailto:public-hcls-dse-request@w3.org] *On Behalf Of *Kashyap, Vipul
> *Sent:* Tuesday, October 16, 2007 8:46 PM
> *To:* public-semweb-lifesci hcls; public-hcls-dse@w3.org
> *Cc:* Stanley Huff; Yan Heras; Oniki, Tom (GE Healthcare, consultant); 
> Joey Coyle; Landen Bain; Bron W. Kisler
> *Subject:* [BIONT-DSE][COI] Clinical Observations Interoperability 
> Telcon October 23rd, Tuesday 11:00am - 12:00pm US EDT
> 
>  
> 
>  
> 
> _Clinical Observations Interoperability Telcon_
> 
>  
> 
> http://esw.w3.org/topic/HCLS/OntologyTaskForce/BIONTDSEDCM
> 
> */ /*
> 
> _Date and Time:_
> 
> October 23^rd  Tuesday 11:00am – 12:00pm EDT
> 
>  
> 
> _Agenda_
> 
> 1.   Semantic Web Related questions from Landen Bain, Bron Kissler and 
> Tom Oniki – Alan to post minutes and discuss feedback
> 
> 2.   Discuss DCM Models wrt Functional Requirements – Tom Oniki
> 
> 3.   Feedback and refinement of F2F agenda.
> 
> 4.   Discuss SDTM Models wrt Functional Requirements – Bo, Kirsten, Bron 
> Kissler, Rachel (time permitting)
> 
> 5.   Discuss BRIDG Model wrt Functional Requirements – Alan, Vipul, 
> Rachel (time permitting)
> 
>  
> 
> _Telcon Details:_
> 
>  
> 
> Phone
> 
> 	
> 
> +1 617 761 6200, conference 24668 ("BIONT")
> 
> IRC
> 
> 	
> 
> irc://irc.w3.org:6665/hcls
> 
> Browser-based IRC client
> 
> 	
> 
> http://www.w3.org/2001/01/cgi-irc
> 
>  
> 
> Cheers,
> 
>  
> 
> ---Vipul
> 
>  
> 
>  
> 
> The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
>

Received on Monday, 29 October 2007 16:21:09 UTC