A program, information processing method, information processing device, and recording medium for generating and managing patient checklists based on electronic medical record information.

Abstract

Conventional systems lacked established methods for managing the progress of medical treatment in conjunction with electronic medical records, and for generating and managing checklists tailored to each patient's diagnosis, symptoms, and condition. This resulted in challenges such as missed checks by healthcare professionals and increased workload. [Solution] The checklist system works in conjunction with electronic medical records to automatically generate checklist information based on disease name, symptoms, and condition, evaluate and manage the progress of treatment, and support notification and approval processes for uncompleted items. It utilizes a large-scale language model to optimize the diagnosis and treatment process.

Description

Technical Field

[0001] The present invention relates to a tool (program, system, method) that cooperates with an electronic medical record system in the medical field, generates a checklist for patients from a checklist template based on the patient's disease name, symptoms, and condition, and further evaluates and manages the implementation status thereof.

Background Art

[0002] In recent years, with the spread of electronic medical record systems, the digitization of medical information has advanced, aiming to improve the efficiency of medical practitioners' diagnoses and operations. Electronic medical records have various functions such as recording and managing medical histories, referring to test results, and managing prescriptions.

[0003] Patent Document 1 discloses a medical accident prevention support system that cooperates with an electronic medical record system. This technology extracts check items related to a doctor's instruction information, arranges them in descending order of occurrence frequency based on an incident database, and displays them, aiming to prevent medical accidents by preferentially presenting high-risk items.

[0004] Patent Document 2 discloses an electronic medical record system that collates symptom information input into an electronic medical record with a statistical information database and presents related disease names, treatments, and tests to doctors. This technology aims to assist doctors' diagnoses and provide support for selecting appropriate tests and treatments by utilizing past medical data.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, conventional technologies do not integrate with electronic medical record systems to manage the progress of treatment plans or track the implementation status of necessary examinations and procedures. Furthermore, a mechanism for linking checklists for appropriately managing each patient's diagnosis, symptoms, and treatment plan with electronic medical records is not yet fully established. A checklist is a list of multiple items arranged in a list format, with a checkbox to the left or right of each item. Typically, users can visually and quickly grasp the progress and status of work by marking the corresponding checkbox when they have completed or confirmed each item. However, checkboxes are not always necessary; simply displaying items in a list format can serve as a checklist. For example, displaying the text of multiple items after the checkboxes in a list format can also function as a checklist.

[0007] The checklist items disclosed in Patent Document 1 are presented in a different order based on the frequency of incidents, allowing for verification in order of high-priority related checklist items followed by low-priority related checklist items. This is not based on the patient's diagnosis or symptoms; rather, the checklist items, backed by the incident frequency, are obtained after statistically processing the incident frequency. The reference information disclosed in Patent Document 2 indicates the most frequent related diagnoses, treatments, and tests based on symptoms, and is therefore also obtained after statistical processing.

[0008] In other words, both patented technologies assist healthcare professionals in making decisions based on statistical data, rather than being directly based on the individual patient's diagnosis or symptoms. Furthermore, there is room for improvement in the system for managing processes and implementation status through integration with electronic medical records. In other words, these existing patents primarily focus on a "reference information suggestion function" that presents candidate diagnoses, treatments, or tests based on physician's instructions and symptom information, and do not systematically manage and present confirmation items (tasks) tailored to the individual patient's condition. In contrast, the present invention includes a checklist database for presenting a "patient checklist" for each individual patient based on one or more pieces of information from disease name, symptoms, or condition, and is configured to comprehensively and accurately present the necessary work items and confirmation points in the patient's medical treatment and care process. Conventional "reference information suggestion functions" cannot discuss guidelines or recommendations based on statistical data, and are only for reactive responses after an incident occurs. This patent, through its configuration, organizes a database based on recommendations such as guidelines, making it easier to proactively identify patient-specific points of caution and procedures to be followed, thereby contributing to the improvement of the quality and safety of medical care. Existing patents do not disclose the generation of "checklists" themselves according to each individual patient's condition and disease name, and their use in task management, so the present invention has a significantly different technical significance. [Means for solving the problem]

[0009] This invention was made in view of the above problems, and aims to provide a tool (program, system, method) that supports medical professionals in clinical practice by linking with an electronic medical record system, selecting a checklist template based on each patient's disease name, symptoms, and condition, and generating a patient checklist. Furthermore, it evaluates the completion status of the patient checklist by comparing it with the information in the electronic medical record.

[0010] (1) The system works in conjunction with an electronic medical record system that has electronic medical record information to select one or more checklist templates that are candidates for application to the patient from a checklist database that stores checklist templates associated with at least one of the patient's disease name, symptoms, or condition, based on at least one of the patient's disease name, symptoms, or condition obtained from the electronic medical record information, and to generate a patient checklist based on the selected checklist template.

[0011] According to the present invention, by generating a patient checklist tailored to each patient's individual situation based on a checklist template stored in a checklist database, the appropriate flow of examinations and treatments based on the disease name, symptoms, etc., can be clarified, and omissions in medical care can be prevented.

[0012] (2) If a patient has multiple diagnoses, symptoms, or conditions, multiple checklist templates corresponding to each are selected. Through a predetermined integration process that adjusts the items included in the selected multiple checklist templates, a single patient checklist is generated and proposed to the user.

[0013] The aforementioned integration process includes the following processes: (3-1) Normalization process to unify concepts through synonym matching: At least one of the names, abbreviations, variations in notation, or concept codes of medical procedure items is normalized to unify concepts. For example, "blood glucose test," "BS test," and "blood glucose level measurement" are normalized as the same test item. This normalization is performed by referring to a synonym table. (3-2) Processing to integrate higher-level and lower-level items based on inclusion relationships: Based on a hierarchical structure that links higher-level and lower-level items as parent-child relationships, the higher-level item is integrated if a lower-level item exists. For example, if there is a higher-level item called "blood test" and lower-level items called "HbA1c test" and "blood glucose test", the higher-level item is integrated if the lower-level item is selected, and duplicate display is avoided. (3-3) Process for determining the selection and order of items based on priority rules: The items to be selected after integration and their display order are determined based on at least one of the following: clinical department, in-facility protocol, urgency, severity, timeline, or deadline. For example, high-urgency test items can be displayed at the top, and items with approaching deadlines can be highlighted. These processes remove duplicates and rearrange the list, generating a single patient checklist.

[0014] The integration process takes multiple sets of medical procedure items obtained separately before integration, consolidates items linked to the same concept into representative items, and outputs them as a single ordered list. This allows healthcare professionals to refer to a streamlined patient checklist without duplication.

