KR20230105897A - System and method for actively collecting patient's medical data - Google Patents

Abstract

The present invention relates to a system and method for actively collecting medical data of a patient, and relates to a collection server for collecting and storing data related to treatment of a patient (hereinafter referred to as 'medical data') obtained from a medical device, and a patient using the medical device. A process management server that defines a plurality of standardized workflows for treating and, when one of the plurality of workflows is selected by a medical staff terminal, provides processes of the selected workflow to medical staff terminals and patient terminals, and A patient terminal generating and transmitting a patient active event to the process management module when patient condition information according to patient judgment is received while treating a patient with a medical device according to processes defined in the workflow; and a process management server. receives the patient's active event, receives medical data stored in the collection server through the data collection module installed in the collection server.

Description

System and method for actively collecting patient's medical data}

The present invention relates to a patient's medical data active collection system and method for actively collecting medical data related to the patient's vital signs at the patient's request.

As the method of treating patients' diseases using digital and network communication expands, interest in and technology for various medical devices such as pacemakers, ventilators, kidney dialysis machines, X-ray equipment, cardiac CT equipment, and gamma knives are also developing in parallel. .

In order to grasp the patient's condition while the patient is receiving treatment or examination through these medical devices, the medical staff must constantly look around the patient.

However, it is not realistically possible for the medical staff to constantly look after the patient by the side of the patient due to difficulties in manpower supply and long time required. Therefore, it is necessary to propose a technology for automatically classifying, extracting, and providing vital sign data generated from a patient or data generated from a medical device in preparation for the absence of a medical staff.

Domestic Patent Publication No. 10-2015-0110924

In order to solve the above problems, the technical problem to be achieved by the present invention is to provide a patient's medical data active collection system and method capable of actively collecting, classifying, and extracting medical data related to the patient's vital signs at the request of the patient. is to present

The problems of the present invention are not limited to those mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the description below.

As a means for solving the above-described technical problem, according to an embodiment of the present invention, a patient's medical data active collection system collects data related to patient's treatment (hereinafter referred to as 'medical data') obtained from a medical device. a collection server that collects and stores; A plurality of standardized workflows for treating patients with the medical device are defined, and when one of the plurality of workflows is selected by a medical staff terminal, processes of the selected workflow are provided to the medical staff terminal and the patient terminal process management server; and a patient terminal generating and transmitting a patient active event to the process management module when patient condition information according to patient judgment is received while treating the patient with the medical device according to the processes defined in the selected workflow. , When the patient active event is received, the process management server receives medical data stored in the collection server through a data collection module installed in the collection server.

The process management server may include a process management module generating anchor data defining a format of medical data to be collected from the collection server when receiving the patient active event, and transmitting the generated anchor data to the data collection module; The data collection module collects medical data from the collection server based on a format defined in the received anchor data and transmits the collected medical data to the process management server.

The process management server maps and stores medical data received from the data collection module to identification information of the patient's active event, and transmits the data to the medical staff terminal.

The process management server creates a plurality of processes sequentially defining treatment tasks to be processed, arranges and groups the created multiple processes according to the order of processing the tasks, and creates a single workflow. Creating a plurality of items defining detailed tasks for each, and automatically classifying and extracting medical data received from the medical device and the data collection module as data of the item defined in the identified process while the selected workflow is in progress process management module; and a DB for storing the workflow generated in the process management module in association with a plurality of processes and a plurality of items, and storing the automatically classified and extracted medical data as data of items defined in the corresponding process. .

On the other hand, in the method of actively collecting patient's medical data, (A) a process management server defines a plurality of standardized workflows for treating patients with medical devices, and one of the plurality of workflows is provided to a medical staff terminal. if selected, providing processes of the selected workflow to the medical staff terminal and the patient terminal; (B) collecting and storing, by a collection server, data related to the patient's treatment progress and the patient's vital signs (hereinafter referred to as 'medical data') obtained from the medical device; (C) While the patient terminal treats the patient with the medical device according to the processes defined in the workflow selected in step (A), when patient condition information according to the patient's judgment is received, a patient active event is generated and the process is performed. sending to the management module; and (D) receiving, by the process management server, medical data stored in the collection server through a data collection module installed in the collection server when the patient active event is received.

The step (D) may include: (D1) generating anchor data defining a format of medical data to be collected from the collection server when the patient active event is received by the process management server; (D2) transmitting, by the process management server, the generated anchor data to the data collection module; and (D3) the data collection module collecting medical data from the collection server based on the format defined in the anchor data received from step (D2) and then transmitting the collected medical data to the process management server.

The present invention combines IT technology and medical devices to actively collect vital sign data at the patient's request, that is, at the initiative of the patient, whereby the medical staff can grasp the patient's condition more accurately and quickly. .

The effects of the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

