Difference between revisions of "Mobile eHealth MeH (PESOS 2012)"

Revision as of 11:42, 18 April 2012

Business Goals and Domain Assumptions

In this page we briefly describe a case study, i.e. the Mobile eHealth (MeH), developed in the context of the IST PLASTIC project aimed at supporting self-adapting and context-aware services. The goal of the case study is to show how to model a service-based application and to demonstrate that model-based solutions are suitable to generate Quality of Service (QoS) models and adaptable code from service models.

In the following sections will be reported the Business Goals and the Domain Assumptions for the current case study.

Business Goals

Table BG1. Business Goal EH-BG-01
Field	Description
UniqueID	EH-BG-01
Short Name	Patient Data Retrìeval (PDR)
Type	Business Goals.
Description	By invoking the PDR service, the doctors retrieve mixed media information of their patients that combines text with or without different kinds of images referring to their personal data, their medical histories and patient-related diseases. The results can be displayed on the doctors’ handheld device. A more detailed description of this service is provided in [1].
Rationale	Provide the service that is tailored to a certain execution context.
Involved Stakeholders	Doctors, Patients
Conflicts	None
Supporting Materials	[2]
Priority of accomplishment	Must have.

Table BG2. Business Goal EH-BG-02
Field	Description
UniqueID	EH-BG-02
Short Name	Remote Diagnosis
Type	Business Goals.
Description	By invoking the RD service, the patients update some vital parameters (e.g. heart rate) thus to provide the knowledge aimed at monitoring their health. On the basis of such data an alarm is sent in case of warning conditions that can be forwarded to his/her relatives, rural doctors and social workers. A more detailed description of this service is provided in [3].
Rationale	Improve the effectiveness and reliability of healthcare activities. Reduce costs of healthcare activities.
Involved Stakeholders	Doctors, Patients
Conflicts	None
Supporting Material	[4]
Priority of accomplishment	Must have.

Domain Assumptions

Table DA1. Assumption EH-DA-01
Field	Description
UniqueID	EH-DA-01
Short Name	Context/Resource Awareness
Type	Domain assumption
Description	The MeH system shall be a context-aware and adaptable service. Context is a set of heterogeneous information that can be sensed by and influence the system behavior. At design time, it results in artifacts (i.e., models) where structural and behavioral descriptions of the MeH System can be combined with a context model. At run time, it corresponds to the availability of an appropriate middleware that is capable to monitor the execution context and to adapt the system behavior accordingly.
Rationale	Provide the best QoS in an ubiquitous environment despite a continuosly evolving execution context.
Involved Stakeholders	Doctors, Patients
Conflicts	None
Supporting Material	[5]
Priority of accomplishment	Must have.

Domain Analysis

Strategic Dependency Model and Context Diagram

The SDD figure illustrates the strategic dependency diagram of the case study. The diagram puts in evidence the business goals shared among the related actors. For example, in the diagram we can note that the Doctor makes a diagnosis for the Patient, and plans examinations and treatments which are managed by the EHealth Organizations. He/She can also request a consultancy to some experts. Moreover, the medical staff can monitor patient’s data.

The following figure illustrates the context diagram of the current case study. In the context diagram, all the actors that appear in the business goals and scenarios are agents.

Domain Model

The figure below illustrates the domain model of the current case study. The model is represented using a UML notation. In particular the model shows the entities of the scenario, the actors and the relationship among them.

Scenarios

The following figure shows the general use-case diagram for the EHealth case study.

Table S1: Scenario EHEALTH-S-01
Field	Description
UniqueID	EHEALTH-S-01
Short Name	Access previously collected health data
Related To	EHEALTH-BG-01, EHEALTH-DA-02
Involved Actors	Doctor, Other Medical Staff
Detailed Operational Description	During the medical examination, the doctor or other medical staff may need access to the patient’s previously recorded and now archived health data (that is, blood test results, X-ray images, etc.) which were either recorded in the same location or at a different place. For instance, this data might have been recorded at a different hospital (which possibly belongs to a different hospital chain).
Problems and Challenges	The problems and challenges related to this scenario are the following: Legal and technical issues with distributed and shared patient records Integration across domains Horizontal (enterprise information systems) and vertical integration (devices) Platform heterogeneity, interoperability HIPAA privacy and security compliance Patient chart autorization access and protection Procedure that maintain electronic protected health information to allow access only to those persons or programs that have been granted access rights Emergency access procedure for obtaining necessary electronic protected health information during an emergency Dependability, performance, security, and trust
Additional Material	None

