Re: [COI] Clinical Observations Interoperability Telcon January 15 2008

[Samson Tu]

Kashyap, Vipul wrote: [VK] That may be so, but given that it is so difficult and confusing to use. May be Semantic Web specifications can help here? Just to let you know that we have started an effort to create an RDF Representation of sample patient data based on classes/properties/vocabularies based on HL7/RIM/CDA.   The sample patient data is available at: http://esw.w3.org/topic/HCLS/ClinicalObservationsInteroperability/MockedUpPatientData   We are also looking at the SDTM, Detailed Clinical Models and the "Realist" approach for creating the RDF representations. Some slides taht illustrate our thoughs are available at: http://esw.w3.org/topic/HCLS/ClinicalObservationsInteroperability?action="">   Look forward to your feedback and involvement. In the SAGE project, the approach we took was that (1) patient data are represented by information model entities derived from HL7 RIM, (2) legal patient data are constrained by DCM, (3) standard terminologies such as SNOMED CT provides codes used in instances of information model entities, (4) criteria are logical expressions composed from HL7 data types, variables, functions, and queries on information structures.We had a collection of templates for logical expressions that correspond to stereotypical GELLO expressions. . Yes, I was thinking about the temporal dimensions when I said that I don't see RDF/OWL as having particular advantages. There have been a lot of work on temporal databases in the database community. OWL/SWRL's open-world semantics is also a problem. The availability of classification reasoners, however, allow you to have complex descriptions of patient states.That's an advantage. [VK] Agree with you that this the ability to specify and classify complex patient state descriptions is a key advantage. In the SAGE project, we used DL expressions to define post-coordinated terminology codes. The information model remains fixed. Complex description of patient states are, in effect, handled in terminology. How do you plan to deal with the open-world-assumption problem? If an eligibility criterion says the patient should not be taken certain drug, do you have to write closure axioms for every patient? Samson -- Samson Tu email: [EMAIL PROTECTED] Senior Research Scientist web: www.stanford.edu/~swt/ Center for Biomedical Informatics Research phone: 1-650-725-3391 Stanford University fax: 1-650-725-7944