1 is a diagram showing a system for actively collecting medical data of a patient according to an embodiment of the present invention;
2 is a block diagram showing a process management server 400;
3 is a diagram for explaining an operation of creating a workflow by registering processes and items to be configured in the workflow by the process management module 462;
4 is a diagram for explaining an operation of assigning a patient terminal 200 to each medical device 100 by a process management module 462;
5 is a view for explaining an operation in which the process management module 462 automatically classifies and extracts medical data based on the process created in the workflow;
6 is an example of a UI screen 600 displayed on the terminal 200 of a patient undergoing renal dialysis;
7 is a view showing a system for actively collecting medical data of a dialysis patient according to an embodiment of the present invention;
8 is a flowchart schematically illustrating a method for actively collecting patient medical data according to an embodiment of the present invention;
9 is a flowchart showing step S810 of FIG. 8 in detail when the medical device 100 is the dialysis device 100', and
10 to 12 are flowcharts showing steps S830 to S890 of FIG. 8 in detail when the medical device is the dialysis machine 100'.

The above objects, other objects, features and advantages of the present invention will be easily understood through the following preferred embodiments in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments described herein and may be embodied in other forms.

In some cases, it is mentioned in advance that parts that are commonly known in describing the invention and are not greatly related to the invention are not described in order to prevent confusion for no particular reason in explaining the present invention.

Further, when a first component is referred to as being operated or executed on (ON) a second component, the first component is operated or executed in an environment in which the second component is operated or executed, or with the second component. It should be understood that it is operated or executed through direct or indirect interaction.

When a component, device, or system is referred to as comprising a component consisting of a program or software, even if not explicitly stated otherwise, the component, device, or system refers to hardware (necessary for the program or software to execute or operate). For example, memory, CPU, etc.) or other programs or software (eg, operating system or driver required to drive hardware) should be understood as including.

In addition, it should be understood that, unless otherwise specified, the component may be implemented in any form of software, hardware, or both software and hardware.

In addition, in this specification, terms such as 'unit', 'module', 'server', 'system', 'device' or 'terminal' refer to functional and structural aspects of hardware and software driven by the hardware or for driving the hardware. It may be intended to refer to a bond. The hardware may be a data processing device including a CPU or processor. Also, software driven by hardware may refer to a running process, an object, an executable file, a thread of execution, a program, and the like.

In addition, the terms may mean a predetermined code and a logical unit of hardware resources for executing the predetermined code, and do not necessarily mean physically connected codes or one type of hardware in the present invention. can be easily deduced to the average expert in the art.

Hereinafter, with reference to the accompanying drawings for the specific technical content to be carried out in the present invention will be described in detail.

Each component shown in the drawing indicates that it can be functionally and logically separated, and does not necessarily mean that each component is classified as a separate physical device or written as a separate code. An expert will be able to infer easily.

1 is a diagram illustrating a system for actively collecting medical data of a patient according to an embodiment of the present invention.

Referring to FIG. 1 , a patient medical data active collection system according to an embodiment of the present invention includes a medical device 100, a patient terminal 200, a medical staff terminal 300, a process management server 400, and a collection server ( 500) may be included.

The medical device 100 may be connected to a patient's body to perform treatment and obtain data (hereinafter referred to as 'medical data') related to the patient's treatment. Medical data may include biosignal data of a patient generated during treatment with the medical device 100 and additional information for treatment.

The patient terminal 200 is a terminal that is synchronized to communicate with the medical device 100 , the medical staff terminal 300 , or the process management server 400 and is used by a patient. The patient terminal 200 may include, for example, a wearable terminal worn by a user, a tablet, a smart phone, and the like.

The medical staff terminal 300 is a terminal used by medical staff and can select a workflow to be applied to a patient from a plurality of workflows by receiving an input from the medical staff. The medical staff terminal 300 may include, for example, a tablet, a smart phone, and a personal computer.

A workflow service program for a patient and a workflow service program for a medical staff may be installed and executed in the patient terminal 200 and the medical staff terminal 300, respectively. The workflow service program for patients/medical staff is a program for providing a service for treating patients by using the workflow provided by the process management server 400 .

The collection server 500 may periodically and automatically collect patient's medical data from the medical device 100 and store it in a built-in storage medium. The collection server 500 may be a server designed in advance to interwork with the medical device 100 . When the medical device 100 is a dialysis device, the collection server 500 may be a dialysis management system (TDMS, Therapy, Data, Management, System).

The memory (not shown) of the collection server 500 has a data collection module 510 that collects medical data stored in the collection server 500 according to a request of the process management server 400 and transmits the collected medical data to the process management server 400. installed, and may be executed by a processor (not shown).

When the data collection module 510 is executed in the collection server 500, the data collection module 510 may communicate with the process management server 400 through TCP/IP. When it is impossible to install the data collection module 510 in the collection server 500, the process management server 400 may directly access the collection server 500 and collect medical data.

The process management server 400 defines a plurality of standardized workflows for treating a patient with the medical device 100, and according to a workflow selected by the medical staff terminal 300 in consideration of the patient's condition among the plurality of workflows. When treatment progresses, medical data received from the data collection module 510 installed in the collection server 500 may be automatically extracted and classified according to a predefined process.

In addition, the process management server 400 maps the automatically extracted and classified medical data to corresponding items defined in the process, stores them in the DB 440, and sends data to at least one of the medical staff terminal 300 and the patient terminal 200. Can be provided optionally.