[0015] According to the present invention, by integrating multiple selected checklist templates to generate a patient checklist, it becomes possible to review in advance any omissions or unnecessary tests and treatments in medical care. For example, since standard recommended tests for a particular disease are presented, even inexperienced medical professionals can more easily adhere to the appropriate medical care process. Furthermore, checklists are extremely important in medical settings, and it is known that their consistent use can dramatically reduce infections in hospitals. For example, there is a report that introducing a checklist during central venous catheter placement in the intensive care unit reduced catheter-related bloodstream infections to zero.

[0016] (3) The system has a function to acquire the items that make up the patient checklist, to compare the events or records in the electronic medical record system with the items based on matching conditions defined for each item, to automatically evaluate the implementation status of each item based on the matching results, and to display and / or save the evaluation results.

[0017] According to the present invention, by providing a function to evaluate the implementation status of each item based on information from the electronic medical record, the implementation status can be automatically compared with medical records and test results in the electronic medical record, without requiring medical professionals to manually manage patient checklists. This enables accurate and consistent data management.

[0018] (4) An approval operation to confirm the completion of the above items will be received from an authorized healthcare professional, and the items on the patient checklist will be confirmed as completed in accordance with the approval operation.

[0019] According to the present invention, after evaluation, each item is finalized by accepting approval from an authorized medical professional, thereby ensuring the appropriateness of each treatment step through the approval process. For example, even if a specific test is performed, approval from a physician or person in charge is required to determine whether the results meet the standards and whether the treatment flow is appropriate. When the approval operation is received, the medical professional's approver identification information, approval time, target item identification information, and the status before and after finalization are recorded as an audit log. This makes it possible to track who finalized which item, when, and from what state, contributing to the proof of the appropriateness of medical procedures. This reduces the risk of inappropriate actions occurring during the treatment process and ensures the provision of appropriate medical care to patients.

[0020] The approval process can include multi-stage approvals depending on the healthcare professional's role or profession. For example, a configuration where a nurse provides initial approval followed by a physician's final approval clarifies responsibility for the completion of patient checklist items, thereby ensuring medical safety.

[0021] The audit log is retained in a tamper-detectable manner by at least one of hash chaining, digital signatures, or WORM storage. Hash chaining makes tampering detectable by including the hash value of the previous entry in each log entry, so that hash value inconsistencies can be detected in case of tampering. Digital signatures prevent tampering and forgery by signing the log entries. WORM storage is a storage medium that physically makes it impossible to overwrite or delete data that has been written once. By these technologies, the integrity of the audit log is ensured, and the evidentiary ability in medical litigation and the like is secured.

[0022] (5) The patient checklist includes check boxes or check marks for each of the above items and has a data structure in which text fields are arranged.

[0023] According to the present invention, by providing check boxes and check marks for each item, it becomes easier to visually grasp the implementation status, and omissions in medical treatment can be prevented. In addition, by arranging text fields, not only the presence or absence of a check but also detailed supplementary information (presence or absence of abnormal findings and additional findings) regarding the content and implementation status of medical treatment can be recorded.

[0024] The data structure combining check boxes / check marks and text fields is designed as a format for structured data. Check boxes / check marks can be managed by having fields that define the completed / uncompleted state with a completion flag, define the multi-stage status management of unimplemented / implementing / completed / on hold / expired / scheduled for request / before request registration / in request / unknown / inadmissible / scheduled for implementation by someone other than oneself by the status of the check mark, and define a timestamp for recording the date and time when the check was completed. The implementation status is unimplemented, implementing, completed, on hold or The system includes at least one condition that is overdue, and these conditions are visually distinguished by the display of checkmarks and color coding, allowing healthcare professionals to grasp the progress at a glance. The text fields are defined by free-text fields that healthcare professionals can input into, auto-input fields that are automatically inserted in conjunction with the electronic medical record, and historical information that retains the input content as a log. In addition, it stores information about the person in charge, approval flags, and electronic medical record links as related metadata.

[0025] (6) The generation or evaluation function uses a large-scale language model.

[0026] According to the present invention, by using a large-scale language model (LLM), the accuracy of generating and evaluating patient checklists is improved, enabling advanced decision support and the promotion of personalized medicine that were not possible with conventional systems. In other words, it can analyze medical records and test data obtained from electronic medical records and generate optimal patient checklists tailored to each patient's specific situation. Even with the same diagnosis, it can suggest appropriate examination and treatment procedures while taking into account the patient's age, presence or absence of complications, and treatment history. Furthermore, the evaluation function using LLM analyzes electronic medical record information and patient checklists, and its main role is not merely to check whether an item was performed or completed, but to enable the determination of the appropriateness of the medical process. In this invention, LLM can contextually understand the contents of medical records and make a more sophisticated determination of whether appropriate medical procedures were performed. Furthermore, while there may be multiple checklist templates for several different diseases, each used in multiple situations, it is possible to rearrange them by situation and chronological order, allowing users to complete the checklists accurately and with good visibility.

[0027] • One of the aforementioned conditions is the state of readiness for discharge, and the aforementioned proposal or evaluation includes the state of readiness for discharge based on the electronic medical record and / or test results. The checklist template based on the aforementioned disease name includes one or more of the following: tests for diagnosing the aforementioned disease name, tests for assessing the severity of the aforementioned disease name, and tests for assessing complications of the aforementioned disease name. • The checklist template based on the aforementioned disease name includes a list of treatment items. The checklist template based on the aforementioned symptoms includes a list of tests that should be evaluated before the patient is permitted to go home.

[0028] According to the present invention, it is possible to provide an optimal patient checklist tailored to each patient's condition and medical status. Managing discharge preparation status allows for evaluation of whether necessary tests and treatment processes for patient discharge are being properly implemented by linking them with electronic medical records and test results. This ensures that all necessary procedures are performed without fail, reducing the risk of readmission after discharge. For example, when a patient with a chronic disease is discharged, it is possible to appropriately assess the need for adjustments to drug therapy and follow-up, and to clarify the post-discharge care plan to ensure patient safety. Furthermore, if discharge conditions are not met, appropriate action is prompted for the medical staff. A checklist template based on disease names, including diagnosis, severity assessment, and complication assessment, enables more accurate medical treatment. In conventional medical practice, tests are performed according to standard diagnostic protocols, and the selection of tests according to each patient's condition is sometimes insufficient. This invention improves diagnostic accuracy by presenting appropriate test items related to a specific disease name based on electronic medical record information. By including treatment items in a checklist template based on the disease name, the standardization of the medical treatment process and improvement of the quality of treatment can be achieved. Although treatment policies largely depend on the physician's judgment, this invention utilizes a patient checklist to support medical treatment in accordance with standard treatment protocols and maintain the appropriateness of the treatment plan. This will lead to an increase in the rate of implementation of standard treatment and an improvement in the patient's prognosis. A symptom-based checklist template that includes evaluation items before discharge prevents resident physicians from sending patients home without a thorough examination in the emergency room, thus establishing a system to support the safe return of patients. This invention lists the necessary evaluation items for each symptom and supports healthcare professionals in ensuring their reliable review, thereby preventing errors in judging early discharge and enabling appropriate responses according to the patient's recovery status. In fact, many hospitals have been the subject of medical malpractice lawsuits due to issues such as resident physicians' nighttime care, making this very important for hospital risk management. [Effects of the Invention]

