RE: An argument for bridging information models and ontologies at the syntactic level

Perhaps you can elaborate on your idea of SNOMEDCT the information and what kind
of transformations are involved to get SNOMEDCT the terminology.
[VK] SNOMED-CT the terminology would be a set of codes, but as Alan suggests in
a follow up e-mail, there is an ontology underlying these codes, e.g., the
Ontylog representation
of Snomed. The transformation is analogous to what Alan has proposed in his
KR-MED paper. 

			Several years ago, I tried to formulate the Clinical
Element Model as an ontology without any success. I came to see it as a very
flexible data structure for encoding information. If you have better luck
formulating it as an ontology, I'd like to know about it.
			[VK] Tom Oniki, I and others are working on capturing
the semantics underlying the Clinical Element Models as an ontology as a part of
the COI project. We need to understand the semantics of each of the attributes
before creating an ontology. This is close
			to completion and will be putting it on the wiki
shortly. We are working off the more recent XML based CEMs as opposed to the
older ASN1 based CEMs you may have worked on earlier.
			 
			----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.