2 is a block diagram illustrating a process management server 400 .

Referring to FIG. 2 , a process management server 400 according to an embodiment of the present invention includes a communication unit 410, a user interface unit 420, a display unit 430, a DB 440, a memory 450, and a processor 460. ) may be included.

The communication unit 410 may support wired or wireless communication between the process management server 400 and the patient terminal 200 , the medical staff terminal 300 , the collection server 500 , or the data collection module 510 . The communication unit 410 is a wired communication circuit such as LAN (Local Area Network), WAN (Wide Area Network), Ethernet, and/or ISDN (Integrated Services Digital Network) and/or wireless Internet (eg, wi-fi) , short-distance communication (eg, Bluetooth, ZigBee, and infrared communication), and wireless communication circuits such as mobile communication.

The user interface unit 420 may generate data according to a user's manipulation. The user interface unit 420 may be implemented as an input device such as a keyboard, keypad, button, switch, touch pad, and/or touch screen.

The display unit 430 may display a screen according to manipulation of the user interface unit 420 .

The DB 440 stores a plurality of workflows generated by the process management module 462 and stores medical data received from the patient terminal 200, the medical staff terminal 300, or the collection server 500 in advance. It can be stored based on ERD (Entity Relationship Diagram).

Memory 450 may include volatile memory and/or non-volatile memory. The memory 450 may store commands or data related to components, one or more programs and/or software, an operating system, and the like in order to implement and/or provide operations and functions provided by the process management server 400. there is.

The program stored in the memory 450 creates a workflow based on the previously built ERD, and when treatment proceeds according to the created workflow, the patient terminal 200, the medical staff terminal 300 or the data collection module ( A process management module 462 for automatically extracting and classifying medical data received from 510) according to a predefined process may be included.

The processor 460 controls the overall operation of the process management server 400 by executing one or more programs stored in the memory 450 . For example, the processor 460 executes the process management module 462 according to a user request through the user interface unit 420 to generate a plurality of screens for creating a workflow, and stores the created workflow in a DB ( 440), and when actual treatment is performed according to the workflow, medical data received from the patient terminal 200, the medical staff terminal 300, or the data collection module 510 is automatically extracted according to a predefined process. And it can be classified and stored in the DB (440).

In detail, as shown in FIG. 3, the process management module 462 generates a plurality of processes sequentially defining treatment tasks to be processed, and arranges and groups the generated multiple processes according to the order of processing the tasks to form a single process. You can create a workflow and create a number of items defining detailed tasks for each process. The process management module 462 may match the created workflow with a plurality of processes and a plurality of items and store them in the DB 440 .

3 is a diagram for explaining an operation of creating a workflow by registering processes and items to be configured in the workflow by the process management module 462 .

Referring to FIG. 3, the workflow creation operations in the flow from the ERD perspective include registering services (①), registering modules (②), registering workflows (③), creating process templates to be configured in the workflow (④), and items for each process. Creation (⑤) and workflow definition (⑥) of the process can be included.

In detail, the process management module 462 registers a service using the service entity 31 (①). In the service entity 31, service-related information (Attribute) such as a service name (eg, hospital A), detailed description, and first registrant is registered.

Then, the process management module 462 registers the module using the module entity 32 (②). In the module entity 32, information related to the module, such as the module name (eg, dialysis module), whether the module is used, whether it is deleted, and the first registrant, is registered.

Thereafter, the process management module 462 registers basic information of the workflow to be created using the workflow entity 33 (③). The workflow entity 33 registers information related to the workflow, such as the name of the workflow to be created (eg, general dialysis or infection dialysis), whether the workflow is used, whether to delete it, and the first registrant.

Thereafter, the process management module 462 creates a process template to be configured in the workflow using the process entity 34 (④). In the process entity 34, information related to the process, such as a process name to be created (eg, P1) priming process, detailed description, whether or not there is a decision, whether it is used or not, whether it is deleted or not, is registered. Since multiple processes can be created in one workflow, multiple process templates can be created at this time.

Then, the process management module 462 creates an item defined for each process using the item entity 35, the item detail entity 36, and the process detail entity 37 (⑤). Items define detailed processes (or detailed tasks) to be performed for each process. The item entity 35 registers information related to the item, such as an item name, an ID of a process belonging to the item, an item type code, use or not, EMR (electronic medical record) linkage, linkage with the medical device 100, and the like.

Information such as an initial value of an item and a first registrant is registered in the item detail entity 36 . In the process detail entity 37, information registered in the item entity 35 and the item detail entity 36, such as a process detail ID, an item name defined in the process, an initial value of an item, whether or not EMR is interlocked, may be registered.

Then, the process management module 462 sequentially defines the flow of processes in the workflow using the workflow detail entity 38 (⑥). In the workflow detail entity 38 , information related to process flow, such as a process ID, before and after process IDs, start and end process IDs, and an effective range of collected data, may be registered.

Taking the above-described operations ① to ⑥ as an example, a workflow for general dialysis is created in the dialysis module of hospital A, the workflow consists of six processes, and different items are defined for each of the six processes.

