KR101547188B1 - Clinical decision support system devices and method thereof - Google Patents

Abstract

The present invention relates to a clinical decision support system and a method thereof in hospitals and the like.
An integrated management system unit for managing various disease codes used in the hospital and delivering the disease code mapping table requested from the middleware; A middleware system unit connected to each component of the system for performing data request and transmission; A data providing system unit for searching and processing the requested information through the middleware when the user requests desired information through the apparatus and outputting the requested information through the user apparatus; A CDSS management system unit for providing various chart information, CP information, process information, cooperative / linked disease information, and other data on a mobile CDSS screen; A legacy data system part for processing or providing legacy data related to existing hospital systems; And a data management system unit for managing data on patient individual and patient cluster.

Description

[0001] Clinical decision support system and method [

The present invention relates to a clinical decision support system and method. More specifically, the present invention provides clinical decision-making contents and information to medical service providers and patients on a medical delivery system in a medical institution. It integrates the system of the hospital and analyzes the information of the patients in an integrated manner, To a clinical decision support system and method for supporting the process.

The hospital business system and its method through online are developed and utilized. An invention relating to a Clinical Decision Support System (CDSS) using online is disclosed. Korean Patent Publication No. 10-2010-0097522 discloses an invention of " System and method for supporting clinical decision support ".

The disclosed invention includes an application driver for driving a clinical decision support application in response to a user's clinical decision support request; An interface repository storing standards and EMR schemes for each hospital; An interface server for referring to the interface repository and retrieving patient information for clinical decision support according to the driving of the application driver; A knowledge authoring unit that performs standards - based knowledge authoring for clinical decision support; A knowledge repository for storing knowledge authored by the knowledge authoring unit; And an interface server for referring to the knowledge repository and searching for knowledge for supporting ad-hoc decision support corresponding to the patient information retrieved from the interface server, wherein the application driver comprises: To the hospital information system of the user as information for supporting clinical decision making, by combining the knowledge-oriented architecture and the architecture in which the clinical decision application is centralized independently of the hospital information system, .

In addition, Korean Patent Publication No. 10-2011-0109170 discloses an invention of " a system and method for supporting clinical decision support in a plurality of medical care processes ".

The disclosed invention is a method for computerizing two or more medical providers and a plurality of medical care performing processes that take a long time by a clinical decision support system, wherein: among the analyzed business logic and the clinical decision logic, Constructing the knowledge base to be processed in an application of the medical record system, constructing a knowledge base by performing knowledge writing and encoding with the rule element and the process element; Constructing a clinical decision support system architecture that is independent of the electronic medical record system; And implementing a knowledge engine that processes the rule elements and the process elements of the knowledge base together and stores and manages intermediate results of knowledge execution in the clinical decision support system.

The disclosed inventions passively digitize clinical decision support, or support only medical processes based on computerized data. However, since it does not provide the configuration and analysis method of the device, there is a problem that it can not cope with the clinical decision support through the integration of the proper hospital operation system.

Therefore, it is possible to provide efficient service by integrating the existing hospital service system, to provide a treatment method suited to individual characteristics of the patient according to the patient's actual medical record, to provide customized clinical decision support suitable for the actual procedure of the hospital, There is a need for a clinical decision support system and method that can serve various terminals regardless of the type of terminal.

Korean Patent Publication No. 10-2010-0097522 Korean Patent Publication No. 10-2011-0109170

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems of the prior art, and it is an object of the present invention to provide an efficient service by integrating an existing hospital service system and to integrate the hospital service system by using middleware, It is possible to provide customized clinical decision support, clinical decision support through patient information conversion and analysis, and web based application service on various terminals regardless of the type of user terminal. A clinical decision system and a method thereof.

According to a first aspect of the present invention, there is provided an integrated management system for managing various disease codes used in a hospital and delivering a disease code mapping table requested from the middleware; A middleware system unit connected to each component of the system for performing data request and transmission; A data providing system unit for searching and processing the requested information through the middleware when the user requests desired information through the apparatus and outputting the requested information through the user apparatus; A CDSS management system unit for providing various chart information, CP information, process information, cooperative / linked disease information, and other data on a mobile CDSS screen; A legacy data system part for processing or providing legacy data related to existing hospital systems; A clinical decision support system is presented that includes a data management system unit for managing patient individual and patient cluster data.

According to a second aspect of the present invention, there is provided a method of operating a data processing apparatus, The data providing system unit activating the application at the request of the user apparatus; The user device requesting a disease code mapping from the data providing system unit; Transmitting the disease code mapping request to the middleware system unit by the data providing system unit; The middleware system requesting transmission of a disease code mapping table to the integrated management system unit at the request of the user equipment; Transmitting the disease code mapping table and rule requested by the integrated management system unit to the middleware system unit; The middleware system unit transmitting the disease code mapping transmitted from the integrated management system unit to the data providing system unit; The data providing system unit sending the disease code mapping to the user equipment; Requesting the user equipment to transmit patient information to the data providing system unit; Requesting the user equipment to transmit the patient information requested by the data providing system unit to the middleware system unit; Requesting the CDSS management system unit to transmit basic and medical information of a patient requested by the middleware system unit; The CDSS management system unit transmitting patient information to the middleware system unit; Transmitting the patient information transmitted from the CDSS management system unit to the data providing system unit by the middleware system unit; Transmitting the patient information transmitted from the middleware system unit to the user apparatus by the data providing system unit; Requesting the user device to transmit a chart and CP of patient information received by the data providing system unit; Setting and checking a chart and a CP requested by the user equipment in the data providing system unit and transmitting the chart and CP to the middleware system unit; The middleware system requesting the CDSS management system to request a chart and a CP component; Transmitting a chart and a CP component requested by the CDSS management system unit to the middleware system unit; Transmitting the chart and the CP transmitted from the CDSS management system unit to the middleware system unit; Outputting the received chart and the CP; The middleware system part making a legacy data processing request to the legacy data system part; Transmitting the legacy data list and definitions required by the legacy data system unit to the middleware system unit; The middleware system requesting a legacy data system to connect to the legacy data system based on the received legacy data list and definition; Transmitting the legacy data requested by the hospital system to the middleware system; The middleware system part transmitting the required legacy data to the legacy data system part; The legacy data system part providing legacy process data to the middleware system part; And storing the legacy processing data in the CDSS management system unit by the middleware system unit.

According to the present invention, it is possible to provide an efficient service by integrating the existing hospital service system, and by using the middleware of the integration of the hospital service system, it is possible to provide customized clinical decision support suited to the work flow of the actual hospital, Support for clinical decision making through conversion and analysis, and service to various terminals regardless of the type of user terminal.

1 is a schematic block diagram of an embodiment of a clinical decision support system of the present invention.
2 is a detailed configuration diagram of the embodiment of FIG.
Figure 3 is a schematic diagram of an embodiment of a core device of the clinical decision support system of the present invention.
4 is a schematic block diagram of an embodiment of an integrated management system unit which is a main part of an embodiment of a core device of the clinical decision support system of the present invention.
5 is a schematic block diagram of an embodiment of a middleware system unit which is a main part of an embodiment of a core device of the clinical decision support system of the present invention.
6 is a schematic block diagram of an embodiment of a data providing system unit which is a main part of an embodiment of a core device of the clinical decision support system of the present invention.
7 is a schematic configuration diagram of a web application unit which is a main part of the data providing system unit of FIG.
FIG. 8 is a schematic block diagram of a CDSS requesting unit, which is a main part of the data providing system unit of FIG.
FIG. 9 is a schematic diagram of a main configuration of a CDSS management system unit, which is a main part of an embodiment of a core device of the clinical decision support system of the present invention.
FIG. 10 is a schematic configuration diagram of a CDSS DB unit which is a main part of the CDSS management system unit of FIG.
FIG. 11 is a schematic configuration diagram of a chart type management unit which is a principal part of the CDSS management system unit of FIG.
12 is a schematic configuration diagram of a process management unit which is a main part of the CDSS management system unit of FIG.
FIG. 13 is a schematic diagram of a main configuration of a legacy data system unit which is a main part of an embodiment of a core device of the clinical decision support system of the present invention.
FIG. 14 is a schematic configuration diagram of an embodiment of data in which the main data of the embodiment of the legacy data system unit of FIG. 13 is studied.
FIG. 15 is a schematic block diagram of an embodiment of a hospital system which is a main part of an embodiment of the legacy data system unit of FIG. 13;
16 is a schematic block diagram of a data management system unit which is a main part of an embodiment of a core device of the clinical decision support system of the present invention.
17 is a schematic configuration diagram of a personalized data management unit which is a main part of the data management system unit of FIG.
FIG. 18 is a schematic configuration diagram of a cluster analysis data management unit, which is a main part of the data management system unit of FIG. 16. FIG.
FIG. 19 is a schematic configuration diagram of a cluster characteristic management unit, which is a major part of the data management system unit of FIG. 16;
20 is a flowchart for explaining an embodiment of the clinical decision support method of the present invention.
21 is a flowchart for explaining an embodiment of a clinical decision support method using a core device of the clinical decision support system of the present invention.
Fig. 22 is a flow chart following the flow chart of Fig.
FIG. 23 is a flowchart for explaining a process of driving an application to a user apparatus in the embodiment of the clinical decision support method of FIGS. 21 and 22. FIG.
FIG. 24 is a flowchart for explaining a process of providing request data to a user apparatus in the embodiment of the clinical decision support method of FIGS. 21 and 22. FIG.
FIG. 25 is a flowchart for explaining a process of matching a disease code in the middleware system unit in the embodiment of the clinical decision support method of FIGS. 21 and 22. FIG.
FIG. 26 is a flowchart for explaining a disease code mapping process of the integrated management system unit receiving a disease code mapping request from the middleware system unit in the embodiment of the clinical decision support method of FIGS. 21 and 22. FIG.
FIG. 27 is a flowchart for explaining a process of providing requested patient information and a chart / CP from the data providing system unit in the middleware system in the embodiment of the clinical decision support method of FIGS. 21 and 22. FIG.
FIG. 28 is a flowchart illustrating a process of confirming a chart / CP setting requested by the web application unit of the data providing system unit in the CDSS request unit in the embodiment of the clinical decision support method of the present invention.
29 is a flowchart illustrating a process of providing a disease code to a middleware system unit of the CDSS management system unit in the embodiment of the clinical decision support method of the present invention.
30 is a flowchart illustrating a process of providing patient information and a necessary chart / CP component to the CDSS management system unit middleware system unit in the embodiment of the clinical decision support method of the present invention.
31 is a flowchart for explaining a process of the legacy data system processing by the legacy data processing part requested by the middleware system part in the embodiment of the clinical decision support method of the present invention.
FIG. 32 is a flowchart for explaining a process of the CDSS management system process of storing the processed data requested by the middleware system unit in the embodiment of the clinical decision support method of the present invention.
FIG. 33 is a flowchart for explaining a process of the CDSS management system unit for processing the necessary charts and components requested by the middleware system unit in the embodiment of the clinical decision support method of the present invention.
FIG. 34 is a flowchart for explaining a process of processing data of a legacy data system unit in legacy data processing requested by a middleware system unit in an embodiment of the clinical decision support method of the present invention.
FIG. 35 is a flowchart for explaining a process of processing the required legacy data requested by the middleware system unit in the hospital system of the legacy data system unit in the embodiment of the clinical decision support method of the present invention.
FIG. 36 is a flowchart for explaining a process in which the personalized data management unit of the data management system unit processes the personal requirement data mart storage in the CDSS management system unit in the embodiment of the clinical decision support method of the present invention.
FIG. 37 is a flowchart for explaining a process of the cluster analysis data management unit of the data management system unit storing the cluster analysis data mart in the CDSS management system unit in the embodiment of the clinical decision support method of the present invention.
FIG. 38 is a flowchart for explaining a process of the cluster characteristic management unit processing the cluster characteristic data mart storage requested by the cluster analysis data management unit of the data providing system unit in the embodiment of the clinical decision support method of the present invention shown in FIG.
FIG. 39 is a flowchart for explaining procedures from requesting a disease code of a middleware system part to providing a necessary chart and a component in the embodiment of the clinical decision support method of the present invention shown in FIGS. 21 and 22. FIG.
40 is a flowchart for explaining a processing procedure in the process management unit according to the patient basic information and the medical care information request by the CDSS management system unit of the middleware system unit in the embodiment of the clinical decision support method of the present invention shown in FIG.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the structure of the invention according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a schematic block diagram of an embodiment of a clinical decision support system of the present invention. As shown in FIG. 1, the clinical decision support system of the present invention comprises: a master database 1 to n (100) operated in an external hospital system (legacy); A database broker (200) for monitoring and scheduling contents in the master database (100) and for extracting necessary results and storing the contents; A database server 300 for storing a database extracted from the database broker 200; A web server 400 for receiving a request from a user mobile terminal and providing data to the mobile terminal in cooperation with the database server 300; A user mobile terminal 500 for requesting and receiving data from the web server 400; And a touch panel terminal 600 for accessing the database server 300 to request and receive data.

The database broker 200 extracts various file formats from a local legacy system DB, a remote legacy system DB, a cloud, and provides standardized data and interfaces. In addition, data standardization is performed through scheduling for data synchronization, scheduling for scheduled schedules of real time, minutes, hours, weeks, days, months, and years. In addition, the database broker 200 can be created in various types of programs and is configured not to be affected by the platform.

Fig. 2 is a configuration diagram showing the configuration of the embodiment of Fig. 1 in more detail. An interface unit 210 for defining and processing a common interface for providing a web service provided to the mobile terminal 500 and a service provided to the touch pad terminal, A scheduling composure unit 220 for ensuring the atomicity of data through execution of database monitoring and database update for minutes, hours, days, weeks, months, years, and reservations; A data connection composure unit 230 as a module for accessing various legacy systems, a cloud, and a file system; An observer composure unit 240 for performing a time inspecting function for monitoring and scheduling modules to be monitored in real time; A database broker 200 including a service and a daemon unit 250 for increasing the portability of services and daemon types provided by the platform through a common module; a database broker 200 for storing data received through the database broker 200; A web server 400 for receiving a data transmission request from the mobile terminal 500 in cooperation with the database server 300 and providing data and a web server 400 for providing data to the mobile terminal 500, And an interface unit 510 for defining and processing a common interface for providing services to the touch pad terminal; A middleware unit 520 for processing and controlling data provided to the interface unit 510 and providing final results to the web application; A mobile terminal 500 including a web application unit 530 for providing a result processed by the middleware unit 520 to a user and a service provided to a web service and a touch pad terminal provided to the mobile terminal 500 An interface unit 610 for defining and processing a common interface for providing a common interface; A document unit 620 for creating and providing a moving picture, a still image, a hypertext, a chart, and a table through data provided through the interface unit 610; And a touch pad terminal 600 including an application unit 630 for providing a result configured by the document unit 620 to a user.

In the database broker 200, data connection is made up of remote data and local data. In case of private data, the data broker 200 is accessed through an authentication request. In case of public data, data is processed through a parser. In the case of remote data, the extracted data is EMR, LIS, OCS, PACS, MIS, HIS, ERP and disease code. You can connect the cloud system using cloud SDK, XML and API, Connect using Nonse, SQL, SDK, or connect public institution web system through http, https or open API.

In the case of local data, the extracted data includes CDSS (Clinical Decision Support System) knowledge, chart, CDSS category, and the like. The file I / O system can be connected through a file system or an I / O stream, .

The mobile terminal 500 or the touch pad terminal 600 (hereinafter, referred to as a "user device") accesses the web server 400 and requests application activation. The web server 400 responds to the request of the user apparatus and drives the application to the user apparatus. And transmits a disease code mapping request to the web server 400 in the driven application of the user apparatus. The web server 400 transmits a disease code mapping request to the DB server 300 according to a disease code mapping request of the user device. The DB server 300 transmits the disease code mapping to the web server 400 in response to a request from the web server 400. The web server 400 delivers the received disease code mapping to the user device. The web server 400 transmits patient information and chart / CP request information requested from the DB server 300 to the web server 400. The web server 400 receives the patient information and chart / To the user device. In addition, the DB server 300 transmits a legacy data processing request to the database broker 200, and the database broker 200 responds to the legitimate data processing request by providing the DB server 300 with a data list / definition to provide. The database server 300 receiving the required data list / definition from the database broker 200 requests the necessary legacy data to the master DB 100 as the hospital system. The master DB 100, which has received the data request from the DB server 300 in the case of the necessary legacy, provides the legacy data to the DB server 300.

3 is a schematic block diagram of an embodiment of a core device of the clinical decision support system of the present invention. As shown in FIG. 3, the clinical decision support system of the present invention includes an integrated management system 1000 for managing various disease codes used in hospitals and delivering a disease code mapping table requested from the middleware; A middleware system 2000 connected to each component of the system for performing data request and transmission; A data providing system 3000 for searching and processing the requested information through the middleware system 2000 and outputting the requested information through a user device when the user requests desired information through the apparatus; A CDSS management system unit 4000 for providing various chart information, CP information, process information, cooperative / linked disease information, and other data on a mobile CDSS screen; A legacy data system unit 5000 for processing or providing legacy data related to the existing hospital system; And a data management system unit 6000 for managing data on a patient individual and a patient cluster.

The middleware system unit 2000 may be included in the data providing system unit 3000.

The integrated management system unit 1000 manages various disease codes used in hospitals as an integrated management system of a disease classification system and sends a disease code mapping table requested from the middleware system unit 2000 to each management unit, And receives and provides a mapping table / rule.

The data providing system unit 3000 is a core of the CDSS process and includes a middleware system unit 2000 connected to all the system units 1000 to 6000, touch pad terminals used by the user, web- When requesting information desired by the user through the terminal, the central processing unit 2000 searches for and processes the requested information through the middleware system unit 2000, and outputs the requested information through a web-based application that is independent of the terminal and the OS .

In addition, the CDSS management system unit 4000 is configured to manage a portion of the mobile CDSS screen that the user can actually see, and includes various chart information, CP (Clinical Pathway) information corresponding to a doctor's manual, Process flow information, collaborative / linked disease information, a data mart (Mart), a data warehouse, and a database that requests and provides personal and cluster data.

The legacy data system unit 5000 includes data processing of legacy data related to the existing hospital system and a hospital system. In the middleware system unit 2000, legacy data processing, Time data, and provides the requested machining data and necessary legacy data.

In addition, the data management system unit 6000 includes a personalized data management unit, a cluster analysis data management unit, and a cluster property management unit for managing individual individuals and communities, and the personalized data management unit and the cluster analysis data management unit Wherein the management server receives individual and cluster processing data from the CDSS database and transmits the mart archive data to the management unit and stores the individual and cluster required data marts in the CDSS database, And stores the mart archive data, stores each characteristic and mart archive data in the management unit, and stores the cluster characteristic data mart.

FIG. 4 is a schematic configuration diagram of an embodiment of an integrated management system unit which is a main part of the embodiment of FIG. 3; A middleware interworking unit 1100 for interworking with the middleware system unit 2000 to manage various disease codes; A code mapping processor 1200 for requesting a code mapping table requested from the middleware system to each code manager to define a disease code mapping / rule; An ICD management unit 1300 for providing and managing an International Classification of Diseases and Related Health Problems (ICD) code table, which is an international disease classification requested by the code mapping processing unit 1200; A KCD management unit 1400 for providing and managing a KCD code table as a Korean disease classification requested from the code mapping processing unit 1200; A Ucode management unit 1500 for providing and managing a Ucode code table requested by the code mapping processor 1200; A SEER management unit 1600 for providing and managing a SEER (Surveillance, Epidemiology, and End Results) code table requested from the code mapping processing unit 1200; A CCPC management unit 1700 for providing and managing a CCPC code table as a certificate for the clinical care program requested from the code mapping processing unit 1200; And a code management unit 1800 for providing and managing other disease related code tables requested from the code mapping processing unit 1200. [

 FIG. 5 is a schematic configuration diagram of a middleware system unit 2000, which is a main part of the embodiment of FIG. The middleware system part 2000 of the present invention is a system part that integrates all hospital systems using middleware as a core device of CDSS and enables customized clinical decision support according to actual work flow of a hospital.

As shown in FIG. 5, an application interworking unit 2100 for interworking the middleware system unit 2000 with a web-based application; A data study unit 2200 for receiving and defining a data list / definition in case of a necessary legacy from the middleware system unit 2000; A disease classification system mapping management unit 2300 for delivering a disease code mapping / rule requested from the middleware; A CDSS generating unit 2400 for generating CDSS data and requesting the CDSS DB interworking unit for necessary data; A hospital system interlocking unit (2500) for interlocking with a hospital system related to legacy data; A messaging control unit 2600 for coding the OCS information necessary for processing the required chart / CP component into HL7; A SNomed CT interlocking unit 2700 for transforming the EMR information necessary for processing the necessary chart / CP element by using the SNomed CT; And a CDSS DB interlocking unit 2800 for interlocking the middleware system unit and the CDSS DB unit.

FIG. 6 is a schematic configuration diagram of the data providing system unit 3000, which is a main part of the embodiment of FIG. As shown in FIG. 6, the data providing system unit 3000 of the present invention includes a user device 3100 that is a terminal used by a user such as a tablet PC, a smart phone, and a PC; A web application unit 3200 for running on a standardized web-based basis regardless of the type of the user device 3100; And a CDSS request unit 3300 for managing the requested CDSS data (chart, CP, patient / cluster, options, etc.) and requesting the corresponding data to the middleware system unit 2000.

Among the configurations of the data providing system unit 3000, the user apparatus 3100 includes various terminals that can be actually used by the user (not shown). Basically, the user apparatus 3100 has a function of processing data for requests A control unit, a device computing device, an output device, and a wireless Internet security kit. When the user inputs a request to the controller, the input / output information of the request is separated and transmitted to the device processor. The device arithmetic unit outputs data requiring output based on the input information received from the control unit through the output device and transmits the data to the wireless Internet security kit for security of input information. Encrypts the information received in the wireless Internet security kit, transmits the secured information to the application driver, and finally operates the user device.

FIG. 7 is a schematic configuration diagram of a web application unit 3200, which is a main part of the embodiment of the data providing system 3000 of FIG. As shown in FIG. 7, a device interworking unit 3210 for interworking a user apparatus with a web-based application; A rights management unit 3220 for confirming various rights such as login information and requesting a drive to operate an application requested by the user; An application interface unit 3230 for connecting the web application unit 3200 with the authority and request for driving the application; A CDSS interworking unit 3240 for interworking the CDSS requesting unit 3300 and the web application unit 3200 to be described later; A middleware interworking unit 3250 for interfacing the web application unit 3200 with the middleware system unit 2000; And a screen output unit 3260 for outputting a screen to the user device 3100.

FIG. 8 is a schematic configuration diagram of a CDSS request unit 3300, which is a major part of the embodiment of the data providing system 3000 of FIG. An application interworking unit 3310 for receiving data requested by the web application unit 3200 and interworking the web application unit 3200 and the CDSS request unit 3300 as shown in FIG. 8; A chart selection unit 3320 for selecting a chart type suitable for the requested data; An option management unit 3330 for selecting an option of a corresponding chart selected by the chart selection unit 3320; A CP data management unit 3340 for storing the CP data and receiving the CP request to distinguish the CP type according to the CP type; A patient / cluster management unit 3350 for managing data on patients and clusters and receiving requests for patient / cluster related data; And a data classifying unit 3360 for confirming necessary data and requesting the application interworking unit 3310 with necessary data.

FIG. 9 is a schematic configuration diagram of a CDSS management system unit 4000, which is a main part of the embodiment of FIG. As shown in Fig. 9, a structure actually viewed on the mobile CDSS screen includes a CDSS DB unit 4100; A chart type management unit 4200 for managing various charts for clinical decision support, and providing required charts and components requested from the middleware system unit; And a process management unit 4300 for managing various processes in cooperation with the CDSS DB unit 4100.

FIG. 10 is a schematic configuration diagram of a CDSS DB unit 4100, which is a main part of the CDSS management system unit 4000 of FIG. A middleware interworking unit 4110 for interworking the CDSS DB unit 4100 and the middleware system unit 2000; A process interlocking unit 4120 for interlocking with the process management unit 4300; A chart type interlocking unit 4130 for interlocking the chart type management unit 4200 and the CDSS DB unit 4100; A CP information management unit 4140 for receiving CP information and providing the corresponding information; A CDSS data supplier 4150 having a data warehouse (DW) function for storing the processed data DB and providing the data when the data is requested; A CDSS mart storage unit 4160 having a data mart function for storing individual and cluster related data marts; A personal data management unit 4170 for managing personal processing data and connecting the personal processing data management unit 6100 and the CDSS DB unit 4100 to be described later; A cluster data management unit 4180 for managing cluster analysis data and connecting the cluster analysis data management unit 6200 and the CDSS DB unit 4100 to be described later; And a disease data management unit 4190 for managing and providing data on the patient's associated diseases and cooperation.

FIG. 11 is a schematic configuration diagram of a chart type management unit 4200, which is a major part of the CDSS management system unit 4000 of FIG. 11, a CDSS DB interlocking unit 4210 for interlocking the CDSS DB unit 4100 and the chart type management unit 4200; A retry interval managing unit 4220 for calculating a retry interval of the patient through a visit date and a visit count of the patient; A VIP customer analysis unit 4230 for analyzing the VIP by classifying the patient group showing a similar pattern according to the visiting pattern using the behavior of the interval data; A utilization rate management unit 4240 for charting the reduction time due to the movement of the group, the increased patient, and the increased utilization ratio according to the group movement rate of the equipment and the operation rate of the equipment for each group; A trust / support management unit 4250 for managing the use of a chart or the like to increase the efficiency of equipment / prescription under a specific condition based on a lift according to conditions such as prescription / treatment / medication; A lead-in rate management unit 4260 for obtaining the number of first-visit patients in the total number of patients during a certain period of time and obtaining the ratio of the first-time patients; A departure rate management unit 4270 for calculating the number of patients who have decreased as the visit date is reached and calculating the patient departure rate; A conversion rate management unit 4280 for calculating the percentage of patients who have visited the patient for the first time during a certain period of time, Patients who are scheduled to visit the next meeting of the patient based on the behavior pattern of the patient's behavior and the maximum interval of retention interval of the patient to manage to improve the patient survival rate through advance contact at a certain point before the patient departs A survival rate management unit 4290; A reservation default rate management unit 4292 for calculating an interval in which a retention interval of individual patients is higher than a maximum retention interval of a corresponding community by a community divided on the basis of behavior as a behavior pattern of the patient; A patient satisfaction management unit (4294) for managing the satisfaction of the patient and the satisfaction of the patient through the comparison and analysis of the average satisfaction of the corresponding group; And a patient fee management unit (4296) for calculating an appropriate medical fee of the patient through comparison and analysis between the medical fee of the individual patient and the average medical fee of the corresponding group.

The interval of patient retention in the interval management unit 4220 of the CDSS management system unit 4000 may generate a line chart with the following pseudo code.

- subscript: i *, c *, j (number of visits) * patient i * ∈ cluster c *

- Interval i * j = Julian (visiting date i * j) - Julian (visiting date i * (j-1))

*

= 0- average retry interval c * j =

*

= 0

- For the number of visits j [j = 2 ... ∞]

plot interval i * j over j

plot average resilience interval c * j over j

- End j

Also, the VIP customer analyzer 4230 can analyze the VIP customer by generating an area chart using the following pseudo code.

- subscript: i, c (group 1 ... group 4), j (number of visits)

- Cumulative retry interval = 0

- Number of visits = 0

- For patient i [i = 1 ... ∞]

-For ij [j = 2 ... ∞]

Interval ij = Julian (visit ij) - Julian (visit i (j-1))

Cumulative retry interval = cumulative retry interval + retry interval ij

Visits = Visits + 1

-End ij

Average interval i =

- End i

Quantile (오름차순 {재진간격ij , i=1…∞})) over jGroup 1: plot max interval interval 1j (= interval between intervals

Quantile (ascending {retry interval ij, i = 1 ... ∞})) over j

Quantile (오름차순 {재진간격ij , i=1…∞})) over jGroup 2: plot max interval interval 2j (= interval between intervals

Quantile (ascending {retry interval ij, i = 1 ... ∞})) over j

