EHR (Electronic Health Record) System Enterprise Information Architecture

This report explores the design and implementation of an Electronic Health Record (EHR) system, focusing on its Enterprise Information Architecture (EIA). The report outlines the key components of the EHR system, including its three-tier architecture, data management strategies, and security considerations. It also discusses the integration of various data sources and the importance of data integrity and access control. The report concludes with recommendations for ensuring the reliability, security, and efficiency of the EHR system.

ICT705 Data and System Integration - Assignment 1
Data and System Integration
Task 1
Windows User
[Email address]

ICT705 Data and System Integration - Assignment 1
Executive Summary
The EHR (Electronic Health Record) system is the part of a Health IT system that is being
developed by the Health Services department in combination with the government. The
EHR (Electronic Health Record) is directed to provide a highly secure, centralised, health
information system that will connect service providers, patients, and others involved in
supporting healthcare.
In an effort to provide support to these goals an EHR (Electronic Health Record) Enterprise
Architecture is designed that provides both technical as well as operational guidance for its
operation. The EHR (Electronic Health Record) Enterprise Architecture is articulated as a
collection of three types of needs, and each of these provides a diverse perspective of the
system architecture. These are
 Business Needs - This need discusses EHR (Electronic Health Record) objectives and
goals. This provides the targets on which all other viewpoints are developed.
 Enterprise Architectural Needs – This need looks at the architectural frameworks
which are based on the requirement of the business. These frameworks are the
basically the requirements which are used to define the enterprise architecture.
These drivers include various types of secured exchange of health information
between participant organizations, information interoperability built on the
standards that are followed by industries, consumer control of the access to the
required information, and to provide support to a completely non-centralized type of
operational enterprise architecture.
 Enterprise Reference Architecture - This need defines the outlines by which the EHR
(Electronic Health Record) system is developed. The reference architecture defines
basically the legal and governance needs to be required by the EHR (Electronic
Health Record) system and its participant organizations; technologies and
operational infrastructure that are to be used, core services that are available to
support the information exchange and most importantly specific information flow
that are defined by the IT Health Communities.
Enterprise Information Architecture is also discussed in this report, which will clearly outline
the Electronic Health Record System components and functions. This architecture is
prepared to keep all the specification of them in mind. A Three-tier architecture is
developed in this report namely: Plug and Play application, Plug and Play Data Source and
EHR Information Services. Data Integration is also designed in this architecture to allow the
Electronic Health Record to access a wide range of data sources. As there will be different
ways to store the data, this integration component will help to provide a common access to
the data.
At the end of this report, recommendations have been outlined for the EHR (Electronic
Health Record) system. Some of the key recommendations are authentication data integrity,
data access and data backup. These recommendations will help to deliver a reliable and
efficient Electronic Health Record system.
i
Student Name

ICT705 Data and System Integration - Assignment 1
Contents
Executive Summary.....................................................................................................................i
List of Figures..............................................................................................................................ii
1.0 Introduction.........................................................................................................................1
2.0 Enterprise Information Architecture Reference Architecture.............................................2
3.0 Information Management and Integration..........................................................................6
4.0 Conclusion............................................................................................................................8
5.0 Recommendations...............................................................................................................8
Bibliography...............................................................................................................................9
List of Figures
Figure 1 EHR Services Architecture............................................................................................2
Figure 2 EHR Enterprise Architecture........................................................................................3
Figure 3 EHR Business Architecture (adapted from Sicuranza, et al 2013)...............................4
ii
Student Name

ICT705 Data and System Integration - Assignment 1
1.0 Introduction
Enterprise information architecture (EIA) is basically considered as an important component
of the entire enterprise architecture. The enterprise information architecture is designed to
provide a support framework that can help in maintaining cost-effective data sharing across
the different units of the organization and it takes care of both privacy and security of the
information. It is most commonly recommended to design an enterprise information
architecture in certain conditions.
The enterprise information architecture mainly comprises of three types of sub-
components:
 Business-related architecture
 Technical related architecture
 Organization related architecture
