📊 Diagram: (Patient Monitoring System Monitoring)
🔗 Link to Original Paper/Article
Open Example Model in Example Models Bundle
📝 Short Description
This Diagram shows the structure of the Patient Ponitoring System with a focus on the monitoring features of the system.
🔤 Abbreviations
GP: General PractitionerPMS: Patient Monitoring SystemGPS: Global Positioning System
📖 Extensive Description
A Wearable Sensor sends different types of biological data to a Local Buffer. This data is aggregated and the aggregated_data is sent to (abstracted) Communication Technologies and made available to a GP Portal via the PMS Back-End. The Physician can change the rate of transmission for the Wearable Sensor, GPS Chip and Smart Scale as well as change_risk_level for the patient's health. The patient can see a simplified version of their health data via a Patient Interface via their local App.
🏷️ Label description
🗂️ Data Labels:
- DataType: There are different types of sata in this system:
RawDatafrom the different sensors,PackagedDatain communication channelsandSimplifiedData`, which is the only data type the patient may access.
🏷️ Node Labels:
- PMS: The PMS is comprised of two parts: A
Gatewayand aBackEndpart. These parts communicate via Communication Technologies. - Role: There are three other actors in this system:
AbstractCommunicationtechnologies which connect the technical parts of the PMS, thePhysicianand thePatient.
⚠️ Constraints
DataSec
This constraint ensures that no raw data from the sensors flows to the Physician directly and only via AbstractCommunication, which uses PackagedData formats.
DataSec: data DataType.RawData neverFlows vertex PMS.BackEnd
SimplePatient
The Patient may only see a part of the data and risk analysis there is. This data is labelley SimplifiedData. The constraint ensures that this is the only data the patient may access.
SimplePatient: data DataType.PackagedData neverFlows vertex Role.Patient
🚨 Violations
None.