Quantile (오름차순 {재진간격ij , i=1…∞})) over jGroup 3: plot max interval interval 3j (= interval between intervals

Quantile (ascending {retry interval ij, i = 1 ... ∞})) over j

Group 4: plot max interval interval 4j (= max interval interval {interval interval ij, i = 1 ... ∞}) over j

In addition, the operation rate management unit 4240 may generate a pie chart and a bar chart that can be divided into groups for equipment operation and equipment operation according to the group by the following pseudo code.

<Relative operation rate by group>

- subscript: c, e (inspection equipment, {e | bonescan, MRI, CT, X-ray})

- Relative operation rate by group ce =

- plot relative operating rate ce over c (c = 1 ... 4)

<Relative operation rate by device>

- subscript: c, e (inspection equipment, {e | bonescan, MRI, CT, X-ray})

- Relative operation rate per unit ce =

- relative operation rate per plot device ce over e

<Bar Chart>

- Subscript: o (Orderset, {o | Imaging and Radiotherapy, Rehabilitation and Physical Therapy, CT, MRI, SONO}), c, j

- shortening time cj = average interval of retry cj - average interval of retry (c-1) j

- Total shortening time c =

- increased patient c =

- plot total shortening time c over c

plot patient c over c

<Increased utilization>

- subscript: e, c