[0029] This invention, by linking with electronic medical record information, automatically generates patient checklists tailored to each patient's disease, symptoms, and condition, and allows for evaluation of the progress of treatment based on the electronic medical record information. This prevents omissions in treatment and ensures that necessary tests and treatments are carried out reliably.

[0030] Furthermore, by placing check boxes / check marks and text fields for each item in the patient checklist, it becomes possible not only to confirm completion but also to record detailed information about the medical treatment. In addition, by incorporating an approval process, the appropriateness can be ensured through physician verification, reducing the risk of incorrect treatment or inadequate response. For example, after checking the check marks, text can be created to be copied to the electronic medical record. [Brief explanation of the drawing]

[0031] [Figure 1] A diagram showing the network configuration of a checklist system according to an embodiment of the present invention. [Figure 2] This diagram shows the system configuration and hardware layout of this system. [Figure 3] A block diagram showing an example of the functional configuration of a processing device. [Figure 4] A block diagram showing an example of the functional configuration of Server 20. [Figure 5]A flowchart showing the processing procedure executed by the application program of the checklist system according to an embodiment of the present invention. [Figure 6] A flowchart showing the processing procedure executed by the application program of the checklist system according to an embodiment of the present invention. [Figure 7] An example of a checklist. [Figure 8] Example of a display screen for a patient checklist. [Figure 9] Examples of data from a checklist database and examples of patient-specific checklists. [Best Mode for Carrying Out the Invention]

[0032] Figure 1 shows a network configuration centered around the checklist system 2, where user terminals 1 (such as PCs and tablet devices) and hospital medical systems 3 (such as electronic medical record systems and image management systems) are connected via telecommunication lines through communication networks such as the Internet, intranet, or hospital LAN. This configuration allows requests from user terminals 1 to be sent to the checklist system 2, enabling it to retrieve and process the necessary information. Data from the medical system 3 is sequentially input and output by user terminals 1 and may be stored in a data warehouse (DWH) not shown. The medical system 3 centrally manages individual patient test information, prescription history, and medical images, and a general-purpose search engine (not shown) can be used to execute processing by the checklist system 2. The search engine may utilize a large-scale language model.

[0033] Figure 2 shows the system configuration and hardware layout of the checklist system. The server 20 computer of the checklist system is equipped with a communication interface 22, an input / output interface 23, memory 25, storage 26, and a processor 29. Similarly, the computer of the user terminal 1 is equipped with a communication interface, an input device, an output device, memory, a storage unit, and a processor (not shown). The user terminal 1 is a desktop or laptop PC, a tablet, a smartphone, or other mobile device.

[0034] <Server 20> Communication IF22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices. Input / Output IF23 functions as an interface to input and output devices for receiving input operations from the user. Memory 25 is for temporarily storing programs and data processed by programs, and is a volatile memory such as DRAM. Storage 26 is a storage device for saving data, such as flash memory, HDD, or SSD. Processor 29 is hardware for executing the instruction set written in the program and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0035] <User terminal> The user terminal's communication interface is the interface that allows user terminal 1 to communicate with external devices and input / output signals. The input device is an input device (such as a keyboard, touch panel, touchpad, mouse, or other pointing device) that accepts input operations from the user. The output device is an output device (such as a display or speaker) that presents information to the user. Memory is for temporarily storing programs, data processed by programs, etc., and is a volatile memory such as DRAM. The storage unit is a storage device for saving data, such as flash memory or an HDD. The processor is hardware for executing the instruction set written in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0036] Figure 3 is a block diagram showing an example of the functional configuration of the processing hot water means 294 shown in Figure 4, and Figure 4 is a block diagram showing an example of the functional configuration of the server 20. Server 20 comprises communication means 220, input device 230, display device 240, notification device 250, storage means 280, and control means 290, with each of these components electrically connected via a bus. Furthermore, a data storage area 283 is provided within the storage means 280 and is managed integrally.

[0037] The communication means 220 performs modulation and demodulation processing for the server 20 to communicate with the user terminal 10, processes the signal calculated by the control means 290 for transmission, and transmits it to external devices and equipment. The communication means 220 also processes signals received from the outside and outputs them to the control means 290. In this way, the communication means 220 interprets commands or input content and provides them to each means, and also functions as an interface that interprets various display commands issued from the storage means 280 and performs output control.

[0038] The input device 230 is a device used by an administrator to input instructions or information to operate the server 20 as needed, and may be a keyboard, mouse, reader, or touch-sensitive device. The input device 230 also converts the instructions input by the administrator into electrical signals and outputs the electrical signals to the control means 290. The input device 230 also includes a receiving port that accepts electrical signals input from external input devices.

[0039] The display device 240 is a display device such as an LCD or organic EL display 241 for presenting information to an administrator who operates the server 20 as needed. The display 241 can display data according to the control content of the control means 290 and can check the communication status between the server 20 and other external devices 10. The notification device 250 is a device (such as a speaker 251) for presenting information to the administrator.

[0040] The storage means 280 is implemented by memory (RAM) 25 and storage 26 such as a disk device (floppy disk, hard disk, or magneto-optical disk, etc.) and stores data, programs, etc. used by the server 20. The storage means 280 stores the application program 282 of this system, as well as data for the work area 281, data storage area 283, and screen definition storage area 284.

[0041] The work area 281 is a region that is secured when the system is started and where various data input and output by the system are temporarily stored. The data storage area 283 is a region where data temporarily stored in the work area 281 is semi-permanently stored through write control by the data management means 285 when a save request is made for the data. The screen definition area 284 is a region where screen definition information for various screens to be output and displayed on the user terminal 10 is stored in advance, and includes format information for screen settings to be displayed by the display control means 292.

[0042] The data storage area 283 is an area for the integrated management of various data in the checklist system, and it holds databases such as the checklist DB283A and the disease name / symptom / condition DB283B. The information stored in the data storage area 283 is managed and controlled to ensure data consistency. In addition to functioning as simple storage, the data storage area 283 can also operate as a data processing means for performing various operations. For example, it can perform update processing when it is necessary to update the data held in the checklist DB283A or the disease name / symptom / condition DB283B.

