If I understood some of the earlier discussion, HL7 does not have a
formal ontology, or at least the implementation is not constrained by
it.
If HL7 did have a formal ontology, you could map it to the openEHR
ontology and develop a combined ontology to resolve differences.
Since it doesn't, it's sensible to constrain HL7 messages to fit the
openEHR ontology by mapping at the interface level.
Colin
-----Original Message-----
From: openehr-technical-bounces at openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Gerard
Freriks
Sent: Thursday, 23 April 2009 7:56 AM
To: For openEHR technical discussions
Subject: Re: Layers of interoperability, OWL and openEHR
Dear Seref,
HL7 made serious mistakes.
They used the RIM to model the real world events and
documentation about it.
Mixing two different types of models is impossible.
The best that can happen is that in one model-world one refers
to constructs in the other world.
Models of reality.
Ontologies are models of reality and in semantic
interoperability we use them to construct lists of codes, labels and
descriptions.
Because of the ontology we are able to make inferences, to
express knowledge behind the lists of codes, labels and descriptions.
Because of the ontologies we are able (eventually) to make
applications more intelligent and kind of let them reason.
Models of documentation.
EN13606/openEHR and HL7v3 CDA are models that help people
document data and information.
It helps them archive, exchange and re-use.
All data and information stored, is stored with all contextual
information and meta-information about the documentation process.
Models of documentation store data and information in named
chapters, sections, paragraphs.
They allow users to write complex sentences, using documentation
patterns humans agreed upon.
They use words from dictionaries (coding systems, terminologies,
classifications and code lists).
They never map to ontologies. Should never map to ontologies and
vice versa.
Any attempt to try to map Ontologies to Syntax structures is
bound to fail.
It is squaring the circle.
Gerard
-- <private> --
Gerard Freriks, MD
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands
T: +31 252544896
M: +31 620347088
E: gfrer at luna.nl
Those who would give up essential Liberty, to purchase a little
temporary
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11
Nov 1755
On Apr 22, 2009, at 11:06 PM, Seref Arikan wrote:
Hi Charlie, a couple of good points! Comments are
inline.
I am working on how the NHS Logical Record
Architecture (LRA) asserts conformance/compliance to external standards.
One thing that is required is a semantic mapping between the LRA
specifications and the external standard. Initially I am mainly
interested in mapping the static models. (Reference models, datatypes,
templates, archetypes, etc)
Great starting point. My question is: let's assume
you'll have the complete mappings tomorrow morning, given to you by
someone. For now, let's say they are expressed in OWL. All the possible
mappings for static models you've liste are complete. Now, what would
you do with them? I'd love to hear your use cases for the situation
where you have these mappings.
#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared
by MailMarshal
#####################################################################################
####################################################################################################################
IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be
read or used by the named addressee.
It is confidential and may contain legally privileged information. No
confidentiality or privilege is waived or lost
by any mistaken transmission to you. The CTC is not responsible for any
unauthorised alterations to this e-mail or
attachment to it. Views expressed in this message are those of the individual
sender, and are not necessarily the
views of the CTC. If you receive this e-mail in error, please immediately
delete it and notify the sender. You must
not disclose, copy or use any part of this e-mail if you are not the intended
recipient.
#####################################################################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090423/50dddb3f/attachment.html>