The following case study is related to A Pervasive Health System Integrating Patient Monitoring, Status Logging and Social Sharing conducted by Andreas K. Triantafyllidis. Read them very carefully. A Pervasive Health System Integrating Patient Monitoring, Status Logging and Social Sharing The communication flow concerns four diverse nodes: the mobile device referred to as Mobile Base Unit (MBU), the Sensors, the Back-end Platform, and the External Social Network Platform. The MBU is the system's core part consisting of 5 layers: a) the Personal Health Information Repository, b) the Personal Health Information Controller, c) the Social Networking Controller, d) the Communication Controller, and e) the User Interface. The MBU is connected wirelessly with the sensors, and it is Personal Health Information Controller handles the information reflecting the patient's status. The Personal Health Information Repository is constructed based on the MBU's built-in record management system, which is utilized to record the various conditions or problems met, along with the patient's activities and alerts. All captured information is replicated to the back-end platform of the Medical Center offering the services and acts as the MBU surrogate host. Moreover, since the specific mobile device can be still considered as a limited platform to deploy advanced data/information processing, health information persisted in the back-end infrastructure can enable the employment of sophisticated data analysis methods for pattern and trend discovery. Communication between the MBU and the back-end platform is achieved via a set of communication interfaces defined and implemented according to the SOA paradigm. This provides significant advantages compared to other architectures, such as interoperability and extensibility. In particular, Simple Object Access Protocol (SOAP) messages over HTTP are transmitted from the MBU, after calling the pre-defined Web service operations related to health information management, e.g., getConditions(), getSituations(), etc., via communication stubs corresponding to the Web Service Description Language (WSDL) interface. The Communication Controller module is responsible for utilizing and controlling the entire client communication with the back-end infrastructure, also persisting unsent information due to potential network unavailability for later transmission. The MBU communicates with the External Social Network Platform via a SOAP/WSDL Application Programming Interface (API) or a Representational State Transfer (REST) API, as many existing social sharing platforms commonly provide. These APIs provide a way for accessing and using externally the most typical functionalities provided by the platform while also providing the necessary mechanisms for authentication and privacy via the adoption of protocols, e.g., OAuth. Thus, the MBU may safely connect to the External Social Network Platform via the design and implementation of appropriate client methods incorporated in the Social Networking Controller module. Information conveyed by the user to micro-blogging services is realized by combining predefined tags (information labels) and optional status descriptors following the general format: #*Alert/Symptom , where * denotes a mandatory term from a standard medical terminology system, and <> optional status descriptors from an application-specific vocabulary, e.g., #*Light-headedness while Shopping this Morning. The tags provide a convenient way to discover messages of interest in one's social network; for example, the asterisk (*) character is used after the hash to distinguish the medical terms related to symptoms/alerts provided within our system. Moreover, social analytics and processing may be supported and employed, due to the availability of this semi-structured information, without the need for applying complex natural language processing mechanisms. The user may browse/search messages within their group(s) of subscribers, making it easy to track messages of interest. (a) Based on the explanation above, build a Sequence Diagram illustrating monitoring (via available sensors), status logging, and sharing of health information by the patient.
The following case study is related to A Pervasive Health System Integrating Patient
Monitoring, Status Logging and Social Sharing conducted by Andreas K. Triantafyllidis. Read
them very carefully.
A Pervasive Health System Integrating Patient Monitoring, Status Logging
and Social Sharing
The communication flow concerns four diverse nodes: the mobile device referred to as Mobile
Base Unit (MBU), the Sensors, the Back-end Platform, and the External Social Network
Platform. The MBU is the system's core part consisting of 5 layers: a) the Personal Health
Information Repository, b) the Personal Health Information Controller, c) the Social
Networking Controller, d) the Communication Controller, and e) the User Interface. The MBU
is connected wirelessly with the sensors, and it is Personal Health Information Controller
handles the information reflecting the patient's status. The Personal Health Information
Repository is constructed based on the MBU's built-in record management system, which is
utilized to record the various conditions or problems met, along with the patient's activities and
alerts. All captured information is replicated to the back-end platform of the Medical Center
offering the services and acts as the MBU surrogate host. Moreover, since the specific mobile
device can be still considered as a limited platform to deploy advanced data/information
processing, health information persisted in the back-end infrastructure can enable the
employment of sophisticated data analysis methods for pattern and trend discovery.
Communication between the MBU and the back-end platform is achieved via a set of
communication interfaces defined and implemented according to the SOA paradigm. This
provides significant advantages compared to other architectures, such as interoperability and extensibility. In particular, Simple Object Access Protocol (SOAP) messages over HTTP are transmitted from the MBU, after calling the pre-defined Web service operations related to health information management, e.g., getConditions(), getSituations(), etc., via communication stubs corresponding to the Web Service Description Language (WSDL) interface. The Communication Controller module is responsible for utilizing and controlling the entire client communication with the back-end infrastructure, also persisting unsent information due to potential network unavailability for later transmission. The MBU communicates with the External Social Network Platform via a SOAP/WSDL Application Programming Interface (API) or a Representational State Transfer (REST) API, as many existing social sharing platforms commonly provide. These APIs provide a way for accessing and using externally the most typical functionalities provided by the platform while also providing the necessary
(a) Based on the explanation above, build a Sequence Diagram illustrating monitoring (via available sensors), status logging, and sharing of health information by the patient.
Step by step
Solved in 3 steps with 1 images
