Components of the EIA RA for e-Health Information System
This report mainly focuses on the Preparation of the e-Health system so as to maintain a proper integration of the system and manage the data. The enterprise architecture has been designed for the purpose of showing the link that exists between the different strategies of the business as this has been integrated with the different applications of the business along with the different layers of the infrastructure and also all the information. For the improvement of the consistency and predictability of the project the information has been divided into various layers and lastly information centric approach has been adopted for the purpose of developing the EIA RA (Enterprise Information architecture reference architecture).
Enterprise Information Architecture Reference Architecture:
The different components that has been identified for the purpose of development of the EIA RA includes the following:
- IT strategy
- IT infrastructure
- It architecture
- Business processes
- Business Information
- Business drivers
This applications are mainly used for the purpose of managing the different types of services which the individuals using the information system get which is followed by responding according to the query of the users which is mainly regarding the health related information of a patient. The identified goal of the e-health is the entire health related information of the patients inside the information system. The external applications mainly includes the data providers, platforms and the supply chain. This applications have a great influence over the architecture of the information system. In case of absence of the external applications might lead to different types of error so it is very much necessary to maintain this applications in order to increase the efficiency and reduce the time needed for response.
There exists different types of data services and for the development of a general framework there is a need of different standards, technology and users. The general framework mainly consists of the:
- Master data service
- Data service
- Meta data service
- Content service
- Analytic service
This is very much important as this helps in increasing the accuracy of the entire system. Along with this there is a need of integration of the data for the purpose of using the data with the same meaning and also for the purpose of using it in the different sources. All this data needs to be integrated with the data sources as well as the different units of the business. Lastly, all this integration would greatly help in the making of the decisions by the teams by providing a combined view of all the information.
Different types of problem has been identified in the standalone system and the functionality of the information system can also be increased by understanding the Interoperability. Along with this reduction of the various types of complexities should also be done and for doing this there exists different types of applications can be used.
Data Integration for e-Health Information System
The Information system consists of different data stored in it and all this data need to be secured form any types of unauthorized access. One of the way by which this can be done is by encryption of the data. Along with this accessing of the sensitive data in the database should also be restricted in order to see that this data are not misused and the privacy of the patient is maintained.
Fig 1: Architectural Diagram
Fig 2: Logical Architecture
The main reason for including the delivery service is for the purpose of connecting the end users and also consists of the external data service providers, user interface which are collaborative in nature, and many more. The main use of the information channel includes the representation of the different data blocks and eth storage of the data which is mainly associated with recording the e-Health records. The enterprise information represents the connection that exists between the services of the enterprise and the information services which are mainly provided by the e-Health Information system.
The flow of the data mainly starts from the data collection from different sources. For improving the efficiency data is to be collected from the laboratories and is to be added to the information system. The collection of the data is to be done at single place and also a block diagram is to be made in order to demonstrate the flow of data.
In this architecture the domain and the database are associated with acting as the central component of the whole IS. This is to be managed in a proper way in order to implement all the data services. Due to the fact that the system would be present in different locations it is to be made sure that the design is made in such a way that accuracy of the system is increased.
The EIA RA has several benefits and this happens due to the reason that facilitation of the common understandings is done which is mainly required by the business lines while application of various models. This models are generally created with a wide point of view. The implementation of the corporate data model it is possible to analyze the data framework which is existing and this is mainly used for the reengineering purpose in order to maintain the integration of the different sets of data along with this the implementation of the new model would be helping in the mapping and integration of the data with the data models of different database.
Benefits of EIA RA for e-Health Information System
This is mainly done by the software which is mainly associated with combining of the different information and data from different sources. Associated with this is the recording of the different health related information. The main use of the service is done for the purpose of monitoring of the data which is followed by representation of those data and the services by the information system. Integration of other applications of business like the ERP and many more can be used for the purpose of managing the information of the patients and the staffs which would be very much beneficial.
Fig 3: Component Relation Diagram
Master Index: This is mainly used for the purpose of creating the interaction between the government and the constituents and this mainly includes the information about the LAB reports, billing, pharmacy and many more. This master index is also associated with acting as the collaborative service along with acting as the main database for the healthcare providing organizations in order to maintain the records of the patients and the accuracy of the data. Along with this it also acts as the main component for the security and the privacy. All the patients get their unique identification code which can be used for identifying them any time.
Presentation should be done only after updating and integrating the data with the other information which is very much helpful while responding to the various types of queries. It is very much essential to look into the matter that the data is correct and the interfaces are acting as the hub between various collaborative services. There are various way in which the problems related to integration can be mitigated and this includes the enrichment of the data, development of agile frameworks and application of eth new innovative technologies.
Various type of difficulties are there in the healthcare industry which needs to be addressed. In the e-Health service there is an essential need of including the various hospitals so as to address any type of disparities present in healthcare sector. The quality of the service can be greatly increased by including eth various organizations. Along with the challenges there are also various types of opportunities. One such opportunity includes the reduction of the errors and increase of flexibility. There is a need of improving the way in which the data is collected along with enhancing the storage options so as to create a platform for the purpose of sharing the information.
Besides all this there exists dissimilarities in the systems nature and the entities. They are analyzed in order to develop the logical architecture of the system. Along with this evalution of the technical functionalities and the functional services are done in order to establish the relationship between the presentation layer and the application layer. The main reason for the development of the component diagram is for the purpose of delivering the functionality of the logic model.
Different types of tools are used for the purpose of analyzing the structured as well as the unstructured data. Along with this the tools also helps in the identification of the different patterns and the items which has been searched. Relational database is used for the purpose of managing the structured data where clear and defined data types are used. Data hadoop is mainly used for the purpose of handling the unstructured data and this is done mainly because it is designed for the purpose of supporting the big data.
Generally the representation of the structured as well as the unstructured data is done by making use of the operational model as it is associated with taking the components form the component model and then distributing it across various locations. There are more than one component in the node and this are known as the deployment units. The design of the component model is to be done in such a way that there is continuous availability and reliance.
The management data is greatly challenged due to sensitive data. In order to maintain the privacy the VPN technology can be used as it is associated with providing a secure channel for communication. User authentication is present along with this so as provide the users with authentic access to the data present at different locations. VPN is greatly affected by the internets speed. Along with this there also exists various protocols which are very much helpful in establishing the connection. The use of gateway helps in identifying the user and also helps the user in reaching the internal resources located at different locations.
Integration is generally used for the purpose of combining the data which is generated from different sources rather than storing the information by making use of different new technologies. It is very much important to combine the different subsystems in order to have a unified view of the whole system. Development of data warehouse and migration of the data from different sources is very much important. The hardware can also be improved so as to make the migration of data much more easy and merging the new data with the existing one so as to create a common view.
Conclusion:
The report helps in concluding to the fact that there is a need of analysis so as to develop the new enterprise architecture. This ERA RA template has been used for the purpose of designing of the architecture diagram and identification of eth various capabilities in order to create the block diagram and how the e-Health service is used. And from the architectural diagram the overview of the conceptual level is analyzed and after this it has been broken down into different logical levels which mainly consists of the logical architecture and the model of the components. By making use of the operational model different nodes have been identified which are located in different locations along with the various data connections. The information of eth enterprise is gathered in order to develop the reference architecture.
References:
Abie, H. and Balasingham, I., 2012, February. Risk-based adaptive security for smart IoT in eHealth. In Proceedings of the 7th International Conference on Body Area Networks (pp. 269-275). ICST (Institute for Computer Sciences, Social-Informatics and Telecommunications Engineering).
Baker, T.B., Gustafson, D.H. and Shah, D., 2014. How can research keep up with eHealth? Ten strategies for increasing the timeliness and usefulness of eHealth research. Journal of medical Internet research, 16(2).
Barakat, A., Woolrych, R.D., Sixsmith, A., Kearns, W.D. and Kort, H.S., 2013. eHealth technology competencies for health professionals working in home care to support older adults to age in place: outcomes of a two-day collaborative workshop. Medicine 2.0, 2(2).
Finch, T.L., Mair, F.S., O’Donnell, C., Murray, E. and May, C.R., 2012. From theory to’measurement’in complex interventions: methodological lessons from the development of an e-health normalisation instrument. BMC medical research methodology, 12(1), p.69.
Gustafson, D.H., DuBenske, L.L., Namkoong, K., Hawkins, R., Chih, M.Y., Atwood, A.K., Johnson, R., Bhattacharya, A., Carmack, C.L., Traynor, A.M. and Campbell, T.C., 2013. An eHealth system supporting palliative care for patients with non–small cell lung cancer. Cancer, 119(9), pp.1744-1751.
Habib, K., Torjusen, A. and Leister, W., 2015. Security analysis of a patient monitoring system for the Internet of Things in eHealth. In The Seventh International Conference on eHealth, Telemedicine, and Social Medicine (eTELEMED).
Kayser, L., Kushniruk, A., Osborne, R.H., Norgaard, O. and Turner, P., 2015. Enhancing the effectiveness of consumer-focused health information technology systems through eHealth literacy: a framework for understanding users’ needs. JMIR human factors, 2(1).
Moen, A., Hackl, W.O., Hofdijk, J., Van Gemert-Pijnen, L., Ammenwerth, E., Nykänen, P. and Hoerbst, A., 2012. eHealth in Europe: status and challenges. EJBI, 8(1), p.2.
Petersen, L.S., Bertelsen, P. and Bjørnes, C., 2013. Cooperation and communication challenges in small-scale eHealth development projects. International journal of medical informatics, 82(12), pp.e375-e385.
Sahama, T., Simpson, L. and Lane, B., 2013, October. Security and Privacy in eHealth: Is it possible?. In e-Health Networking, Applications & Services (Healthcom), 2013 IEEE 15th International Conference on (pp. 249-253). IEEE.
Scandurra, I., Holgersson, J., Lind, T. and Myreteg, G., 2013, September. Development of novel eHealth services for citizen use–Current system engineering vs. best practice in HCI. In IFIP Conference on Human-Computer Interaction (pp. 372-379). Springer, Berlin, Heidelberg.
Schiza, E.C., Neokleous, K.C., Petkov, N. and Schizas, C.N., 2015. A patient centered electronic health: eHealth system development. Technology and Health Care, 23(4), pp.509-522.
Schweitzer, J. and Synowiec, C., 2012. The economics of eHealth and mHealth. Journal of health communication, 17(sup1), pp.73-81.
Scott, R.E. and Mars, M., 2013. Principles and framework for eHealth strategy development. Journal of medical Internet research, 15(7).
Soceanu, A., Egner, A. and Moldoveanu, F., 2013, May. Towards interoperability of eHealth system networked components. In Control Systems and Computer Science (CSCS), 2013 19th International Conference on (pp. 147-154). IEEE.
Stanimirovi?, D. and Vintar, M., 2014. Development of eHealth at a national level–comparative aspects and mapping of general success factors. Informatics for Health and Social Care, 39(2), pp.140-160.
Van Velsen, L., Wentzel, J. and Van Gemert-Pijnen, J.E., 2013. Designing eHealth that matters via a multidisciplinary requirements development approach. JMIR research protocols, 2(1).
Yeh, K.H., Lo, N.W., Wu, T.C., Yang, T.C. and Liaw, H.T., 2012, August. Analysis of an eHealth care system with smart card based authentication. In Information Security (Asia JCIS), 2012 Seventh Asia Joint Conference on (pp. 59-61). IEEE.