See also: IRC log
<vipul> rrsagnet, make logs world-visible
<vipul> Zakim aabb is Rachel_Richesson
taking up 2. Functional Requirements distillation from Rachel’s Use Cases: Vipul
we are reviewing functional requirement spreadsheet
First sheet is slide 11 from HIMSS document
rules will come when looking at protocol specification
Data content tab:
vipul went through rachel's set of protocols. comments that they cover a wide space
in sheet listed all kinds of information in the protocols
second list are things we are interested in from the medical history
medical conditions are mixture of expressions (lab result x > 4.5) and plain terms (Bradycardia)
missed last discussion - someone else say what happened?
a primitive concept is one that can only be determined by direct observation
Rachel mentions SNOMED has a definition of primitive
SNOMED CT concepts are either primitive or fully defined. A concept
is primitive when its modeling (attributes and parents) does not fully
express its meaning.
Fully defined concepts can be differentiated from their parent and
sibling concepts by virtue of their relationships. Primitive concepts do
not have the unique relationships needed to distinguish them from
their parent or sibling concepts
that the one, rachel?
oops rachel not on irc
4th list is lab results
t(8;21)(q22;q22). is a lab? or a condition?
human variation sometimes said to be 1%
lab: give a sample, get a result
signs: more subjective
Polyadenopathy = condition
dosage of medication doesn't seem to play in criteria, as opposed to when in medical setting
need to check on "incarcerated"
<scribe> ACTION: yan: To review the list to see which terms are in her system [recorded in http://www.w3.org/2007/10/16-hcls-minutes.html#action01]
<scribe> ACTION: Alan/Vipul to review BRIDG for these [recorded in http://www.w3.org/2007/10/16-hcls-minutes.html#action02]
<scribe> ACTION: Kersten, Bo, Landen, Rachel for SDTM [recorded in http://www.w3.org/2007/10/16-hcls-minutes.html#action03]
review mapping requirements
relations between intervals usually determines represenation
Susie: Lilly has their own terminology. Could possibly be convinced to open it
Vipul: At F2F want to talk about
what pharmas can do to open this up
... F2F convince health care to give us 40-50 records
Mapping is more than equality assignment
<Susie> Got to go...
Two issues with mapping - lack of definitions/ disagreement of definition with usage
units and data types
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: Vipul_Kashyap, +1.317.435.aaaa, Susie_Stephens, Alan, +1.813.396.aabb, +1.781.316.aacc, Rachel_Richesson, Dan_Corwin, Kavitha, +1.801.736.aadd, Yan Present: Vipul_Kashyap +1.317.435.aaaa Susie_Stephens Alan +1.813.396.aabb +1.781.316.aacc Rachel_Richesson Dan_Corwin Kavitha +1.801.736.aadd Yan 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: 16 Oct 2007 Guessing minutes URL: http://www.w3.org/2007/10/16-hcls-minutes.html People with action items: alan kersten vipul yan 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[End of scribe.perl diagnostic output]