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 -----Original Message----- From: "Birger Haarbrandt" <birger.haarbra...@plri.de> Sent: ?5/?09/?2014 12:03 PM To: "For openEHR clinical discussions" <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 http://www.plri.de -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20140905/c60c387c/attachment.html>