Table S2: Scenario EHEALTH-S-02
Field	Description
UniqueID	EHEALTH-S-02
Short Name	Access current health data
Related To	EHEALTH-BG-01, EHEALTH-DA-02
Involved Actors	Doctor, Other Medical Staff
Detailed Operational Description	The doctor also needs access to the data recorded online during the consultation by either the doctor himself or his assistants. He may, in addition, need data that was recorded shortly before the consultation, or that was collected in the hospital or at home during a long-term monitoring with a mobile diagnostic device like, for instance, an ambulatory blood pressure unit. It is even conceivable that the doctor would use diagnostic data received from nanobots (that is, agent-like devices of nanometre-size brought into a human body for diagnosis or even for therapy). In addition, whatever kind of data he is using, the doctor should be supported in his analysis by expert systems and databases.
Problems and Challenges	The problems and challenges related to this scenario are the following: Integrate on demand data from various devices Store working sessions and allow to move sessions between devices Integration of distributed workflows, distributed transactions, federated identities Integration across domains Horizontal (enterprise information systems) and vertical integration (devices) Platform heterogeneity, interoperability HIPAA privacy and security compliance Use or disclosure of Protected Health information (PHI): Health Mitigation procedures to address unauthorized user Patient chart autorization access and protection Dependability, performance, security, and trust
Additional Material	Sub use case:

Table S3: Scenario EHEALTH-S-03
Field	Description
UniqueID	EHEALTH-S-03
Short Name	Access health data during examinations
Related To	EHEALTH-BG-01, EHEALTH-BG-04, EHEALTH-DA-02
Involved Actors	Doctor, Patient, Other Medical Staff
Detailed Operational Description	To reach a diagnosis during a complex examination, the doctor may need to use several devices in several locations. The devices could be a general-purpose handheld computer or a specific integrated device for medical diagnostics, for instance, an X-ray device. They are often located in the same hospital, but also their usage in a different place, e.g. the patient’s home, is conceivable. For the execution of patient checks a doctor could exploit different devices. In this case, their status has to be properly aligned.
Problems and Challenges	The problems and challenges related to this scenario are the following: Integrate on demand data from various devices Store working sessions and allow to move sessions between devices Integration of distributed workflows, distributed transactions, federated identities Integration across domains Horizontal (enterprise information systems) and vertical integration (devices) Platform heterogeneity, interoperability HIPAA privacy and security compliance Patient chart autorization access and protection Emergency access procedure for obtaining necessary electronic protected health information during an emergency Dependability, performance, security, and trust
Additional Material	Sub use-case:

Table S4: Scenario EHEALTH-S-04
Field	Description
UniqueID	EHEALTH-S-04
Short Name	Expert Consultation
Related To	EHEALTH-BG-02, EHEALTH-BG-05, EHEALTH-DA-02
Involved Actors	Doctor, Expert
Detailed Operational Description	The doctor might need to call a colleague for consultation or to evaluate a specific result. To this end, the doctor has access to directories and can place a phone call by one mouse-click from just the computer he uses at that moment. This feature may be taken a step further to collaborative environments and expert call centres.
Problems and Challenges	The problems and challenges related to this scenario are the following: Legal and technical issues with distributed and shared patient records Store working sessions and allow to move sessions between devices Integrate external applications (telephony, reservation, external patient records) Integration of distributed workflows, distributed transactions, federated identities Integration across domains Horizontal (enterprise information systems) and vertical integration (devices) Platform heterogeneity, interoperability Procedure that maintain electronic protected health information to allow access only to those persons or programs that have been granted access rights Emergency access procedure for obtaining necessary electronic protected health information during an emergency Dependability, performance, security, and trust
Additional Material	Sub use-case:

Difference between revisions of "Mobile eHealth MeH (PESOS 2012)"

Revision as of 11:42, 18 April 2012

Contents

Business Goals and Domain Assumptions

Business Goals

Domain Assumptions

Domain Analysis

Strategic Dependency Model and Context Diagram

Domain Model

Scenarios

Navigation menu

Views

Personal tools