(c≥2)- increased utilization ce =

(c? 2)

- plot increased utilization rate ce over c

over e

In addition, the trust / approval management unit 4250 may use the following pseudo code to increase the efficiency of equipment / prescription under specific conditions based on conditional lift using a bar chart and a line chart You can create a chart.

- subscript: o orderset, o | blood test, x-ray, MRI, CT, SONO, medication,

e {equipment, e | bonescan, MRI, CT, X-ray}

- support orderset = o *

- Confidence rate = 0

- Condition orderset = null

recursion1

For o

> 신뢰율if

> Reliability

then trust =

(Condition orderset = o)

end if

plot confidence rate over reliability (number of people)

manual interruption

end o

Supports orderset =

Go to recursion

In addition, the reserve default rate managing unit 4292 stores the pseudo code of the patient based on the behavior of the patient based on individual characteristics such as age, sex, height, and weight, The reservation default rate can be grasped and predicted by highlighting a section where the interval between individual patients is higher than the interval.

- subscript: i *, j, c *

- For the number of visits j [j = 2 ... ∞]

plot interval i * j over j

plot max interval interval c * j over j

- if interval i * j> max intervals c * j then highlight

- end if

- end j

In addition, the patient survival rate management unit 4290 calculates the patient survival rate and the patient's next visit date and the time difference between the patient's age, sex, height, and body weight based on the Behavior, which is a behavior pattern of the patient, with the following pseudo code Based on the date of visit, the survival rate of non-individual communities based on the final visit date, behavior, and patient survival rate can be combined to allow patients to analyze patients with low survival for prior contact at a specific point in time before departure .

