| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| pentominos:registration [2009/02/19 20:04] – deva | pentominos:registration [2009/02/20 11:53] (current) – deva |
|---|
| The system consists of five basic units: | The system consists of five basic units: |
| - A system ''A'' is used by a nurse that binds the patient with an UID, for the day. | - A system ''A'' is used by a nurse that binds the patient with an UID, for the day. |
| - The ''Pidiod''((PatientID Input Output Daemon)) server that stores the mapping of a location with patient and operator IDs (through UIDs). | - The ''Pidio''((PatientID Input Output)) client that retrieves UID from an external reader, and sends it to the ''Pidiod'' server, together with its location ID. |
| - The ''Pidio''((PatientID Input Output)) client that tells the ''Pidiod'' server to connect a patient or operator ID with its location ID (through UIDs). | - The ''Pidiod''((PatientID Input Output Daemon)) server that: |
| - The ''Feed'' data retrieval client that makes the actual apparatus communication. | * Handles the maps between UID to patient ID. |
| | * Handles the maps between location ID to UID. |
| | - The ''Feed''((Feed Extravagates External Devices)) data retrieval client that makes the actual apparatus communication. |
| - The ''Artefact'' data server. | - The ''Artefact'' data server. |
| |
| {{:pentominos:registration.svg?300x200}} | {{ :pentominos:registration.png?300 |Systems overview diagram. Arrows indicate data transmission/sharing.}} |
| |
| The system works in the following steps: | The system works in the following steps: |
| * The ''Pidiod'' server responds with the patient and operator ID. | * The ''Pidiod'' server responds with the patient and operator ID. |
| * The ''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. | * The ''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. |
| * ... further treatment is taken ... | * ... jump back to step //The patient is sat down in front of an apparatus.// and cycle until done ... |
| * The patient optionally returns the RFID tag when leaving. | * The patient optionally returns the RFID tag when leaving. |
| | |
| | =====What is already there===== |
| | 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) |
| | {{ :pentominos:cpr_tastatur.jpg?200 |The numerical keyboard and a magnetic strip reader}} |
| | 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. |
| | |
| | =====What needs to be made===== |
| | 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. |
