<texit info> author=Bent Bisballe Nyeng (deva@aasimon.org) title=The Pentominos Patient Registration System </texit>
The patient registration system handles the pairing of a patient, an operator and an apparatus at a given location at a given time interval.
This is necessary in order to correctly store the produced data in a way that makes it possible to retrieve it at a later point in time, for further analysis.
The system consists of five basic units:
A
is used by a nurse that binds the patient with an UID, for the day.Pidio
1) client that retrieves UID from an external reader, and sends it to the Pidiod
server, together with its location ID.Pidiod
2) server that:Feed
3) data retrieval client that makes the actual apparatus communication.Artefact
data server.The system works in the following steps:
Pidiod
server, using A
.Pidio
client (by using a similar UID).Pidio
client.Feed
data retrieval client.Feed
data retrieval client sends its preconfigured location ID to the Pidiod
server.Pidiod
server responds with the patient and operator ID.Feed
data retrieval client sends the retrieved data, alongside the preconfigured apparatus ID, the newly retrieved patient and operator IDs, a timestamp and its preconfigured location ID, to the Artefact
dataserver.
Currently we have a running implementation of all systems but A
(hence the non-name). The current implementation of Pidio
utilizes a simple numerical keyboard and a magnetic strip reader, for danish health insurance card.
To improve simplicity on the system, no identification is currently made of the operator (this is at the time being not mission critical data, but must be added at a later point due to documentation procedures)
Documentation of all communication protocols between the systems exists but are not yet written in a formal way. These documents will be produced A.S.A.P.
We suggest that a new Pidio
implementation is created based on the RFID technology, reusing the rest of the patient registration system.
In order to make it more 'sexy' it is essential that the reader itself is given a sturdy look-and-feel design.
The application A
must be designed as a GUI application (and named properly) and implemented at least as a working prototype.