PMUPMU

Personal Medical UnitPersonal Medical Unit

Kasper Høj Jæger Nielsen – 19980150

Martin Kjeldsen – 20002072

Lars Sarbæk Kristiansen - 20050013

PMU ArchitecturePMU Architecture

PMU RequirementsPMU Requirements

R1 R1 Syncronization of data between PMU and Syncronization of data between PMU and synchstation should be possible..synchstation should be possible..

R2 R2 There should exist an adapter repository There should exist an adapter repository that that specifies a protocol for representing PMU specifies a protocol for representing PMU data in data in different EPR systems.different EPR systems.

R3 R3 It should be possible to store data from It should be possible to store data from personal personal medical devices.medical devices.

PMU RequirementsPMU Requirements R4 R4 The PMU can be used in emergencies, e.g. a The PMU can be used in emergencies, e.g. a

paramedic can read medical data on paramedic can read medical data on location.location.

R5 R5 Data should be displayed in a simplified Data should be displayed in a simplified form to the form to the paramedic on his Portable PMU paramedic on his Portable PMU Reader (e.g. a Reader (e.g. a PDA).PDA).

PMU RequirementsPMU Requirements

R6 R6 Data should be displayed in a detailed form Data should be displayed in a detailed form to a to a doctor on a PC.doctor on a PC.

R7 R7 A schedule for a user of the PMU in regards A schedule for a user of the PMU in regards to to medicine intake should exist.medicine intake should exist.

R8 R8 Authentication should be employed when Authentication should be employed when synchronizing. synchronizing.

Class diagramClass diagram

Modelling of requirementsModelling of requirements

R1: Modelled in the PMU and R1: Modelled in the PMU and SyncStation classesSyncStation classes

R2: Modelled in the Server classR2: Modelled in the Server class R3: The MedicalDevice class collects R3: The MedicalDevice class collects

data from a medical device and data from a medical device and transmits this to the PMUtransmits this to the PMU

R4: Modelled in the PMUReader classR4: Modelled in the PMUReader class R5: Considered in the PMUReader classR5: Considered in the PMUReader class

Modelling of requirementsModelling of requirements

R6: Also considered in the R6: Also considered in the PMUReader classPMUReader class

R7: Modelled in the PatientRecord R7: Modelled in the PatientRecord and PMU classand PMU class

R8: Considered with the R8: Considered with the requestSynchronization and requestSynchronization and acknowledgeSyncRequest functionsacknowledgeSyncRequest functions

SignaturesSignatures

acknowledgeSynchRequeacknowledgeSynchRequest: () ==> ()st: () ==> ()

configurePMU: () ==> ()configurePMU: () ==> () timeToTakeMedicine: () timeToTakeMedicine: ()

==> ()==> ()

SignaturesSignatures

getMedicineSchedugetMedicineSchedules: () ==> set of les: () ==> set of MedicineSheduleMedicineShedule

transmitMedicalDetransmitMedicalDeviceData: viceData: MedicalDeviceData MedicalDeviceData ==> ()==> ()

SignaturesSignatures

readMedicalDeviceDreadMedicalDeviceData: () ==> set of ata: () ==> set of MedicalDeviceDataMedicalDeviceData

readPatientRecord: () readPatientRecord: () ==> PatientRecord==> PatientRecord

uploadPatientRecord: uploadPatientRecord: PatientRecord ==> PatientRecord ==> ()()

requestSynchronizatirequestSynchronization: () ==> ()on: () ==> ()

SignaturesSignatures

uploadPatientRecord: uploadPatientRecord: PatientRecord ==> ()PatientRecord ==> ()

retrievePMUData : () retrievePMUData : () ==> PatientRecord==> PatientRecord

synchronizeDataWithsynchronizeDataWithServer: PatientRecord Server: PatientRecord ==> ()==> ()

requestSynchronizatirequestSynchronization: () ==> ()on: () ==> ()

SignaturesSignatures

convertPatientRecoconvertPatientRecord: PatientRecord, rd: PatientRecord, PatientRecordFormPatientRecordFormat ==> ()at ==> ()