On Mon, 22 Dec 2003, Thomas Beale wrote:
...
> In an openEHR system, BPs are captured as Observations, which are a
...
> described by the archetype for BP measurement, which I have reproduced
> below
Thomas,
As we previously discussed in February 2003:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07983.html
like OIO, OpenEHR also allows ad hoc definition of new archetypes.
Therefore, I believe OpenEHR will still require archetype-to-archetype
translators - despite the much more complex structure for describing
archetypes (compared to OIO forms).
> And yet - this still can be treated as quite simple data in the EHR, and
> it can be queried in the same way, regardless of whether it was part of
> a neonatal exam, general exam, or whatever else.
This is the same as saying if you use the _same OIO form_ to record a
neotatal exam, general exam, etc, your reporting application will be able
to "understand" the semantic content without an additional translation
step.
If you use the same "archetype" across all these "exams", that is.
What if you use different archetypes across these exams to represent
blood pressure?
Now, maybe OpenEHR says "no, end-users cannot be allowed to use the wrong
archetype to represent the same/similar/related semantic content". Well,
then how do you propose to detect/enforce/prevent that? (I don't think you
can without entirely eliminating ad hoc archetype authorship.)
So, in the end, the more complex archetype description language developed
by OpenEHR does not eliminate the need for archetype-to-archetype
translators, which is what I explained on Feb 10, 2003 during a discussion
with Helma van der Linden:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07879.html
Consequently, maybe a minimalistic metamodel for forms (=archetypes) + a
robust translation facility will be adequate (and much simpler). That's
what we hope to find out via OIO's new translator module (thanks to
Horst's help, it should become part of OIO-1.0.8 to be released in the
next few weeks.)
Best regards,
Andrew
---
Andrew P. Ho, M.D.
OIO: Open Infrastructure for Outcomes
www.TxOutcome.Org