In addition, as shown in FIG. 4 , the process management module 462 may set a plurality of treatment rooms, medical devices 100 and beds provided in the plurality of treatment rooms to register and interoperate in advance.

FIG. 4 is a diagram for explaining an operation of allocating the patient terminal 200 to each medical device 100 by the process management module 462 .

Referring to FIG. 4 , in the flow from the ERD perspective, the operation of allocating the patient terminal 200 for each medical device 100 is to register Unique Device Identification (UDI) information of the medical device 100 (①) and use it for the medical device 100. It can include medical device equipment registration (②), treatment room and bed information registration (③), and medical device allocation management information registration (④).

In detail, the process management module 462 registers UDI information of the medical device 100 using the UDI management entity 41 and the UDI detailed entity 42 (①).

Thereafter, the process management module 462 uses the medical device management entity 43 to provide detailed information (eg, equipment name, location in the treatment room, registration date, UDI ID, etc.) of the medical device 100 as an attribute. Register (②).

Thereafter, the process management module 462 registers bed and treatment room information such as a bed name, a treatment room name, and a first registrant using the BED management entity 44 and the treatment room management entity 45 (③).

Thereafter, the process management module 462 uses the medical device assignment management entity 46 to register the ID of the treatment room where the medical device 100 is located, the ID of the medical device, and the registration date (④).

In addition, after a plurality of workflows are created, as shown in FIG. 5, when a patient moves to a bed in a treatment room for treatment, the medical staff terminal 300 selects a workflow selected by a medical staff from among a plurality of pre-generated workflows. Processes may be received and set up from the process management server 400 , and an event may be generated and transmitted to the process management server 400 whenever processes of the selected workflow are sequentially changed according to a task processing sequence. The medical staff terminal 300 may generate an event when a corresponding process in progress is completed, and transmit medical data collected while the process is in progress to the process management server 400 .

The process management module 462 checks a currently ongoing process based on an event generated in the medical staff terminal 300, and while the identified process is in progress, the patient terminal 200, the medical staff terminal 300, or a data collection module ( 510) may be automatically classified and extracted as data corresponding to an item defined in the identified process.

In addition, the process management module 462, when an event occurs in the medical staff terminal, Based on the event, a currently ongoing process is identified, and when the identified process is set to interwork with the collection server 500, anchor data defining a format of medical data to be collected for each identified process is generated, The generated anchor data may be transmitted to the data collection module 510 .

The role of anchor data is to define the timing and cycle of data collection by the collection server 500, define the format of medical data to be collected for each process, collect medical data according to the defined format, and process management server 400 again. including sending to

The data collection module 510 may collect medical data from the collecting server 500 based on a format defined in the received anchor data and transmit the medical data to the process management server 400 . The process management module 462 automatically classifies and extracts the medical data received from the data collection module 510 as data of items defined in the process identified above, and stores the data in the DB 440 .

5 is a diagram for explaining an operation of automatically classifying and extracting medical data based on a process generated in a workflow by the process management module 462. Referring to FIG.

Referring to FIG. 5, in the ERD perspective flow, the automatic classification and extraction operation of medical data involves selecting a workflow to treat a patient in the medical staff terminal 300 (①), and medical data corresponding to an item defined in the priming process of the workflow. It may include collection (②), generation of patient active events according to patient judgment (③), and generation of anchor data selectively after the priming process (④).

In detail, when information registered in the workflow entity 33 is displayed on the medical staff terminal 300 and the medical staff selects a workflow to treat a patient by referring to the workflow entity 33 information, the process management module 462 ) stores the process information defined in the workflow detailed entity 38 of the selected workflow in the plan workspace entity 51 (①).

Thereafter, the process management module 462 performs the priming process when medical data (for example, an ID value of a line, filter, or needle to be used for treatment) defined in the initial process, the priming process, is received from the medical staff terminal 300 . Upon entry, the action workspace entity 52 and the action workspace detail entity 53 are used to determine the plan work ID, the currently ongoing priming process ID, the item type code defined in the currently ongoing priming process, and the item input value (i.e. , medical data corresponding to the item) is stored (②). The action workspace entity 52 is stored only when the priming process is initially entered, and medical data may be accumulated and stored in the action workspace detail entity 53 when the process proceeds thereafter. In this case, medical data may be accumulated and stored by adding one row in unit of item.

Thereafter, the process management module 462, when a patient active event occurs from the patient terminal 200 according to subjective judgment that the patient feels uncomfortable during treatment, 'user_event defined in the action workspace detailed entity 53 Change the value of 'occurrence_whether' to user event occurrence, use the event management entity 54 to store the patient active event occurrence date, originator, event source, event type, etc., and use the anchor data entity 55 Thus, anchor data may be generated by storing an event ID, an ID of the medical device 100 that is treating a patient, and the like. Further, when the patient's medical data is received from the data collection module 510 by the patient's active request, the process management module 462 may store the medical data using the treatment information interface entity 56 .

