Thanks Hugh for the quick reply. I think this is an excellent example of
what can be achieved. Are the records real or make-up? If Make-up, how
were they generated. I would like to know, if possible, hoe to access and
look at these EHRs.
Thanks
Ed
Hugh Leslie
<hugh.leslie at ocea
ninformatics.com> To
Sent by: For openEHR technical discussions
openehr-technical <openehr-technical at openehr.org>
-bounces at openehr. cc
org
Subject
Re: Formal methods for Evaluation
02/09/2008 07:01 ofInteroperability
AM &Maintainability?
Please respond to
For openEHR
technical
discussions
<openehr-technica
l at openehr.org>
Hi Ed
We have a pure openEHR repository that has been used for load testing over
the last 18 months or so. Currently it has over 350,000 EHRs (i.e. one
persons record) in it and each EHR has about 60 compositions (a composition
being one document such as a discharge or a test result). I have to admit
that there is some variation in the archetypes and templates used but there
is some sameness to the data. So we have a lot of test results, discharge
summaries etc. Some are large and some are small.
Its viewable over a web application that we call EHRView - not a clinical
app, but really just an EHR viewer although you can now capture data
through forms built from openEHR templates. We are getting excellent
performance in terms of query of this number of EHRs.
Happy to take this offline and give you more details if you would like.
regards Hugh
William E Hammond wrote:
Hugh,
Can you expand on 20 million of what. I think htis is an astounding
figure. What is the quality of the compositions? I'd like to have
more
info if possible. I think that number ois much more than any of us
anticipated.
Thanks
Ed Hammond
Hugh Leslie
<hugh.leslie at ocea
ninformatics.com>
To
Sent by: For openEHR technical
discussions
openehr-technical
<openehr-technical at openehr.org>
-bounces at openehr.
cc
org
Subject
Re: Formal methods for
Evaluation
02/08/2008 07:33 ofInteroperability
AM &Maintainability?
Please respond to
For openEHR
technical
discussions
<openehr-technica
l at openehr.org>
Hi Charlie
We have an openEHR repository here with about 20 million compositions
in it
- how many do you want? :)
regards Hugh
--
________________________________________________
Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI
Clinical Director
Ocean Informatics Pty Ltd
M: +61 404 033 767 E: hugh.leslie at oceaninformatics.com W:
www.oceaninformatics.com
Charlie McCay wrote:
Tom
Many thanks for this -- are there examples of TDS schemas or
instances available?
Also are there any example document instances available --
particularly for the draft Extract schema, but any instances or
instance fragments would be useful.
All the best
Charlie
Charlie McCay, charlie at RamseySystems.co.uk
Ramsey Systems Ltd, 23D Dogpole, Shrewsbury, Shropshire SY1 1ES
tel +44 1743 232278 / +44 7808 570172 skype: charliemccay
linkedin:charliemccay
-----Original Message-----
From: openehr-technical-bounces at openehr.org [
mailto:openehr-technical-bounces at openehr.org] On Behalf Of
Thomas
Beale
Sent: 07 February 2008 22:41
To: For openEHR technical discussions
Subject: Re: Formal methods for Evaluation ofInteroperability
&Maintainability?
Charlie McCay wrote:
All
I do not recognize this description of RMIMs as
modifications
to the
HL7 RIM. RMIMs express constraints on the HL7 RIM - the
RMIM is
a
static model that is defined as a constraint on the RIM,
with
all the
semantics defined in the RIM and associated vocabularies.
There
is NO
additional semantics introduced in the refinement
process, just
a
restriction on the set of conforming structures.
It is true that the HL7 XML ITS uses the association
names from
the
RMIM for the XML element names, as a pragmatic choice to
aid
implementation. It would be perfectly possible to write
an ITS
that
used the underlying RIM association names. This was
considered
and
felt to be less useful by those doing implementations
I am yet to see an openEHR XML ITS for instance data, but
am
sure that
a similar implementation trade-off between serializing
the
underlying
reference model or serializing based in the archetype
definitions
would be worth considering
*Charlie,
all the XSDs for openEHR data are here:
http://www.openehr.org/releases/1.0.1/its/XML-schema/index.html
see the top group. These schemas hold for all openEHR data,
regardless
of archetype, template or terminology.
There is a different kind of machine-generated schema which we
call
the
Template Data Schema (TDS); any openEHR template can have this
generated
for it. This enables messages to be created specific to a
template,
e.g.
a specific kind of path result. The data that conform to a TDS
can be
machine converted into standardised openEHR data for addition
to an
openEHR system. The key in all this is that TDSs are completely
machine
generated, not hand-built; the source of truth is always the
archetypes
and templates. The descriptions and diagrams on this page
provide a
high-level explanation.
- thomas beale
*
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
--
________________________________________________
Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI
Clinical Director
Ocean Informatics Pty Ltd
M: +61 404 033 767 E: hugh.leslie at oceaninformatics.com W:
www.oceaninformatics.com _______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