Business-related architecture provides the combined view of the entire data from a
perspective of business. Technical related architecture basically provides the view of the
recent technical configuration and a plan for migration to help in developing the desired
technical environment. Organization related architecture interacts with the top-level
organizational structure and the all the processes that are performed by every individual
unit of a company.
Requirement: All the component and architecture details of how the data will be shared
across the enterprise and what technologies will be used to optimize the functionality of all
the departments.
They are looking for a strategy to optimize the use of cloud service to cater the need of the
entire enterprise to reduce the cost and to maximize the efficiency of the staff and to
improve customer service and satisfaction.
1
Student Name

ICT705 Data and System Integration - Assignment 1
2.0 Enterprise Information Architecture Reference
Architecture
EIA RA approach is the best approach in the scenario when we have to design a system
where information is gathered at several levels and processed by a server to be available at
the time of decision making.
EHR system is the Electronic Health record of patients which are collected from several
hospitals and clinics. These records are then stored in a central server which allows access
to the patient data to all the hospitals and doctors when they need it. EHR System will
provide the required data integration and data sharing to the provider. (Beale, 2018).
Patient Record Requirements
These requirements include the following
• Priority to the patient and doctor interaction
• It must be suitable for all type of patient care
• It must trustworthy
• Technologically very strong
• Low maintenance software
• Support for clinical data
• Supports all pathology data
 Should allow integration with another record system
Figure 1 EHR Services Architecture
EHR service architecture consists of three levels or Tiers:
2
Student Name

ICT705 Data and System Integration - Assignment 1
1. At the first level, the information about health records is obtained from various
sources. First Tier is named as Plug and Play Data Stores. Four different sources have
been outlined in the architecture from where health record will sources.
2. At the second level, the information is processed and it is the level which allows the
information to be accessed from different sources. Tier-2 is named as EHR
Information Services. This Tier combines the data access and application service
layer.
3. The third level the information is stored in various databases depending on the type
of health record. This Tier is named as Plug and Play application, the point of service,
EHR viewers and Records system are part of this Tier.
Point of service includes
 Schools
 Drug stores
 Airports
Personal Health Records are obtained from
 Hospitals
 Clinics
 Health Check-up Centres.
Figure 2 EHR Enterprise Architecture
3
Student Name

ICT705 Data and System Integration - Assignment 1
EHR Enterprise architecture defines the various components that form the entire Electronic
Healthcare system. At the service level, the information is obtained from SOA which acts as
the entry point of information.
Service layer provides data to the interface layer which converts data in the proper format
accessible for processing. This layer acts as a middle layer of the system.
These modules segregate the information at various levels which depends on the type of
information. Patients health record data has several components like personal information,
Disease information, treatment underwent, insurance details, etc.
Figure 3 EHR Business Architecture (adapted from Sicuranza, et al 2013)
Electronic Healthcare business architecture integrates the Electronic Healthcare system to
the business i.e. it allows the use of EHR (Electronic Healthcare) systems information’s to
diagnose the right treatment for the patient by providing all the relevant information about
the patient and the medical history.
Business part involves providing right treatment to the patient and making revenue by
taking fees from the patient and the hospitals using EHR (Electronic Healthcare) system.
4
Student Name

ICT705 Data and System Integration - Assignment 1
Service layer provides data to the interface layer which converts data in the proper format
accessible for processing.
These modules segregate the information at various levels which depends on the type of
information. Patient’s health record data has several components like personal information,
Disease information, treatment underwent, insurance details, etc.
In EHR Business Architecture five different types of analysis are conducted namely:
• Interface Design Analysis
• Service Analysis
• Functional Analysis
• Object Analysis
• Requirement Analysis
5
Student Name

ICT705 Data and System Integration - Assignment 1
3.0 Information Management and Integration
The information gathered is managed by using various policies and validations. Validation is
done at the time of both data entry and data storage by validating the details of the
organization which is entering the data in the system and also by validating the organization
which has requested access to the patient’s data (Sathiyavathi, 2015).
Security:
It is based on the following point
 Information can only be accessed by an organization that is part of the system
 The data integrity of information must be checked at each level of access
 Any information passed can only be read by member organizations only.
 Data access is also needed in the architecture.
This security measure must be implemented at all the levels of the system so that the
system can have a high level of integrity and data is secured all the time.
Technology:
The technology used for developing EHR (Electronic Healthcare) must be latest and it should
use all the best practices for the development of the application. Technology such as
applications for entering patient’s data, data storage and for data processing and integration
of this stored data to the application with grants access to view the information must all
comply with high security and integrity standards. Cloud Storage will be the right database
storage for this Health Record System as it will provide the desired scalability and reliability.
Health IT business integration:
This is the part of the system which provides business value to the health information that
has been captured and stored such as:
 Lab reports
 Patient registration
 Clinical testing
 Medication