Thereafter, when an event indicating that the process has been changed to a treatment progress process or an end process occurs, the process management module 462 stores the date of occurrence of the event, the originator, the event source, the event type, etc. using the event management entity 54. , Anchor data may be generated by storing an event ID, an ID of the medical device 100, a data format to be collected, and the like using the anchor data entity 55 (④). Also, when the patient's medical data is received from the data collection module 510 , the process management module 462 may store the medical data using the treatment information interface entity 56 .

Referring back to FIGS. 1 and 2 , while a patient is being treated according to a workflow selected by a medical staff, the patient terminal 200, when a process requiring the patient's opinion collection among the processes generated in the workflow proceeds, the patient terminal 200 proceeds. A user interface (UI) screen for collecting opinions may be displayed, and patient opinions input through the displayed UI screen may be transmitted to the process management module 462 . That is, if an event is generated whenever a process is changed from the medical staff terminal 300, the process management module 462 may analyze the generated event and determine whether the process has been changed to a process requiring patient opinion collection. Also, the process management module 462 may guide the patient terminal 200 to display the UI screen 600 as shown in FIG. 6 or transmit the UI screen 600 .

6 is an exemplary diagram of a UI screen 600 displayed on the terminal 200 of a patient undergoing renal dialysis.

Referring to FIG. 6 , the UI screen 600 may include a patient information area 610, a process area 620, a workflow area 630, an item area 640, and a patient determination menu 650.

The patient information area 610 displays the patient's registration number, patient name, age, gender, dialysis date, and the like.

In the process area 620, processes generated in the selected workflow are sequentially activated. Completed processes, ongoing processes, and ongoing processes can be distinguished by color.

In the workflow area 630, the name of the workflow being applied to the patient is displayed.

In the item area 640, items defined in the currently ongoing process and each item are displayed. Medical data displayed in the item area 640 may be medical data received through the data collection module 510 and the process management server 400 when requested to the data collection module 510 using anchor data.

The patient status check in the item area 640 is a menu for collecting patient opinions. For example, a survey related to dialysis treatment is provided to the patient, and when the survey is completed, Yes is checked. The process management module 462 automatically classifies and extracts patient opinions (eg, surveys) received from the patient terminal 200 as data of items defined in the process for collecting patient opinions, and stores them in the DB 440. do.

The patient determination menu 650 is a menu for converging patient condition information in real time, and can be directly selected by the patient when the patient feels uncomfortable during dialysis. When the patient determination menu 650 such as 'Do you feel uncomfortable?' is selected, the patient terminal 200 generates a patient active event and transmits it to the process management server 400 .

The patient active event is an event meaning that the patient voluntarily and subjectively submits patient condition information, and is an event that allows the process management server 400 to actively collect the patient's vital sign data.

When a patient active event is received, the process management module 462 determines that the patient has an abnormality, generates anchor data, and transmits it to the data collection module 510 . Anchor data is data that requests the collection of medical data (eg, blood pressure, body temperature, heart rate, etc.) related to the patient's vital signs, and may include identification information of a currently ongoing process. When medical data related to the patient's vital signs is received from the data collection module 510 together with identification information of the currently ongoing process, the process management module 462 converts the received medical data to an item corresponding to an item defined in the currently ongoing process. It can be classified as data and stored in the DB 440 . The process management module 462 may transmit medical data related to the received vital signs to the medical staff terminal 300 so that the medical staff can check them.

7 is a diagram illustrating a system for actively collecting medical data of a dialysis patient according to an embodiment of the present invention.

