Telehealth Service System Disease Remote Monitoring

Question: Discuss about the Telehealth Service System for Disease Remote Monitoring. Answer: Introduction: Within this report the telehealth service system has been discussed in detail. The report describes the parts of the system along with the functional requirement of the system. As per the diagram, the stakeholder mapping and the use case diagram of the system has been provided within the system. The telehealth system can be referred to as the system through the heath related issues of the patient can be address. For developing a telehealth system, the telecommunication and information technology is largely used (Parmanto et al. 2013). Stakeholder Mapping Through Four Quadrants: Figure 1: Stakeholder Mapping of the Tele Health System (Source: Created by Author) Questionnaire: In order to identify the additional issues which are associated with the telehealth monitoring system specifically developed five questions will be asked to the users. The questions will be effective enough to support the purpose of the analysis. What are the functionalities that the patients feel that needs to be integrated within the telehealth service? What issues the patients face due to unavailability of the desired functionalities? What is the overall view of each stakeholder regarding the system? Is there any data access related issues that the users are facing? Is the telehealth service is up and running 24*7? Use Case Diagram of Telehealth Services: Comprehensive description of the use case diagram: The description of the use case diagram of the telehealth services has been provided in the following section with sufficient details. Registration: The patients register their name for the first time within the system. They get a unique key after registering their name (Hsieh, Tsai, Chih Lin, 2015, p. S192). Login: The patient log in to the system with the specific unique key and the password. After logging in to the system, the patients can access all the authorized data. Health information: All the information those are associated with the patient health which is stored in the data base along with the name and outcome of the tests (Cancela, Pastorino, Arredondo Hurtado, 2013, p. 7495). Beds: The status of all the beads those are available in the healthcare will be in the system. The status can be categorized into two phases such as occupied and free. The information of the beds will be available in real-time. Tests: The doctors suggest tests to the patients. The name and outcome along with all the relevant information which are associated with the test will be stored in terms of each patient (Hsieh, Tsai, Chih Lin, 2015, p. S192). Check-up: The data, time, illness, patient, doctor and many more information will be stored regarding check-up. Invoices: The patients will receive invoices against their treatment. All the invoices consist of unique identity key. The invoices will contain the name of the patient (Galiano et al., 2013, p. 1). Custom measurement: All the custom measurement of the patient health will be stored which can be accessed by the patient and the administrator. Legislation and Regulation: Every state, city, locality has its own rules. The rules have to be maintained by the health care service provider. The system takes into account the job of managing the services while following these legislations. The detailed description of the health information use case: The health information of the patient in terms of the system is stored in the electronic health record or EHR. It can be referred to the paper chart of the patient but in the digital version. The test, treatment, illness, assigned-bed, visiting doctor and many more patients diagnosis related information is stored in the electronic health record (Hsiao Hing, 2012, p. 5). In terms of storing the health information of the patient, the electronic medical records could be the option. As the electronic health record stores the treatment history of the patient along with all the other aspects of treatment, the EHR is a way better option for storing the health information of individual patient (Charles, Gabriel Furukawa, 2013, p. 6). There are several advantages of using the EHR. First, patient care can be improved. Second, the information will be available to the patient, doctor and the administration in real time. Third, it is a unique advantage as it refers to more participation from th e patient. Fourth, the practices become more effective and cost efficient. Instead of all the advantages of the EHR the technology has some issues which are harming the healthcare (Hsiao Hing, 2012, p. 5). The healthcare is facing some issues regarding privacy of the patient information. Currently the telehealth service users are facing the issue called data loss. This issues has made the user frustrated and disappointed on using the services. Functional requirements: In terms of the system the functional requirements are as following. Registration: The patients will be registering their name while using the service for the first time. A unique id will be provided to them through which they can access their information until the treatment ends. Login: In order to access the health related information, the patients must log in to the system with the unique key and password which they got at the time of registration. Checkout: If the patients treatment is competed or they do not intend to use the service any more, their authority to access the information is cancelled by deleting their account. If the patient was occupying a bed then bed will be added to the available bed. Report generation: The reports on the patient information is generated and provided to the administration and doctors. Database: All the relevant information of all the stakeholders is stored in the database. The patient information is updated with the as the treatment continues. Conclusion: From the above study it can be concluded that the telehealth service system is a sound solution for facilitating the process of the healthcare. However, the system is not working sufficiently. As per the requirement of the users of the telehealth service, the system has to be more effective and efficient. The system must be able to provide the information of the patient health without any data loss. The stakeholder mapping assisted in recognizing the factors that directly or indirectly affects the process of the telehealth service system. The use case case diagram was helpful in terms of identifying the relation of the stakeholders with the system. In addition to that, the use case diagram proved itself helpful for identifying various aspects of the system. The functional requirement described the portions which makes the system effective. References: Cancela, J., Pastorino, M., Arredondo, M. T., Hurtado, O. (2013). A telehealth system for Parkinson's disease remote monitoring. The PERFORM approach. In2013 35th Annual International Conference of the IEEE Engineering in Medicine and Biology Society (EMBC)(pp. 7492-7495). IEEE. Charles, D., Gabriel, M., Furukawa, M. F. (2013). Adoption of electronic health record systems among US non-federal acute care hospitals: 2008-2012.ONC data brief,9, 1-9. Galiano-Castillo, N., Ariza-Garcia, A., Cantarero-Villanueva, I., Fernandez-Lao, C., Daz-Rodriguez, L., Legeren-Alvarez, M., ... Arroyo-Morales, M. (2013). Telehealth system (e-CUIDATE) to improve quality of life in breast cancer survivors: rationale and study protocol for a randomized clinical trial.Trials,14(1), 1. Hsiao, C. J., Hing, E. (2012).Use and Characteristics of Electronic Health Record Systems Among Office-Based Physician Practices, United States, 2001-2012(pp. 1-8). US Department of Health and Human Services, Centers for Disease Control and Prevention, National Center for Health Statistics. Hsieh, H. L., Tsai, C. H., Chih, W. H., Lin, H. H. (2015). Factors affecting success of an integrated community-based telehealth system.Technology and Health Care,23(s2), S189-S196. Parmanto, B., Pulantara, I. W., Schutte, J. L., Saptono, A., McCue, M. P. (2013). An integrated telehealth system for remote administration of an adult autism assessment.Telemedicine and e-Health,19(2), 88-94. Bibliography: Al-alshuhai, A., Siewe, F. (2015, November). An extension of the use case diagram to model context-aware applications. InSAI Intelligent Systems Conference (IntelliSys), 2015(pp. 884-888). IEEE. Cutrona, S. L., Sreedhara, M., Goff, S. L., Fisher, L. D., Preusse, P., Jackson, M., ... Mazor, K. M. (2016). Improving Rates of Influenza Vaccination Through Electronic Health Record Portal Messages, Interactive Voice Recognition Calls and Patient-Enabled Electronic Health Record Updates: Protocol for a Randomized Controlled Trial.JMIR research protocols,5(2). Jamoom, E., Beatty, P., Bercovitz, A., Woodwell, D., Palso, K., Rechtsteiner, E. (2012). Physician adoption of electronic health record systems: United States, 2011.NCHS data brief,98(July). Seidel, S., Recker, J. C., Vom Brocke, J. (2013). Sensemaking and sustainable practicing: functional affordances of information systems in green transformations.Management Information Systems Quarterly,37(4), 1275-1299. Singh, A., Sharma, E. S. (2014). Functional Test Cases Generation Based on Automated Generated Use Case Diagram. Sweeney, J. C., Danaher, T. S., McColl-Kennedy, J. R. (2015). Customer effort in value cocreation activities improving quality of life and behavioral intentions of health care customers.Journal of Service Research, 1094670515572128. Tiller, R. (2014). OCEAN CERTAIN FP7-ENV-2013.6. 1-1 Project number 603773 Deliverable 6.4 Report on the Stakeholder mapping and database. Van den Bogaert, S., Declercq, J., Van Leuven, S., Christiaens, T., Biltereyst, D., Bracke, P. (2015). Pharmaceuticals as solution for health problems: a stakeholder perspective. In29th European conference on Philosophy of Medicine and Health Care.