transfer/move archetype?

Heath Frankel heath.frankel at oceaninformatics.com
Sun Sep 7 19:14:30 EDT 2014


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 <birger.haarbrandt at plri.de>
To: For openEHR clinical discussions <openehr-clinical at lists.openehr.org>
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 <sam.heard at openehrfoundation.org><mailto:sam.heard at openehrfoundation.org>
To: For openEHR clinical discussions <openehr-clinical at lists.openehr.org><mailto:openehr-clinical at lists.openehr.org>
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:birger.haarbrandt at plri.de>
Sent: ?5/?09/?2014 12:03 PM
To: For openEHR clinical discussions<mailto:openehr-clinical at lists.openehr.org>
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
birger.haarbrandt at plri.de<mailto:birger.haarbrandt at plri.de>
http://www.plri.de



_______________________________________________
openEHR-clinical mailing list
openEHR-clinical at lists.openehr.org<mailto:openEHR-clinical at lists.openehr.org>
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20140907/2bed928c/attachment.html>


More information about the openEHR-clinical mailing list