Referring to FIG. 7 , a system for actively collecting medical data of a dialysis patient according to an embodiment of the present invention includes a dialysis machine 100', a patient terminal 200', a medical staff terminal 300', a dialysis management system (TDMS, 400') and a process management server 400'. The dialysis machine 100', patient terminal 200', medical staff terminal 300', dialysis management system (TDMS, 400'), and process management server 400' are medical devices described with reference to FIGS. 1 to 6 100, the patient terminal 200, the medical staff terminal 300, the collection server 500, and the process management server 400 are the same as or similar to each other, so detailed descriptions are omitted.

The dialysis machine 100' may perform renal dialysis of the patient and acquire dialysis medical data including biosignal data of the patient generated during dialysis and treatment progress rate information.

The patient terminal 200' is a patient terminal capable of communicating with the dialysis machine 100', the medical staff terminal 300', or the process management server 400'. The patient terminal 200' gathers patient opinions such as surveys and patient condition information according to the patient's active judgment, provides them to the process management server 400', and displays ongoing workflows and processes.

The medical staff terminal 300' is a terminal used by medical staff and selects a workflow to be applied to a patient from among a plurality of workflows.

The TDMS 500' may periodically automatically collect and store patient's medical data from the dialysis machine 100'. A data collection module 510' that collects medical data stored in the TDMS 500' and transmits it to the process management server 400' according to the request of the process management server 400' is installed and executed in the TDMS 500'. can

The process management server 400' defines a number of standardized workflows for treating patients with the dialysis machine 100', and a workflow selected from the medical staff terminal 300' in consideration of the patient's condition among the plurality of workflows. When treatment progresses according to the flow, the dialysis medical data received from the data collection module 510' may be automatically extracted and classified according to a predefined process.

In addition, the process management server 400' maps automatically extracted and classified medical data to corresponding items defined in the process, stores them in a DB, and sends data to at least one of the medical staff terminal 300' and the patient terminal 200'. Can be provided optionally.

In addition, when renal dialysis of a patient is performed using the dialysis machine 100', the process management server 400' may create a general dialysis workflow or infection dialysis workflow based on the ERD as shown in FIGS. 3 to 5. At this time, one workflow can have 5 processes as shown in [Table 1].

Table 1 shows an example of a typical dialysis workflow.

workflow name turn process name detailed description general dialysis 1st process (P1) Priming Priming process 2nd process (P2) Patient Identification process of identifying patients 3rd process (P3) Start dialysis The process of starting dialysis 4th process (P4) Dialysis progress Dialysis process 5th process (P5) End of dialysis Dialysis End Process

[Table 2] shows examples of items defined in the processes of [Table 1].

process name defined in the process
item process name defined in the process
item (P1) Priming Dialysis device information (P3) Start dialysis prescription Medical Consumables (Filter) weight before dialysis Medical Consumables (Line) Dialysis progress rate Medical consumables (needle-needle) (P4) Dialysis progress Questionnaires required by patients (input data) (P2) Patient Identification patient name UF Registration Number Blood pressure gender, age AP/VP dialysis date BST (P5) End of dialysis weight after dialysis Blood vessel condition check

Referring to [Table 2], when the general dialysis workflow is selected, the first to fifth processes must be sequentially performed, and medical data items to be collected for each process are defined as items.

The process management server 400' collects, automatically classifies and extracts medical data of items defined for each process using a barcode reader or data collection module 510' provided in the medical staff terminal 300', and optionally, patients It can be transmitted to the terminal 200' or the medical staff terminal 300'. 8 is a flowchart schematically illustrating a method for actively collecting medical data of a patient according to an embodiment of the present invention.

Referring to FIG. 8 , when a workflow to be applied to a patient is selected in the medical staff terminal 300', a plurality of process information generated in the workflow is set up in the medical staff terminal 300' (S810).

The medical staff checks the information of the dialysis machine 100' to be used by the patient, and synchronizes the dialysis machine 100' with the patient terminal 200' (S820).

When treatment proceeds according to the processes set in the workflow selected in step S810, the process management server 400' receives medical data from the patient terminal 200', the medical staff terminal 300', or the data collection module 510'. are automatically extracted and classified according to the items defined in each process (S830).

The process management server 400' stores the medical data classified and extracted in step S830 in the item of the corresponding process, transmits the medical data to the patient terminal 200' or medical staff terminal 300', and displays the medical data (S840). ).

The patient terminal 200' or medical staff terminal 300' matches and displays the medical data received from the process management server 400' as medical data of an item defined in the corresponding process (S850).

If a patient active event occurs in the patient terminal 200' while the workflow is in progress (S860-Yes), the process management server 400' transmits anchor data to the data collection module 510' to determine the patient's vital signs. Data is requested, the patient's vital sign data is received and stored from the data collection module 510', and the received patient's vital sign data is transmitted to the medical staff terminal 300' (S870). Accordingly, the medical staff can determine the patient's condition by analyzing the vital sign data collected by the patient's active request displayed on the medical staff terminal 300'.

When all processes of the selected workflow are terminated (S880-Yes), the medical staff terminal 300' and the process management server 400' terminate the workflow (S890).

On the other hand, if there are still processes to proceed in step S880 (S880-No), step S830 is entered and the remaining processes are performed.

9 is a flowchart showing step S810 of FIG. 8 in detail when the dialysis machine 100' is the dialysis machine 100'.

Referring to FIG. 9, when a general dialysis workflow to be applied to a dialysis patient is selected in the medical staff terminal 300' (S911), the medical staff terminal 300' transmits the selected workflow information to the process management server 400'. Do (S912).

The process management server 400' transmits detailed information including a plurality of processes generated in the workflow retrieved from the DB based on the received workflow information to the medical staff terminal 300' and the patient terminal 200' ( S913, S914, S915).

The medical staff terminal 300' and the patient terminal 200' set up the received process information of the workflow (S916 and S917).

10 to 12 are flowcharts showing steps S830 to S890 of FIG. 8 in detail when the medical device is the dialysis machine 100'.

Referring to FIG. 10 , when information on the dialysis machine 100' to be used by the patient is confirmed by the medical staff in the medical staff terminal 300' and the dialysis machine 100' and the patient terminal 200' are synchronized (S1005) , The medical staff terminal 300' generates an event notifying that the priming process P1 starts and transmits it to the process management server 400' (S1010).

The process management server 400' recognizes that P1 is started (S1015), the medical staff terminal 300' proceeds with P1, which is the first process of the selected workflow, and generates an event when P1 is completed (S1020). In step S1020, when P1 proceeds, the item defined in P1 is displayed on the medical staff terminal 300', and when all medical data (eg, consumable information) corresponding to the item of P1 is input and displayed, the process proceeds to the next step. Triggers an event notifying the change. Consumables information may be input and displayed by, for example, a medical staff reading dialysis machine 100' information and medical consumables (filter, line, needle, etc.) information through a UDI reader.

The medical staff terminal 300' transmits an event notifying the change to the next process and the medical data collected in step S1020 to the process management server 400' (S1025).

The process management server 400' automatically classifies and extracts the received consumable information as medical data of the item defined in P1, and stores it in the DB (S1030).

In addition, when it is changed to the patient identification process (P2) and proceeds, the medical staff terminal 300' displays a screen showing four items defined in P2, and medical data (ie, patient information) corresponding to the four items is displayed. If input, an event notifying that a change to the next step is generated (S1035). In step S1035, when the medical staff receives the patient information by reading the patient information with the barcode reader mounted on the medical staff terminal 300', the medical staff terminal 300' maps the read patient information to an item defined in the patient identification process. display

The medical staff terminal 300' transmits the event notifying the change to the next process generated in step S1035 and the medical data (ie, patient information) input in step S1035 to the process management server 400' (S1040).

In addition, when the process changes to the dialysis start process (P3) and proceeds, the medical staff terminal 300' displays a screen showing three items defined in P3 (S1045).

In addition, the process management server 400' automatically classifies and extracts the patient information received in step S1040 as the medical data of the item defined in P2 and stores it in the DB (S1050).

In addition, the process management server 400' defines an anchor defining a format of medical data to be collected in P3 (ie, a format for receiving medical data corresponding to two or three items) based on the event received in step S1040. Data is generated and the generated anchor data is transmitted to the data collection module 510' (S1055 and S1060). Among the items defined in P3, the prescription execution item requires data on whether or not the medical staff prescribed a prescription, so the medical staff can select it manually or read it from the EMR and display it on the medical staff terminal 300'.

The data collection module 510' analyzes the format defined in the anchor data, collects necessary medical data (ie, dialysis start information) from the TDMS 500', and transmits it to the process management server 400' (S1065, S1070).

The process management server 400' analyzes the received medical data (dialysis start information), automatically classifies, extracts, and stores the medical data of items defined in P3, and transmits the data to the medical staff terminal 300' (S1075, S1080). ).

