Enterprise Information Architecture Reference Essay For HITEC Act.

Discuss the benefits an EIA RA approach can provide to guide development of a EHR system. This discussion should expand on at least three of the identified benefits and should include at least one diagram providing an overview of the proposed system.

Overview of the Enterprise Architecture Approach

The report is prepared for Health Information Technology for Economic and Clinical Health Act or HITEC Act for maintaining the data and system integration. The enterprise architecture is used for creating a link between the business strategies because it is integrated with the business application, layers of infrastructure and the information. The consistency and the predictability of the project is improved by dividing the information into different layers. An information centric approach is used for the development of enterprise information architecture reference architecture.

For the analysis and designing the information centric information about the Health Information Technology for Economic and Clinical Health Act or HITEC Act the enterprise reference architecture is used. It acts as a template approach and follows a systematic process for designing it by assuming that this method would help in designing the building block for the information system. The approach consists of the conceptual architecture, logical architecture, Component modelling and the operational modelling.

Enterprise Information Architecture Reference Architecture

The internal applications identified for the development of the enterprise reference architecture model are listed below:

• Business drivers
• It strategy
• Business process
• Business informations
• IT architecture
• It infrastructure

The internal applications are used for forming the line of business and acting as an interface between the presentation and the delivery channel for processing different service of the healthcare management system.

This are used for management of the service provided to the users of the information system and responding against the query of the users regarding the health information of a patient. The main goal identified for the Health Information Technology for Economic and Clinical Health Act or HITEC Act is to include all the health information of a patient in the information system. The supply chain, platforms and the data providers are the main external application that have an influence on the information system architecture. The unavailability of any of the external application results in error on the information and thus it should be maintained for increasing the efficiency and reducing the response time of the system.

• Meta data services
• Master data services
• Data services
• Content services
• Analytical services

A complex technology set, standards and sets of users are required and a general framework is required for understanding the health IT in the perspective of technology and are given below:

• Meta Data Service –

CPOE (computerized provider order entry), CDS (Clinical Decision Support), E-Prescription (Electronic prescription), eMAR (electronic medication administration records), Electronic documentation, interface engine and electronic documentation.

• Master data service

Coding and messaging standards such as LOINC, ICD-9, NDC, SNOMED CT and HL7, DICOM, X12, ASTM, etc.

• Data Service

Internal Applications and their Functions

MPI (Master patient Index), (near), Health Information Exchange

• Content Service

Personal digital assistants, tablets, application service provider, bar coding, etc.

• Analytic Service

Population health management and identification of the increase in the disease for binding it with the data warehouse.

The integration of the data is important for increasing the accuracy of the health information system because the use of data with the same meaning and used in multiple sources are needed to be integrated with the data sources and the business units. The integration helps in generating a consolidated view for helping the decision support team to take effective decision.

There are different problems found in the standalone system and for increasing the functionality of the information system the interoperability should be understood and the complexity in the system should be reduced. Different application program can be used for the management of the information and reducing the complexity of the system.

The implementation of the cloud service for the management of the health records improves the functionality of the system. The application redundancy can be reduced and it can be accessed from the remote locations for increasing the agility of the project. The cloud vendor should be selected depending upon the services that are required for the development of the health information system.

The data residing in the database of the information system should be secured from illegal access with the application of the encryption mechanism. The access of the sensitive information in the database should be restricted such that it is not misused for affecting the privacy of the patients.

The presentation and the service delivery channel is used for the connecting with the user end and it consists of the external data providers, cross enterprise applications, collaborative user interface, Web and mobile applications, E health search user interface, client user interface, E health portal and the other service proved by the information system. The information service channel is used for representation of the data blocks and the data storage that are used for recording the information of the ehealth information system. The enterprise information service block is used for representation of the connection between the enterprise service and the information service provided by the e health information system.

The data flow for the organizational starts with the collection of the specific health and hospital information. The laboratory information should also be collected and added for increasing the efficiency of the information system. The data should be collected in a single location and a block diagram should be created for demonstration of the flow of the data in the information system. The regulatory information that can affect the records of the patients and the policy formation is required to be translated into a conceptual model. 

External Applications and their Functions

The database and the domain acts as a central component for the information system and it should be managed properly for the implementation of the master data service, operational service, metadata service and unstructured content service. Since the information system would located in different geographical location, it should be designed to increase the accuracy and performance of the employees and the patients for whom the information system is designed.   

There are several benefits of the EIA RA approach because it can facilitate the common understanding that is required for the business lines with the application of different models that are created form the enterprise wide point of view. With the application of the corporate data model the existing data framework can be analyzed and it can be used for reengineering the structure for maintaining the integration of data sets. Another benefit of the EIA RA approach is that the new organizational data can be easily integrated and mapped with the specific data model of the company other than the database. The packaged application can be validated that are required by the organization. It responds quickly for the new resources and is able to access the chosen parts of the model for the enterprise information architecture.