[0043] Checklist DB283A holds standard data for checklist templates created based on disease names, symptoms, and conditions. This database includes standard clinical flows, necessary tests, treatment procedures, and follow-up procedures. For example, a checklist template corresponding to a particular disease name details the tests required for diagnosis, the treatment plan to be implemented after diagnosis, and follow-up items for monitoring the patient's progress. Symptom-based checklist templates show differential diagnostic flows to identify the cause of the symptoms and criteria for assessing urgency. Condition-based checklist templates include discharge preparation status and management criteria after specific medical procedures. Prioritization rules are maintained as switchable rule sets for each facility or department. This allows for prioritization according to each facility's clinical policies and the characteristics of each department. For example, the emergency department can prioritize urgency, while internal medicine departments dealing with chronic diseases can prioritize chronological order. The information in this database is customizable for each medical institution, allowing for the construction of optimal checklists based on standard clinical guidelines, hospital policies, and past clinical data.

[0044] The Disease Name / Symptom / Condition DB283B systematically organizes and stores information related to diseases, symptoms, and conditions. Disease name data includes information such as diagnostic criteria, etiology, severity classification, related test items, and treatment policies. For example, the disease name "diabetes" includes the blood glucose threshold used for diagnosis, the risk of complications, and recommended test items (HbA1c, blood glucose test, etc.). Symptom data records symptoms associated with specific diseases, as well as diagnostic methods and recommended tests for each symptom. For example, the data for "fever" includes possible underlying diseases, a treatment flow based on the degree and duration of fever, and recommended tests and treatment approaches. Condition data stores the patient's health status, treatment progress, and discharge preparation status, and by linking with the electronic medical record, changes in the patient's condition can be reflected in real time.

[0045] The control means 290 implements various processes of the input means 291, user IF 292, display control means 293, and processing means 29294 using a processor. The control means 290 uses the processor to coordinate the processing of the entire system and controls various processes related to input (data acquisition), search, display, generation, and user interface (UI). Note that there is one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be other types of processors such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core. Furthermore, at least one processor may be a broad-sense processor such as a hardware circuit that performs some or all of the processing (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)).

[0046] The input means 291 analyzes the input content of checklist generation conditions and implementation status entered by the user via a keyboard or touchscreen, and accepts the data. It serves as an interface used when creating checklists and recording progress. Healthcare professionals input necessary information via the keyboard or touchscreen, and the system sets the checklist conditions and updates the implementation status of each item. For example, when a doctor enters the patient's diagnosis, a patient checklist based on that diagnosis is automatically generated. When a nurse records the progress of each item on the patient checklist using touch operations on a tablet, that progress information is reflected in the system, and the current completion status is updated in real time. In addition, additional medical notes for the patient can be entered through free-form text in the text field.

[0047] User Interface 292 provides screens and input methods for operating the checklist system. Designed for intuitive operation by healthcare professionals, it allows for the display, editing, and progress tracking of patient-specific checklists. The screen displays automatically generated patient checklists based on disease names and symptoms, with real-time updates of the completion status. For example, completed items are marked with a checkmark, and incomplete items are marked with a reminder. It has a function to automatically update the list based on electronic medical record information such as test results and medical records, in conjunction with the electronic medical record system. Furthermore, it can be customized according to the authority and roles of medical staff, providing an interface focused on diagnosis and treatment planning for physicians, and an interface focused on patient care and medication management for nurses. A touchscreen-compatible control panel, voice input, and handwriting recognition are also available as auxiliary functions.

[0048] The display control means 293 manages the information displayed on the user terminal screen and controls it so that the user can intuitively check the information they need. It works in conjunction with electronic medical records and test data, updating information in real time according to the patient's diagnosis, symptoms, and treatment progress, and displaying it in an appropriate format. For example, when doctors or nurses view a patient checklist, incomplete items are highlighted and completed items are marked with a checkmark, improving visibility. In addition, the information on the screen is automatically switched according to the treatment status of each patient, and it has a function that calls up the appropriate checklist when a diagnosis is entered.

[0049] The processing unit 294 acquires necessary information from the checklist DB 283A and the disease name / symptom / condition DB 283B and passes it to each processing unit, which consists of the electronic medical record linkage unit 294A, the checklist determination unit 294B, the implementation status management unit 294C, the approval unit 294D, the implementation status evaluation unit 295E, and the notification unit 295F.

[0050] The Electronic Medical Record Integration Unit 294A integrates with the electronic medical record system to acquire patient medical information and test results, reflecting the patient's diagnosis, symptoms, treatment / test progress, etc., in the checklist system. For example, when a certain test is completed, the result is recorded in the electronic medical record, and the system automatically updates the corresponding item on the patient's checklist. It also cross-references this with the medical record in the electronic medical record to prevent any missed tests or omissions in treatment. The system automatically reflects check boxes or check marks indicating the progress of treatment / tests, etc., on the patient's checklist, and the text fields are filled with text entered by the user or text automatically generated based on the electronic medical record.

[0051] The checklist determination unit 294B analyzes patient information obtained from the electronic medical record, including disease name, symptoms, condition, and diagnosis results, and selects a corresponding checklist template from the checklist database. If a patient has multiple disease names, symptoms, or conditions, multiple checklist templates corresponding to each are selected. For example, if a standard diagnostic flow for a particular disease is applicable, a checklist template including a list of tests and treatments in accordance with that flow is selected. Furthermore, depending on the patient's disease name, symptoms, and condition, the checklist determination unit 294B selects the checklist template that is best suited to the individual patient by taking into account hospital policies (clinical pathways, etc.) and past medical data. The checklist determination unit 294B generates a single patient checklist by performing an integration process (normalization based on synonym correspondence, integration based on inclusion relationships, and duplicate removal and reordering, including determination of adopted items and order based on priority rules) to adjust the items included in the multiple selected checklist templates, and proposes it to the user.

[0052] The approval unit 294D allows authorized healthcare professionals to make final approvals regarding the completion status of each item on the patient checklist. For example, once a patient's treatment is complete, the physician reviews the patient checklist to confirm that all necessary procedures have been properly performed, and then accepts the approval operation to finalize the completion of each item. Approval is ensured by considering not only the actual implementation status but also the entries in the text fields. Furthermore, if multiple steps are required in a specific treatment process, it is possible to proceed while obtaining approvals at intermediate stages. Upon receiving an approval operation, the approval unit 294D records the healthcare professional's approver identification information, approval time, target item identification information, and the status before and after finalization as an audit log. Once approval is complete, the system saves the record and reflects it in the electronic medical record.

[0053] The Implementation Status Evaluation Unit 295E compares the progress of the patient checklist with information from the electronic medical record to evaluate whether it is being implemented appropriately. The comparison criteria include at least one of the following: order type, order status, implementation date and time, whether results have been registered, result value threshold, or prescription duration. For example, if an order for a blood test is in the "completed" status and the result value meets a predetermined threshold, the item is evaluated as "completed." The test results and medical records are compared with the contents of the patient checklist to determine whether the necessary procedures have been performed appropriately. Furthermore, it is compared with standard guidelines for the treatment process to confirm that recommended medical procedures are being followed. If an abnormal case or inadequate response is detected, it is reflected on the patient checklist, and the system issues an alert to draw the attention of healthcare professionals.