The medical staff terminal 300' displays the received medical data as the medical data (dialysis start information) of the item defined in P3, and generates an event notifying the change to the next step (S1085).

Referring to FIG. 11, the medical staff terminal 300' transmits an event notifying the change to the next process generated in step S1085 and prescription execution information to the process management server 400' (S1090).

The medical staff terminal 300' changes to the dialysis progress process (P4) and displays a screen showing the five items defined in P4 (S1095).

The process management server 400' analyzes the event, confirms that a patient survey is required to collect patient opinions in P4, and displays the process progress status and a process UI screen capable of conducting the patient survey on the patient terminal 200'. command (S1105).

The patient terminal 200' proceeds to P4, displays the UI screen for the patient survey, performs the survey, and transmits the survey result to the process management server 400' (S1110 and S1115). When the survey is completed in step S1110, the patient terminal 200' displays the UI screen 600 as shown in FIG.

The process management server 400' may store the received patient survey in the DB (S1120) and notify the medical staff terminal 300' that the survey has been completed (not shown).

The process management server 400' generates anchor data defining a format of medical data to be collected in P4 (ie, a format for receiving medical data corresponding to 5 items) based on the event received in step S1090. It is transmitted to the data collection module 510' (S1125, S1130).

The data collection module 510' collects dialysis progress information from the TDMS 500' based on the received anchor data and transmits it to the process management server 400' (S1135 and S1140).

The process management server 400' analyzes the medical data (i.e., dialysis progress information such as blood pressure and UF) received from the data collection module 510' and automatically classifies, extracts, and stores the medical data of items defined in P4. and transmitted to the medical staff terminal 300' (S1145, S1150).

The medical staff terminal 300' displays the results of the patient survey and the medical data (dialysis progress information) of the P4 item, and transmits an event notifying the change to the next process to the process management server 400' (S1155, S1160). ).

Then, the medical staff terminal 300' changes to the dialysis end process (P5) and displays a screen showing two items defined in P5 (S1165).

Along with this, the process management server 400' receiving the event indicating the change to P5 in step S1160 defines the format of medical data to be collected in P5 (ie, the format for receiving medical data corresponding to two items). After generating anchor data to be transmitted to the data collection module 510' (S1170, S1175).

The data collection module 510' collects dialysis end information (for example, weight after dialysis, whether or not blood vessel conditions have been checked) from the TDMS 500' based on the received anchor data, and then processes the process management server 400'. It is transmitted to (S1180, S1185).

The process management server 400' analyzes the medical data (dialysis completion information) received from step S1185, automatically classifies, extracts, and stores the medical data of the item defined in P5, and transmits it to the medical staff terminal 300' ( S1190, S1195).

The medical staff terminal 300' displays medical data (dialysis end information) corresponding to the item defined in P5 on the screen, thereby ending the general dialysis workflow (S1200).

Referring to FIG. 12, when the patient determination menu 650 is selected on the UI screen 600 displayed in step S1110 while P4 is in progress (S1210), the patient terminal 200' generates a patient active event to process management server (400') (S1215, S1220).

