Thanks Sam,
Your explanation has been very useful to understand
RM. I work more in implementing EHR and HIS and deal
with users.
Gerard gave the technical explanation but I thought it
will be useful if I can understand it in user?s point
of view.
Your explanation has solved my query. I think while
system design and development, user perspective is
very important. It should based on real life use cases
and scenarios
I thank you and Gerard for clarifications.
Regards,
Ankush
--- Sam Heard <sam.heard at oceaninformatics.biz> wrote:
---------------------------------
Ankush
It is a recording model that contains features
required for all legalrecording and audit trail, for
tracing inputs and outputs and is thebasis for all
software. The software has to know about the
referencemodel. The reference model means that the EHR
can accept anyinformation at all - the way specific
information is recorded dependson the archetype (but
it always uses the features of the referencemodel!).
The clinical concepts are expressed in archetypes.
Most software usingan EHR service will not need to
know what is in archetypes - just howto work with
archetypes. So data entry, display and other
componentsneed to be archetype-aware but not
understand the clinical concepts.The components for
data entry can have archetype-specificspecifications
(we call them templates for data entry and
displayscripts for viewing) of how to present this to
the user.
Decision support and clinicians need to know what an
archetypeexpresses - because the health care of a
patient will depend on this.Some other smart software
will as well - perhaps determining thebilling
automatically - etc.
Does this help?
Sam
ankush shinde wrote:
Thanks Gerard ,This gives some understanding of
RM.Will it be more useful if we can understand it in
moreend user perspective?Regards,Dr. Ankush--- Gerard
Freriks <gfrer at luna.nl> wrote:
Dear Rodrigo,The Reference Model defines a generic
model of anydocument.And is mapped onto (into) the
persistence layer.Archetypes are constraints on the
Reference Modelbut are formed using its own
meta-model.Your possibility number 1 is not
correct.Possibility 2 is correct.Real data is
'validated' (better: defined) using theArchetype (the
constraints)And the archetypes are validated (defined)
using thearchetype meta- model.Gerard-- <private>
--Gerard Freriks, artsHuigsloterdijk 3782158 LR
BuitenkaagThe NetherlandsT: +31 252 544896M: +31 653
108732On 3-jul-2006, at 20:54, Rodrigo Filgueira
wrote:
I've been going round in circles about this
question all weekend,
and have two ideas.1. It's basic and most important
use is to provide
reference to
check the correctness of the arquetypes.2. It is
needed for some types of persistence
design
Why am I asking myself this? because once
assertions are
implemented, all that may be needed for validating
real data may be
included in archetypes, can't it?am I missing
something?thank you
__________________________________________________Do
You Yahoo!?Tired of spam? Yahoo! Mail has the best
spam protection around http://mail.yahoo.com
--
Dr. Sam Heard
MBBS,FRACGP, MRCGP, DRCOG, FACHI
CEO and Clinical Director
OceanInformatics Pty. Ltd.
Adjunct Professor, Health Informatics,Central
Queensland University
Senior Visiting Research Fellow,CHIME, University
College London
Chair, Standards Australia, EHRWorking Group
(IT14-9-2)
Ph: +61 (0)4 1783 8808
Fx: +61(0)8 8948 0215
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