- subscript: i *, c *, s-rate (survival rate), j (number of visits)

s-rate (visiting date i * max (j)) = 100%

s-rate (expected date of visit i * (max (j) +1)) = 100%

s-rate (visit date i * (max (j) + max retry interval c * (j + 1))) = 0%

- For visiting j [j = 2 ... ∞]

plot s-rate (visit date i * max (j)) over visit date

plot s-rate (expected date i * (max (j) +1)) over Date of visit

plot s-rate (visit date i * (max (j) + max recurrence interval c * (j + 1))) over visit date

- End visit j

In addition, the lead-in rate management unit 4260 and the release-rate management unit 4270 use the following pseudo code as a period between data and a specific period, The number of visiting patients can be sought to determine the percentage of people who receive the initial treatment (rate of entry), and the patient turnover rate can be analyzed by the number of patients who have decreased as the visit dates.

<Insertion rate>

- subscript: m (m = 1 ... 12), q (q = 1 ... 4), y (year), c

- Entry rate m =

- plot inclusion rate m over m

For group c (c = 1 ... 4)

plot inclusion rate cm over m

- End c

<Bounce rate>

- subscript: c, j (number of visits), i

- Exit rate j =

[j = 2 ... ∞]

- plot abandonment rate j over j

For group c (c = 1 ... 4)

plot abandonment rate cj over j

- End c

In addition, the conversion rate management unit 4280 analyzes the ratio (conversion rate) of patients who visited the patient for the first time during a certain period (month / quarter / year) with the following pseudo code can do.

- subscript: m (m = 1 ... 12), q (q = 1 ... 4), y (year), c, i, j

- Conversion rate m =

- plot Conversion rate m over m

For group c (c = 1 ... 4)

plot Conversion rate cm over m

- End c

FIG. 12 is a schematic configuration diagram of a process management unit 4300, which is a main part of the CDSS management system unit of FIG. The process management unit is a configuration for managing the 8-step medical care process performed by the patient in the hospital. As shown in FIG. 12, a CDSS DB interlocking unit 4310 for interlocking the CDSS DB unit 4100 and the process management unit 4300; A visiting process management unit 4320 for managing the process when the patient first visits the hospital; A registration process management unit 4330 for managing a process of registering a visiting patient with a hospital; A diagnostic process management unit 4340 for managing a process of diagnosing a registered patient by a doctor; An examination process management unit 4350 for managing the examination process of the MRI, CT, etc. of the patient diagnosed by the doctor; A maintenance process management unit 4360 for managing processes related to the maintenance and management (hospitalization, etc.) of the inspected patient; A payment process management unit 4370 for managing processes related to payment of a medical fee of a patient who has received the medical service; A post-management process management unit 4380 for managing processes related to continuous post-management (telephone, text message, etc.) to the patient after all medical services are terminated; And a Return to Clinic (RTC) process management unit 4390 for managing a process related to a patient who has visited again such as a hospital reservation.

13 is a schematic configuration diagram of a legacy data system unit 5000 which is a main part of the embodiment of FIG. As shown in FIG. 13, data 5100 for processing the legacy data related to the existing system; And a hospital system 5200 configured with all the systems used in the hospital.

FIG. 14 is a schematic configuration diagram of data 5100, which is a main part of the legacy data system unit 5000 shown in FIG. A middleware interworking unit 5110 for connecting the data learning unit 5100 and the middleware system unit 2000 as shown in FIG. 14; An analysis modeling management unit 5120 for performing a modeling request for legacy data processing requested from the middleware system unit 2000 and for managing analysis modeling of necessary data; A statistical analysis management unit 5130 for performing statistical analysis on data that has undergone analysis and modeling of necessary data; And a data mining management unit 5140 for performing data mining on data that has undergone statistical analysis on necessary data.

FIG. 15 is a schematic configuration diagram of a hospital system 5200, which is the main delegate of the legacy data system unit 5000 of FIG. As shown in FIG. 15, a middleware interworking unit 5210 for interworking the middleware system unit 2000 and the hospital system 5200; An EMR management unit 5220 for managing electronic medical records of the hospital; An LIS management unit 5230 for managing the inspection information system of the hospital; An OCS management unit 5240 for managing the prescription delivery system of the hospital; A PACS management unit 5250 for managing the medical image storage and transmission system of the hospital; An MIS management unit 5260 for managing the management information system of the hospital; An HIS management unit 5270 for managing the hospital information system of the hospital; An ERP management unit 5280 for enterprise resource management of the hospital; And a hospital system management unit 5290 for managing other systems of the hospital.

FIG. 16 is a schematic configuration diagram of the data management system unit 6000, which is a main part of the embodiment of FIG. As shown in Fig. 16, there are provided a personalized data management unit 610 for managing processing data of individual patients; A cluster analysis data management unit 6200 for managing data on the patient cluster classified on the basis of the interval between the clusters; And a cluster characteristic management unit 6300 for managing data related to the characteristics of the patient cluster classified on the basis of the interval of intervals.

FIG. 17 is a schematic configuration diagram of a personalized data management unit 6100, which is a main part of an embodiment of the data management system 6000 of FIG. A CDSS DB interlocking unit 6110 for interlocking the personal processing data management unit 6100 with the middleware system unit 2000 through the CDSS DB unit 4100; A unique data management unit 6120 for storing unique data of a patient and delivering mart archive data; A condition variable management unit 6130 for storing the chance variable data such as the age of the patient and delivering the mart archive data; A decision variable management unit 6140 for storing decision variable data of a patient and delivering mart archive data; An action variable management unit 6150 for storing behavior variable data of a patient and delivering mart archive data; And a patient data management unit 6160 for storing other data of the individual patient and delivering the mart archive data.

FIG. 18 is a schematic configuration diagram of the cluster analysis data management unit 6200, which is a main part of the embodiment of the data management system 6000 of FIG. A CDSS DB interlocking unit 6210 for interlocking the cluster analysis data management unit 6200 with the middleware system unit 2000 through the CDSS DB unit 4100; A period management unit 6220 for storing period related data for analyzing the patient cluster and delivering mart archive data; A cluster reference management unit 6230 for storing data on the cluster reference of the patient cluster analysis and delivering mart archive data; And a cluster characteristic interlocking unit 6240 for connecting the cluster analysis data management unit 6200 and the cluster characteristic management unit 6300.