Navigation

Search

Tools

@@ Line 2: / Line 2: @@
 ==Business Goals and Domain Assumptions==
-In the following sections will be reported the Business Goals and the Domain Assumptions for the current
+In this page we briefly describe a case study,
-case study.
+i.e. the Mobile eHealth (MeH), developed in the context of the
+IST PLASTIC project aimed at supporting self-adapting and
+context-aware services. The goal of the case study is to show
+how to model a service-based application and to demonstrate
+that model-based solutions are suitable to generate Quality of
+Service (QoS) models and adaptable code from service models.
+In the following sections will be reported the Business Goals and the
+Domain Assumptions for the current case study.
 === Business Goals ===
 {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
-|+ Table BG1. Business Goal RD-BG-01
+|+ Table BG1. Business Goal EH-BG-01
 !Field !! Description
 |- style="background:#f0f0f0; color:black"
 ! UniqueID
-||RD-BG-01
+||EH-BG-01
 |- style="background:white; color:black"
 ! Short Name
-| Ubiquitous and Immediate Access to Patient Data
+| Patient Data Retrìeval (PDR)
 |- style="background:white; color:black"
@@ Line 25: / Line 34: @@
 |- style="background:white; color:black"
 ! Description
-| The system shall be able to provide the best QoS (intended as a combination of non-functional properties) by adapting its behavior according to different execution context.
+| By invoking the PDR service, the doctors retrieve mixed media information of their patients that combines text with or without different kinds of images referring to their personal data, their medical histories and patient-related diseases. The results can be displayed on the doctors’ handheld device. A more detailed description of this service is provided in [http://www.sti.uniurb.it/paco/Products/fase_2010b.pdf].
-reduce the overall duration of healthcare activities through ubiquitous and immediate access to Patient data.
-Patient data shall be ubiquitously available for the Doctor for further examinations.
 |- style="background:white; color:black"
 ! Rationale
-| Improve the effectiveness and reliability of healthcare activities. Reduce costs of healthcare activities.
+| Provide the service that is tailored to a certain execution context.
 |- style="background:white; color:black"
@@ Line 52: / Line 59: @@
 {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
-|+ Table BG2. Business Goal RD-BG-02
+|+ Table BG2. Business Goal EH-BG-02
 !Field !! Description
 |- style="background:#f0f0f0; color:black"
 ! UniqueID
-||RD-BG-02
+||EH-BG-02
 |- style="background:white; color:black"
 ! Short Name
-| Ubiquitous Access to Expert Consultancy
+| Remote Diagnosis
 |- style="background:white; color:black"
@@ Line 69: / Line 76: @@
 |- style="background:white; color:black"
 ! Description
-| The system shall facilitate the ubiquitous access to expert consultancy whenever a doctor working for a diagnosis for a specific patient needs it.
+| By invoking the RD service, the patients update some vital parameters (e.g. heart rate) thus to provide the knowledge aimed at monitoring their health. On the basis of such data an alarm is sent in case of warning conditions that can be forwarded to his/her relatives, rural doctors and social workers. A more detailed description of this service is provided in [http://plastic.paris-rocquencourt.inria.fr/test-1/uda_icsoc2007.pdf].
 |- style="background:white; color:black"
@@ Line 77: / Line 84: @@
 |- style="background:white; color:black"
 ! Involved Stakeholders
-| Doctors
+| Doctors, Patients
 |- style="background:white; color:black"
@@ Line 92: / Line 99: @@
 |}
+=== Domain Assumptions ===
 {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
-|+ Table BG3. Business Goal RD-BG-03
+|+ Table DA1. Assumption EH-DA-01
 !Field !! Description
 |- style="background:#f0f0f0; color:black"
 ! UniqueID
-||EHEALTH-BG-03
+| |EH-DA-01
 |- style="background:white; color:black"
 ! Short Name
-| Adaptation to heterogeneous execution context.
+| Context/Resource Awareness
 |- style="background:white; color:black"
 ! Type
-| Business Goals.
+| Domain assumption
 |- style="background:white; color:black"
 ! Description
-| The system shall be able to maintain a certain Quality of Service (intended as a combination of non-functional properties like performance, reliability, availability etc) according to some Service Level Agreement between system users (Doctors) and the provided software service.
+| The MeH system shall be a context-aware and adaptable service. Context is a set of heterogeneous information that can be sensed by and influence the system behavior. At design time, it results in artifacts (i.e., models) where structural and behavioral descriptions of the MeH System can be combined with a context model. At run time, it corresponds to the availability of an appropriate middleware that is capable to monitor the execution context and to adapt the system behavior accordingly.
 |- style="background:white; color:black"
 ! Rationale
-| Improve the effectiveness, reliability and duration of healthcare activities. Reduce costs of healthcare activities.
+| Provide the best QoS in an ubiquitous environment despite a continuosly evolving execution context.
 |- style="background:white; color:black"
 ! Involved Stakeholders
-| Doctors, EHealth Organization
+| Doctors, Patients
 |- style="background:white; color:black"
@@ Line 135: / Line 143: @@
 |}
-=== Domain Assumptions ===
-{| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
-|+ Table DA1. Assumption EHEALTH-DA-01
-!Field !! Description
-|- style="background:#f0f0f0; color:black"
-! UniqueID
-| |EHEALTH-DA-01
-|- style="background:white; color:black"
-! Short Name
-| Device Integration and Vertical integration
-|- style="background:white; color:black"
-! Type
-| Domain assumption
-|- style="background:white; color:black"
-! Description
-| The system shall consist of devices fully integrated in service-oriented architectures, that is, it shall be vertically integrated. For different kind of devices different embedded SOAs have to be developed including respective standards. The system shall provide a dependable device integration which will enable the data from different devices to be accessible in a dependable way. The complex diagnostic workflow system shall provide dependable access when the devices are used during a diagnosis or for monitoring a patient’s health status, that is, after the health data is integrated into application specific workflows, it shall be accessible in a dependable way.
-In practice, there exist domain specific standards or best practices for device handling, such as the Microsoft Connected Health Framework (CHF) or the Eclipse OpenHealthFramework. Such standards are of great importance to the developers of applications for devices. These standards often contain domain specific information models and/or protocols and hence substantially facilitate the application development and interoperability.
-|- style="background:white; color:black"
-! Rationale
-| Enforce overall system integration, dependability and adaptability
-|- style="background:white; color:black"
-! Involved Stakeholders
-| Doctors, Other Medical Staff
-|- style="background:white; color:black"
-! Conflicts
-| None
-|- style="background:white; color:black"
-! Supporting Material
-| None
-|- style="background:white; color:black"
-! Priority of accomplishment
-| Could have.
-|}
-{| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
-|+ Table DA2. Assumption EHEALTH-DA-02
-!Field !! Description
-|- style="background:#f0f0f0; color:black"
-! UniqueID
-| |EHEALTH-DA-02
-|- style="background:white; color:black"
-! Short Name
-| Compliance to Health Privacy and Security requirements
-|- style="background:white; color:black"
-! Type
-| Domain assumption
-|- style="background:white; color:black"
-! Description
-| The system should be compliant to security and privacy functions regarding treatments, services, workflows and individual services interactions. For example, in the Health domain the US-regulations are defined within the HealthPortability and Accounting Act (HIPAA) Privacy and Security rules. This standard covers all health stakeholders: individuals including doctors, nurses, pharmacists, physical therapists and organisations including hospitals, laboratories, pharmacies, nursing facilities and more generally, all health services and clearinghouses. The privacy and security rules require safeguarding all PHI (e.g. Protected Health Information).
-|- style="background:white; color:black"
-! Rationale
-| Effectively manage security and privacy policies, by relying on recognized standards in the world of healthcare. Without this requirement, a
-specific security and privacy policy will have to be defined.
-|- style="background:white; color:black"
-! Involved Stakeholders
-| Doctors, Patients, Other Medical Staff, EHealth Organization
-|- style="background:white; color:black"
-! Conflicts
-| None
-|- style="background:white; color:black"
-! Supporting Material
-| Some documents that illustrate and explain this requirement:
-* http://www.hipaa.org/
-* http://www.hhs.gov/ocr/hipaa/finalreg.html
-* http://privacyruleandresearch.nih.gov/resources.asp
-* http://www.hipaacomply.com/
-* http://www.ioma.org/pdf/iomahipaahelp.pdf
-|- style="background:white; color:black"
-! Priority of accomplishment
-| Should have
-|}
 == Domain Analysis ==