[0054] This system allows healthcare professionals to manually change the status of a procedure. If the results of the automated evaluation differ from the actual situation, healthcare professionals can manually change the status. In this case, the reason for the manual change and the person who performed it will be recorded in the audit log. This makes it possible to track the change history and facilitates verification from a medical safety perspective.

[0055] The notification unit 295F notifies medical staff of the progress of the patient checklist. When there are important unperformed tests, items requiring approval, etc. remaining, it sends an alert to the person in charge. Also, when there is a significant change in the patient's condition, it immediately notifies the relevant medical staff. The notifications are provided via pop-ups on the screen, e-mail / SMS messages, app notifications, etc.

[0056] FIG. 5 is a flowchart showing the processing procedure executed by the application program of the checklist system according to an embodiment of the present invention. Through the following series of processes, an optimal patient checklist according to the situation of each patient is generated and managed while cooperating with the electronic medical record.

[0057] <S501: Acquisition of patient data><S502: Extraction of disease name, symptoms, and status information> The electronic medical record cooperation unit 294A acquires electronic medical record information such as the patient's basic information (name, age, gender, etc.), medical records, and examination data from the electronic medical record system. Next, from the patient data, the checklist determination unit 294B extracts information related to the disease name / symptoms / status DB 283B to identify the disease name, symptoms, diagnosis result, progress of treatment, etc. that the patient currently has. For example, the diagnosis code recorded in the electronic medical record is analyzed to specify the corresponding disease name.

[0058] <S503: Condition setting> Based on the extracted disease name and symptoms, conditions for generating the patient checklist are set. The checklist determination unit 294 designs parameters for referring to the checklist DB 283A corresponding to the relevant disease, and designs all aspects including specific severity and the presence or absence of complications as conditions.

[0059] <S504: Search in the database><S505: Determination of checklist information> The checklist determination unit 294B searches the checklist DB 283A to obtain a checklist template that matches the set conditions. It searches for checklist templates including standard medical processes and treatment plans. Based on the data of the searched checklist template, it generates a patient-specific checklist according to the patient's individual situation. Here, it optimizes by selecting necessary items based on the disease name, symptoms, and medical records. It reflects the information in the electronic medical record and generates a customized patient-specific checklist for each patient.

[0060] <S506: Generation of Patient-Specific Checklist> Execute an integration process to adjust between items for the items included in the selected multiple checklist templates. The integration process includes a process of normalizing to the same concept by synonym correspondence, a process of integrating items of the upper concept and items of the lower concept based on the inclusion relationship, and a process of determining the adopted items and order based on the priority rule. Through these, duplicate elimination and rearrangement are performed. As a result of the integration process, a patient-specific checklist is generated as a single checklist. The generated patient-specific checklist is displayed on the user terminal via the user interface for medical staff to confirm. The display control means 293 organizes the information in an appropriate format according to the user's role (such as doctor, nurse, etc.) to improve visibility. It performs color coding and status display so that unimplemented items are clear.

[0061] <S507: Proposal of Checklist Information> The displayed patient-specific checklist is proposed to medical staff for confirmation and approval. Prompt for correction and approval work as necessary. Medical staff perform a final confirmation through the approval unit 294D and determine it as the patient-specific checklist to be officially operated.

[0062] FIG. 6 is a flowchart showing the processing procedure executed by the application program of the checklist system according to the embodiment of the present invention. Through the cooperation with the electronic medical record, the management of the patient-specific checklist is realized, enabling corresponding measures according to the patient's condition while preventing omissions in medical treatment.

[0063] <S601: Acquisition of Patient Data> The electronic medical record linkage unit 294A acquires the latest patient data from the electronic medical record system. It acquires information necessary for evaluating the patient checklist, such as medical records, test results, treatment status, medication history, etc. Through this process, the current state of the patient can be grasped, and the progress of the implementation status can be confirmed.

[0064] <Comparison with the Patient Checklist> The acquired patient data is compared with the patient checklist to confirm the current implementation status. The implementation status management unit 294C analyzes whether each item defined in the patient checklist has been achieved, while matching with the information in the electronic medical record. For example, if the test item is completed, the result is reflected, and if there are unimplemented items, they are listed up.

[0065] <S603: Progress and Evaluation of Implementation Status> The implementation status evaluation unit 295E evaluates the progress status of each checklist item based on the patient data. It analyzes the medical records and test results to clarify the implemented items and unimplemented items, and evaluates the implementation content based on the text column even if it has been implemented. For example, in the case of a checklist for discharge preparation, it determines whether all necessary tests have been completed and whether the treatment plan is progressing appropriately. If necessary, it notifies the medical staff of the uncompleted items.

[0066] <S604: Judgment of Approval><S605: Urging Re-Implementation in Case of Disapproval> The approval unit 294D determines the approval result by a medical staff (doctor) based on the progress evaluation result of the patient checklist. If all check items are properly implemented, it approves. On the other hand, if there are unfinished items, it urges re-implementation. In case of disapproval, the notification unit 295F notifies the person in charge to urge re-implementation. Regarding the unfinished items, tasks are assigned to the corresponding medical staff, and follow-up management is carried out until the necessary measures are implemented. For example, if the pre-discharge examination is unfinished, a notification is sent to the person in charge to urge priority response. When all items are implemented, it returns to the approval judgment process (S604) again.

[0067] <S606: Final determination of each item in case of approval><S607: Update of patient checklist> When all necessary items are completed and approval is obtained, the approval unit 294D determines the completion of each item. By this process, the status of the patient checklist is updated to "completed". Also, this information is recorded in the electronic medical record and saved as the patient's medical history. Finally, the implementation status evaluation unit 295E updates the patient checklist in cooperation with the electronic medical record. It reflects the completion status of the patient checklist in the electronic medical record and integrates it into the patient's medical record. For example, when the discharge preparation is completed, a flag for the dischargeable status is assigned and the process moves to the next medical phase.

Example 1