FIG. 19 is a schematic configuration diagram of a cluster characteristic management unit 6300, which is a major part of the embodiment of the data providing system unit 6000 of FIG. As shown in FIG. 19, a cluster analysis data management unit 6310 for managing data related to cluster analysis; Equipment for managing and storing data on equipment operation characteristics per patient cluster and transmitting mart archive data is provided with a dynamic characteristic management unit 6320; A CBD modeling management unit 6330 for managing and storing the Chance - Behavior - Decision modeling of the patient cluster and delivering the mart archive data; And a cluster visiting characteristic management unit 6340 for managing and storing data according to the visiting characteristic of each patient cluster and delivering the mart archive data.

The operation of the embodiment of the clinical decision support system of the present invention described above will be described below. The description of the operation of the clinical decision support system of the present invention is the same as that of the clinical decision support method of the present invention, so that the following embodiments of the clinical decision support method of the present invention will be referred to.

20 is a flowchart for explaining an embodiment of a method for supporting clinical decision making using the clinical decision support system of the present invention. As shown in FIG. 20, the clinical decision support method using the clinical decision support system of the present invention includes: a step (S100) of connecting a user apparatus to a web server; (S101) the user device transmitting application drive request data to the web server; (S102) the web server driving an application to the user device; (S103) transmitting disease code mapping request data to be input to the application of the user device to the web server; Transmitting the disease code matching request signal received from the user device to the DB server (S104); (S105) the DB server transmits a disease code mapping table / rule to the web server according to the disease code mapping request; (S106) the web server transmits a disease code mapping to the user device based on a disease code mapping table / rule transmitted from the DB server; Transmitting (S107) patient information and chart information / CP transmission request data to the web server in the application of the user apparatus; Transmitting, by the web server, the patient information, chart information / CP request data to the DB server (S108); Transmitting the patient information and chart information / CP to the web server (S109); And transmitting, by the web server, the patient information and the chart information / CP to the user equipment (S110).

[Full flowchart]

FIGS. 21 and 22 are flowcharts for explaining an embodiment of a method for supporting clinical decision making using a core apparatus of the jury decision support system of the present invention. As shown in FIGS. 21 and 22, the clinical decision support system of the present invention comprises: a step (S200) of transmitting user application request data to a web application unit of a data providing system unit; (S201) of causing the web application unit to run an application on the user device; Transmitting disease code mapping request data to the web application unit in a driven application of the user equipment (S202); (S203) transmitting the disease code mapping request data requested by the user device to the web application unit middleware system unit; (S204) of transmitting the disease code mapping table request data to the integrated management system of the middleware system unit; (S205) transmitting the disease code mapping table / rule requested by the integrated management system to the middleware system unit; Transmitting the disease code mapping to the web application unit by the middleware system unit (S206); The web application unit transmitting the disease code mapping to the application of the user equipment (S207); (S208) of transmitting the patient information request data to the web application unit of the data providing system unit in the application; (S209) of transmitting the patient information request data transmitted from the user apparatus to the middleware system unit by the web application unit; (S210) of transmitting the basic information of the patient and the medical care information request data to the CDSS DB unit of the CDSS management system unit of the middleware system unit; Transmitting the patient information from the CDSS DB unit to the middleware system unit (S211); Transmitting the patient information to the web application unit by the middleware system unit (S212); The web application unit transmitting patient information to the application of the user equipment (S213); Transmitting (S214) the chart / CP request data to the web application unit of the data providing system unit in the application of the user apparatus; Transmitting the chart / CP setting request data to the CDSS request unit of the data providing system unit (S215); Transmitting the chart / CP setting confirmation data to the web application unit (S216); (SS217) transmitting the chart / CP request data to the middleware system unit by the web application unit; Transmitting the request chart / CP element request data to the CDSS DB unit of the CDSS management system unit (S218); (S219) the CDSS DB unit transmits the necessary chart / CP element to the middleware system unit; (S220) of transmitting the chart / CP to the web application unit by the middleware system unit; A step S221 of causing the web application to output a chart / CP to the application of the user device; (S222) the data of the legacy data system unit of the middleware system unit transmits legacy data processing request data to the study; (S223) of transferring the data list / definition required by the data to the middleware system; (S224) of transmitting data request data to the hospital system of the legacy data system unit when the legacy middleware system unit is in the legacy system; (S225) the legacy system transmits the legacy data to the middleware system; (S226) the middleware system part transmits the necessary legacy data by the data study; (S227) when the data is transferred from the middleware system to the middleware system; And transmitting the processed data to the CDSS DB unit and storing the processed data in the middleware system unit (S228).

[Application driving, processing in the data providing system section]

FIG. 23 is a detailed flowchart of a step of the application of the web application unit to the user apparatus in the embodiment of the clinical decision support method of the present invention shown in FIGS. 21 and 22; FIG. As shown in FIG. 23, the step (S300) of receiving the application drive request data transmitted from the user apparatus by the apparatus interworking unit of the web application unit; (S301) of transmitting application authorization confirmation data to the application interface unit in response to the received application activation request; Transmitting application authorization data from the application interface unit to the authority management unit (S302); And a step S303 in which the right management unit drives an application to the user device based on the received application right confirmation data.

[Disease Code Mapping, Patient Information, Chart / CP, Processing in Data Delivery System Section]

FIG. 24 is a flowchart illustrating a process of processing a disease code mapping, a patient information, and a chart / CP in a data providing system unit requested by a user apparatus in an embodiment of the clinical decision support method of the present invention shown in FIG. 21 and FIG. FIG. 24, in the application in which the user apparatus is driven, request data such as a disease code mapping request, a patient information request, and a chart / CP request are received by a device interfacing unit included in the web application unit of the data providing system unit (S400); (S401) of inputting the received request data to the application interface unit; Transmitting the chart / CP setting request data to the application interface unit (S402); Transmitting the chart / CP setting confirmation data to the application interface (S403); The application interface unit transmits the request data of the user equipment to the middleware interworking unit (S404); Transmitting the chart / CP setting request data to the CDSS requesting unit (S405); Transmitting the chart / CP setting confirmation data to the web application unit (S406); Transmitting the disease code mapping request data requested by the user device to the middleware system of the web application unit (S407); (S408) of transmitting the disease code mapping table / rule to the web application unit by the middleware system unit; The web application unit transmits patient information request data to the middleware system unit (S409); (S410) of transmitting the patient information to the web application unit by the middleware system unit; (S411) transmitting the chart / CP request data to the middleware system unit by the web application unit; (S412) transmitting the screen output command data and the screen output sub chart / CP of the web application unit; (S413) the screen output unit transmitting screen output command data to the apparatus interlocking unit; And the step S414 of providing the disease code mapping, the patient information, and the chart / CP to the application of the user device.

In connection with the chart / CP request and provision in the above embodiment, when a user device requests a chart (request from a patient or a physician) or a CP (mainly a request from a physician), the application interface unit Enter the details. The application interface unit provides a list and kind of charts and CPs on the screen of the user device so that the user can conveniently use them. When the user requests a specific chart or CP, the CDSS request unit selects the chart and CP type suitable for the user request, checks the chart / CP setting in the application interface unit, and transmits the chart / CP to the web application unit do.

[Disease Code Mapping, Processing in the Middleware System Section]

FIG. 25 is a flowchart illustrating a method of supporting clinical decision support according to an embodiment of the present invention; FIG. 25 is a flowchart illustrating a process of transmitting a disease code mapping table / rule to the web application unit, And FIG. As shown in FIG. 25, the step S500 of the application linkage unit of the middleware system unit receives the disease code mapping request data from the web application unit; (S501) of transmitting the disease code request data to the CDSS DB unit by the application interlocking unit; Transmitting the disease code to the CDSS DB interlocking unit of the middleware system unit (S502); Transmitting the mapping request data of the disease code to the CDS mapping unit (S503); (S504) the disease classification system mapping management unit transmitting the disease code mapping table / rule request data to the CDSS DB linking unit; (S505) the CDSS DB interworking unit requests a disease code mapping table to the integrated management system unit; The integrated management system transmits the disease code mapping table / rule to the disease classification system mapping management unit of the middleware system unit and transmits a mapping request (S506); And the disease classification system mapping management unit transmits the disease code mapping table / rule to the web application unit (S507).

[Disease Code Mapping, Processing in Integrated Management System]

FIG. 26 is a detailed flowchart of a configuration in which the integrated management system transmits the disease code mapping table / rule to the middleware system in the embodiment of the clinical decision support method of the present invention shown in FIGS. 21 and 22. FIG. 26, a step S600 of transmitting code mapping table request data to a middleware interworking unit in the integrated management system unit, which has requested the transmission of the disease code mapping table from the middleware system unit, to the code mapping processing unit; The code mapping processing unit transmits the ICD code table request data to the ICD management unit (S601); The ICD management unit transmitting KCD code table request data to the KCD management unit (S602); Transmitting the Ucode table request data to the Ucode management unit (S603); The Ucode management unit transmitting the SEER code table request data to the SEER management unit (S604); The SEER management unit transmits CCPC code table request data to the CCPC management unit (S605); (S606) the CCPC management unit transmits the other code table request data to the code management unit; (S607) of the code management unit transmitting the necessary code table to the code mapping processing unit; (S608) the code mapping processing unit transmitting the disease code mapping table / rule to the middleware interworking unit; And the step S609 in which the middleware interworking unit transmits the disease code mapping table / rule to the middleware system unit.

The disease code mapping means, for example, mapping the disease name and the disease code (ICD, KCD, etc.) used in the hospital in the database or the process.

