CC BY
25Разработка процессной модели системы электронных медицинских карт
Такий Эммануель Фетсон
аспирант, кафедра автоматизированного проектирования и дизайна, Институт информационных технологий и компьютерных наук, Национальный исследовательский технологический университет МИСиС, m1606626@edu.misis.ru
С момента разработки в 1970-х гг. методология фунцкиональ-ного моделирования (Icam Definition for Function Modeling, IDEF) служит инструментом для моделирования решений, действий и деятельности систем. IDEF используется в качестве стандартного метода документирования и стандартизации процессных моделей бизнесов и систем. Моделирование процессов систем полезно для определения системных функций вводов, механизмов, выводов и контроля. Сейчас этот метод используется при моделировании системных процессов, процессов «как есть» и деятельности систем. В настоящей работе объясняются процессы в системе электронных медицинских карт (ЭМК). Каждая система имеет тенденцию меняться, принимая входные и выдавая выходные данные. IDEF0 указывает на все процессы, происходящие в системе ЭМК. Созданная IDEF0 модель облегчает понимание системы ЭМК от потока входных данных до результатов, являющихся выходными данными. В работе также описываются некоторые важные функции и процессы, используемые в системе для выполнения ее задачи, которые ранее не наблюдались. Система ЭМК, как и любая другая система, имеет внутренние процессы и деятельность, что обуславливает ее сложность. Моделирование функциональных требований системы с помощью IDEF0 улучшает общее понимание и производительность (результаты) всей системы. Ключевые слова: методология функционального моделирования (IDEF0), система электронных медицинских карт (ЭМК), ввод, вывод, механизм, ограничения (ICOM), процессная модель, картирование процесса.
Introduction
Every information system is made up of functional and non-functional analysis and requirements. To define these system requirements, there is a need to bridge the gap between system requirements definition and the development of the system itself. There have been low-cost tools that can be used to model business and software process models. This establishes the baseline of the system and also the areas or aspect of the system that needs improvements. Integration Definition or IDEF refers to modeling language used in the field of system and software engineering. The main aim of IDEF is to model systems and subsystems, sharing information and defining business processes between the components and the various processes in the system. IDEF supports the paradigm of addressing modelling needs of systems and their processes. This modelling technology has evolved over the years and sometimes used for competitive advantage.
Using IDEF0 to model software and system process has a lot of advantages. It is essential that software developers and designers have mutual understanding of the functions and processes in the system. It is very difficult to understand such processes and functions in only text view. Process modelling makes it easier to understand, create a visual and graphical interpretation of the processes and functions of the system, allowing for mutual and unambiguous understanding of parties involved in the development of the system. This process also forms part of the system documentation. Through all the processes of discussing and mapping of all the tools, components, inputs and outputs description of the system, IDEF0 converts this tacit tribal knowledge into a more documented one. Using process modelling also creates some sort of performance guide. It provides a bright light regarding how work activities are performed, clearly stating all the requirements and the people who are supposed to handle them.
x x О го А С.
Input-
Constraint
1
Perform Activity
Output
Mechanism (Resource)
Fig 1 - IDEFO Representation
X
ro m
о
IO .
2 О M M
Now looking at the above figure (Fig 1), we see the representation of the five-element of IDEF0 functional model. The activity or process is always represented by boxes and the description of the process; the input is also represented by the arrow lowing to the left side to the process box; the output is denoted by the arrow on the right from the process box and constraints or control is denoted by the arrow from the top of the process. Below the process is the mechanism which is the final element that carries out the activity.
Objectives
Hospitals and health centers are now more interested in automating their system of record keeping to help them better understand patient health care. Sometimes, getting all these data, including patient vital signs and previous health history helps health practitioners make better diagnostics decisions. This research will use IDEF0 to create a process diagram, using the inputs of data from patients, control rom medical rules, mechanism from health workers and produce an output of patience health state. The IDE0 that will be produced will help the development team and the users of the system to better identify needs, build consensus, enhance vision, provide and open architecture basics and broadens the automation potential of the system.
Method
Through series of structured and unstructured interviews, health workers were interviewed on the type of data record daily, the staff responsible for a task at a time and the precautions taken to take these data. Analysis of the data was done by eliminating redundancies and also grouping all lap data into one category. The patience vital signs were decomposed to draw more meaning to the data and the mechanism use to gather this data. The IDEF0 was designed with Allfusion process modeler r7, because it has detailed parameters and labels. It is also easy to decompose a process and differentiate the other parameters form it.
Results and Discussion
Electronic Medical Record (EMR) is a system of keeping medical records and health related information about patience in the hospital or clinic. This information can be created, gathered and managed with the system. These systems facilitate workflows and improve the quality of patience care in the hospitals and clinics. Despite all the benefits of EMRs, the adoption of this system at hospitals is relatively low. This is as a result of many reasons including the staff inability to understand and use the system. The implementation of EMRs with IDEF0 will clearly states the functions and guide developers, designers and users to know how to better understand and use the system to its full capacity.
AUTHOR: Takyi E. Fetson PROJECT: Electronic Medical Record
NOTES: 123456789 10
DATE: 14-Feb-22 HHWORKING^ REV: 18-Feb-22
RECOMMENDED
CONTEXT:
TOP
PUBLICATION
Safety Manual
Oxyen Level
Blood Pressure
Patient Medication Information
Patient Allergies
Temperature
Patient Health State
Stethoscope
Therm|ometer sphygnc
pulse oxi
A-0
Documenting Patient's Record
Fig 2 - Base IDEF0 of EMR System
manometf r
Every IDEF0 has a base system which is usually made of the inputs, outputs, control and mechanism. Considering the functions of the EMR system, the outputs which is patients health state, is dependent on the inputs. The inputs of the system are basically patient vital signs which includes heart rate, blood pressure, temperature, respiratory rate and also the lab data of the patience. The control, which governs or give a set of instructions on how an activity can occur in this sense are the staff orientation and safety man-
uals. The staff orientation will govern or serve as training on how to undertake the whole process of documenting the patient record. The inputs will be the data needed to achieve the output. Then there is mechanism, which identifies the primary means by which an activity is executed. The mechanism for documenting patient's record depends on what data is being captured. For example, a stethoscope helps to take heartbeat data. With the help of doctors and nurses, these data can be captured into the system.
AUTHOR: Takyi E. Fetson PROJECT: Electronic Medical Record
NOTES: 123456789 10
DATE: 14-Feb-22 REV: 14-Feb-22
■ WORKING READER DATE CONTEXT:
DRAFT
RECOMMENDED
PUBLICATION A-0
Staff Orientation
pulse oximeter
AO
Documenting Patient's Record
Fig 3 - Full IDEF0 of EMR System
The above diagram (Fig 3) shows the fully decomposed process model of the EMR. The process of checking vital signs of patients, as seen in the diagram is carried out by doctors and nurses with pulse oximeter, stethoscope and sphygmomanometer. The input of these takes the oxygen levels and other inputs as seen in the diagram and the safety manuals controls this process. Also, the process of getting the vital signs from patients, checking electrolyte level, and accessing previous health history serves as the input for the process of analyzing these data which also produce the final output of patients' health state. Based on the requirements gathered, the process of the IDEF0 signifies the individual processes of the EMR system and
also emphasizes on the tools and staff that is responsible for a task in the system.
Conclusion
Every system requirement needs to be modeled to identify functional and non-functional requirements. The IDEF0 makes it easier for the functional part of the system be modeled. The functional aspect off the system can be one or more processes which also has their own inputs, control, output and mechanism (ICOM). The use of IDEF0 in developing and documenting system modelling offers advantages which outweigh its disadvantages. It is also very helpful for complex system, because they can be decomposed into smaller processes for easy understanding. The
x
X
o
OD A c.
X
OD m
o
io .
2 O IO IO
cs cs o cs
fO
o m m
X
process model with IDEF0 decomposed the process of documenting patient's records into smaller processes of checking vital signs, electrolyte levels and accessing previous healthcare. This was very meaningful because the outputs rom these processes, which are glucose and oxygen levels, vital signs normal range and other outputs from the process of patient's medical history was required to get the patient health state. The IDEF0 helped achieved all these. IDEF0 has not been used for all projects, this means that using IDEF0 on a system development project should be on decided based on the case at the time and base on the type of system project.
References
1. Colquhoun, G.J., Baines R.W. A State-of-the-Art Review of IDEF0. International Journal of Computer Integrated Manufacturing. 1993, Vol 6, pp. 252-264.
2. Mayer, Richard. IDEF0 Functional Modeling. College Station Texas; Knowledge Based Systems Inc, 1990, pp 34 - 45
3. Presley, A., Johnson, M. Enterprise Excellence: Small Manufacturers and Continuous Improvement. The 2nd Industrial Engineering Research Conference. 1993, pp 105 - 108
4. Luo, M., Gay, R. Automatic generation of IDEF model. Journal of Intelligent Manufacturing, 1994, vol. 5, no. 2, p. 79-92.
5. Cheng-Leong, A., Pheng, K.L., Leng, G.R.K. IDEF: A Comprehensive Modeling Methodology for Development of Manufacturing Enterprise System, International Journal of Production Research, 1999, vol. 37, no. 17, p. 3839- 3858.
6. Cho, H., Lee, I. Integrated framework of IDEF modeling methods for structured design of shop floor control systems. International Journal of Computer Integrated Manufacturing, 1991, vol. 12, no. 2, p. 113128.
7. Marca, David, McGowan, Clarence. IDEFO -SADT Business Process and Enterprise Modeling. Eclectic Solutions Corporation, 1993. p. 290.
8.Waissi R.G., Demir M., Humble J., Lev B. Automation of strategy using IDEF0 - A proof of concept // Operations Research Perspectives. 2015. Vol 2, p.106 - 161. https://doi.org/10.1016/j.orp.2015.05.001
9. Fedorova N., Shcheglov Y., Kobylyackiy P. Application of IDEF0 functional modeling methodology at the initial stage of design the modernization of TPP in ETC. // E3S Web of Conferences. 2020. Vol 209, https://doi.org/10.1051/e3sconf/202020903013
10. Bravoco, R.R. Requirement definition architecture - an overview // Computers in Industry,
1985. - T. 6. - №. 4. - P. 237-251.
https://www.sciencedirect.com/science/article/pii/016
6361585900466
11. Colquhoun G. J., Baines R. W., Crossley R. A state of the art review of IDEFO // International Journal of Computer Integrated Manufacturing. 2007. Vol 6, Issue 4. https://doi.org/10.1080/09511929308944576
Design of process model of electronic medical record system Takyi E.F.
National University of Science and Technology, MISIS
JEL classification: C10, C50, C60, C61, C80, C87, C90_
Since its development in 1970s, the Icam Definition for Function Modeling (IDEF) is a tool that helps to model the decisions, actions and the activities of a system. Its development was made to be used as a standard method of documenting and standardizing business and system process models. System process modelling is very useful in identifying system inputs, mechanism, output and control functions in the system. Now this method is used as an acceptable approach to system process modelling, in modelling the "as - is" process models and activities in the system. This paper explains the processes of an Electronic Medical Record (EMR) system. Every system has the tendency to change by accepting inputs and giving output. The IDEF0 points out all the processes that goes on in the EMR system. The model created by IDEF0 will facilitate the understanding of the EMR system from the flow of inputs to the results which is the output. It will also outline some important functions and processes used in the system to perform its task that were not previously observed. The EMR system, as any other system has internal processes and activities which presents its complications. Modelling the functional requirements of the system with IDEF0 improves the general understanding and productivity (output) of the overall system. Keywords: Icam Definition for Function Modeling (IDEF0), Electronic Medical Record (EMR) system, inputs, outputs, mechanism, constraints (ICOM), process model, process mapping. References
1. Colquhoun, G.J., Baines R.W. A State-of-the-Art Review of IDEF0.
International Journal of Computer Integrated Manufacturing. 1993, Vol 6, pp. 252-264.
2. Mayer, Richard. IDEF0 Functional Modeling. College Station Texas;
Knowledge Based Systems Inc, 1990, pp 34 - 45
3. Presley, A., Johnson, M. Enterprise Excellence: Small Manufacturers and
Continuous Improvement. The 2nd Industrial Engineering Research Conference. 1993, pp 105 - 108
4. Luo, M., Gay, R. Automatic generation of IDEF model. Journal of Intelligent
Manufacturing, 1994, vol. 5, no. 2, p. 79-92.
5. Cheng-Leong, A., Pheng, K.L., Leng, G.R.K. IDEF: A Comprehensive Mod-
eling Methodology for Development of Manufacturing Enterprise System, International Journal of Production Research, 1999, vol. 37, no. 17, p. 3839- 3858.
6. Cho, H., Lee, I. Integrated framework of IDEF modeling methods for
structured design of shop floor control systems. International Journal of Computer Integrated Manufacturing, 1991, vol. 12, no. 2, p. 113-128.
7. Marca, David, McGowan, Clarence. IDEFO - SADT Business Process and
Enterprise Modeling. Eclectic Solutions Corporation, 1993. p. 290.
8.Waissi R.G., Demir M., Humble J., Lev B. Automation of strategy using IDEF0 - A proof of concept // Operations Research Perspectives. 2015. Vol 2, p.106 - 161. https://doi.org/10.10167j.orp.2015.05.001
9. Fedorova N., Shcheglov Y., Kobylyackiy P. Application of IDEF0 functional
modeling methodology at the initial stage of design the modernization of TPP in ETC. // E3S Web of Conferences. 2020. Vol 209, https://doi.org/10.1051/e3sconf/202020903013
10. Bravoco, R.R. Requirement definition architecture - an overview // Computers in Industry, 1985. - T. 6. - №. 4. - P. 237-251. https://www.sciencedirect.com/science/article/pii/0166361585900466
11. Colquhoun G. J., Baines R. W., Crossley R. A state of the art review of IDEFO // International Journal of Computer Integrated Manufacturing. 2007. Vol 6, Issue 4. https://doi.org/10.1080/09511929308944576
<
m o x
X