[0068] <Automatic checklist generation for pre-admission examination> (Claims: 1, 2, etc.) (A) System configuration and data flow Electronic medical record integration: In cooperation with the hospital information system (HIS), using the patient ID as a key, data such as the patient's disease name, symptoms, past history, allergy information, etc. of the patient scheduled for admission is obtained. The program of the present invention operates on the "checklist management server" arranged in the hospital (Claim 1). Checklist database: The checklist database (hereinafter referred to as the "CL database") contains recommended standard tests and potential additional tests depending on the risk of complications. For example, for digestive system diseases, gastroscopy and colonoscopy are registered as mandatory tests, and if a co-existing heart condition is suspected, an echocardiogram is suggested as an additional test. Processing steps Obtaining disease name and symptom information: The checklist management server retrieves the patient's diagnosis, major symptoms, and medical history from the electronic medical record system. Generation of a patient checklist (Claim 1): The CL database is searched, and a list of tests related to the disease or symptoms is extracted as initial candidates. Based on the extracted list of tests, a list of individual patient tests is created, referencing their necessity and priority. Combinations, sorting, and duplicate removal (Claim 2): For patients with multiple illnesses, there may be overlapping lists; therefore, these lists are sorted together, and duplicate items are eliminated. For example, if a blood test (general parameters) is recommended for multiple diseases, it should be indicated that it can be covered in a single test, eliminating unnecessary duplication.

[0069] (B) User Interface Screen display: A "Pre-Admission Test List" for each patient is displayed on the screen, with checkboxes indicating whether each test item can be performed. In addition to the list with duplicates removed, the necessity of recommended tests ("Required," "Recommended," "Reference," etc.) is indicated with icons and color coding. Furthermore, the list can be sorted based on necessity, with required items at the top and reference items at the bottom. Adjustment function: Medical staff can change the order of test items or remove some items. These changes are recorded on a server, allowing for later auditing and review. (C) Effects This reduces the number of tests that should be completed before hospitalization, minimizing the need for patients to return to outpatient clinics after admission. Furthermore, even novice staff can suggest tests according to standard procedures, making it easier to maintain a consistent level of medical quality throughout the hospital. [Example 2]

[0070] <Cancer Severity Assessment and Time-Series Optimization> (Applicable Claims: 1, 2, 3, 12, etc.) (A) System Configuration Integration with multiple departmental systems: We obtain test results from different departmental systems, including the pathology department, radiology department, and surgery / internal medicine department. The checklist management server queries the APIs or databases (table / document format) of each departmental system using the patient ID as the key. Severity assessment database: Essential test items for each type of cancer (e.g., tumor markers, CT scans, pathological diagnosis, biochemical tests, etc.) are registered and managed together with criteria for determining the severity (stage classification and TNM classification).

[0071] (B) Processing flow Reading patient data (Claim 1): The system retrieves the patient's registered diagnosis (cancer type) and known comorbidity risk (diabetes, hypertension, etc.) from their electronic medical record. The system retrieves a list of tests required for the specific type of cancer from the CL database. Time-series optimization of the list (Claim 3): The system automatically rearranges the order in which tests are performed, taking into account the patient's next appointment date and the number of days required to prepare for the tests (such as the need for test reservations and the timing of sample collection). For example, we propose a rational workflow such as performing a blood test first and then scheduling a CT scan once the results are available. Implementation status evaluation (Claim 12) Once each test result is registered in the departmental system, the checklist management server retrieves the completion status and result values ​​via API. The system automatically determines the status of the item (completed, abnormal, retest required, etc.) and notifies the medical staff.

[0072] (C) Effects Because all the information necessary for cancer staging can be collected without omission, the decision on the appropriate treatment plan can be made more smoothly. In addition, time-series optimization minimizes the number of hospital visits, simultaneously reducing the burden on patients and efficiently utilizing hospital resources. [Example 3]

[0073] <Checklist before discharge permission after outpatient visit> (Applicable claims: 1, 12, 16, etc.) (A) System Configuration Symptom-based checklist database: Based on the patient's chief complaint and symptoms (headache, chest pain, shortness of breath, etc.), we register the "tests that are desirable to perform before granting permission to go home." For example, in the case of chest pain, the checklist includes a list to determine whether an electrocardiogram, chest X-ray, and echocardiogram can be performed. UI screen configuration: A checkbox is displayed to the left of each item, and "text (supplementary explanations and specific testing methods)" is displayed to the right. Priority levels such as "Required," "Recommended," and "Physician's Decision" are displayed for each item.

[0074] (B) Processing procedure Integration with electronic medical records (Claim 1): The system retrieves symptom information (for example, "chest pain") entered by the patient when they register at the outpatient reception. A list of standard tests associated with the relevant symptoms was extracted from the CL database. Evaluation of the implementation status (Claim 12): If tests that have already been performed are registered in the electronic medical record, those tests will be automatically updated to a "completed" status. Incomplete tests will remain on the list, and once the medical staff have finished the tests, the system will automatically determine whether they are "finished" or require "continued investigation." Termination confirmed by approval (Claim 16): Once all required items are completed, the system notifies the doctor that the patient is "ready to go home." The doctor will perform a final confirmation (approval) on the screen to finalize the procedure. (C) Effects By visualizing "Is it okay to send the patient home?" and "Does further testing need to be done?" using a checklist, it contributes to medical safety. In fact, there are many cases where resident doctors have been sued for medical malpractice because they sent patients home in the middle of the night without calling a senior doctor. Because a certain process is followed regardless of whether the doctor is veteran or new, the risk of overlooking a diagnosis due to insufficient testing is reduced. [Example 4]

[0075] <Visualization of discharge preparation status> (Applicable claims: 1, 12, 16, etc.) (A) System Configuration Discharge preparation database: The system registers necessary items before discharge (medication guidance, rehabilitation assessment, final examination, referral letter preparation, etc.). It also includes "additional discharge instructions" and "follow-up outpatient appointments" tailored to the patient's condition (post-surgery, chronic disease management, infection risk, etc.). Electronic medical record integration (Claim 1): The checklist management server dynamically updates the discharge checklist by referencing the scheduled discharge date, ward nursing records, and the progress of test results.

[0076] (B) Specific Flow Identifying patients who are candidates for discharge: Based on factors such as the length of hospital stay and treatment progress, the system generates a patient checklist once the attending physician instructs the patient to "begin preparing for discharge." Progress management of required items: Examples: Checking for signs of inflammation in the final blood test, confirming wound care status, arranging home nursing care after discharge, providing medication guidance, etc. Once each item is recorded in the electronic medical record, it is automatically determined whether it is "completed" or "incomplete." Approval flow (Claim 16): Once the nurse completes each item, they press the approval button or leave a comment if necessary. The discharge preparation list is considered complete once the attending physician has finally approved that the patient is ready for discharge. (C) Effects This eliminates last-minute panic before discharge and allows for comprehensive discharge preparation. Pre-discharge coordination with the patient's family becomes more visible, leading to a smoother discharge and a reduced risk of readmission. It also reduces the need for additional tests after admission, resulting in fewer out-of-pocket expenses for testing, which is beneficial from a healthcare management perspective. [Example 5]