In the above embodiment, the middleware system receives the disease code mapping request from the user equipment-web application unit-CDSS request unit, and requests the mapping table through the middleware interworking unit in the integrated management system. A code table to be mapped to the code mapping processor is requested, and a code corresponding to the name of the disease currently used in the hospital, that is, ICD, KCD, Ucode, SEER, CCPC, Process. When the code mapping operation is completed, the necessary code table is transmitted again to the code mapping processing unit, and the mapping table and rules regarding the disease code are defined in the code mapping processing unit. And transmits the defined mapping table and rules to the middleware system unit through the middleware interworking unit.

[Patient Information, Chart / CP Provision, Processing in Middleware System]

FIG. 27 is a flowchart for explaining the processing procedure in the middleware system section of the patient information and chart / CP in the embodiment of the clinical decision support method of the present invention of FIGS. 21 and 22. FIG. 27, the step S700 of receiving the patient information request, chart / CP request data transmitted from the web application unit, and transmitting the CDSS knowledge request data to the CDSS generating unit by the application interworking unit of the middleware system unit; Transmitting the required data request data to the CDSS DB interworking unit (S701); Transmitting the chart / CP element request data to the CDSS DB unit of the CDSS management system unit (S702); Transmitting the necessary chart / CP component to the CDSS DB interworking unit (S703); Transmitting the processing request data of the necessary chart / CP component to the CDSS generating unit (S704); Transmitting the HL7 coding request data of the necessary chart / CP element to the CDSS generating unit (S705); The messaging control unit transmits SNomed CT utilization request data to the SNomed CT interface unit (S706); (S707) the SNomed CT interworking unit transmits processing completion information of the necessary chart / CP element to the application interworking unit; And transmitting the patient information, chart / CP to the web application unit (S708).

[Provided to web application part of chart / CP setting check, processed in CDSS request part]

FIG. 28 is a flowchart illustrating a procedure for requesting a chart / CP setting in the CDSS request unit of the data providing system unit and receiving a setting confirmation by the web application unit of the data providing system unit in the embodiment of the clinical decision support method of the present invention shown in FIGS. 21 and 22 Fig. 28, the step S800 of receiving the chart / CP setting request data from the web application unit and transmitting the chart type selection request data to the chart selecting unit is performed by the application linking unit of the CDSS request unit included in the data providing system unit, Wow; (S801) of transmitting the chart option selection request data to the chart selection unit management unit; The option management unit transmits request data of patient / cluster related data to the patient / cluster management unit (S802); (S803) of transmitting the necessary data confirmation request data to the data classification unit by the patient / cluster management unit; Transmitting the request data of the required data to the application interlocking unit (S804); Transmitting the CP request data to the CP information management unit (S805); The CP information management unit transmits the classification request data according to the CP type to the data classification unit (S806); Transmitting the request data of the necessary data to the application interlocking unit (S807); And transmitting the chart / CP setting confirmation data to the web application unit (S808).

In the above embodiment, the chart / CP transmitted to the application interlocking unit in the CDSS request unit selects a chart type suitable for an e-book request in the chart selection unit. If the chart requires an option such as age or gender of the patient, select the option in the option management section. In addition, when patient / cluster related data is required, the patient / cluster management unit requests the corresponding data. The data extracted from the patient / clustering management unit is confirmed by the necessary data or data classification unit, and the necessary data is transmitted to the application interlocking unit. The application interworking unit requests the CP information management unit for the CP, and the CP information management unit finds and provides the CP set for the disease and the patient in the CP DB. Sends the provided CP to the data classifier, classifies it according to the CP type, and transmits the necessary data to the application interlocking part.

[Request and provide disease code, process within CDSS DB department]

FIG. 29 is a flowchart illustrating a procedure of a CDSS DB unit for processing a corresponding disease code for requesting a disease code from the CDSS DB unit of the CDSS management system unit in the embodiment of the clinical decision support method of the present invention shown in FIG. 25 Fig. 29, the middleware interworking unit of the CDSS DB unit included in the CDSS management system unit receives the disease code request data from the middleware system unit and transmits the disease code calling data to the CDSS DW unit (S900); (S901) the CDSS DW unit transmits the disease code to the middleware interworking unit; And transmitting the disease code to the middleware system (S902).

[Patient information, chart / CP component processing, processing within the CDSS DB department]

FIG. 30 is a flowchart illustrating a method of supporting clinical decision support according to an embodiment of the present invention shown in FIGS. 21 and 22, in which a middleware system requests a patient basic and treatment information, a necessary chart / CP component to a CDSS DB unit of a CDSS management system, Is a flowchart for explaining the process of processing the request. 30, the middleware interworking unit of the CDSS DB unit included in the CDSS management system unit receives the patient basic and treatment information and the necessary chart / CP component request data from the middleware system unit and transmits the process flow call data (S1000); (S1001) of transmitting the chart type call data to the chart interworking unit of the process interworking unit; The step (S1002) of transmitting the CP call data to the CP information management unit by the chart type interworking unit; The CP information management unit transmitting patient progress information request data to the process management unit (S1003); The CP information management unit confirms the patient progress information and transmits the required chart and the component request data to the chart type management unit (S1004); Transmitting the required data mart call data to the CDSS mart management unit (S1005); (S1006) the CDSS mart management unit transmitting necessary data to the middleware interworking unit; And transmitting the patient information and the required chart / CP component to the middleware system unit (S1007).

[Legacy data processing storage, processing in the middleware system part]

31 is a flowchart for explaining a legacy data processing and storage processing process in the middleware system in the embodiment of the clinical decision support method of the present invention shown in Figs. 21 and 22. Fig. 31, the CDSS generating unit of the middleware system unit transmits legacy data processing request data to the legacy data system unit (S1100); A step (S1101) of sending data of the middleware system unit to the studying unit when a data list / definition in which the data is required to be studied; (S1102) the data is transferred from the study to the hospital system interface unit in the case of a necessary legacy data definition; (S 1103) of transmitting data request data to the hospital system of the legacy data system unit when the legacy system interworking unit requests the legacy system; Transmitting (S1104) legacy data from the hospital system to the hospital system linkage; (S 1105) of transmitting the data processing request data to the hospital system interworking unit; (S1106) processing the data to transmit the necessary data to the integrated management system unit; (S1107) the integrated management system transmitting the processed data of the data of the middleware system unit; (S1108) of sending the processed data storage command to the CDSS DB interlocking unit; And transmitting the processed data storage request data to the CDSS DB unit of the CDSS management system unit (S1109).

[Processing data CDSS DB part storage, processing in CDSS DB part]

FIG. 32 is a flowchart illustrating a process of storing the processed data of the CDSS DB unit in the step of transmitting and storing the processed data to the CDSS DB unit of the CDSS management unit in the embodiment of the clinical decision support method of the present invention shown in FIGS. 21 and 22 Fig. 32, the middleware interworking unit of the CDSS DB unit included in the CDSS management system unit receives the processed data storage request transmitted from the middleware system unit and transmits a DW (Data Warehouse) storing request of the processed data to the CDSS DW unit Transmitting data (S1200); Transmitting the DW storage request data of the processed data to the personal data management unit (S1201); The personal data management unit transmitting personal management request data to the cluster data management unit (S1202); A step S1203 of transmitting the personalized data and the cluster analysis data to the personalized data management unit and the cluster analysis data management unit of the data management system unit, respectively, by the cluster data management unit; The personalized data management unit and the cluster analysis data management unit transmit the required data mart storage request and required cluster analysis data mart storage request data to the CDSS mart management unit of the CDSS DB unit (S1204).

[Requests and delivery of necessary charts and components, processing in the chart type manager of the CDSS management system section]

FIG. 33 is a flow chart for explaining a processing procedure in the chart type management section of the CDSS management system section for a necessary chart of the middleware system section and a component request in the embodiment of the clinical decision support method of the present invention shown in FIG. 21 and FIG. to be. 33, the CDSS DB interlocking unit of the chart type management unit included in the CDSS management system unit receives the necessary chart and the component element request data transmitted from the middleware system, and sends the interval chart and the component request Transmitting data (S1300); (S1301) of transmitting the interval-based VIP analysis chart and the component element request data to the VIP analysis unit by the interval management unit; (S1302) transmitting the VIP analysis based operation rate chart and component request data to the VIP analysis unit operation rate management unit; The operation rate management unit transmits the operation rate based trust / support chart and the component request data to the trust / support management unit (S1303); (S 1304) the trust / support management unit transmits each chart and component request data to the CDSS DB interworking unit; (S1305) transmitting the lead-in rate chart and the element request data to the lead-in rate management unit by the CDSS DB interlocking unit; (S1306) transmitting the pull-in rate-based bounce rate chart and the element request data to the bounce rate management unit; The abandonment rate management unit transmits an attraction rate based trust / support chart and component request data to the conversion rate management unit (S1307); (S1308) transmitting the chart and component request data to the CDSS DB linking unit; (S1309) transmitting the patient survival rate chart and the component request data to the CDSS DB interlocking unit to the patient survival rate management unit; The patient survival rate management unit transmits the patient survival rate reservation default rate chart and the component request data to the reservation default rate management unit (S1310); (S1311) of transmitting the chart and component request data to the CDSS DB linking unit by the reservation default rate managing unit; Transmitting the patient satisfaction chart and the component request data to the patient satisfaction management unit (S1312); (S1313) the patient satisfaction management unit transmits the treatment fee chart and the component request data to the patient fee management unit; (S1314) transmitting the chart and component request data to the CDSS DB linkage unit; And transmitting the necessary charts and elements to the middleware system unit through the CDSS DB interworking unit (S1315).

