hi vipul

<vipul> EricP, what's the status of the invited status requests?

<Susie> +1.781.662.aaee is Susie

<eneumann> vipul, should we see how is on the call?

<eneumann> I mean, who is on the call

<eneumann> who is from 813?

<vipul> Rachel

<vipul> http://esw.w3.org/topic/HCLS/OntologyTaskForce/BIONTDSEDCM

<vipul> For the wiki use case Look under Use Case Scenarios

<vipul> and click on "Latest Use Case Descriptions"

One issue I see is whether there needs to be an explicit marking

of those criteria that can, in fact, be determined from the

EMR. If not, we don't know whether a particular criterion isn't

satisfied because it can't, using the information at hand, or

whether it isn't satisfied.

e.g. 9. The patient consent for contralateral prophylactic irradiation.

Not the same kind of criterion - happens after selection rather than before

Similarly, 6. Patients who are unable to lie on their back and raise their arms above their heads in the treatment planning position for radiotherapy are excluded -

Can sometimes be determined to be true (broken arms), but in many other cases not (fatigue)

<vipul> who's on 336?

you need to also present why they satisfied criteria

e.g. navigate to treatment records to inspect them

<chimezie> +q doing too much with post processing on cohort

<eneumann> believe clinical trials (CT) need a more flexible mechanism for assessing inclusion/exclusion criteria at various clinics

<Helen> +q

<vipul> http://www.clinicaltrials.gov/ct/show/NCT00496288?order=2

<vipul> http://www.clinicaltrials.gov/ct/show/NCT00316836?order=4

<vipul> http://www.clinicaltrials.gov/ct/show/NCT00445445?order=13

<Helen> +q

e.g. 6. Patients who are unable to lie on their back and raise their arms above their heads in the treatment planning position for radiotherapy are excluded -

versus:

There is no condition noted in EMR that would prevent the patient from raising arms...

<eneumann> ACTION: Landen and Eric to work on high level set of candidate selection processes and activities [recorded in http://www.w3.org/2007/09/11-hcls-minutes.html#action01]

This is scribe.perl Revision: 1.128  of Date: 2007/02/23 21:38:13  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: alanr
Inferring Scribes: alanr

WARNING: No "Topic:" lines found.

Default Present: +1.813.396.aaaa, Vipul_Kashyap, Kerstin_Forsberg, +46.4.63.3.aabb, Alan, +1.801.736.aacc, Chimezie_Ogbuji, +1.801.736.aadd, susie, Eric_Neumann, Rachel, Stan_Huff, Bo, +1.336.788.aaee, Helen_Chen
Present: +1.813.396.aaaa Vipul_Kashyap Kerstin_Forsberg +46.4.63.3.aabb Alan +1.801.736.aacc Chimezie_Ogbuji +1.801.736.aadd susie Eric_Neumann Rachel Stan_Huff Bo +1.336.788.aaee Helen_Chen

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 11 Sep 2007
Guessing minutes URL: http://www.w3.org/2007/09/11-hcls-minutes.html
People with action items: eric landen

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report