[0077] <Automatic suggestion of check lists using a large-scale language model> (Applicable claims: 1, 2, 12, etc.) (A) System Configuration LLM Integration Module: The checklist management server includes a module that communicates with a large-scale language model (LLM). The LLM utilizes either a model trained on a medical knowledge base or a fine-tuned model specialized for a specific domain. Division of roles between databases and LLMs: The database continues to manage basic examination and treatment items for each disease, as before. LLM analyzes the text in the free-form fields of the electronic medical record (e.g., "The patient complained of lower left abdominal pain since last night..."). Predicting possible symptoms and complications: The system automatically generates additional test items based on the analysis and sends them back to the checklist management server.

[0078] (B) Specific processing procedures Create an input prompt: The system compiles the medical record text and past history (e.g., "history of colon polyp removal," "poorly controlled diabetes") from the electronic medical record and sends it to the LLM as a prompt. LLM response analysis: The information returned from the LLM includes a list of suspected complications in this case and additional tests that should be performed. The system integrates that list with the basic checklist in the database, and then performs duplicate removal and chronological adjustment. Automatic evaluation of implementation status: If any tests have already been performed, refer to the electronic medical record and mark them as complete. The completion status will be updated when the results of additional tests become available. (C) Effects LLM can identify complication risks that might be overlooked by human analysis through text analysis, and use this information to suggest appropriate tests. By combining it with the basic database, it becomes possible to propose tests more flexibly than with conventional rule-based systems. The completion status is managed in the electronic medical record system as before and incorporated into the approval process, thus simultaneously ensuring medical safety.

[0079] <Summary> As described above, the program of the present invention automatically determines a checklist corresponding to each patient's disease name, symptoms, and condition in conjunction with an electronic medical record (Claim 1), and presents them to healthcare professionals in an optimized form through procedures such as "combining, rearranging, and eliminating duplicates (Claim 2)," evaluation of the implementation status (Claim 12), and "confirming completion by approval (Claim 16)." Furthermore, by utilizing large-scale language models (LLMs), it becomes possible to propose test lists tailored to specific diseases and outpatient test items based on symptoms more flexibly and comprehensively. It can also manage checklists specific to particular phases, such as discharge preparation status, and is expected to be applied in a variety of situations in the medical field. Furthermore, as an example of a UI, the chatbot may display a checklist and include a process for checking it, or a screen may be created that allows users to view a list of those who have not checked the checklist, and this may be linked to performance evaluations.

[0080] Figure 7 shows an example of a checklist template for preventing the onset of infectious diseases, which is stored in checklist DB283A. This checklist template lists standard infection prevention measures and is used for infection control in healthcare settings. For example, it includes specific items to prevent the spread of infection, such as thorough hand sanitization, wearing of personal protective equipment, and confirmation of cleaning and disinfection procedures.

[0081] Figure 8 shows an example of a display screen for a particular patient, illustrating an example of a user interface for a patient checklist linked to an electronic medical record system. This screen displays a patient checklist for a specific patient, allowing healthcare professionals to easily track the progress of each patient's treatment and examinations. The screen includes the following elements: • Basic patient information (name, age, diagnosis, medical department, etc.) • List of items on the patient checklist (the progress of each item is indicated by checkboxes or marks) • Alerts displayed for items that have not yet been completed. • Input area for healthcare professionals (allows for additional comments and recording of test results) This type of UI allows healthcare professionals to intuitively manage each patient's treatment process and ensure that no incomplete tasks are overlooked.

[0082] Figure 9 shows the data structure stored in the checklist database and an example of a patient-specific checklist. The checklist DB stores checklist templates based on standard clinical protocols, and an appropriate list is generated according to the patient's diagnosis and symptoms. Specifically, the following data structure is expected. • Checklist DB (Standard Checklist) Standard checklist items corresponding to each disease name, symptom, and condition. • Lists categorized according to the medical process, such as diagnosis, treatment, and discharge preparation. Patient-specific checklists • Individualized lists linked to electronic medical record information • Completed items and incomplete items are clearly distinguished. Includes a text field where the attending physician / nurse can record comments. The checklist database assigns names to checklist templates, making it easier to understand the purpose of each checklist. It also includes natural language descriptions of when each checklist should be triggered. The system can be operated by using AI to evaluate whether the trigger criteria are met based on electronic medical record information, and displaying the checklist if it determines that a trigger is warranted. Figure 9 shows the checklist database containing the grouping name "Cancer Patient Severity Assessment Checklist" and its trigger, "Hospitalization Preparation." Figure 9 illustrates how the system utilizes standard checklists and provides personalized checklists tailored to each patient. This allows healthcare professionals to adhere to standard treatment protocols while providing flexible care for each individual patient. [Industrial applicability]

[0083] The tools of this invention are useful in improving the quality of medical care in healthcare institutions, reducing workload, ensuring patient safety, and ultimately reducing the risk of medical malpractice lawsuits.

[0084] Specifically, it has high practical value in the medical field because it can be linked with electronic medical record systems to automatically generate patient checklists tailored to each patient's diagnosis, symptoms, and condition, thereby enabling appropriate management of the progress of diagnosis and treatment. In particular, medical institutions are required to standardize diagnosis and manage the execution of treatment plans, and a tool that manages patient checklists in conjunction with electronic medical records will contribute to improving operational efficiency and the quality of medical services.

[0085] Furthermore, in medical settings, insufficient verification of treatment implementation and omissions in examinations and procedures can lead to medical accidents, which are often the cause of medical malpractice lawsuits. This invention proposes an appropriate patient checklist for each patient based on information recorded in the electronic medical record, and allows for real-time evaluation of the implementation status of each item. This prevents omissions in treatment and enhances the transparency of the treatment process. In addition, by incorporating a system to clearly record the progress of the treatment plan and obtain approval, it becomes easier to prove the appropriateness of medical procedures, ultimately leading to a reduction in the risk of medical malpractice lawsuits.

[0086] Furthermore, this invention can be applied not only to medical institutions such as hospitals and clinics, but also to nursing care facilities and home healthcare. By recording and managing the status of care provided according to the patient's condition, it can reduce the burden on medical and care workers and support the provision of high-quality services. In addition, by utilizing technologies such as large-scale language models (LLMs), the accuracy of suggesting and evaluating patient checklists can be improved, making it useful as an AI-powered medical support system. [Explanation of symbols]

[0087] 1: User terminal, 2: Medical information retrieval system, 3: Medical system 10: User terminal (communication interface (12), input device (13), output device (14), processor (19), memory (15), storage unit (16)) 20: Server (Processor (29), Memory (25), Storage (26))