In the above embodiment, the necessary charts and constituent elements are transmitted to the middleware system unit through the interval management unit, the VIP analysis unit, and the patient management unit. Select one or more charts requested depending on the type and condition of the patient, without having to select all the charts. In the embodiment, the trust / support management unit transmits each chart and the element request data to the CDSS DB interworking unit (S1304). The CDSS DB interfacing unit transmits the fetch rate chart and the element request data to the fetch rate management unit (S1305), the conversion rate management unit transmits each chart and component request data to the CDSS DB linkage unit (S1308), and the CDSS DB linkage unit transmits the patient survival rate chart and the component request data to the patient survival rate management unit A step S1311 of transmitting the respective chart and component request data to the CDSS DB linking unit by the reservation default rate managing unit and transmitting the patient satisfaction chart and the component request data to the patient satisfaction managing unit by the CDSS DB linking unit Although it has been described that step S1312 is included, in another embodiment, The necessary charts and constituent elements are continuously requested, and the necessary charts and constituent elements are provided to the middleware system unit by the patient's medical fee management unit.

[Processing of legacy data, provision of legacy data system data, processing in the study]

FIG. 34 is a flowchart for explaining a process of processing data of a legacy data system unit in legacy data processing requested by a middleware system unit in the embodiment of the clinical decision support method of the present invention shown in FIGS. 21 and 22; to be. (S1400), as shown in FIG. 34, receiving the legacy data processing request data transmitted from the middleware system unit of the middleware interworking unit of the study, and transmitting the legacy data processing request data to the analysis modeling management unit ; The analysis modeling management unit generates a necessary data list / definition and transmits the data list / definition to the middleware interworking unit (S1401); (S1402) transmitting the required legacy data list / definition to the middleware system; (S 1403) of transmitting the necessary data to the middleware interworking unit of the middleware system unit; (S 1404) of transmitting analysis modeling call data to the analysis modeling management unit by the middleware interworking unit; The analysis modeling management unit transmitting statistical analysis request data to the statistical analysis unit (S1405); Transmitting data mining analysis request data to the statistical analysis unit data mining analysis unit (S1406); (S1407) the data mining analysis unit generates and transmits processing data to the middleware interworking unit; And transmitting the processed data to the middleware system unit (S 1408).

The above embodiment relates to a process in which the data constructed by analyzing and mining various data such as the patient visit frequency, medical expenses, and the disease name is related to the processing in the study, Analytical modeling of required data After analyzing modeling process in management section, statistical analysis is requested to statistical analysis section. The statistical analysis department performs the statistical analysis necessary for processing the data and sends the statistical analysis data to the data mining analysis section to request data processing. The data mining analysis unit can perform data mining based on the necessary statistical analysis data, generate the processed data, and transmit the processed data to the middleware system unit through the middleware interworking unit.

[Requesting and providing data at the time of required legacy, processing in the legacy data system department hospital system]

FIG. 35 is a flowchart for explaining a process of processing the required legacy data requested by the middleware system unit of FIGS. 21 and 22 in the hospital system of the legacy data system unit. 35, the middleware interworking part of the hospital system included in the legacy data system part receives the required legacy data request data transmitted from the middleware system part and transmits EMR data request data to the EMR management part (S1500); The EMR management unit transmits the LIS data request data to the LIS management unit (S1501); (S1502) the LIS management unit transmits the OCS data request data to the OCS management unit; The OCS management unit transmitting the request data of the PACS data to the PACS management unit (S1503); Transmitting the request data of MIS data to the MIS management unit by the PACS management unit (S1504); A step (S 1505) of the MIS management unit transmitting request data of HIS data to the HIS management unit; The HIS management unit transmitting the request data of the ERP data to the ERP management unit (S1506); (S1507) the ERP management unit transmits request data of other data to the hospital system management unit; (S1508) the hospital system management unit transmits necessary legacy data to the middleware interworking unit; And transmitting the required legacy data to the middleware system through the middleware interlocking unit (S1509).

The above embodiment is a series of processes for bringing an existing hospital system (EMR, OCS, PACS, HIS, etc.) into a DB for use in the CDSS of the present invention. Since systems used for each hospital are different from each other, The legacy data corresponding to each stage of the hospital system is transferred to the middleware system unit through the middleware interworking unit according to the present invention.

[Personal processing data mart storage, processing in personal processing data management part of data management system part]

FIG. 36 is a flowchart illustrating a process in the personal processing data management unit of the data management system unit of the personal demand data mart storage requested in the CDSS DB unit of the CDSS management system unit in the embodiment of the clinical decision support system of the present invention shown in FIG. 32 Fig. 36, the CDSS DB linked portion of the personalized data management unit included in the data management system unit receives the personal processed data mart store request data transmitted from the CDSS DB unit of the CDSS management system unit, Transmitting data storage request data and mart archive data (S1600); (S1601) transmitting the condition variable (Chance Variable) request data and the mart archive data to the patient condition variable management unit; (S1602), the condition variable management unit transmits decision data (Decision Variable) request data and mart archive data to the decision variable management unit; (S1603) transmitting the behavior variable storing request data and the mart storage data to the behavior variable manager; (S1604) the behavior variable management unit transmits patient data storage request data and mart archive data to the patient data management unit; And the patient data management unit transmits and stores the personal needs data to the CDSS DB unit (S1605).

The above embodiment is a method for extracting, storing, and managing various data and parameters for managing individual patient data, comprising the steps of: storing personalized data received from the CDSS DB linking unit, Lt; / RTI &gt; The variables such as chance variable, patient's decision variable, and patient's behavior variable such as age and gender of the patient were stored in the corresponding management department and the data of the mart archive was transmitted to the CDSS DB And stored in the subsidiary mart management unit.

[Cluster Analysis Data Mart Storage, Processing in Data Management System Cluster Analysis Data Management Section]

FIG. 37 is a flowchart illustrating a procedure of a cluster analysis data management unit of the data management system unit of the cluster analysis data mart storage requested by the CDSS DB unit of the CDSS management system unit in the embodiment of the clinical decision support system of the present invention of FIG. Fig. 36, the CDSS DB interlocking unit of the cluster analysis data management unit included in the data management system unit receives the cluster analysis data mart store request data transmitted from the CDSS DB unit of the CDSS management system unit, Transmitting data store request data and mart archive data (S1700); (S1701) transmitting the cluster reference-related data storage request data and the mart storage data to the cluster reference management unit; (S1702) the cluster reference management unit transmits the cluster property-related data storage request data and the mart archive data to the cluster property management unit; And storing the necessary data in the CDSS DB unit by the cluster property management unit (S1703).

In the above example, the recurrence interval is based on the recurrence interval (the quadrants in the order of shortest interval, for example, the first group = the upper 25% in the ascending interval interval, the second = 25% in the quartile ascending interval) And storing and managing various data and parameters in order to manage data related to the patient cluster divided by the CDSS DB. The method includes storing the cluster data received from the CDSS DB linking unit in the period management unit, Mart store data is transferred to the cluster management management department, and information on the patient cluster standard is stored and mart archive data is transmitted. The characteristic data of each cluster is stored in the cluster characteristics management section, and the mart storage data is transmitted. Since each cluster and cluster data are used as comparative analysis data, it is a method of requesting the cluster characteristic management section to store the cluster characteristics and store the mart archive data.

[Cluster analysis data storage, management by cluster characteristics manager]

FIG. 38 is a flowchart for explaining a process of the cluster characteristic management unit processing the cluster characteristic data mart storage requested by the cluster analysis data management unit of the data providing system unit in the embodiment of the clinical decision support method of the present invention shown in FIG. 37, the cluster analysis data interworking unit of the data management system unit receives the cluster characteristic storage and the mart archive data storage request transmitted from the CDSS DB unit of the CDSS management system unit and transmits the equipment to the dynamic characteristics management unit (S1800 )Wow; A step (S1801) of the equipment to transmit the C (Chance) -B (Behavior) -D (Decision) modeling storage request and the mart archive data to the CBD modeling management unit; A step (S1802) of the CBD modeling management unit transmitting a cluster visiting property storage request and a mart archive data to a cluster visiting characteristic management unit; And the cluster visiting characteristic management unit transmits the cluster characteristic data mart storing request data to the cluster analysis data managing unit (S1803).

In the embodiment of FIG. 37, in response to a request to store cluster characteristics and mart archive data transferred to the cluster analysis data linkage unit, the embodiment stores and manages information related to equipment operation characteristics, CBD modeling, and cluster visiting characteristics related to the cluster As a method, the request received from the cluster analysis data linking unit is transmitted to the dynamic characteristics management unit so that the data on the equipment operation characteristics for each group is stored, and the storage data of the mart is transmitted. In order to analyze CBD visit characteristics, CBD modeling management department stores data related to CBD by group and transmits mart archive data, stores cluster visit characteristic data in cluster visit characteristic management section, and transmits mart archive data. Finally, And the characteristic data mart storage is requested and transmitted to the cluster analysis management unit.

[Providing necessary chart components from requesting disease code, handling CDSS DB part]