It is software that is used for the combination of the data and information of the enterprise and record different information of the healthcare information system. The integration service is used for monitoring the data for the uniform representation of the data and service provided by the information system. Different business applications such as the ERP system can be integrated for the management of the patient and the staff information and increasing the correctness and manageability of the system.

It is related with data repository used for creating an interaction between the government and the constituents regarding the information about the LAB information, Pharmacy, Electronic billing, registration, etc. the master patient index does acts as a collaboration service and it acts as a database for the healthcare organization for maintaining the patient records and maintaining the accuracy in the data for each of the departments. It also acts as the main component of the HIPAA privacy/ Security. The patients are assigned with a unique identifier such that they can be represented across the organization only one time. The data of the patients contains the name, address, SSN, gender, DOB, contact information, insurance information, diagnosis information, date of admission and discharge in hospital, etc.

Importance of Data Integration

Interfaces

On the presentation side the data of the patients should be updated and the data should be integrated with other information for responding to the query of the users. The data of the patient should be correct and the interface acts as a hub between the multiple collaboration service instances that are provided by the collaboration services.

The following strategies are used for the mitigation of the integration problem and are given below:

Enrichment of the data – With the implementation of data integration technologies the data is broken into manageable elements and it is cleansed such that user can take right decision based on the accuracy of the data.

Development of agile infrastructure – It is used for the accommodation of the changes in the requirement of the project and implementation of new technologies for delivering the agility of the healthcare organization.

Application of new generation technology – The implementation of cloud computing, Hadoop, etc. helps in management of the huge volume of unstructured data and creating relation between the data for meeting the goals and objectives of the information system.

There are different hospitals that are required to be included in the e health information system for addressing the disparities of the healthcare and involving the organizations for the management of the quality. There are different opportunity and challenges that are common for the health care organization and collection and sharing of the data across the health care information system is important for reducing the errors in the system and increasing its flexibility. The data collection process should be improved and storage options of data must also be enhanced for creation of common platform for the patients and the healthcare organization for sharing of the data and information among each other.

Dissimilar nature of the systems and the entities within the health care are analyzed for the development of the logical architecture. The technical functionality that are required for the development of the business view and the functional service are evaluated for the establishment of relationship between the application and the presentation layer of the network. The no functional requirements such as the compliance, availability, interoperability, capacity and the security of the data should be analyzed for the creation of the relation between the processes. The component model is created for delivering the functionality of the logic model and the components are described as a logically grouped set of software application for delivering the specific functionality of the information system developed for the Health Information Technology for Economic and Clinical Health Act or HITEC Act.

Strategies for Overcoming Integration Problems

There are different tools used for the analysis of the structured and unstructured data and it helps in identification of the pattern or the searched item. Clearly defined data types are used for the structured data and it is managed using the relational database. As an example of structured data it can be the details of the patients such as patient name, address, phone number, address, etc. The records also contains the text strings and it is simplified by dividing it into structured and unstructured data. For the management of the unstructured data Hadoop can be used because it is designed for supporting big data. There are different application such as HIVE, HBASE that can be used for structuring the unstructured data. It can be used for writing custom codes and increasing the flexibility of the information system.

Volume of structure and unstructured data are presented using the operational model because it takes the component from the component model and distributes it to the nodes located in the geographical location. The flow of data between the nodes are specified for the different geographical locations. Each of the nodes in the network have more than one specific components and is called deployment units. The component model is broken into functional and nonfunctional operational model. The operational model should be created such that a continuous availability and resiliency should be maintained and it helps in continues improvement of the current business process.  

For maintaining privacy in the data communication the VPN technology can be used because it creates a secure communication channel between two geographical locations. The Secure tunnels are used along with user authentication for gaining the access of the remote location and transmit the data. The internet connection speed can affect the performance of the VPN and there are different protocols such as IP security, secure socket layer, transport layer security, point to point tunneling protocol for the establishment of a connection. The gateway is used for the authenticating the identity of the user and reach the internal resources of the remote locations which includes the intranets, printers and the servers.

It is used for combining of data generated from different sources than stores the information using different technologies. It is important for merging of the smaller sub system and creating a unified view of the data assets of the e health information system. It is also important for the development of a data warehouse and migration of the data from different platforms. The existing hardware of the company can be upgraded with the implementation of the data migration and it can merged with the data existing data for the creation of the common view. For the integration of the data the current assets required for the development of the e health information system should be identified with the quality of the data and finding the volumes of data that needs to be processed.

Benefits of EIA RA Approach

Conclusion

From the above report it can be concluded that for the development of the enterprise architecture diagram an analysis should be made on the current business process of Health Information Technology for Economic and Clinical Health Act or HITEC Act. The architecture reference architecture  template are used for designing the architecture diagram and the capabilities are identified for building the block diagram and a non-technical view of the e health are used. From the architecture diagram the conceptual level overview is analyzed and it is broken down into the logical level consisting of the logical architecture and the component model. The geographically located nodes are and the data connections can be identified from the operational models. From each of the steps of the design phase the requirement is referenced for the development of the enterprise information system. The enterprise information are gathered for the development of the reference architecture for the organization. The main goals and objectives of the organization needs to be identified for management of the information and integrating it with the architecture diagram.