[0088] <Note> The program of the present invention can be installed in computer terminals having computer functions such as CPU, memory, and storage, as well as mobile devices such as smartphones, tablets, and wearable devices, digital home appliances such as smart TVs, smart speakers, and smart home appliances, recording media such as USB memory, SD cards, hard disk drives (HDDs) / solid state drives (SSDs), dedicated equipment and terminals such as POS terminals, vending machines, ATMs, and medical equipment, and game consoles (home and portable). When this program is installed in medical equipment, it may be linked with the hospital's electronic health record (EHR / EMR) system. <Note C1> The aforementioned processor, (1) Obtain multiple items that make up the patient checklist, (2) The event or record in the electronic medical record system is compared with the aforementioned multiple items based on the matching conditions defined for each item. (3) Based on the comparison results, the implementation status of each of the above multiple items is automatically evaluated, displayed, and / or saved. <Note C2: Example of matching conditions> The matching conditions include at least one of the following: order type, order status, execution date and time, whether or not results have been registered, threshold value for the result, or prescription duration. <Note C3: Exceptions and manual corrections are also logged> The processor accepts manual changes to the implementation status by medical personnel and records the reason for the manual change and the operator in the audit log. <Note D1: Audit and Responsibility> The aforementioned processor, (1) Approval operations to confirm the completion of checklist items are accepted from authorized healthcare professionals' terminals. (2) In accordance with the approval operation, the checklist item is finalized and confirmed, (3) The approver's identification information, approval time, target item identification information, and the status before and after finalization shall be recorded as an audit log. <Note D2: Multi-stage approval / Job-specific approval> The aforementioned approval process includes multi-stage approvals depending on the job type or role. <Note D3: Tampering detection> The aforementioned audit logs are maintained in a tamper-detectable manner by at least one of hash chaining, digital signatures, or WORM storage.

Claims

1. A program that is executed by a computer, The computer is linked to a checklist database that stores checklist templates associated with at least one of disease names, symptoms, or conditions, and to an electronic medical record system that has electronic medical record information. To the aforementioned computer, (1) Obtain at least one of the patient's disease name, symptoms, or condition from the electronic medical record information, (2) Based on at least one of the acquired disease name, symptoms, or condition, select one or more checklist templates from the checklist database that are candidates for application to the patient. (3) Generate a patient checklist to be applied to the patient based on one or more of the checklist templates mentioned above. In (3) above, multiple checklist templates are selected, and a predetermined integration process is performed to adjust the items included in the multiple checklist templates, thereby generating the patient checklist as a single checklist. A program characterized by the following features.

2. The program according to claim 1, The aforementioned integration process involves performing at least one of the following actions on the items included in the multiple checklist templates: combining, rearranging, and removing duplicates. The aforementioned patient checklist is generated as a single checklist. A program characterized by the following features.

3. The program according to claim 2, The aforementioned sorting takes into account at least one of the following: the patient's next appointment date, whether an appointment for testing is necessary, the timing of sample collection, or the number of days required to prepare for the test. Determine the order in which the above items will be implemented. A program characterized by the following features.

4. The program according to claim 2, The aforementioned duplicate removal process involves consolidating identical inspection items that are commonly included in the multiple checklist templates into a single inspection item. The system should display that performing the single test item in question makes it possible to use the aforementioned multiple checklist templates. A program characterized by the following features.

5. The program according to claim 2, Each item on the aforementioned patient checklist is assigned at least one necessity category: essential, recommended, reference, or physician's judgment. The display format of each item is changed and / or reflected in the sorting based on the aforementioned necessity classification. A program characterized by the following features.

6. The program according to claim 1, In (2) above, based on at least one of the acquired disease name, symptoms, or condition, the system selects from a plurality of checklist templates that are candidates for application to the patient. In (3) above, regarding the multiple items included in the multiple checklist templates, (3-1) Normalize to the same concept through synonym correspondence. (3-2) Integrate items of higher-level concepts and items of lower-level concepts based on the relationship of inclusion. (3-3) Determine the items to be adopted and their order based on the priority rules. The resulting integration process, which includes removing duplicates and rearranging, generates the patient checklist as a single checklist. A program characterized by the following features.

7. The program according to claim 6, The aforementioned synonym correspondence is a program characterized by being executed based on a process that normalizes at least one of the names, abbreviations, or variations in notation of medical procedure items into the same concept.

8. The program according to claim 6, The aforementioned inclusion relationship is based on a hierarchical structure that links higher-level and lower-level conceptual items as parent-child relationships, and is executed based on a process that integrates higher-level conceptual items when lower-level conceptual items exist. A program characterized by the following features.

9. The program according to claim 6, The aforementioned priority rules determine the items to be adopted after integration and their display order based on at least one of the following: medical department, in-house protocol, urgency, severity, timeline, or deadline. A program characterized by the following features.

10. The program according to claim 6, The aforementioned priority rules are maintained as a set of rules that can be switched for each facility or each clinical department. A program characterized by the following features.

11. The program according to claim 1, The aforementioned integration process aggregates multiple sets of medical procedure items obtained separately before integration into a single ordered list, with items linked to the same concept being grouped into a representative item. A program characterized by the following features.

12. The program according to claim 1, The items constituting the aforementioned patient checklist are obtained, The event or record in the electronic medical record system and the item are compared based on matching conditions defined for each item. Based on the comparison results, the system automatically evaluates the implementation status of each of the above items and displays and / or saves the evaluation results. A program characterized by the following features.

13. The program according to claim 12, The matching conditions include at least one of the following: order type, order status, execution date and time, whether or not results have been registered, threshold value for the result, or prescription duration. A program characterized by the following features.

14. The program according to claim 12, The aforementioned status of implementation includes at least one of: not implemented, in progress, completed, pending, or overdue. A program characterized by the following features.

15. The program according to claim 12, The system will accept manual changes to the implementation status by medical personnel, and the reason for such manual changes and the operator will be recorded in the audit log. A program characterized by the following features.

16. The program according to claim 1, The approval process to confirm the completion of the aforementioned items will be submitted by an authorized medical professional. In response to the aforementioned approval operation, the items on the patient checklist are finalized and confirmed. The following information will be recorded as an audit log: the medical professional's approver identification information, approval time, target item identification information, and the status before and after confirmation. A program characterized by the following features.

17. L according to claim 16, The aforementioned approval process includes multi-stage approval according to the healthcare professional's occupation or role. A program characterized by the following features.

18. L according to claim 16, The audit log is maintained by at least one of hash chaining, digital signature, or WORM storage. The hash chain and the digital signature each maintain the audit log in a way that allows for detection of tampering. The WORM storage is a program characterized by making it impossible to overwrite or delete the data that has been written to it.

19. A program according to any one of claims 1 to 18, After generating the patient checklist, the system accepts user requests to change the order and / or remove items. To make the details of the operation known A program characterized by the following features.

20. An information processing method that realizes a function obtained by a computer executing a program according to any one of claims 1 to 18.

21. An information processing device having a function obtained by a computer executing a program according to any one of claims 1 to 18.

22. A computer-readable recording medium having a program according to any one of claims 1 to 18 recorded on it.

Images