1 / 15

PMU

PMU. TI-VDM2 project. Agenda. Proposed class diagram Thread Identification Communication channels Synchronization Stimuli Open issues. Proposed Class diagram. Agenda. Proposed class diagram Thread Identification Communication channels Synchronization Stimuli

mark-nixon
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 TI-VDM2 project

  2. Agenda • Proposed class diagram • Thread Identification • Communication channels • Synchronization • Stimuli • Open issues

  3. Proposed Class diagram

  4. Agenda • Proposed class diagram • Thread Identification • Communication channels • Synchronization • Stimuli • Open issues

  5. Thread Identification (1) • HospitalBaseStation - Base station located at hospital. Responsible for handling incoming data over a wired connection from home base stations • EmergencyBaseStation • Base station located at hospital. Responsible for handling incoming emergency messages over a wireless connection (eg. SMS, WI-FI) • HomeBaseStation • Base station located at the home of the PMU owner. Communicates with the PMU when in proximity and relays the data to the hospital over a cheap wired connection

  6. Thread Identification (2) • Analyzer - Analyzes collected data and determines if a critical condition is imminent. If this is the case it sends a priority emergency message directly to the hospital • DataCollector • Collects data from the connected medical devices (wired or wireless) • PMUHandler - Listens for incoming emergency data from the Analyzer • HomeBaseHandler - Listens for incoming data from the HomeBaseStation

  7. Agenda • Proposed class diagram • Thread Identification • Communication channels • Synchronization • Stimuli • Open issues

  8. Communication channels • MedicalDevice -> DataCollector - Data acquired on the MedicalDevice is transmitted to the DataCollector • PMU -> HomeBaseStation - PMU transmits all collected data to the HomeBaseStation when in proximity • HomeBaseStation -> HospitalBaseStation - The HomeBaseStation transmits all collected data to the hospital for doctors to review. This is done via a wired connection. • HospitalBaseStation -> HomeBaseStation - A doctor can issue a new PatientRecord based on the collected data and transmit this back to the HomeBaseStation for upload when in proximity. • Analyzer -> EmergencyBaseStation - In case of a detected emergency, the Analyzer transmits an emergency message directly to the hospital

  9. Agenda • Proposed class diagram • Thread Identification • Communication channels • Synchronization • Stimuli • Open issues

  10. Synchronization • Communication between Analyzer and PMU - producer/consumer • Communication between Analyzer and EmergencyBaseStation - producer/consumer • Communication between HomeBaseStation and HospitalBaseStation - producer/consumer • Hospital needs to lock patientrecord when base stations update patientrecords - scoped locking

  11. Agenda • Proposed class diagram • Thread Identification • Communication channels • Synchronization • Stimuli • Open issues

  12. Stimuli • Proximity • The pmu is close enough to the base station to start transmission. • Data from medical device • The pmu receives a heartbeat from a medical device and meaning the medical device is ready to start transmission of collected data. • New patient record • The patient record is updated on the central EPR system • Time to take medicine • According to the patient record it is time for the patient to take some specific medicine • Medical condition • An acute medical condition has arised (eg. heart failure imminent)

  13. Agenda • Proposed class diagram • Thread Identification • Communication channels • Synchronization • Stimuli • Open issues

  14. Issues • Channel implementation -> nedarvning • Communication types -> også nedarvet ? En klasse for alle typer ? • MessageChannelBuffer -> bruges denne overhovedet til noget ? • Medical devices -> Er det interessant for os at inkludere kommunikations elementet til/fra devices. • System -> skal denne have fat i alle klasser ?

  15. Summary • Today: - Concurrent model diagram has been presented - Initial thoughts on communication and synchronization - Test scenarios proposed • Future: • Update model based on feedback

More Related