• For the development of the health information system the following recommendations are made:
• A formal description of the connectivity and arrangement of the system should be identified and it should be used as a guide for the implementation, structure of the component and create an interrelation for governing the design and evolution of the component.
• The concerns should be deal with the architect and a document should be created for reconciling the potential conflicts of the different stakeholders.
• The enterprise integration is used for creating an interaction between the enterprise entities and it is necessary for achieving the domain specific objectives. The physical integration approach should be applied for the development of the database system.

Adenuga, O.A., Kekwaletswe, R.M. and Coleman, A., 2015. eHealth integration and interoperability issues: towards a solution through enterprise architecture. Health information science and systems, 3(1), p.1.

Carvalho, J.V., Rocha, Á. and Abreu, A., 2016. Maturity models of healthcare information systems and technologies: A literature review. Journal of medical systems, 40(6), p.131.

Chakraborty, P. and Sarkar, A., 2017, June. Context Driven Approach for Enterprise Architecture Framework. In IFIP International Conference on Computer Information Systems and Industrial Management (pp. 277-289). Springer, Cham.

Dixon, B.E., Colvard, C. and Tierney, W.M., 2015. Identifying health facilities outside the enterprise: challenges and strategies for supporting health reform and meaningful use. Informatics for Health and Social Care, 40(4), pp.319-333.

El-Sheikh, E., Zimmermann, A. and Jain, L.C. eds., 2016. Emerging Trends in the Evolution of Service-Oriented and Enterprise Architectures. Springer International Publishing.

Foorthuis, R., Van Steenbergen, M., Brinkkemper, S. and Bruls, W.A., 2016. A theory building study of enterprise architecture practices and benefits. Information Systems Frontiers, 18(3), pp.541-564.

Hameed, K., Shah, H., Ahsan, K. and Yang, W., 2014. An enterprise architecture framework for mobile commerce. In Designing Enterprise Architecture Frameworks: Integrating Business Processes with IT Infrastructure (pp. 277-290). Apple Academic Press.

Hussein, R., 2017. The Promise of Enterprise Architecture for Global Health Informatics. Journal of medical systems, 41(7), p.108.

Kaushik, A. and Raman, A., 2015. The new data-driven enterprise architecture for e-healthcare: Lessons from the Indian public sector. Government Information Quarterly, 32(1), pp.63-74.

Khan, M.F.F., Sakamura, K. and Koshizuka, N., 2017. Robust Enterprise Application Security with eTRON Architecture. In Enterprise Security (pp. 155-178). Springer, Cham.

Lake, D., Milito, R.M.R., Morrow, M. and Vargheese, R., 2014. Internet of things: Architectural framework for ehealth security. Journal of ICT Standardization, 1(3), pp.301-328.

Lange, M., Mendling, J. and Recker, J., 2016. An empirical analysis of the factors and measures of Enterprise Architecture Management success. European Journal of Information Systems, 25(5), pp.411-431.

Mondorf, A. and Wimmer, M., 2017, January. Contextual Components of an Enterprise Architecture Framework for Pan-European eGovernment Services. In Proceedings of the 50th Hawaii International Conference on System Sciences.

Närman, P., Buschle, M. and Ekstedt, M., 2014. An enterprise architecture framework for multi-attribute information systems analysis. Software & Systems Modeling, 13(3), pp.1085-1116.

Nelson, R. and Staggers, N., 2016. Health Informatics-E-Book: An Interprofessional Approach. Elsevier Health Sciences.

Niemi, E. and Pekkola, S., 2017. Using enterprise architecture artefacts in an organisation. Enterprise Information Systems, 11(3), pp.313-338.

Pearlson, K.E., Saunders, C.S. and Galletta, D.F., 2016. Managing and Using Information Systems, Binder Ready Version: A Strategic Approach. John Wiley & Sons.

Singh, S. and Singh, N., 2015, October. Internet of Things (IoT): Security challenges, business opportunities & reference architecture for E-commerce. In Green Computing and Internet of Things (ICGCIoT), 2015 International Conference on (pp. 1577-1581). IEEE.

Suciu, G., Suciu, V., Martian, A., Craciunescu, R., Vulpe, A., Marcu, I., Halunga, S. and Fratu, O., 2015. Big data, internet of things and cloud convergence–an architecture for secure e-health applications. Journal of medical systems, 39(11), p.141.

Zarvi?, N. and Wieringa, R., 2014. An integrated enterprise architecture framework for business-IT alignment. Designing Enterprise Architecture Frameworks: Integrating Business Processes with IT Infrastructure, 63.