Enterprise Information Architecture Reference Architecture Templates
The management and maintenance of health information technology has been legislated and proposed by United States Government. The health information technology is electronic health record system that is proposed to be managed and maintained by health providers, customers and patients. The facilitation of data integration and sharing will be achieved by the electronic health record system proposed by the Government. United States Government requires brief description and analysis of Enterprise Information Architecture Reference Architecture, a framework that provides different templates as a design for developing any system or project. Enterprise Information Architecture Reference Architecture helps in providing information centric design for electronic health record system in this report. The architecture provides different templates that are used in a systematic way of processes which has assumptions that the processes are true and also tried methods. Enterprise Information Architecture Reference Architecture provides benefits to organizations to design a system that helps to manage and maintain a system from its initial phase to closing phase. The purpose of this report is to provide an analysis of electronic health record system through approach of Enterprise Information Architecture Reference Architecture templates along with its benefits and issues/challenges.
The structure of this report is Enterprise Information Architecture Reference Architecture templates consisting of conceptual architecture, logical architecture, component relationship diagram, component interaction diagram and operational model diagram. The benefits and issues/challenges are also provided in this report with reference to Enterprise Information Architecture Reference Architecture.
Enterprise Information Architecture Reference Architecture
Enterprise Information Architecture Reference Architecture provide following benefits for designing and development of electronic health record system.
- Integration- Enterprise Information Architecture Reference Architecture helps to achieve goals and objectives of electronic health record system. The interaction is enabled and ensured between the component and entities of enterprises. The integration approach is achieved differently at all levels of enterprise. The levels of integration are application level, business level and physical level.
- Interoperability- The information in the form of conflicting and distributed databases, in different locations are stored. The two information systems in interoperability approach are characterized by each other’s functionality two improve the understanding between them. The interaction among various information systems are facilitated by the approach of this architecture. The benefits provided are at three levels and they are services, data and procedures.
- Data domains- The accurate response via a particular individual source is provided in this architecture where the correct information at a particular give time is provided to electronic health record system. The data domains comprising of unstructured operational data, content data, master data and meta-data, which are central system is provided benefits from data domain approach. The enterprise management and integration of central services in enterprise is achieved by integration.
- Interaction of information system- The operational and functional benefits are provided to electronic health record by the approach of enterprise architecture (Charter and Tischner 2017). This benefit provides to accomplish the respective tasks and services of delivery channels through its presentation methods and procedures. The operational and functional features are provided by the system.
The electronic health record system overall requirement as per the plan of United States Government are described by the architecture called conceptual architecture that is an integral part of Enterprise Information Architecture Reference Architecture. The various ideas and concepts are introduced to be characterized by the conceptualism used by Enterprise Information Architecture Reference Architecture. The architecture overview diagram is provided in this report to illustrate the electronic health record system development (Chang 2016). Prior to architecture overview diagram, basic building blocks for developing electronic health record system is introduced to determine the basic components, entities and relationships. The architecture overview diagram is developed through the basic building blocks for developing electronic health record system.
The electronic health record system development requires various ideas and concepts that are described by architecture overview diagram. The architecture overview diagram illustrates the functional and operational features for developing electronic health record system. The systems, existing and present, for communication and presenting services are determined by architecture overview diagram (Galliers and Leidner 2014). The privacy and security are provided by architecture overview diagram. The architecture overview diagram presents objectives of patient’s safety, secure surroundings, management and facilitation of sensitive data.
Conceptual Architecture
The logical architecture provides feasible functionality in terms of technical features for developing electronic health record system. The aspects shown in the diagram given below are primary and their relationships are also provided by the diagram. The engineers and featured framework modelers are also related with this diagram for developing electronic health record system (Laudon and Laudon 2016). The logical view diagram is the next phase of architecture overview diagram.
The requirements for developing the system and its effectiveness at various levels of the system are determined by the logical view diagram. The end customers/medical providers are illustrated along with their requirements in the diagram to present the functions and features essential for electronic heath record system development. The warehouse given in the diagram is used for providing broadcasting and essential data as initial input for the operation of electronic health record system (Giachetti 2016). The phases of planning, cost, essential requirements, design and associated data are presented by the logical view diagram as a primary objective for developing electronic health record system.
This diagram, component relationship diagram, is the next phase of the previous diagram which shows the relationship between the required entities, components and required interfaces. The components are easily determined by the system developers that are there in the component relationship diagram. The developers can easily identify to understand the working and functionality of the system through the components relationship diagram (Peppard and Ward 2016). The previous diagrams, architecture overview diagram and logical view diagram, leads to component relationship diagram. The logical functions via components connections are provided by this diagram. The Co-production and Collaboration Hub are the two components that differ from the previous diagrams. The relationships of entities and components are described in this diagram to effectively develop electronic health record system.
The component relationship diagram is presented in a pictorial view in this diagram called component interaction diagram. The component interaction diagram presents interaction of different components and entities along with their relationships. The interactions shows the sequences and steps through which the components will interact and communicate within the system (Stein and Morrison 2014). The messages in the sequences and steps are shown to better illustrate the interaction of the components. This diagram is derived from component relationship diagram to show the process of developing electronic health record system.
The various components and entities are geographically distributed in this diagram and the geographically distributed nodes are illustrated by this diagram called operational model. The component model comprising of component relationship diagram and component interaction diagram, is the foundation for the operational model. The breakup of functional entities and non-functional entities are described by this diagram. This breakup further used for future processes for developing electronic health record system (Schwalbe 2015). The breakup of components and entities facilitate the necessary requirements for developing electronic health record system. The final expected outcome of operational model provides description of operational activities of the electronic health record system development. The front and head office, and events of disaster recovery are the primary or basic aspects for developing electronic health record system.
Logical Architecture
The above description shows that there are challenges for the Enterprise Information Architecture Reference Architecture where the developing of electronic health record system is facilitated. The challenges are given below as follows.
- Barriers for electronic health record system implementation- The barriers are cost related, great expertise and privacy and security related to the system (Andrus et al.2015). These barriers the major barriers and they should be mitigated in order to achieve the development of electronic health record system development.
- Barriers in the system learning- The learning of electronic health record system is the basic barrier where lack of knowledge will hinder the participants to use the system (Whetzel and Wheaton 2016). This issue should be given first priority as it is very important for the use of electronic health record system.
- Unfamiliarity to the system- The system cannot be developed and deployed if stakeholders are not involved and there is possibility of them to not involve in the system due to unfamiliarity to the system (Arndt et al.2017). This can hinder the adoption of electronic health record system.
- Quality reporting maintenance- The quality reporting should be maintained by the system. However, there are issue regarding the quality reporting of the system (Jamoom, Yang and Hing 2016). This is because of the manual entry of the data in the system.
- Enterprise Interoperability- The patients receiving treatment at two ends of the location where they are given two different treatments for the single information provided by the electronic health record system (Lim et al.2015). This will pose challenge where people will not adopt the system.
The possible strategies for the challenges posed by the electronic health record system in terms of Enterprise Information Architecture Reference Architecture are as follows.
- The adequate components, entities and resources should be assured with the development of the electronic health record system. This will ensure effectiveness and efficiency.
- The management should be involved with the system development and implementation to control and maintain the system effectively and efficiently to mitigate the challenges.
- The appropriate stakeholders must be selected for the development and implementation of electronic health record system as this will ensure better facilitation and operations.
- The implementation that is negotiated to be utilized for the electronic health record system before the initial start and closure of the system.
- The pre-preparation for the system is necessary to mitigate the challenges for the risks that can occur in future.
Conclusion
Therefore, from discussions it can be concluded that Enterprise Information Architecture Reference Architecture approach is helpful in determining the electronic health record system. The full potential of the Enterprise Information Architecture Reference Architecture is used for the development of the system that will ensure effective and efficient development. The different diagrams in this report describes brief description for the development of electronic health record system. The diagrams such as basic block for developing electronic health record system, architecture overview diagram, logical view diagram, component relationship diagram, component interaction diagram and operational model. Enterprise Information Architecture Reference Architecture provides benefits and challenges that are given in this report and the possible strategies are also provided to mitigate these challenges. The report presents a brief description and design for the electronic health record system through Enterprise Information Architecture Reference Architecture.
The recommendations for the overall Enterprise Information Architecture Reference Architecture approach for developing electronic health record system are as follows.
- Identification of suitable project manager- The project should be developed, maintained and managed by the identified project manager that is suitable for the particular project. This will ensure effective delivery of project and its implementation.
- EHR system awareness- The awareness of the system is necessary as it will helps to generate participants and will help to approach to large section of people.
- Leadership capabilities- The leadership capabilities will ensure that the goals and objectives of the project are met with suitable requirements and as per the people’s requirements.
- Correct resources and its utilization- The correct resources must be used to minimize any future risks that can happen. This will ensure effective and efficient development of electronic health record system.
- Proper training to people- The proper training is required to be given to the medical providers, patients and customers to improve their knowledge and help them to effectively use the system.
References
Ahmad, E. and Brosio, G. eds., 2015. Handbook of Multilevel Finance. Edward Elgar Publishing.
Andrus, M.R., Forrester, J.B., Germain, K.E. and Eiland, L.S., 2015. Accuracy of pharmacy benefit manager medication formularies in an electronic health record system and the Epocrates mobile application. Journal of managed care & specialty pharmacy, 21(4), pp.281-286.
Arndt, B.G., Beasley, J.W., Watkinson, M.D., Temte, J.L., Tuan, W.J., Sinsky, C.A. and Gilchrist, V.J., 2017. Tethered to the EHR: primary care physician workload assessment using EHR event log data and time-motion observations. The Annals of Family Medicine, 15(5), pp.419-426.
Buede, D.M. and Miller, W.D., 2016. The engineering design of systems: models and methods. John Wiley & Sons.
Bussler, C., 2013. B2B integration: Concepts and architecture. Springer Science & Business Media.
Chang, J.F., 2016. Business process management systems: strategy and implementation. CRC Press.
Charter, M. and Tischner, U. eds., 2017. Sustainable solutions: developing products and services for the future. Routledge.
Galliers, R.D. and Leidner, D.E. eds., 2014. Strategic information management: challenges and strategies in managing information systems. Routledge.
Giachetti, R.E., 2016. Design of enterprise systems: Theory, architecture, and methods. CRC Press.
Goetsch, D.L. and Davis, S.B., 2014. Quality management for organizational excellence. Upper Saddle River, NJ: pearson.
Henry, J., Pylypchuk, Y., Searcy, T. and Patel, V., 2016. Adoption of electronic health record systems among US non-federal acute care hospitals: 2008-2015. The Office of National Coordinator for Health Information Technology.
Hsiao, C.J., Hing, E. and Ashman, J., 2014. Trends in Electronic Health Record System Use Among Office-based Physicians, United States, 2007-2012. US Department of Health and Human Services, Centers for Disease Control and Prevention, National Center for Health Statistics.
Jamoom, E., Yang, N. and Hing, E., 2016. Adoption of certified electronic health record systems and electronic information sharing in physician offices: United States, 2013 and 2014. US Department of Health and Human Services, Centers for Disease Control and Prevention, National Center for Health Statistics.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education India.
Lim, S.N., Keung, C., Zhao, L., Curcin, V., Ethier, J.F., Burgun, A., McGilchrist, M., Bródka, P., Tuligowicz, W., Delaney, B.C. and Arvanitis, T.N., 2015, January. Transform: Implementing a Learning Healthcare System in Europe through Embedding Clinical Research into Clinical Practice. In System Sciences (HICSS), 2015 48th Hawaii International Conference on (pp. 3176-3185). IEEE.
Palvia, P., Jacks, T. and Brown, W.S., 2015. Critical Issues in EHR Implementation: Provider and Vendor Perspectives. CAIS, 36, p.36.
Peppard, J. and Ward, J., 2016. The strategic management of information systems: Building a digital strategy. John Wiley & Sons.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Stein, B. and Morrison, A., 2014. The enterprise data lake: Better integration and deeper analytics. PwC Technology Forecast: Rethinking integration, 1, pp.1-9.
Whetzel, D.L. and Wheaton, G.R. eds., 2016. Applied measurement: industrial psychology in human resources management. Routledge.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
