Dear all,
Isn't the Archetype Type of the Pregnancy archetype: an organiser
archetype that is called a 'Template' in openEHR parlance?
Isn't this type of archetype one with a function of collecting/
assembling observations, evaluations and instructions?
Isn't this type of archetype the equivalent of a special screen/sheet
of paper.
One that in the Netherlands in the world of GP's is labelled now:
'Episode' and not to long ago: "Problem" in the "Problem List"?
All relevant recorded items will be linked to the "Episode".
I doubt that Evaluation is the proper label.
I propose that specific the Archetype Type is a "Template" (a complex
Archetype Type) with the function of an organiser, related to the
concept " Episodes" as constraints on the "Folder" and consisting of
links to one or more "Observations", "Evaluations" and Instructions,
etc.
Gerard
====================================================
In an off-line discussion I proposed to introduce the Archetype Type.
Below some of my thoughts after this archetype discussion day.
I felt that HISA could provide a solution. (Health Information
Services Architecture will become a CEN/tc251 European standard)
The proposal at the end helps to harmonise, combine EHRcom and HISA
plus ContSys any EHR-system.
A- COMPLEX/SIMPLE
Complex archetypes will be build using one or more Simple archetypes.
(primitive, atomic archetypes)
Complex archetypes will constrain more the Folder, Composition.
Simple archetypes will constrain mostly the Section and Entry.
Question: What are the rules? Do we need rules to decide what is a
complex and what is a simple archetype?
B- HISA
HISA defines at the Enterprise Viewpoint three workflows:
1-Subject of Care workflow
users? activities related to the management of the personal and
statistic information regarding subjects of care and to the
management of encounters of the Subject of Care with the organisation
itself, including the interactions with the funding organisations.
2- Activity management workflow
users? activities related to the management of the different types
of activities that are executed in the organisation during their
whole life-cycle, including ?but not limited to- the aspects related
to the initial requesting, the booking, the planning, the execution
and the reporting.
3- Clinical information workflow
users? activities related to the management of the clinical data,
including ?but not limited to- the aspects relating to their
collection and validation as well as the aggregation and structuring
of the elementary data according to the specific requirements of the
different disciplines and users.
This results in the following items at the Information viewpoint:
Objects
Enterprise process
Subject of care objects Subject
of Care Workflow
Activity management objects
Activities management workflow
Clinical information objects
Clinical Information Workflow
Organisation, users and authorisation objects Management of
authorisations
Resources objects
Management of resources
Classification objects
Management of dictionaries and coding
Messaging objects
Interactions with other systems
For each of the generic Enterprise Processes and the attached Objects
we will have to have Types of Archetypes. (At least 7 Major Types of
Archetypes)
If for instance we have a Complex Archetype that is used as a
clinical pathway (protocol) this must be a different Type of
Archetype than one used in documentation in a health record.
Most archetypes that can be designed in the present archetype editor
deal with Clinical information objects Type of of Archetype:
Observation, Evaluation, Plan, Instruction.
The Demograpic Archetype will belong to the class of Classification
objects.
The Patient Mandate Archetypes is part of the Organisation, users and
authorisation object class.
The discussed archetype type of Action: will belong to the Archetype
Type: Activity management objects.
ContSys will help build archetypes that can end in several Archetype
Types: Subject of Care Objects, Activity management objects,
Organisation, users and authorisation objects, ...
Archetypes used for Querry's will have to be differentiated from
those defining the semantic content of data.
So this will be Major Type of Archetype number 8, possibly.
These (eight?) Types of Archetypes will be Specific Complex archetypes.
Each Specific Complex Archetype will indicate a specific function
(context) it will be used in.
C- PROPOSAL
I propose the following Archetype Type Classification.
- 8 Types of Archetypes (Specific Complex Archetypes indicating a
specific function)
-- SubTypes of Archetypes build using:
- Generic Complex Archetypes
- Simple Archetypes
-- Generic Complex Archetypes build using:
- Generic Complex Archetypes
- Simple Archetypes
-- work --
Gerard Freriks, arts
TNO ICT
Brassersplein 2
Delft, the Netherlands
T: +31 15 2857105
M: +31 653 108732
G.Freriks at telecom.TNO.nl
On 18-jul-2006, at 22:24, Sam Heard wrote:
> The pregnancy archetype is a new approach and therefore draft - but
> I think it will be a more common approach in the future - I could
> be wrong! We are debating this at the moment and I am not sure of
> the final outcome. The pregnancy archetype has the benefit, at the
> moment, of keeping key information about a pregnancy in one place -
> a coherent data set that can persist over a long period, be shared
> and copied - find its way into the baby's health record etc. It is
> an evaluation, as it has a lot of dates, even decisions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20060719/498f8909/attachment.html>
