1. PMU Personal Medical Unit Kasper Høj Jæger Nielsen – 19980150 Martin Kjeldsen – 20002072 Lars Sarbæk Kristiansen - 20050013

2. PMU Architecture

3. PMU Requirements R1 Syncronization of data between PMU and synchstation should be possible.. R1 Syncronization of data between PMU and synchstation should be possible.. R2 There should exist an adapter repository that specifies a protocol for representing PMU data in different EPR systems. R2 There should exist an adapter repository that specifies a protocol for representing PMU data in different EPR systems. R3 It should be possible to store data from personal medical devices. R3 It should be possible to store data from personal medical devices.

4. PMU Requirements R4 The PMU can be used in emergencies, e.g. a paramedic can read medical data on location. R4 The PMU can be used in emergencies, e.g. a paramedic can read medical data on location. R5 Data should be displayed in a simplified form to the paramedic on his Portable PMU Reader (e.g. a PDA). R5 Data should be displayed in a simplified form to the paramedic on his Portable PMU Reader (e.g. a PDA).

5. PMU Requirements R6 Data should be displayed in a detailed form to a doctor on a PC. R6 Data should be displayed in a detailed form to a doctor on a PC. R7 A schedule for a user of the PMU in regards to medicine intake should exist. R7 A schedule for a user of the PMU in regards to medicine intake should exist. R8 Authentication should be employed when synchronizing. R8 Authentication should be employed when synchronizing.

6. Class diagram

7. Modelling of requirements R1: Modelled in the PMU and SyncStation classes R1: Modelled in the PMU and SyncStation classes R2: Modelled in the Server class R2: Modelled in the Server class R3: The MedicalDevice class collects data from a medical device and transmits this to the PMU R3: The MedicalDevice class collects data from a medical device and transmits this to the PMU R4: Modelled in the PMUReader class R4: Modelled in the PMUReader class R5: Considered in the PMUReader class R5: Considered in the PMUReader class

8. Modelling of requirements R6: Also considered in the PMUReader class R6: Also considered in the PMUReader class R7: Modelled in the PatientRecord and PMU class R7: Modelled in the PatientRecord and PMU class R8: Considered with the requestSynchronization and acknowledgeSyncRequest functions R8: Considered with the requestSynchronization and acknowledgeSyncRequest functions

9. Signatures acknowledgeSynchRequest: () ==> () acknowledgeSynchRequest: () ==> () configurePMU: () ==> () configurePMU: () ==> () timeToTakeMedicine: () ==> () timeToTakeMedicine: () ==> ()

10. Signatures getMedicineSchedules : () ==> set of MedicineShedule getMedicineSchedules : () ==> set of MedicineShedule transmitMedicalDevice Data: MedicalDeviceData ==> () transmitMedicalDevice Data: MedicalDeviceData ==> ()

11. Signatures readMedicalDeviceDat a: () ==> set of MedicalDeviceData readMedicalDeviceDat a: () ==> set of MedicalDeviceData readPatientRecord: () ==> PatientRecord readPatientRecord: () ==> PatientRecord uploadPatientRecord: PatientRecord ==> () uploadPatientRecord: PatientRecord ==> () requestSynchronizatio n: () ==> () requestSynchronizatio n: () ==> ()

12. Signatures uploadPatientRecord: PatientRecord ==> () uploadPatientRecord: PatientRecord ==> () retrievePMUData : () ==> PatientRecord retrievePMUData : () ==> PatientRecord synchronizeDataWithS erver: PatientRecord ==> () synchronizeDataWithS erver: PatientRecord ==> () requestSynchronizatio n: () ==> () requestSynchronizatio n: () ==> ()

13. Signatures convertPatientRecord: PatientRecord, PatientRecordFormat ==> () convertPatientRecord: PatientRecord, PatientRecordFormat ==> ()