Hi Heath,
it's been a while, but sometimes the old stuff becomes relevant again :)
Would still be great to take a look at this Archetype, as my colleague
Sarah Ballout is currently working on this topic. It would also be great
to learn how you use this in practice!
Thank you very much in advance!
Best,
--
*Birger Haarbrandt, M. Sc.
Peter L. Reichertz Institut for Medical Informatics (PLRI)
Technical University Braunschweig and Hannover Medical School
Software Architect HiGHmed Project *
Management Board, openEHR Foundation
Tel: +49 176 640 94 640, Fax: +49 531/391-9502
[email protected]
www.plri.de
Am 08.09.2014 um 01:14 schrieb Heath Frankel:
No problem from me. I'll need to find out how this is done.
Heath
------------------------------------------------------------------------
-------- Original Message --------
Subject: Re: transfer/move archetype?
From: Birger Haarbrandt <[email protected]>
To: For openEHR clinical discussions <[email protected]>
CC:
Hi Heath,
do you think it would make sense to share this one at the ckm? While
it would be easy for us to generate an archetype that fits our local
needs, it might be worth to contribute this archetype as a starting
point in the openEHR ckm to create something reusable.
Best,
Birger
Am 05.09.2014 14:43, schrieb Heath Frankel:
We use a patient location archetype in addition to a patient
admission archetype so that we can track patient movement around the
hospital as part of a hospital episode.
Heath
------------------------------------------------------------------------
-------- Original Message --------
Subject: RE: transfer/move archetype?
From: Dr Sam Heard <[email protected]>
To: For openEHR clinical discussions <[email protected]>
CC:
Would a patient location archetype be better? Apart from Hospital,
Building, floor, Ward, Room, Bed for example, there is a need for
planned time of transfer, actual time, time of arrival, time of
planned departure, actual time of departure.
Updates could be managed by versioned data in a persistant
composition if you wanted only one location per patient.
Needs some thought.
Cheers Sam
------------------------------------------------------------------------
From: Birger Haarbrandt <mailto:[email protected]>
Sent: 5/09/2014 12:03 PM
To: For openEHR clinical discussions
<mailto:[email protected]>
Subject: transfer/move archetype?
Hi again,
I was wondering if somebody has put some thoughts on a "patient
transfer" archetype which would serve to record the transfer of
patients between different wards within a hospital. Why would it be
interesting to have this information archetyped? For example we'd
like to calculate the time that a catheter has been applied at the
ICU. As a catheter often doesn't get removed when the patient leaves
the ICU, we need to calculate the time by using both the catheter
documentation and the patient transfer data.
In our case, SAP i.s.h. med has a simple data model for patient
transfers (Patient-ID, Type of transfer/move, timestamp, department,
ward, sometimes (bed)). Are there any use cases you can think of that
would require additional information? Would the creation of such an
archetype would be of interest for someone else?
Kind regards,
--
*Birger Haarbrandt, M.Sc.*
Peter L. Reichertz Institut für Medizinische Informatik
Technische Universität Braunschweig und
Medizinische Hochschule Hannover
Mühlenpfordtstraße 23
D-38106 Braunschweig
T +49 (0)531 391-2129
F +49 (0)531 391-9502
[email protected]
http://www.plri.de
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