When a patient active event is received, the process management server 400' determines that the patient has an abnormality, generates anchor data for collecting the patient's vital sign data, and transmits it to the data collection module 510' (S1225). S1230).

The data collection module 510' collects the patient's most recently collected biosign data and the most recently collected biosignal data within a predetermined time range from the TDMS (500') based on the received anchor data, and collects the process management server. (400') (S1235, S1240).

The process management server 400' classifies and extracts the biosign data of the patient received from step S1240 as data corresponding to a process in progress locally, and transmits the data to the medical staff terminal 300' (S1245 and S1250).

The medical staff terminal 300' displays the received biosign data of the patient so that the medical staff can analyze it (S1255).

The service provision system through automatic extraction and classification of medical data described with reference to FIGS. 1 to 12 is an example of services related to kidney dialysis, and is not limited to kidney dialysis, and all fields of treatment services using medical devices, or non-dialysis services. Even for medical devices, it can be applied to electronic fields that require automatic classification and extraction of data.

In the above, even though all the components constituting the embodiment of the present invention have been described as being combined or operated as one, the present invention is not necessarily limited to these embodiments. That is, within the scope of the object of the present invention, all of the components may be selectively combined with one or more to operate. In addition, although all of the components may be implemented as a single independent piece of hardware, some or all of the components are selectively combined to perform some or all of the combined functions in one or a plurality of pieces of hardware. It may be implemented as a computer program having. Codes and code segments constituting the computer program may be easily inferred by a person skilled in the art. Such a computer program may implement an embodiment of the present invention by being stored in a computer readable storage medium, read and executed by a computer.

On the other hand, although the above has been described and illustrated in relation to preferred embodiments for illustrating the technical idea of the present invention, the present invention is not limited to the configuration and operation as shown and described in this way, and departs from the scope of the technical idea. It will be apparent to those skilled in the art that many changes and modifications can be made to the present invention without modification. Accordingly, all such appropriate alterations and modifications and equivalents are to be regarded as falling within the scope of the present invention. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the attached claims.

100, 100': medical devices
200, 200': patient terminal
300, 300': medical staff terminal
400, 400': process management server
500, 500': collection server

Claims (6)

A collection server that collects and stores data related to patient treatment (hereinafter referred to as 'medical data') obtained from medical devices;
A plurality of standardized workflows for treating patients with the medical device are defined, and when one of the plurality of workflows is selected by a medical staff terminal, processes of the selected workflow are provided to the medical staff terminal and the patient terminal process management server; and
A patient terminal generating and transmitting a patient active event to the process management module when patient condition information according to the patient's judgment is received while treating the patient with the medical device according to the processes defined in the selected workflow;
The process management server,
A system for actively collecting medical data of a patient receiving medical data stored in the collection server through a data collection module installed in the collection server when the patient active event is received.
According to claim 1,
The process management server,
a process management module generating anchor data defining a format of medical data to be collected from the collection server when the patient active event is received, and transmitting the generated anchor data to the data collection module;
including,
The data collection module,
The system for actively collecting patient's medical data, wherein the medical data is collected from the collection server based on a format defined in the received anchor data and then transmitted to the process management server.
According to claim 1,
The process management server,
The system for actively collecting medical data of a patient, characterized in that the medical data received from the data collection module is mapped to identification information of the patient's active event, stored, and transmitted to the medical staff terminal.
According to claim 1,
The process management server,
A plurality of processes defining treatment tasks to be processed in sequence are created, a plurality of processes are created by arranging and grouping them in order of processing to create a single workflow, and a number of detailed tasks are defined for each of the plurality of processes. A process management module that generates an item of and automatically classifies and extracts medical data received from the medical device and the data collection module as data of an item defined in the identified process while the selected workflow is in progress; and
a DB for storing the workflow generated by the process management module in association with a plurality of processes and items, and storing the automatically classified and extracted medical data as data of items defined in a corresponding process;
Patient's medical data active collection system comprising a.
(A) If the process management server defines a plurality of standardized workflows for treating patients with medical devices, and one of the plurality of workflows is selected by a medical staff terminal, the process of the selected workflow is performed by a medical staff member. providing to terminals and patient terminals;
(B) collecting and storing, by a collection server, data related to the patient's treatment progress and the patient's vital signs (hereinafter referred to as 'medical data') obtained from the medical device;
(C) While the patient terminal treats the patient with the medical device according to the processes defined in the workflow selected in step (A), when patient condition information according to the patient's judgment is received, a patient active event is generated and the process is performed. sending to the management module; and
(D) receiving, by the process management server, medical data stored in the collection server through a data collection module installed in the collection server when the patient active event is received;
Patient's medical data active collection method comprising a.
According to claim 5,
In the step (D),
(D1) generating, by the process management server, anchor data defining a format of medical data to be collected from the collection server when the patient active event is received;
(D2) transmitting, by the process management server, the generated anchor data to the data collection module; and
(D3) the data collecting module collects medical data from the collection server based on the format defined in the anchor data received from step (D2) and transmits the collected medical data to the process management server;
A method for actively collecting medical data of a patient comprising a.

Images