See also: IRC log
<vipul> EricP, LeeF: how do I make the logs open to the public?
<LeeF> vipul: less verbose :)
<vipul> Thanks Lee
<vipul> Do you know the commands for entering the agenda items?
<alanr> not me
Vipul: during the last call I posted some slides. are there any comments?
Alan: had a question on slide 4: what is P1?
Vipul: we will work on
representing temporal constraints of the data. Parsa from Texas
suggested that we can probably leverage OWL-time
... to look at the GALEN encounter model as well, and will be informing the group as progess is being made
Helen: discussed the representing
parts of HL7 in OWL
... HL7 is based on the over-arching RIM model. A class hierarchy is constructed according to the ACT type code definition.
... looked at all the codes (originally represented in OO approach), and modeled them as OWL classes
Alan: are the ACT classes modeled as RDF:List?
Helen: they are modeled as OWL
sub-classes in a hierarchy
... HL7 also has the vocabulary and code and they were also modeled as OWL classes (Slide 6
... HL7 also has "own" datatype which is different than XSD or RDF datatypes
Vipul: can we use XML schema to represent the datatypes?
Helen: perhaps not
... HL7 has clinical document arch. (CDA) for recording clinical events. These events are typically sent as HL7 messages in a hospital setting.
<alanr> example CDA -> http://www.biomedcentral.com/content/download/xml/1472-6947-7-14.xml
Helen: A comparison between XSD
schema elements and OWL constructs as made
... some can be modeled, but not all XSD constructs
... does OWL have the notion of "optional" similar to XML Schema?
Alan: OWL is missing the mandatory idea. OWL just talks about what "exists", not what should be known
Helen: OWL has everything has "optional", but only "mandatory" stuff
Alan: OWL does not make the distinction between "optional" and "mandatory"
Helen: explained slides 10, 11, 12, and 13 which contained mock up patient data described using elements from the HL7 RIM
Alan: how do we distinguish between "past" and "present" medical condition of the patient?
Helen: there is a way of saying "effective time" and "activity time" which can be used for making the distinction
Alan: what is moodCode="EVN"?
Helen: "EVN" corresponds to an event, it includes things such as "order", "request", "refferal" etc. These are more process oriented stuff
<alanr> "HL7 Clinical Document Architecture, Release 2"
<alanr> “EVN” (event), meaning that the Act is describing something that occurred; “DEF” (definition), meaning that the Act is providing a master file type of description; “INT” (intent), where the Act is describing an action plan or order; “GOL” (goal), for describing a desired outcome; “EVN.CRT” (event criterion), which represents an event that must apply for an associated...
<alanr> ...service to be considered.
Helen: will also consider more details on interval reasoning rules
Vipu to Alan: did you talk with Dan Russler?
Alan: spoke briefly with Dan and
found out that HL7 is a "model of reality"
... HL7 is trying to be an ontology, but not a file format?
Helen: data entry is also considered as "ACT" too
Alan: suggested Helen that we should take all the entries and put them in correct places.
Helen: HL7 actually never meant to be an ontology. It is more of a coding system and modeling in an old-fashioned way
Vipul: Agrees with Alan that we should view HL7 as a source of content. Also, we need to distinguish between "observations" and "acts"
Vipul: proposed that Alan, Holger
et al. take a look at how they would model the patient data in
... good bye!
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 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: Jyoti Inferring Scribes: Jyoti WARNING: No "Topic:" lines found. Default Present: Jennifer.Fostel, Jyoti, Alan, Vipul_Kashyap, Helen, Kerstin_Forsberg, Bo, Holger, LeeF Present: Jennifer.Fostel Jyoti Alan Vipul_Kashyap Helen Kerstin_Forsberg Bo Holger LeeF 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: 12 Feb 2008 Guessing minutes URL: http://www.w3.org/2008/02/12-hcls-minutes.html People with action items: 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]