Hospital Enterprise Architecture Framework (Study of Iranian University Hospital Organization)
Hospital Enterprise Architecture Framework (Study of Iranian University Hospital Organization)
Hospital Enterprise Architecture Framework (Study of Iranian University Hospital Organization)
A R T I C LE I N FO A B S T R A C T
Keywords: Backgrounds: Nowadays developing smart and fast services for patients and transforming hospitals to modern
Hospital organization hospitals is considered a necessity. Living in the world inundated with information systems, designing services
Information system architecture based on information technology entails a suitable architecture framework.
TOGAF architecture Objectives: This paper aims to present a localized enterprise architecture framework for the Iranian university
Enterprise architecture
hospital.
Methods and results: Using two dimensions of implementation and having appropriate characteristics, the best 17
enterprises frameworks were chosen. As part of this effort, five criteria were selected according to experts’
inputs. According to these criteria, five frameworks which had the highest rank were chosen. Then 44 general
characteristics were extracted from the existing 17 frameworks after careful studying. Then a questionnaire was
written accordingly to distinguish the necessity of those characteristics using expert’s opinions and Delphi
method. The result showed eight important criteria. In the next step, using AHP method, TOGAF was chosen
regarding having appropriate characteristics and the ability to be implemented among reference formats. In the
next step, enterprise architecture framework was designed by TOGAF in a conceptual model and its layers. For
determining architecture framework parts, a questionnaire with 145 questions was written based on literature
review and expert’s opinions. The results showed during localization of TOGAF for Iran, 111 of 145 parts were
chosen and certified to be used in the hospital.
Conclusion: The results showed that TOGAF could be suitable for use in the hospital. So, a localized Hospital
Enterprise Architecture Modelling is developed by customizing TOGAF for an Iranian hospital at eight levels and
11 parts. This new model could be used to be performed in other Iranian hospitals.
1. Introduction systems in hospitals [2]. On the other hand, due to the rapid pro-
liferation of wearable devices and smartphone, the IoT enabled tech-
The new emerging technology will consist of big data, Internet of nology is used in healthcare and other hospital’s business process [3]. In
things (IoT) and cloud computing. As a result, all parts of the hospital such a situation a hospital, without infrastructure and suitable archi-
including patient’s information, machines, and patient’s rooms are tectural features is not able to use this information technology [4].
identified through an ID number and special sensors. For maintaining Nowadays, unstable and changing settings of enterprise framework are
this great amount of information, Big Data technology is used [1]. Many the result of a wondrous increase in the use of information interchange
applications are developed for exchanging electronic medical records and creating informatory society. In such a situation a careful percep-
(EMRs) among hospital organization, in the form of outpatient records, tion of different enterprise parts based on a system is necessary for
medical imaging reports, discharge summaries, laboratory test reports, adapting enterprise settings with these unstable and changing settings
and outpatient medical records. For this reason, the digital information [5].
flow in hospital organizations increases day by day. It is necessary to Lack of enterprise architecture framework equals lack of official
use cloud computing platform for appropriate managing information procedures and as a result lack of official organization. The absence of
⁎
Corresponding author.
E-mail addresses: atefeh.hoseini@alumni.ut.ac.ir (A. Haghighathoseini), hossein.bobarshad@ut.ac.ir (H. Bobarshad), fsaghafi@ut.ac.ir (F. Saghafi), ms.rezaei@ut.ac.ir (M.S. Rezaei),
nader@uci.edu (N. Bagherzadeh).
https://doi.org/10.1016/j.ijmedinf.2018.03.009
Received 13 February 2017; Received in revised form 16 March 2018; Accepted 19 March 2018
1386-5056/ © 2018 Elsevier B.V. All rights reserved.
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
access to an official organization will create an essential challenge in Rijo and others [17] presented a conceptual model for providing the
effective managing of the enterprise. Hence an architecture framework needs of a hospital with 700 beds for having the managing attitude for
which presents a logical structure for ranking, organizing and pre- using complex modern information technology. Four Zachman, TOGAF,
senting a description of enterprise, is considered important [7]. A fra- FEDERAL and DODAF frameworks, were the frameworks which were
mework presents a specific definition of different aspects and attitudes referred in this paper. First, three frameworks were not considered
of an enterprise and suggests necessary descriptions [8]. appropriate for the hospital, and 4th framework was considered in-
Hospitals and Health enterprises are very complex organizations. appropriate, and it was only considered a good model for being op-
They have a high degree of specialization and a heterogeneous com- erational. Then a framework was presented in which the steps of en-
bination of actors and interests. Hospitals and Health enterprises have terprise architecture framework’s concepts and not architecture
very complex ICT infrastructures. So it is necessary to create customized framework by itself were presented.
enterprise architectures that can accommodate agile changes in ser- According to Walsh and others [18], the keywords architecture and
vices, processes, and systems [4]. hospital were found, but this essay is not about Enterprise architecture
Zachman presented a framework for an architecture of systems or model but about the architecture of leadership models for enabling
information [9], some other enterprise architecture frameworks were medical systems.
presented to use this framework. Federal Enterprise Architecture fra- Searching on Google only one article was found. In that article, Lu
mework [10], The Open Group Architecture Framework (TOGAF) [11] and others [15] have worked on hospital enterprise architecture fra-
and Command, Control, Communication, Computers, Intelligence, mework but their work focuses on a strategy for purchasing hospital
Surveillance, and Reconnaissance (C41SR) [12] are those Frameworks equipment different from suitable standards from different sellers, and
extracted from the Zachman. their work is not Enterprise architecture, but it is a strategy which is
A hospital is a very complicated and critical organization regarding done using a neural network. The 4th International Conference will be
structure, responsibilities, rules, and procedures. Therefore, im- held by Medical Informatics World Conference in April 2016 meetings
plementing Information Technology entails an appropriate archi- and conferences will give information about Enterprise architecture
tecture. So, researchers try to define an appropriate framework for the framework strategy [19].
description of the hospital organization. This framework helps man- The main aim of this article is to present a model of Enterprise ar-
agers to arrange information technology for health services and goals. chitecture for enabling hospitals in Iran, with the support of
Authors in [9], introduced a hospital as a complicated system with lots Information Technology for providing the patient’s needs and giving
of beneficiaries, needs, and disharmonious aims. These authors also them satisfaction. As it was mentioned before using Hospital Enterprise
considered a hospital as a system with capabilities to deliver suitable architecture framework is important for Enterprise architecture as well
healthcare services in suitable time, suitable place and with appropriate as its products. On the other hand, implementing the framework de-
costs. The main challenge though was lacking systematic and compre- pends on every country's native condition. So, we try to modify current
hensive attitude in outside as well as inside the Enterprise [13]. enterprise architecture models by choosing appropriate enterprise ele-
In another article which, authors wrote about one of the hospitals in ments for modeling hospitals’ organization in Iran.
Japan, they analyzed the architecture framework of this hospital for In the remainder of this paper, we first describe the objective and
planning electronic medical care and designing enterprise; then it was method of research and process of performing it, followed by a de-
designed according to the hospital aims. Then an implementation map scription of questionnaires and experts that were used in the study. We
was designed for creating necessary changes for accessing to suitable next present the results of the study in choosing the best frameworks
enterprise framework [14]. In another research in China doing Medical and recognizing the best features for appropriate enterprise archi-
Services is considered a challenge because of variety and disharmony of tecture frameworks. Then we customize the proposed model for Iranian
Hospital Systems. Then with redesigning systems and enterprise struc- hospital. In Sections 5 and 6, we conclude the paper with an analysis of
tures, a harmonious structure of the various medical system was de- our results in the context of previously reported literature.
signed [15].
In another research in England, a medical care modeling was per- 2. Objective
formed considering the complexity of designing medical care system
because of the complexity of activities which is the result of challenges This research seeks to present an appropriate architecture frame-
of resource management and improving services. The results of this work for enterprise information system. It is a framework for designing
research showed that enterprise architecture could help in a worthy a suitable system in hospitals, to deal with the possible challenges in the
way for converging medical care processes and information technology medical arena. There are main and secondary questions.
and developing medical care management. It's also explained that Main question: what is a suitable hospital enterprise architecture
Enterprise architecture is a leading activity and a tool for Enterprise framework [HEAF] for Iran’s hospitals?
designing in which decision making is done easily, and it causes the Sub-question 1: What is the most appropriate framework regarding
presence of the ability of conceptual attitude to an enterprise from implementation in the hospitals of Iran?
different aspects and it causes efficient development [16]. Sub-question 2: What are elements and components of Enterprise
Olsen [4] reviews implementation enterprise architecture in Nor- architecture framework?
wegian health sector and founds some challenges that impeded the
process toward a common enterprise architecture(EA). These chal- 3. Method
lenges include unclear enterprise architecture roles, ineffective com-
munication, low EA maturity and commitment, and complicated EA The approach of the research is to use details and observations for a
tools. He reported the ambiguity of the EA concept, difficult EA ter- case study. The strategy of this research is a survey in a case. The aims
minology, and the complexity of EA frameworks as three causes of the and choices of methods are exploratory-descriptive.
challenges. Lack of appropriate EA framework for hospitals and health The horizontal time of research is from July 2015 to Aug. 2016. The
organizations is the main reason for this challenge in implementation collecting information tools are interviews, expert panels, and ques-
EA. An appropriate EA framework must be clear and simple in health tionnaires. The process of research in five steps for performing the
sector organization. Enterprise architecture framework is shown in Fig. 1.
Searching in Elsevier essay database, using two keywords hospital The aim of the preliminary step is studying the literature of the
and architecture, showed that there are only 22 essays about having subject. In the first step, 17 existing Enterprise architecture frameworks
those keywords in the summary or introduction. were studied, and 44 characteristics were extracted. Moreover, the
89
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
90
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
Table 3 time, and there has been agreement on eight cases, so the first and
Weighted ranks of all frameworks. second time ideas are the same. Therefore, Delphi method using has
Row The frameworks name Criterion Weighted been stopped. According to this, Delphi panel experts’ agreement on
ranks “Definition and clear understanding of architecture”, “Supporting and
1 2 3 4 5 developing architecture”, “Considering entrepreneurs”, “Considering
existing architecture framework”, “Presenting business model”,
0.25 0.15 0.2 0.225 0.175
“Presenting systems model”, “Transmission project”, and “Ability to run
1 C4ISR 0 0 10 0 10 3.75 supported by components”. Therefore, these criteria were considered
2 CIMOSA 0 0 3 0 0 0.6 important for hospitals.
3 DODAF 0 9 10 0 10 5.10
4 E2AF 0 6 10 5 3 4.55
5 MODAF 0 8 5 0 7 3.425
4.3. Choosing the most appropriate hospital enterprise architecture
6 TOGAF 0 10 10 10 10 7.50 framework
7 Zachman framework 0 0 10 10 10 6.00
8 ISE Enterprise 0 8 10 5 0 4.33 After recognizing evaluation criteria, and considered options in
Architecture framework
choosing appropriate Enterprise architecture framework an appropriate
9 Prado Enterprise 0 0 3 0 0 0.6
Architecture framework for Hospital was chosen through group decision making by
10 Treasury Enterprise 0 0 10 3 0 2.67 implying and Analytical Hierarchy Process which is listed below:
Architecture framework
11 Denmark’s state 0 9 3 0 0 1.95 1. – Building decision-making hierarchy
Enterprise Architecture
2. – Group decision-making information collection
framework
12 Pragmatic Enterprise 0 10 3 0 0 2.1 3. – Calculations with (expert Choice software)
Architecture framework 4. – Examining rate of adjustments
13 Federal Enterprise 0 0 10 3 3 3.2
Architecture framework
4.4. Choosing the most appropriate hospital enterprise architecture
14 The Netherlands 0 7 3 0 0 1.65
Enterprise Architecture framework
framework
15 NATO Enterprise 0 7 3 0 0 1.65 After recognizing evaluation criteria, and considered options in
Architecture framework choosing appropriate Enterprise architecture framework an appropriate
16 Gartner Enterprise 0 5 3 3 0 2.02
framework for Hospital was chosen through group decision making by
Architecture framework
17 Integrated Architectural 0 10 10 2 0 3.95 implying and Analytical Hierarchy Process which is listed below:
process
1. – Building decision-making hierarchy
2. – Group decision-making information collection
framework, five Frameworks had the highest rank (Table 3). As it is 3. – Calculations with (expert Choice software)
shown in Table 3 that TOGAF framework, ZACHMAN framework, 4. – Examining rate of adjustments
DODAF, and E2AF and Enterprise architecture framework ISE have the
highest rank, respectively. Also, none of those Enterprise architecture Step 1: Building decision-making hierarchy: in performing the first
frameworks could fulfill the hospital relating activities and goals of the step of hierarchy analysis process, the hierarchy was depicted according
process as mentioned in the literature previously. to aim, criteria, and decision-making options. Five frameworks,
DODAF, E2AF, OGAF, Zachman and ISE EAF, have all eight experts’
4.2. Recognizing the best features for appropriate enterprise architecture considered options in choosing appropriate Enterprise architecture
frameworks for a hospital framework (mentioned in Section 4.2).
The objectives: Choosing an appropriate Enterprise architecture
44 criteria were extracted for finding the most appropriate en- framework. The criterion of decision-making was recognized through
terprise architecture frameworks. These criterions were based on ex- Delphi and decision-making options involved five selected Frameworks
perts opinion and reviewing the researches done on enterprise archi- in previous parts.
tecture frameworks, specially Teng and co-workers [21,22]. As it is Steps 2: Group decision-making, data collection: The questionnaires
listed in Table 4. of pairwise comparisons for the AHB analysis was composed and
Among criteria in Table 4, ten criteria were chosen according to completed in a meeting with the presence of Information Technology
expert’s opinions with Delphi method. For doing this a questionnaire managers in the field of hospital and enterprise architecture
with the 5-points, the Likert scale was designed for the survey of ex- Frameworks Consultants, through an interview.
perts. The outcome of opinions reached an agreement in the 2nd round Step 3: Calculations using expert Choice software: The results were
of Delphi. Kendall's Concordance (W) Coefficient was used for evalu- analyzed through this software, and relative weight of criteria of esti-
ating agreements among experts. Considering the calculations done by mation was calculated. These criteria and their relative weights are:
SPSS software, statistics of Kendall’s W equals 0.242. Zero probability “Definition and clear understanding of architecture (0.153)”,
of Kendall’s W can be examined. The statistics equal 1666.72792 and p- “Architecture support and development (0.066)”, “Considering en-
value equal 0.000. According to the p-value, it could be concluded that trepreneurs (0.142)”, “Considering existing architecture (0.153)”,
the zero probability of Kendall’s W is rejected, it means that expert’s “Presenting business model (0.153)”, “Presenting system model
opinion about the importance or lack of importance of criteria is con- (0.153)”, “Presenting transmission project (0.094)”, and “The cap-
vergent. ability of being performed and supported through tools (0.085)”. In the
After collecting questionnaires and analyzing information, Delphi meantime, the options of relative weight connected to each criterion
stop conditions should be examined and in the case of lack of Delphi were calculated for selected five enterprise architecture framework.
stop conditions, the second time of sending questionnaires and col- The final consequence of options’ absolute weight shows that
lecting information is done. Because, the aim of using Delphi method is TOGAF framework has the highest absolute weight among decision-
extracting important criteria regarding Enterprise architecture frame- making options and as a result has the highest rank (Table 5).
work choice, and because the aim mentioned is fulfilled in the first After TOGAF, DODAF and then ZEKMAN, after that E2AF and
91
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
Table 4
characteristics and criteria for an appropriate enterprise architecture framework for hospital selection.
Row Criteria and characteristics
1 Definition and clear understanding of architecture frameworks: using standard phrases, principles, and guidelines for correct usage of Frameworks and transforming
Enterprise architectural information.
2 A process-dependent architecture: Using processes which are defined accurately and are the instructions for building and architecture.
3 Supporting and development of architecture: Using processes and setups in the system which supports systems development.
4 Architectural analysis: Providing a collection of attitudes for analyzing and collecting the information guidance for creating the architecture.
5 Design tradeoffs: The possibility of choosing one design among many designed options by deciding on multi-dimensional contradictory needs.
6 The comprehensiveness of architectural models: providing logical standards for architectural characteristics documentation for, planning, communication management
and performing relative activities for adapting to other systems and present situation in enterprises.
7 Design rationale: the reasons design decisions documentations base on the analysis of different dimension of inputs for confirming the decision.
8 Standardizing: Providing a standard for keeping standard qualification for ensuring architectural development and designing standards.
9 Architecture based on knowledge: providing a logical collection of the content and the reasons are reviewing designing and architecture.
10 Architectural verifiability: Given enough information or explanation of architecture for measurements and studying architectural verifiability.
11 Entrepreneurs important: Businesses aims, orientations, principles, strategies and priorities.
12 Considering inputs of Technology: Architectural strategic orientation consisting of platforms, future architecture interoperability and the standards of emerging
technologies.
13 Considering needs of business: Considering the user's needs, functional requirements, data needs, and other business-related needs.
14 Considering environment of information system: Budget, schedule, technical limitations, sources and expert knowledge, enterprise structure and knowledge and
limitations.
15 Considering existing architecture Frameworks: Considering existing standards and infrastructure.
16 Presenting business model: Describing business models, business needs, business processes, and determining the policy and enterprise rules.
17 Presenting a system model: Presenting modeling of an original component of the system, for the achieving system architectural model, in which future should be
considered, and the main decision should be taken, and substitute designs should be chosen.
18 Presenting information model: Including data model and data interface.
19 Non-functional requirements of design: Modeling the system’s structure for reflection of non-functional requirements. These needs refer to the Quality of attributes or
quality of services. It also involved access, credibility, Scalability, Security, generalizability, modifiability, and tenability. Integration: Providing methods for business
rules, stability and performing the system inside the Enterprise.
20 Presenting computation model: Including functional system description, system processing progress, system operation, software component and interactions
21 Presenting software configuration model: describing software development, saving, management, and sharing.
22 Presenting software processing model: describing the ways of software designing and its runtime.
23 Executive software environment: describing some cases for performing software like operating systems, hardware and a network component, protocols and standards.
24 Presenting transmission projects: providing designs and maps for supporting development and development of the systems.
25 Component interactivity: providing information and guidance for facilitating communication and using information among users and systems.
26 Complexity: providing information and guidance for helping enterprise incompatibility or changes according to the inside or outside needs.
27 Reusability: providing solutions for the possibilities of using the systems and architectural products in more than one system.
28 Presenting implementation model: physical construction description like operating environment and hardware and network components of the system. Implementation
process including installation and running, development, configuration, and management.
29 Scalability: guiding helping to create effective changes for system development.
30 Portability: providing a method for facilitating movement of the systems or components to another place.
31 Alignment: providing solutions for aligning management aims with the system technology, aligning business stimulants with system development and aligning enterprise
and aligning intended system to the enterprise with the intended system to the project.
32 Integration: providing methods for business rules, stability and performing the system inside the enterprise.
33 Communication: Providing information for developing business organized communication and information technology at the Enterprise level.
34 Sharing and quality of information: Providing methods for developing quality and sharing information throughout Enterprise in an effective way; like timelines and
consistency of information.
35 Customizable framework: It examines the framework flexibility to match the special needs of an Enterprise.
36 Information redundancies decrease Providing information about redundancy in the existing system.
37 Creativity, change management, survival, success, and compatibility with enterprise: Providing businesses favorable positions for the designer for enterprises survival and
success.
38 Decision making, and planning investing in information technology, information system managing, supplies, distinguishing opportunities and decreasing risk: Providing
information about the existing situation and favorable situation of Enterprise and new technologies for managers and people who make decisions for business and
information technology for defining key subjects.
39 Reducing time of Supply to Market maximizing return on investment better and faster Services, Effectiveness: Communications Management in system’s lifetime recycled
and Enterprise architectural models for increasing Effectiveness in Enterprise.
40 Fitting the environment and Enterprises Mission: Presenting an appropriate Enterprise architecture framework for a specific environment and organizations.
41 the presence of technical support knowledge, and expert knowledge: the amount of the access to sources, Instruments and experts and their technical knowledge about the
framework
42 The performance and support of tools: The possibility of Performing and implementing Enterprise architecture framework and fulfilling enterprises aims using appropriate
tools for management and production.
43 Expenses: the required expenses fiscal and human expenses for implying the Frameworks.
44 The Simplicity of concepts: a simple statement of Concepts, principles, considered methods in an architecture framework for education and easier usage on understanding
the framework.
Table 5 finally, ISER ranked. Considering this fact, one can conclude that
Frameworks absolute weight relating to the aim. TOGAF is the most appropriate framework for hospitals in this research.
Rank Item Absolute weight
Step 4: Checking inconsistency rate: Inconsistency rate of de-
scribing decision-making system in previous parts equals 0.01, con-
1 TOGAF 0.318 sidering that this amount should be between 0–0.1, one can conclude
2 DODAF 0.219 that systems inconsistency is an appropriate limit. For assigning credit
3 Zachman enterprise 0.187
4 E2AF 0.144
to choose Enterprise architecture frameworks, all the results were given
5 ISE enterprise architecture framework 0.132 to 5 experts involving decision-making experts who were not an em-
ployer and then the results were admitted. Therefore, TOGAF was
chosen as the most appropriate framework for hospitals. This
92
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
framework has been created by open Group in eight years. TOGAF’s in the country. The center has about 600 active beds, 32 hospital beds,
first version was created in 1995 according to TAFIM, and it was sup- 34 para clinic units, which provide various types of specialized and
ported by America's Department of Defense (DOD). The open group was specialized services to visitors from all over the country and even
given authority by DOD to create TOGAF on the according to TAFIM neighboring countries.
which was the results of years of trying and spending a lot of money by The hospital provides over 190,000 outpatient careers per year,
America's government. Indeed, TOGAF is an Enterprise framework more than 305,000 outpatient para-clinics, and about 1800 emergency
which enables Enterprise to design, estimate an appropriate archi- services annually. So, for managing this hospital using EA is a necessity.
tecture, it also decreases planning expenses, design, and implementa- Enterprise architecture describes Enterprises with such a layer [27], on
tion and it is also supported by the best scientific approach and a col- the other hand, TOGAF covers four main layers of Enterprise archi-
lection of architecture components. tecture Like Below [28]:
93
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
94
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
17 The establishment of a comprehensive system of Health Service These activities involve defining an architecture for hospitals, tools
management with an emphasis on the fair and efficient and defining its principals. Business architecture involves business
allocation of resources. strategies, control, organizing and physical processes existing in a
18 The establishment of reporting and documentation system in hospital. This layer determines the lines of business and every business
Health Department. line, has a single rule in performing a business mission and operations
19 The establishment of the national health accounting system. of a business determines a group of Business Services. Having a business
architecture is a prerequisite for architecture in any other field, data,
c-The hospital's capability: Capabilities are visible combinations applications, and technology. Therefore, it is that first architectural
of knowledge, skills, and abilities which result in the steady develop- activity which is needed to be done. Treatment processes have a great
ment of individual and organizational capabilities for the hospital's effect on the service quality of the hospital. Accordingly, existing in-
responsibilities be done with favorable results. definite equal pattern for processes instructions and determining the
These are H0 or null hypothesis which they were analyzed with order of the level and the time for better performance of processes of
binomial test, and all of them was approved. providing help for individuals in the hospital is necessary. Accordingly,
the hospital’s business architecture is described with below details:
95
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
96
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
Hospital functional services The data storage and retrieval of data: considering the results of
Considering binomial test results below hypotheses were admitted the binomial test below hypotheses were admitted with 95% of cer-
with 95% of certainty: tainty.
1 Electronic medical record (EMR) 1 Correct registration of patient information during reception and
2 Electronic nursing record therapy.
3 Personnel Staffing and scheduling information system 2 Data registration in information and statistics systems of
4 Bed management information system hospitals statistics and Hospital information system
5 Telemedicine service 3 Registering the individual's health records in hospital’s
6 Resource management information system information system.
And four below hypotheses were rejected: Data’s access and data integration: considering ANOVA and bi-
nomial test results, below hypotheses with 95% of certainty.
1 Security Service
2 Decision Support 1 The possibility of easy, fast and correct access to hospital’s
System information system data.
3 Communication Service
And one hypothesis was rejected:
4 Terminology Service
i-Architecture of Hospital information system (data): the ar-
chitecture of Data, emphasizes on necessary information about 1 Existing of a fast and simple method for entering data into
Enterprise architecture framework for using in hospitals. The assets of hospital’s information system.
this layer of Data and information which supports the line of businesses j-Hospital technology infrastructure architecture: Technology
plan and operation. In other words, it is a frame for the defining col- architecture involves a set of hardware and software capabilities and
lectivity, integration, integrity and amount of data access. This archi- network which is needed for businesses development, support data, and
tecture includes four main parts [29]: services application. Considering the results of the binomial test below
hypotheses were admitted with 95% of certainty.
1. data entity
2. Analyzing and reporting data
3. Storing and retrieving data 1 Software infrastructure including Hospital’s physical and
4. Data’s access and data integration necessary administrative Soft-wares and software equipment in
hospitals like basic software, software help, public software and
The results which are extracted from Shariati hospital are as follows. the services of Hospital workflow management.
The data entity: The Hospitals data entity were admitted with 95 of 2 Application platform interfaces including describing necessary
certainty. Considering the results of the binomial test according to the soft-wares for connections between applications and services for
list below: access to hospital services
3 Content management infrastructure including access control
tools, the protection tool, and data security forth security of
1 The patient records including the personal information, the Health Information Systems, the data’s management tools for
disease records, and health records storage and retrieving existing information in hospitals, content
2 The medical records including the personal information, management tools, for collecting and identifying patient’s
scientific records, the field of expertise. information.
3 The information about that method of therapy for each disease
4 The information about diseases symptoms And 6 below hypotheses were rejected
5 Descriptive information about diseases
6 The information and sources of scientific health
1 The network infrastructure including access to Port can be
And one hypothesis was rejected. connected to internet networks with internet broadband, the
details of a technical network of hospital, equipment
communication, The networks of hospitals. The soft-wares of
1 The information about Hospitals and Clinics for instance network and Hospital Network management
location, equipment, and Records 2 Hardware infrastructure: including ports can be connected to the
The Data Analysis and Reporting: Considering binomial test re- internet, the internet Broadband access, architectural details of
sults below hypotheses were admitted with 95% of certainty. hospitals, technical Network equipment of hospitals,
communication network, the network and network management
software.
1 Description and definition of different data and Hospital data 3 The operating system that was compatible with Hospital
2 Description of important information about the process of information systems: could be any operating system.
therapy 4 Free storage infrastructure including restoring tools for restoring
information of Hospital for accelerating restoring and retrieving
And two below hypotheses were rejected
operation (integrated database management tools for hospitals)
5 Communicative infrastructure: Including describing necessary
1 Describing the entity of network of data hardware and software for communicating between different
2 Data technological description of the definition of each entity as systems and organizations.
a required data for the information system in hospitals
97
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
6 Telecom infrastructure: Including telecommunication Networks, supporter as well as investigators were not admitted and the rest were
the connection between users, health centers, and databases. admitted. It means that among two groups of stakeholders, 12 were
Stakeholders and hospital system, access to internet broadband rejected. The omitted items are justified for this reason that Shariati
network, the hardware of security equipment for physical data Hospital has outsourced some of its services and does not need em-
protection like providing physical backup guard, etc. ploying new staffs. In the meantime, because the hospital is a subset of a
university and its staff and doctors themselves are researchers, there is
no capacity for other researchers.
5. Discussion In the 3rd subdivision, eight processes were admitted out of nine,
and one was rejected. The rejection is due to outsourcing services which
17 Hospital Enterprise architecture Frameworks were examined in are reasonable.
the present research. Due to the lack of appropriate research on using In the 4th subdivision, 7 cases were admitted out of 9 hospitals
these models in hospitals, the decision was made based on determining wards. The rejection of “Central Committee” and “Research centers” is
the frameworks with hospital conditions. Therefore five criteria were because it is under the state of University Not the Hospital.
chosen by experts to determine the suitability. Then TOGAF was de- Part 6: The hospital architecture of Information Technology in-
termined as the best framework using expert’s opinions and Analytical cludes two subdivisions; Hospital information system and hospitals
hierarchy process. Five mentioned criteria are 1- covering Hospital usage Information Systems.
activities and processes 2-An up to date framework 3 -Access to First subdivision i.e. Hospital information system consists of ten
Frameworks details and information 4 -Adaptability of customizing and theories, nine were admitted, and the Hospital nutrition system was
applying in Hospitals 5-Support by Hospitals modeling tools. rejected because of Outsourcing. The importance of these services is
The results show that according to experts none of the works satisfy focused on Velde [30] article. Ten services in the field of functional
first Criterion, i.e. covering hospital activities and processes. It means services were recognized in the form of questions, among that six ser-
that despite their need for a framework in this field, there is a witness in vices were admitted. Security Services, decision-making backup system,
this part because there is no extracted framework for this field. Communication Service and terminology service were rejected. Because
Then TOGAF was designed with eight parts (Fig. 2). Then a ques- these services are not considered a priority, and they are also expensive.
tionnaire with 145 questions was designed using different sources and According to Haren [23], an information system architecture, the sys-
interviewing with experts and following sources [25–28] for de- tems may develop steadily or simultaneously. Therefore these systems
termining effective factors for every 8 Frameworks. The results of these could be developed at other levels in case it is needed.
parts are as follow: Part 7: The architecture of Hospital information system (Data): this
The analyses of calculated result through one-way analysis of var- part consists of 4 subdivisions. Velde [31] and Wager and others [29]
iance admitted all 145 hypotheses, in other words, it showed that there has also focused on the importance of these four parts.
is no meaningful difference between at least two hypotheses. Then bi- The subdivisions of the hospital data entity have seven hypotheses
nomial test which shows experts equipment was used to show its ap- among these seven hypotheses only one is not admitted. Hospital in-
propriateness or inappropriateness of the condition of the hospital. formation and health centers are rejected because Enterprise archi-
Part 1: It means hospitals point of view including two subdivisions tecture inside the hospital is not considered a priority and could be
of view and driver. In Point of View Part, four hypotheses were ad- developed later. Second subdivision is analysis and Reporting data
mitted out of seven. These four hypotheses emphasize on the highest which consists of four hypotheses. The hypothesis of description of
service level, satisfaction and a decrease in vulnerability. network entities and technologic description data which is used in
It seems that three omitted cases, i.e. a better understanding of so- hospitals where rejected. The first one was rejected because individuals
ciety and more Justice are related to the health system, not the hospital. in the organizations are familiar with these descriptions and that second
In the meantime, a decrease in the time of the first dose the appoint- one was rejected because the individuals are not interested in that
ment is acceptable in first four primary hypotheses. technology part.
In driving part, seven hypotheses were admitted, and two were re- In the third subdivision – saving and retrieving data- all hypotheses
jected i.e. people's expectations from health information safety and an were admitted. The importance of this case has been focused in Velde
increase in the quality of life. [31].
Part 2: Strategy sector of a hospital: in strategic sector 19 strategies In the 4th Subdivision – access and integration of data’s hypothesis –
were certified. Using Information Technology and all subsystems of and – the possibility of fast, easy and accessible access to data or
Enterprise architecture were admitted as a strategy. It shows the im- Hospital information- were admitted, and second hypothesis – the
portance of related issues. presence of a simple and fast method for entering data in systems or
Part 3: Hospitals capacities which have eight hypotheses which Hospital information- was rejected. Because the priority is information
were all admitted. These capabilities are in line with the Vision and accuracy and not its speed.
strategy. Part 8: Hospital infrastructure architecture; this part has nine in-
Part 4: Hospital standard: In this part, the necessity of all 12 hy- frastructures among which 3 cases were admitted, and the other 6 cases
potheses, in other words, all standards related to hospital wards were which are about Services support had been outsourced and therefore
admitted. are not considered a priority.
Part 5: Architecture of business hospital has 4 Fields; First field Recently, a research was done in Portuguese showed hospitals with
involves micro activities and the other three fields involved needed about 700 beds claimed for the urgent need of using new management
organizations for doing the activities. 16 activities were mentioned as approaches for dealing with the complexity of their information sys-
hypotheses in the first subdivision, 11 hypotheses were accepted, and tems, the high duplication in data and inefficiency in the communica-
five hypotheses were rejected. tion. They presented an Enterprise Architecture as a solution for their
The results of interviews with stakeholders for result analysis needs.
showed that because of the necessity of doing the decree of the pre- They distinguished for main contributes in the field: 1) the Zachman
sident and since hospital chief considers himself committed to pur- framework; 2) The Open Group Architectural Framework (TOGAF); 3)
chasing the best equipment, therefore, the rejected hypotheses are not The Federal Enterprise Architecture (FEA); and 4) the Gartner
considered as main activities despite their importance. It seems that the Methodology, but this work didn't use any special EA and was based on
result could be generalized to other countries if there is such a com- an exploratory and empirical study to apply the principles of the EA
mitment. In a second subdivision, the stakeholder’s roles, the role of a architecture body of knowledge to the reality of a Portuguese Hospital
98
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
[32]. This study was done in 2015, and it was based on empirical study. Conflict of interest
They didn't use any special EA. However, they stated that TOGAF is a
good EA and considered a process definition to obtain the architecture. None.
FEA has a comprehensive taxonomy, like Zachman’s, and an archi-
tectural process, like TOGAF. They didn’t show their customized fra- Summary points
mework, and they only explain the process of their work.
99
A. Haghighathoseini et al. International Journal of Medical Informatics 114 (2018) 88–100
considerations, and applications, Inf. Manage. 42 (1) (2004) 15–29. [27] H. Jonkers, et al., Towards a language for coherent enterprise architecture de-
[21] N. Lim, T. Lee, S. Park, A comparative analysis of enterprise architecture frame- scriptions, Enterprise Distributed Object Computing Conference, 2003. Proceedings.
works based on EA quality attributes, 10th ACIS International Conference on Seventh IEEE International (2003) 28–37.
Software Engineering, Artificial Intelligences, Networking, and Parallel/Distributed [28] R. Harrison, TOGAF® 9 Foundation Study Guide, Van Haren, 2013.
Computing, 2009. SNPD ’09, 2009 (2018) 283–288. [29] K.A. Wager, F.W. Lee, J.P. Glaser, Health Care Information Systems: A Practical
[22] A. Tang, Jun Han, Pin Chen, A Comparative Analysis of Architecture Frameworks, Approach for Health Care Management, 2 ed., Jossey-Bass, 2009.
(2004), pp. 640–647. [30] R. van de Velde, Hospital Information Systems – The Next Generation, Softcover
[23] V. Haren, TOGAF Version 9.1, 10th ed., Van Haren Publishing, 2011. Reprint of the Original 1st Ed, 1992 ed., Springer, 2013.
[24] R. Weisman, An Overview of TOGAF® Version 9.1, (2011). [31] R.V. de Velde, P. Degoulet, Clinical Information Systems: A Component-Based
[25] S.C. McKean, J.J. Ross, D.D. Dressler, D.J. Brotman, J.S. Ginsberg, Principles and Approach, 2003 ed., Springer, New York, 2003.
Practice of Hospital Medicine, 1 ed., McGraw-Hill Medical, New York, 2012. [32] R. Rijo, R. Martinho, D. Ermida, Developing an Enterprise Architecture proof of
[26] U. S. N. and W. Report, Best Hospitals 2015. U.S. News and World Report, (2014). concept in a Portuguese hospital, Procedia Comput. Sci. 64 (2015) 1217–1225.
100