1 / 13

PMU

PMU. Kasper Høj Jæger Nielsen – 19980150 Martin Kjeldsen – 20002072 Lars Sarbæk Kristiansen - 20050013. Personal Medical Unit. PMU Architecture. PMU Requirements. R1 Syncronization of data between PMU and synchstation should be possible..

bruno-rojas
Download Presentation

PMU

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. PMU Architecture

  3. PMU Requirements • 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. • 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. • 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. • R7 A schedule for a user of the PMU in regards to medicine intake should exist. • R8 Authentication should be employed when synchronizing.

  6. Class diagram

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

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

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

  10. Signatures • getMedicineSchedules: () ==> set of MedicineShedule • transmitMedicalDeviceData: MedicalDeviceData ==> ()

  11. Signatures • readMedicalDeviceData: () ==> set of MedicalDeviceData • readPatientRecord: () ==> PatientRecord • uploadPatientRecord: PatientRecord ==> () • requestSynchronization: () ==> ()

  12. Signatures • uploadPatientRecord: PatientRecord ==> () • retrievePMUData : () ==> PatientRecord • synchronizeDataWithServer: PatientRecord ==> () • requestSynchronization: () ==> ()

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

More Related