FIG. 39 is a flowchart for explaining procedures from requesting a disease code of a middleware system part to providing a necessary chart and components in the embodiment of the clinical decision support method of the present invention shown in FIG. 21 or FIG. (S1900) of receiving the disease code request data transmitted from the middleware system unit of the CDSS DB unit of the CDSS management system unit; The CDSS DB unit transmitting the disease code to the middleware system unit (S1901); (S1902) the CDSS DB receiving the processed data storage request data transmitted from the middleware system unit; A step (S 1903) of transmitting the processed data to the personalized data management unit of the CDSS DB attached data management system unit; A step (S 1904) of the personal processing data management unit transmitting mart storage request data of required personal processing data to the CDSS DB unit; Transmitting the required personal processing data to the cluster analysis data management unit (S1905); (S1906) the cluster analysis data management unit transmits the required personal processing data to the CDSS DB unit as the required cluster analysis data by transmitting the storage request data to the Mart; (S1907) the CDSS DB receiving the patient basic information and the medical care information request data from the middleware system unit; The CDSS DB transmits the patient progress information request data to the process management unit of the CDSS management system unit (S1908); (S1909) of confirming and transmitting the patient progress information to the CDSS DB unit; (S1910) the CDSS DB unit transmits requested patient information to the middleware system unit; (S1911) of transmitting the necessary chart and element request data to the CDSS DB unit by the middleware system unit; (S1912) transmitting the necessary chart and element request data to the chart type management unit of the CDSS DB-attached CDSS management system unit; (S1913) the chart type management unit transmits the necessary chart and the constituent elements to the CDSS DB unit; And transmitting the necessary charts and components to the CDSS DB unit (S1914).

* 200 [Requesting and providing patient progress information, processing in the process management section of the CDSS management system]

40 is a flowchart for explaining a processing procedure in the process management unit according to the patient basic information and the medical care information request by the CDSS management system unit of the middleware system unit in the embodiment of the clinical decision support method of the present invention shown in FIG. 40, the CDSS DB interlocking unit of the process management unit included in the CDSS management system unit receives the patient progress information request data transmitted from the middleware system unit and transmits the patient progress information confirmation request data to the visit process management unit (S2000); A step (S2001) of the visit process management unit transmitting the patient progress item information confirmation request data to the registration process management unit; (S2002) of transmitting the patient progress item information confirmation request data to the diagnosis process management unit by the registration process management unit; A step (S2003) of transmitting the patient progress item information confirmation request data to the diagnosis process management section by the diagnosis process management section; (S2004) of sending the patient progress information confirmation request data to the maintenance process management unit by the diagnosis process management unit; (S2005) of transmitting the patient progress item information confirmation request data to the payment process management unit; (S2006) of transmitting the patient progress information confirmation request data to the post-management process management unit by the payment process management unit; (S2007) of transmitting the patient progress information confirmation request data to the RTC process management unit by the post management process management unit; And the RTC registration process management unit transmits the patient progress information to the middleware system unit (S2008).

In the above embodiment, in step S2001, the visiting process management unit informs the registration process manager of all information about the patient's hospital approach, how it came to the hospital (self, public transportation, walking, etc.) (Internet search, advertisement, word of mouth), and patient progress information confirmation request data.

In step S2002, the registration process management unit may transmit data including information such as hospital registration information, information on whether the patient is a reservation patient or a non-reservation patient, registration waiting time, and patient progress information confirmation request data to the diagnosis process management unit have.

In the step S2003, the diagnosis process management unit transmits all the information about the diagnosis and the medical care performed by the medical actor, the data including the medical care actions such as inspection / operation / treatment according to diagnosis, the order related information, To the management unit.

In step S2004, the inspection process management unit transmits data including all information related to various tests such as MRI, CT, X-ray, physical therapy, and the patient progress information confirmation request data to the maintenance process manager Lt; / RTI &gt;

In step S2005, the maintenance process management unit may transmit data including information such as all information on the inpatient management and maintenance of the patient, the date of discharge and discharge, and the patient progress information confirmation request data to the payment process management unit.

In step S2006, data including information such as all information related to the payment of the patients who have completed the medical care service, medical care cost settlement, daily insurance premium, and the patient progress information confirmation request data may be transmitted to the post management process management unit.

In step S2007, the post-management process management unit may transmit to the RTC process management unit all the information on the patient management, the health status through the text message or telephone, the provision of the inspection information, and the patient progress information confirmation request data have.

In step S2008, the RTC process management unit can transmit data including information related to the patient's re-visit (re-admission), re-visited patient record management, disease management frequently re-admitted, and patient progress information data to the middleware system have.

The embodiments of the present invention described above are only a few of various embodiments of the present invention. The present invention supports the medical treatment process of the hospital and the like and the supporting process therefor efficiently, supports effective decision-making in the medical care decision-making stage of the clinic through the tablet PC, (MIS), PACS, OCS, and EMR are integrated through the middleware system, and each patient's treatment pattern is analyzed. The CP (Clinical Pathway), efficient process flow, and similar patterns are grouped by similar groups, and information about the cluster, such as behavior patterns according to the characteristics of patients, is stored, and if necessary, The information is processed through the middleware system and the patient and its The hospital system using the middleware system which enables efficient treatment and increase the satisfaction of the patient by shortening the treatment period, and the hospital system that uses the middleware system Various embodiments included in the technical idea of integrated management are included in the protection scope of the present invention.

1000: Integrated Management System Department
2000: Middleware System Department
3000: Data providing system unit
4000: CDSS Management System Department
5000: Legacy Data System Department
6000: Data management system part

Claims (6)

Transmitting disease code mapping request data input to an application of a user apparatus to a web server; Transmitting the disease code mapping request data received from the user device to the DB server; Transmitting the disease code mapping table / rule to the web server according to the disease code mapping request; Transmitting the disease code mapping to the user device based on a disease code mapping table / rule transmitted from the DB server by the web server; Sending patient information and chart / CP transmission request data to the web server in an application of the user device; Transmitting, by the web server, the patient information and chart / CP transmission request data to the DB server; Transmitting the patient information, chart / CP, to the web server; The web server sending the patient information, chart / CP, to the user device;
The disease code mapping is a direct mapping of the disease name and the disease code (ICD, KCD, etc.) currently used in the medical institution,
The patient information and the chart information / CP are respectively analyzed for the treatment patterns of the patients, and the CPs formed by dividing the groups into groups are derived from the clusters through the clusters, and the information about the clusters And is processed by the middleware system into information corresponding to the patient and the community to which the patient belongs,
Wherein the chart / CP includes information on the patient's management interval, the number of visits, and the weight of the patient to which the VIP is weighted. Transmitting disease code mapping request data from an application of the user apparatus to the web application unit; Transmitting the disease code mapping request data requested by the user apparatus to the middleware system unit of the web application unit; Transmitting the disease code mapping table request data to the integrated management system unit by the middleware system unit; Transmitting the disease code mapping table / rule requested by the integrated management system unit to the middleware system unit; Transmitting the disease code mapping to the web application unit by the middleware system unit; The web application unit sending a disease code mapping to an application of the user equipment; Transmitting the patient information request data to the web application unit of the data providing system unit in the application; Transmitting the patient information request data transmitted from the user apparatus to the middleware system unit by the web application unit; Transmitting the basic information of the patient and the medical care information request data to the CDSS DB unit of the CDSS management system unit of the middleware system unit; Transmitting the patient information from the CDSS DB to the middleware system; Transmitting the patient information to the web application unit by the middleware system unit; The web application unit sending patient information to an application of the user device; Transmitting chart / CP request data from the application of the user apparatus to the web application unit of the data providing system unit; Transmitting the chart / CP setting request data to the CDSS request unit of the data providing system unit by the web application unit; Transmitting the chart / CP setting confirmation data to the web application unit by the CDSS request unit; Transmitting the chart / CP request data to the middleware system unit by the web application unit; Transmitting the required chart / CP element request data to the CDSS DB unit of the CDSS management system unit; Transmitting the necessary chart / CP component to the CDSS DB unit in the middleware system unit; Transmitting the chart / CP to the web application unit by the middleware system unit; The web application unit outputting a chart / CP to an application of the user apparatus;
The disease code mapping is a direct mapping of the disease name and the disease code (ICD, KCD, etc.) currently used in the medical institution,
The patient information and the chart / CP analyze the patients' treatment patterns and derive groups of similar CPs and patterns, which are formed between the groups, through groups, and include information on the community such as behavior patterns according to the characteristics of the patients And the information is processed by the middleware system unit into information corresponding to the patient and the community to which the patient belongs,
Wherein the chart / CP includes information on the patient's management interval, the number of visits, and the weight of the patient to which the VIP is weighted. The method of claim 2,
The step of transmitting the disease code mapping request data requested by the user device to the middleware system part of the web application unit comprises:
Receiving a disease code mapping request data transmitted from the user apparatus and receiving the disease code mapping request data from an application interface unit of the web application unit; Transmitting the disease code mapping request data to the middleware interworking unit of the application interface unit; Wherein the middleware interworking unit transmits the disease code mapping request data to the middleware system unit. The method of claim 2,
The step of transmitting the disease code mapping table / rule from the integrated management system unit to the middleware system unit comprises:
Transmitting code mapping table request data to a code mapping processor of a middleware interlocking unit of the integrated management system unit requested to transmit a disease code mapping table from the middleware system unit; At least one code management unit associated with the disease name used by the code mapping unit receives the corresponding code table, maps the code table, and transmits the disease code mapping table / rule to the middleware coordination unit; Wherein the middleware interworking unit transmits the disease code mapping table / rule to the middleware system unit. The method according to any one of claims 1 to 4,
Wherein the step of causing the web application unit to run an application on the user device comprises:
Receiving application driving request data transmitted from a user apparatus by a device interlocking unit of the web application unit; Transmitting the application authorization confirmation request data to the application interface unit with respect to the application activation request received by the device interaction unit; Transmitting application authorization data from the application interface unit to a rights management unit; And the rights management unit is operable to cause the application to run on the basis of the received application authorization data. A computer-readable recording medium containing a computer program for performing the method of claim 1.

Images