All these aspects can be used to generate revenues as lab reports for any case are always
chargeable, patient registration can also be charged with a minimal fee, Clinical testing is
done when recommended by a doctor and it consists of the charge based on the nature of
the test. Medication is provided after diagnosis of a disease and regular medication is also
an item that generates revenues. Data Integration is essential for this architecture as data
sources are diverse and need to integrate in order to make this Health Record System
effective to use.
Information access:
Since the data will be stored on a central server the data access must be provided to all the
member organizations with proper validations and security checks.
Information access must be limited based on the level of the user access to the healthcare
data is of high sensitivity and confidentiality nature.
Service layer provides data to the interface layer which converts data in the proper format
accessible for processing.
6
Student Name

ICT705 Data and System Integration - Assignment 1
These modules segregate the information at various levels which depends on the type of
information. Patient’s health record data has several components like personal information,
Disease information, treatment underwent, insurance details, etc.
7
Student Name

ICT705 Data and System Integration - Assignment 1
4.0 Conclusion
Based on the above discussion and the thorough analysis of EHR (Electronic Health Record)
and it's Enterprise Information Architecture we can conclude that maintaining of electronic
health record has become a necessity in recent times because with the growing population
it is becoming more and more difficult to maintain offline data for so many patients.
Electronic Health Record System Architecture is successfully designed with three-tier
architecture. First Layer source the information related to Health. Middle Layer Process the
raw information and Third Level provide access to the Health Records.
EHR (Electronic Health Record) provides a central platform to access the patient’s
information and all his medical history at one place in an easy to access format which allows
a speedy treatment process and also it eliminates possibilities of error in treatment.
EHR (Electronic Health Record) has enormous potential for development as it will help in
maintaining a proper health care system which can be used by entire hospitals and clinics in
Australia and that will help patients in a great deal that will just have to contact a hospital
and their treatment can start without waiting for the arrival of physical medical record or
record maintained at various places in different forms.
5.0 Recommendations
We have the following recommendations for EHR (Electronic Health Record) system
 Security should be considered a top priority
 Data integrity must be maintained at all the time
 Data access should be monitored to prevent any kind of misuse of the medical data
 Data must be available at all times to avoid any mishappening due to data
unavailability
 Data entry should be a hassle-free process with the clear formatting of data entry
forms which are classified under proper headings
 Data stored must be backed up at several levels to protect data from kind of attack
 A copy of data must be kept a safe place so that in case of data loss due to any
reason, data can be recovered from the copy.
These recommendations must be followed for a smooth functioning of the EHR (Electronic
Health Record) system and its continuous functioning. These recommendations not only
helps to deliver a smooth functioning but will also help to deliver a reliable and secure
Electronic Health Record system.
8
Student Name

ICT705 Data and System Integration - Assignment 1
Bibliography
 Adenuga, O. A., Kekwaletswe, R. M. & Coleman, A., 2015. eHealth integration and
interoperability issues: towards a solution through enterprise architecture. [Online].
Available at: https://doi.org/10.1186/s13755-015-0009-7
 Beale, T. and Heard, S. 2018. Openehr. [Online] Available at:
https://www.openehr.org/releases/1.0.2/architecture/overview.pdf
 Ibarra I., Gómez E., Mejía L.2017. Software Ecosystem of electronic medical record to
facilitate the exchange of inter institutional information.[Online] Available at:
Available at: https://doi.org/10.1186/s13755-015-0009-7
 Sathiyavathi, R. 2015. A survey: big data analytics on healthcare system. [Online].
Available at: http://www.m-hikari.com/ces/ces2015/ces1-4-2015/sathiyavathiCES1-
4-2015.pdf
 Sicuranza, M., Ciampi, M., Pietro, G. and Esposito, C. 2013. Secure healthcare data
sharing among federated health information systems. [Online].Available at:
https://www.inderscienceonline.com/doi/abs/10.1504/IJCCBS.2013.059023?
journalCode=ijccbs
9
Student Name