Program, information processing method, and information processing device

Abstract

This program causes a computer to execute processing for: acquiring registration information including the usage history of a consumable used in a catheter treatment; and generating a report on the catheter treatment by providing the registration information and a catheter treatment report-creation instruction to a language model. Here, the time and date when identification information of the consumable is read and the identification information may be saved as registration information together with any of inventory, usage, and disposal information.

Description

Program, Information Processing Method, and Information Processing Apparatus

[0001] The present invention relates to a program, an information processing method, and an information processing apparatus.

[0002] Patent Document 1 discloses that a server acquires medical video information acquired by a video camera and medical information such as the voice of a medical practitioner regarding a procedure accompanying a medical act, and when the medical information meets the editing conditions selected by the medical practitioner, attaches bookmark information in association with a predetermined position over time of the medical video information.

[0003] Japanese Unexamined Patent Application Publication No. 2023 - 147256

[0004] In catheter treatment, a report is created that records the patient's condition and the usage status of consumables over time. However, in catheter treatment involving multiple people simultaneously, it has not been easy to create a report that accurately reflects the quantity of consumables used.

[0005] One aspect of the present disclosure provides a program or the like that can create a report of catheter treatment more easily and accurately.

[0006] (1) A program according to one aspect of the present disclosure is a program that causes a computer to execute a process of generating a report of the catheter treatment by acquiring registration information including a usage history of consumables used in the catheter treatment and providing the registration information and a report creation instruction of the catheter treatment to a language model.

[0007] (2) The program according to (1) above may generate the report by acquiring a captured image obtained during the treatment of the catheter treatment and providing the captured image and the acquisition date and time of the captured image to the language model.

[0008] (3) The program according to (2) above may generate a report of the catheter treatment by providing the captured image including an angiogram image to the language model.

[0009] (4) The program described in any of (1) to (3) above may generate the report by providing the language model with the electronic medical record information of the patient undergoing the catheter treatment, or vital data obtained during the catheter treatment.

[0010] (5) The program described in any of (1) to (4) above may generate the report by providing the registration information of the consumables, including balloons and stents, to the language model.

[0011] (6) The program described in any of (1) to (5) above may generate a report of the catheter treatment by providing the image captured during the catheter treatment to an image analysis learning model to detect the lesion, or the content related to the lesion recorded in the audio during the catheter treatment, along with the date and time on which the image captured or the content related to the lesion was recorded, to the language model.

[0012] (7) The program described in any of (1) to (6) above may generate the catheter treatment report by extracting the report with the same treatment name from a database in which the contents of past reports are stored and providing it to the language model.

[0013] (8) The program described in any of (1) to (7) above may store the date and time when the identification information of the consumables was read at any of the following times: when managing them as inventory, when using them, or when disposing of them, and the identification information, together with inventory, use, and disposal, as the registration information.

[0014] (9) The program described in any of (1) to (8) above may store as an extracted usage history the names and quantities of the consumables used, extracted based on the audio or images recorded during catheter treatment.

[0015] (10) The program described in any of (1) to (9) above may compare the extracted usage history and the usage history of the registered information and, if the consumables used during the catheter treatment do not match each other, display the extracted usage history or the registered information of the consumables that do not match.

[0016] (11) One aspect of the information processing method of the present disclosure is an information processing method that acquires registration information including the usage history of consumables used in catheter treatment, and generates a report of the catheter treatment by providing the registration information and a command to create a report of the catheter treatment to a language model.

[0017] (12) An information processing device in one aspect of the present disclosure is an information processing device comprising a control unit, the control unit acquiring registration information including the usage history of consumables used in catheter treatment, and generating a report of the catheter treatment by providing the registration information and a command to create a report of the catheter treatment to a language model.

[0018] One aspect of this disclosure is that it is possible to create reports on catheter treatment more easily and accurately.

[0019] This is a schematic diagram of the system according to the first embodiment of this disclosure. This is a block diagram showing an example of the configuration of a server device. This is a diagram showing an example of the configuration of a consumables management database. This is a diagram showing an example of the configuration of a catheter treatment report database. This is a block diagram showing an example of the configuration of a terminal device. This is a block diagram showing an example of the configuration of a generation server device. This is a block diagram showing an example of the configuration of a device connection terminal. This is a flowchart showing an example of the server device's identification code reception process. This is a flowchart showing an example of the catheter treatment report creation and display process. This is a flowchart showing an example of the catheter treatment report creation process according to the first embodiment. This is a diagram showing an example of the generation server device's process. This is a diagram showing an example of a prompt. This is a diagram showing an example of a generated catheter treatment report, etc. This is a diagram showing an example of the output screen for a catheter treatment report according to the first embodiment. This is a schematic diagram of the system according to the second embodiment of this disclosure. This is a block diagram showing an example of the configuration of an electronic medical record server device. This is a flowchart showing an example of the catheter treatment report creation process according to the second embodiment. This is a diagram showing an example of the output screen for a catheter treatment report according to the second embodiment.

[0020] The following describes in detail, with reference to the drawings, a system including an example of an information processing method, information processing device, and program relating to one aspect of this disclosure. In the description, similar elements are denoted by the same reference numerals, and redundant explanations are omitted as appropriate.

[0021] [Embodiment 1] Figure 1 is a schematic diagram of a system according to the first embodiment of the present disclosure. The system according to this embodiment includes an information processing device 1, an information processing terminal 2, a generation server device 4, and equipment in a catheter operating room 6. The information processing device 1, the information processing terminal 2, the generation server device 4, and the equipment connection terminal 66 in the catheter operating room 6 each transmit and receive information via a network 5 such as the Internet.

[0022] The equipment in the catheter operating room 6 includes an equipment connection terminal 66, a consumables code reader 61, a microphone 63, a camera 64, and a vital signs measuring device 65. The equipment connection terminal 66 is an information processing device that communicates with each of the consumables code reader 61, microphone 63, camera 64, and vital signs measuring device 65, and acquires the information output by each of them. In Figure 1, only one equipment connection terminal 66 is shown, but there may be multiple. For example, there may be one equipment connection terminal 66 for each of the consumables code reader 61, microphone 63, camera 64, and vital signs measuring device 65. Here, the consumables code reader 61 reads the code attached to the consumables 62.

[0023] The generation server device 4 has a language model 45 (Figure 6), such as a Large Language Model (LLM), stored in internal or external storage of the generation server device 4.

[0024] Information processing device 1 is an information processing device that processes, stores, and transmits various types of information. Information processing device 1 may be configured as, for example, a server device, a personal computer, a tablet terminal, or a smartphone. Information processing device 1 may be composed of multiple information processing devices, or it may be configured as one of multiple virtual devices (virtual machines) configured within a single information processing device. In this embodiment of the disclosure, to avoid complexity in the explanation, information processing device 1 will be read as server device 1. However, information processing device 1 is not limited to a server device and may be configured as any of the above-described types of information processing devices.

[0025] The information processing terminal 2 receives information output from the server device 1 via the network 5, accepts user input from the information processing terminal 2, and transmits information related to the input to the server device 1 via the network 5. The information processing terminal 2 can be, for example, a personal computer, smartphone, mobile phone, wearable device, or tablet. In this embodiment of the disclosure, to avoid complexity in the explanation, the information processing terminal 2 will be read and described as the terminal device 2.

[0026] Figure 2 is a block diagram showing an example configuration of the server device 1. The server device 1 can be an information processing device composed mainly of electronic circuits using semiconductor circuit elements. The server device 1 has a control unit 11, a communication unit 12, a reading unit 13, and a storage unit 14. The control unit 11, communication unit 12, reading unit 13, and storage unit 14 are connected to each other via a bus 19 or the like. Note that the server device 1 may have other configurations, such as not having a reading unit 13.

[0027] The control unit 11 can be configured to have one or more processing units such as a CPU (Central Processing Unit), MPU (Micro-Processing Unit), GPU (Graphics Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), and a quantum processor. The control unit 11 reads and executes the program (or program product) 16 stored in the storage unit 14.

[0028] The communication unit 12 is a communication module for performing communication-related processing and can send and receive information with terminal devices 2, etc., via the network 5. The reading unit 13 can read portable storage media 15 such as CD (Compact Disc)-ROM, DVD (Digital Versatile Disc)-ROM, and USB (Universal Serial Bus) memory. The control unit 11 may read the program 16 from the portable storage media 15 via the reading unit 13 and save it to the storage unit 14. Alternatively, the control unit 11 may download the program 16 from another computer via the network 5, etc., and save it to the storage unit 14.

[0029] The storage unit 14 includes volatile storage units such as RAM (Random Access Memory) and non-volatile storage units such as ROM (Read Only Memory), HDD (Hard Disk Drive), and flash memory. As shown in Figure 2, the storage unit 14 stores, for example, a program 16, a consumables management database 17, and a catheter treatment report database 18. The program 16 is a program executed by the control unit 11. The consumables management database 17 and the catheter treatment report database 18 will be described later. In this embodiment, the program 16 may also be referred to as a program product 16.

[0030] Figure 3 shows an example of the configuration of the consumables management database 17. As shown in this figure, the consumables management database 17 has fields for consumables name, identification code, date and time of receipt, date and time of use, and date and time of disposal. The consumables name field stores the name of the consumables 62. Consumables 62 may be medical devices such as balloons, stents, catheters, or guidewires, or liquids such as pharmaceuticals. The identification code field stores the individual identification code assigned to each consumable. The identification code can be a string of characters, a barcode or two-dimensional code that makes the string of characters readable by the consumables code reader 61, etc.

[0031] The "Date and Time of Entry" column stores the date and time when the consumable code reader 61 reads the identification code of the consumable 62 when it is placed in a shelf or other storage area for the consumable 62. The "Date and Time of Use" column stores the date and time when the consumable code reader 61 reads the identification code of the consumable 62 when it is used. The "Date and Time of Disposal" column stores the date and time when the consumable code reader 61 reads the identification code of the consumable 62 when the used consumable 62 or the container of the consumable 62 is disposed of. When disposing of consumables, a waste box equipped with a consumable code reader 61 may be used. This prevents consumables from being disposed of without being read by the consumable code reader 61. The "Date and Time of Disposal" column may also store the date and time when the identification code of the consumable 62 is read when it is disposed of due to expiration of the expiration date, etc.

[0032] If a single identification code includes multiple consumption units, for example, a sequential number may be added to the last three digits of the identification code so that each consumption unit becomes a separate record. Furthermore, the consumables management database 17 may store reader identification information, which is the identification information of a fixedly positioned consumables code reader 61, along with the date and time, so that the location where the identification code was read can be identified.

[0033] In this way, the server device 1 stores the date and time when the identification information of the consumable 62 is read, along with the identification information itself, as registered information, at one of the following times: when managing it as inventory, when using it, or when disposing of it. As a result, the date and time of use in catheter treatment is also managed, and this information can be provided for creating catheter treatment reports.

[0034] Figure 4 shows an example of the configuration of the catheter treatment report database 18. As shown in this figure, the catheter treatment report database 18 has fields for report identification information, patient name, height, weight, procedure / treatment name, and nursing record. The report identification information field is used to identify the catheter treatment report in the catheter treatment report database 18 and stores a unique string of characters for each record. The patient name field records the name of the patient for whom the catheter treatment report is based.

[0035] The height and weight fields should record the patient's height and weight, respectively. Other personal information included in the catheter treatment report may also be recorded. The procedure / treatment name field should record the string of characters found in the procedure or treatment name field of the catheter treatment report. The nursing record field should save the contents of the catheter treatment report as a string of characters, including line breaks. If the catheter treatment report format is standardized, fields may be created for items within the nursing record, and the corresponding strings may be recorded.

[0036] Figure 5 is a block diagram showing an example configuration of terminal device 2. Here, terminal device 2 can be an information processing device composed mainly of electronic circuits using semiconductor circuit elements. Terminal device 2 may have a control unit 21, a communication unit 22, a reading unit 23, a storage unit 24, a display unit 26, and an input unit 27. The components of the control unit 21, communication unit 22, reading unit 23, storage unit 24, display unit 26, and input unit 27 are connected to each other so as to be able to communicate with one another by a bus 29 or the like.

[0037] The control unit 21 can be configured to have one or more processing units such as a CPU, MPU, GPU, FPGA, DSP, and quantum processor. The control unit 21 reads and executes the program stored in the storage unit 24.

[0038] The communication unit 22 is a communication module for performing communication-related processing and can send and receive information with the server device 1, etc., via the network 5. The reading unit 23 can read portable storage media 25 such as CD-ROMs, DVD-ROMs, and USB memory sticks. The control unit 21 can read programs and / or data from the portable storage media 25 via the reading unit 23 and save them to the storage unit 24. The control unit 21 can also download programs from other computers via the network 5, etc., and save them to the storage unit 24.

[0039] The storage unit 24 includes volatile storage devices such as RAM, and non-volatile storage devices such as ROM, HDD, and flash memory. The display unit 26 can be a liquid crystal display or an organic EL display, etc. The input unit 27 can be an input device such as a keyboard, mouse, touch panel, and camera.

[0040] Figure 6 is a block diagram showing an example configuration of the generation server device 4. The generation server device 4 can be an information processing device composed mainly of electronic circuits using semiconductor circuit elements. The generation server device 4 has a control unit 41, a communication unit 42, a reading unit 43, and a storage unit 44. The reading unit 43 can read a portable storage medium 46. The components of the control unit 41, communication unit 42, reading unit 43, and storage unit 44 are connected to each other so as to be able to communicate with each other by a bus 49 or the like. Except for the contents stored in the storage unit 44, each of these components can be configured the same as the information processing device (server device) 1 in Figure 2, so redundant explanations are omitted. Note that the generation server device 4 may have other configurations, such as not having a reading unit 43, as in the case of server device 1.

[0041] The memory unit 44 can store the language model 45. The language model 45 consists of a program and training data, and the control unit 41 executes the program by referring to the input data and training data input from an external source. The language model 45 may be stored in a storage device or the like outside the generation server device 4, rather than in the memory unit 44.

[0042] The generation server device 4 is an information processing device that handles language models 45, such as large-scale language models (LLM: Large Language Model) like GPT (Generative Pre-trained Transformer, registered trademark), BERT (Bidirectional Encoder Representations from Transformer), and Gemini (trademark). The language models 45 may be stored in the storage unit 44 within the generation server device 4, or they may be stored in storage or the like that is communicated with the generation server device 4.

[0043] The generation server device 4 inputs input data such as images, audio, and text into the language model 45 and generates a response sentence. The language model 45 is a pre-trained machine learning model and can be a large-scale language model such as GPT or BERT, but other language models may also be used.

[0044] The server device 1 may be communicatively connected to the generation server device 4 via the network 5, or may be communicatively connected to the generation server device 4 directly or via a local network or the like without using the network 5. Further, the language model 45 may be provided in the storage unit 14 of the server device 1 without providing the generation server device 4. In this case, the server device 1 includes the functions of the generation server device 4. Since the generation server device 4 is a device that handles the language model 45, from the perspective of the server device 1, the server device 1 sending a prompt or the like to the generation server device 4 is expressed as the server device 1 sending (inputting) it to the language model 45.

[0045] FIG. 7 is a block diagram showing a configuration example of the device connection terminal 66. The device connection terminal 66 can be an information processing device mainly composed of an electronic circuit using semiconductor circuit elements. The device connection terminal 66 includes a control unit 661, a communication unit 662, a reading unit 663, a storage unit 664, a display unit 666, and an input unit 667. The configurations of the control unit 661, the communication unit 662, the reading unit 663, the storage unit 664, the display unit 666, and the input unit 667 are communicatively connected to each other by a bus 669 or the like. The reading unit 663 can read the portable storage medium 665. Since these configurations can be the same as those of the information processing terminal (terminal device) 2 in FIG. 5, duplicate descriptions are omitted.

[0046] Further, the communication unit 662 can communicate with the devices in the catheter operating room 6 via wired communication such as USB or wireless communication such as Bluetooth (registered trademark). For example, the device connection terminal 66 can acquire information by communicating with the consumable code reader 61, the microphone 63, the camera 64, and the vital sign measuring device 65. Further, the device connection terminal 66 is communicatively connected to the network 5, and can transmit the information acquired from the consumable code reader 61, the microphone 63, the camera 64, and the vital sign measuring device 65 to any one of the server device 1, the terminal device 2, and the electronic medical record server device 3.

[0047] The consumable code reader 61 reads the code attached to the consumable 62 at the timing when the consumable 62 is received, used, and discarded, etc. The read code is transmitted to the server device 1 via the device connection terminal 66 together with the state change type such as receipt, use, and discard. The code may be a barcode, a two-dimensional code, or other character strings. The consumable 62 can be a catheter, a wire, a stent, a balloon, physiological saline, an anesthetic, a vasodilator, a drug for thinning blood, a drug for emergency patient changes, and other consumables 62, etc.

[0048] The microphone 63 is a device for acquiring sound, and the camera 64 is a device for acquiring images inside the catheter operating room. The acquired sound and images are transmitted to the server device 1 via the device connection terminal 66. The vital sign measuring device 65 can include a measuring device for measuring blood pressure, pulse, and oxygen saturation, etc. The acquired measured values are transmitted to the server device 1 and the electronic medical record server device 3 via the device connection terminal 66. Also, although not shown, images of the treatment site taken by the treatment device during treatment, such as angiography images or tomographic images, etc., may also be transmitted to the server device 1 with or without passing through the device connection terminal 66.

[0049] FIG. 8 is a flowchart showing an example of the identification code reception process of the server device 1. As described above, the identification code is read by the consumable code reader 61 and transmitted to the server device 1 via the device connection terminal 66 and the network 5. As shown in the flowchart of FIG. 8, the server device 1 determines whether it has received the identification code (step S71). If it is determined that the identification code has not been received (step S71: NO), the process of step S71 is repeated.

[0050] If it is determined that an identification code has been received (Step S71: YES), the server device 1 obtains the status change type, such as receiving, using, or discarding (Step S72). Subsequently, it obtains the current date and time (Step S73) and saves it in the consumables management database 17 (Figure 3) (Step S74). The server device 1 stores the name of the consumable 62 in the "Consumable Name" column of the consumables management database 17. If the name of the consumable 62 includes the product name encoded in the identification code, the server device 1 can use the name obtained by analyzing the identification code. If the identification code does not include the product name, the server device 1 may, for example, use a publicly available database of identification codes to extract the product name and use it in the consumable name column.

[0051] Furthermore, the server device 1 stores the received identification code in the identification code column of the consumables management database 17. The server device 1 also stores the acquired current date and time as follows: if the received status change type is "received," it stores it as the receipt date and time; if the received status change type is "used," it stores it as the use date and time; and if the received status change type is "discarded," it stores it as the discard date and time. In this way, the registration information in the consumables management database 17 includes the usage history of the consumables 62 used in catheter treatment.

[0052] Figure 9 is a flowchart illustrating an example of the process for creating and displaying reports for catheter treatment. Terminal device 2 is located, for example, in the operating room or medical institution where the catheter treatment is performed. As shown in this flowchart, terminal device 2 transmits a message to server device 1 to initiate catheter treatment based on user input (step S11). Upon receiving the message to initiate catheter treatment, server device 1 creates a folder for saving various data to be sent to the device connection terminal 66 (step S12).

[0053] During catheter treatment, the device connection terminal 66 transmits various data received from the consumable code reader 61, microphone 63, camera 64, and vital sign measuring device 65 to the server device 1 via the network 5. The server device 1 stores the various data received from the device connection terminal 66 (step S13). When the catheter treatment is completed, the terminal device 2 transmits a message to the server device 1 indicating the completion of the catheter treatment based on the user's operation (step S16).

[0054] When server device 1 receives notification that the catheter treatment has been completed, it starts the process of creating a catheter treatment report (step S17). Once the process of creating the catheter treatment report is completed, it sends the created catheter treatment report and the differences in the usage status of consumables 62 to terminal device 2 (step S18). Upon receiving the catheter treatment report, terminal device 2 displays the catheter treatment report and the differences in the usage status of consumables 62 on the display unit 26 (step S19).

[0055] Figure 10 is a flowchart showing an example of the catheter treatment report creation process according to the first embodiment. In the catheter treatment report creation process, the server device 1 acquires records from the consumables management database 17 (step S31). The records from the consumables management database 17 may be data extracted from the consumables management database 17 within the range that includes the time period during which the target catheter treatment was performed. Alternatively, if the consumables management database 17 includes reader identification information for the consumables code reader 61, the data can be further narrowed down by the reader identification information to extract the consumables 62 used at the location where the catheter treatment was performed.

[0056] Next, the server device 1 determines whether vital data exists (step S33). Here, vital data may include any or all of (systolic and diastolic) blood pressure, pulse rate, and oxygen saturation. If the server device 1 determines that vital data exists (step S33: YES), it saves a record indicating that vital data exists (step S34).

[0057] After completing the process in step S34, or if the server device 1 determines that there is no vital data (step S33: NO), the server device 1 determines whether there is an audio or image file (step S36). Here, the image file may be either a video or a still image. If the server device 1 determines that there is an audio or image file (step S36: YES), it saves an extracted usage history, which is obtained by extracting the use and usage time of the consumable 62 from the information based on the audio or image (step S37). The audio file may include audio recorded during treatment. The image file may be, for example, an angiography image, an operating room image, or a tomography image taken during treatment.

[0058] In catheter treatment, when using drugs and medical devices, the name and quantity of the drug and medical device to be used are confirmed aloud as the treatment progresses. Therefore, this information is extracted from the content recorded in the audio or image (video) file and stored separately as an extracted usage history in addition to the information in the consumables management database 17. A dedicated learning model that has been pre-trained on the audio or images of catheter treatment can be used to obtain the extracted usage history. The dedicated learning model may be stored in the server device 1, or it may be stored in an information processing device connected to the network 5, etc. The audio-based information may be the audio itself or the audio converted to text. The audio may also be audio contained in a video.

[0059] After completing the process in step S37, or if the server device 1 determines that there are no audio or image files (step S36: NO), the server device 1 creates a prompt (step S39). The prompt will be described in detail in the explanation of Figure 11. Once a prompt is created, the server device 1 inputs the created prompt into the language model 45 and obtains the catheter treatment report and the usage status of consumables 62 from the language model 45 (step S40).

[0060] Next, if there is an extraction usage history, the extraction usage history is compared with the usage status of the acquired consumables 62, the difference is obtained (step S41), and the catheter treatment report creation process is terminated. If the extraction usage history and the usage status of the consumables 62 are not compared, the process in step S41, and the processes in steps S36 and S37 may be omitted.

[0061] As described above, the server device 1 acquires registration information, including the usage history of consumables 62 used in catheter treatment, and generates a catheter treatment report by providing the language model 45 with the registration information and a command to create a catheter treatment report. As a result, a catheter treatment report based on the usage history of consumables 62 recorded by reading by the consumable code reader 61 can be obtained, allowing users to create catheter treatment reports more easily and accurately.

[0062] Furthermore, in this configuration, vital data acquired during catheter treatment is provided to the language model 45 to generate a report, resulting in a catheter treatment report that is easier to understand in terms of the patient's condition progression.

[0063] Figure 11 is a flowchart showing an example of processing by the generation server device 4. In step S40 of Figure 10, the server device 1 sends a prompt to the generation server device 4, inputting the prompt to the language model 45 and creating a catheter treatment report and extraction usage history. In creating catheter treatment reports, the generation server device 4 can obtain similar reports, which are similar catheter treatment reports, from the catheter treatment report database 18, which stores past catheter treatment reports.

[0064] As a result, the generation server device 4 can create a catheter treatment report using the language model 45, referencing the acquired similar reports. In this case, the acquisition of similar reports may be done using RAG (Retrieval-Augmented Generation) technology, which combines information from an external knowledge base. Furthermore, when the server device 1 creates a prompt, by adding phrases such as "If there are similar reports, please refer to them when creating the report" to the prompt, it is possible to execute a process that acquires and references similar reports.

[0065] For example, as shown in Figure 11, the generation server device 4 determines whether it has received a prompt (step S81). If the generation server device 4 determines that it has not received a prompt (step S81: NO), it repeats the process in step S81. If the generation server device 4 determines that it has received a prompt (step S81: YES), it requests a similar report from the catheter treatment report database 18 of the server device 1 (step S82).

[0066] Similar catheter treatment reports may be determined by matching or similarity of one or more of the "procedure" or "treatment name," for example. The "procedure" or "treatment name" may be entered by the user of terminal device 2 when transmitting the start of catheter treatment in step S11 of Figure 9. This allows the generation server device 4 to compare the "procedure" or "treatment name" of the catheter treatment report to be created with the "procedure / treatment name" of the catheter treatment report stored in the catheter treatment report database 18. A vectorized catheter treatment report database 18 may be used for similarity determination.

[0067] The generation server device 4 determines whether it has received a similar report from the server device 1 (step S83). If the generation server device 4 determines that it has received a similar report (step S83: YES), it adds a prompt to indicate that it will create a catheter treatment report using the similar report as a reference (step S87). After the processing in step S87, or if it determines that it has not received a similar report (step S83: NO), the generation server device 4 inputs a prompt to the language model 45 and retrieves the created catheter treatment report (step S88).

[0068] Finally, the generation server device 4 transmits the acquired catheter treatment report, etc., to the server device 1 (step S89). In this way, the server device 1 can generate catheter treatment reports, etc., using a language model 45 that references a database in which the contents of past catheter treatment reports, etc., are stored. This makes it possible to create catheter treatment reports, etc., that follow the entries of past reports. Note that the generation server device 4 may also create catheter treatment reports, etc., without acquiring similar reports.

[0069] Figure 12 shows an example of a prompt. As shown in this figure, the prompt includes the items "Role," "Task," "Important Points," and "Encouragement." The prompt does not have to include all of these items, or it may include other items. The "Role" item describes the role assigned to the language model 45, and in this form it is "You are an excellent medical clerk."

[0070] A task is an item that instructs the language model 45 on what it needs to do, and in this form, three tasks are described. The first task is to "create a nursing record according to the 'example nursing record' based on information about the drugs and consumables of medical devices used in the catheter treatment, as well as vital data." The second task is to "extract information about the drugs from the nursing record you have created." The third task is to "extract information about the medical devices from the nursing record you have created." Here, the "nursing record" is included in the catheter treatment report.

[0071] Here, information on consumables 62 of drugs and medical devices used in catheter treatment can be the information stored in the consumables management database 17 of the server device 1. Vital data can be the information measured by the vital sign measuring device 65 stored in the data receiving folder of the server device 1. If vital data is not available, the first task of the prompt can use one that does not contain vital data. "Important matters" should contain notes and other information covering the entire process of creating the referral letter, and "encouragement" should contain encouragement for the language model 45.

[0072] Figure 13 shows an example of a generated catheter treatment report. In step S40 of Figure 10, the server device 1 acquires the catheter treatment report and the usage status of consumables 62. Figure 13 is an example of a catheter treatment report and the usage status of consumables 62, and consists of items for the catheter treatment report (nursing record) and the usage status of consumables 62 (drug information and medical device information). The nursing record shown here is created based on the usage date and time, the name of the consumable 62, and vital data from the consumables management database 17.

[0073] In this configuration, the nursing record includes the time, followed by the vital data obtained (systolic / diastolic) blood pressure, pulse rate, and oxygen saturation, and finally, the type and quantity of the 62 consumables (drugs and medical devices) used. Here, the nursing record includes terms such as "intracoronary artery" or "intravenous injection," which are not recorded in the consumables management database 17. These terms are added by the language model 45 based on similar past reports. If similar reports are not referenced, only the names of the 62 consumables are recorded in the nursing record.

[0074] Furthermore, the drug information and medical device information fields record the name and quantity of the drug and medical device when their use is confirmed. If the same medical device is used multiple times or the same drug is used multiple times, the records may be repeated multiple times, or the total may be recorded. The consumables management database 17 stores a separate record for each unit of use of each drug and medical device, so if a large quantity is used, the date and time of use will be recorded for multiple records. In Figure 13, drugs are listed in order of use along with the amount used, and the total number of medical devices used is recorded.

[0075] Furthermore, if vital data is not present in the data receiving folder of server device 1, the recording of vital data, such as blood pressure, pulse rate, and oxygen saturation, may be omitted. Vital data is recorded at predetermined intervals, and may also be recorded at these predetermined intervals in the catheter treatment report.

[0076] As described above, the server device 1 can generate catheter treatment reports by using the generation server device 4 to extract reports with the same treatment name, etc., from a database where the contents of past reports are stored, and providing them to the language model 45. This allows the server device 1 to refer to reports with the same treatment name, etc., and to create reports by supplementing them with information such as how consumables 62 were used.

[0077] Figure 14 shows an example of the output screen 91 of a catheter treatment report according to the first embodiment. The output screen 91 of the catheter treatment report is a screen that the terminal device 2 displays on the display unit 26 based on information transmitted from the server device 1 to the terminal device 2. As shown in this figure, the output screen 91 of the catheter treatment report has a nursing record display area 911, a consumable quantity confirmation area 912, and a confirmation button 916.

[0078] The nursing record display area 911 is an area that displays the contents of the nursing record acquired by the server device 1. Following the time display, it sequentially displays vital data such as (maximum / minimum) blood pressure, pulse rate, and oxygen saturation, and then displays the type and quantity of the consumables (drugs and medical devices) 62 that were last used. The consumable quantity confirmation area 912 is an area that displays the comparison results of the extracted usage history in step S41 of Figure 10 and the registered information of the consumable management database 17. In this embodiment, the amount of drugs used and the number of medical devices used are displayed separately in the drug usage area 913 and the number of medical devices used area 914, respectively. However, the amounts of drugs and medical devices used may be displayed together without separating the drug usage area 913 and the number of medical devices used area 914. If the confirmation of the consumable quantity is not displayed, the consumable quantity confirmation area 912 may be omitted. The confirmation button 916 is a button to return to the previous screen.

[0079] The drug usage area 913 may also have a button 9131 for playing audio / image files when a drug is used, in addition to showing the results of comparing the extracted usage history with the registered information in the consumables management database 17. The button 9131 for playing audio / image files when a drug is used will play an audio or image file when the drug (heparin in Figure 14) is used during catheter treatment, when there is a difference between the extracted usage history and the registered information in the consumables management database 17, by touching or other operation.

[0080] For example, if the amount of drug used determined by the analysis of audio / image files (text or image) differs from the amount used by the consumable code reader 61, the server device 1 refers to the record for that drug in the consumable management database 17 and extracts the usage times in which the usage time in the record does not match the usage time extracted by the analysis of the audio / image files. The server device 1 accepts the operation of the audio / image file playback button 9131 and can play the audio / image files around the extracted mismatched usage times. This allows the user to easily check the instances where discrepancies occur between the extracted usage history and the registered information in the consumable management database 17.

[0081] Furthermore, the drug usage area 913 can show the drugs used based on the registration information in the consumables management database 17, and is shown in Figure 14 as the record 9132 by the consumables code reader. This allows for a quick overview of drug usage. This configuration also addresses the possibility of miscounting drug usage. Therefore, for example, insurance claims related to drugs can be processed accurately and without omissions.

[0082] The medical device usage count area 914, like the drug usage amount area 913, displays the results of comparing the extracted usage history with the registered information in the consumables management database 17, and may also have an audio / image file playback button 9141 for when the medical device was used. The audio / image file playback button 9141 for when the medical device was used plays an audio or image file when the medical device (sheath in Figure 14) was used during catheter treatment, when there is a difference between the extracted usage history and the registered information in the consumables management database 17, via touch or other operation.

[0083] For example, if the number of medical device uses determined by the analysis of audio / image files (text or image) differs from the number of uses determined by the consumable code reader 61, the server device 1 refers to the record for the medical device in the consumable management database 17 and extracts the usage times in which the usage time in the record does not match the usage time extracted by the analysis of the audio / image files. The server device 1 accepts the operation of the audio / image file playback button 9141 and can play the audio / image files around the extracted mismatched usage times. This allows the user to easily check the instances where discrepancies occur between the extracted usage history and the registered information in the consumable management database 17.

[0084] Furthermore, the medical device usage count area 914 can show the medical devices that have been used, based on the registration information in the consumables management database 17, and is shown in Figure 14 as the record 9142 by the consumables code reader. This allows for a list of the number of medical devices used. This configuration also addresses the possibility of miscounting medical device usage. Therefore, for example, insurance claims related to medical devices can be made accurately and without omission.

[0085] As described above, the server device 1 stores the names and quantities of consumables 62 used, extracted based on audio or images recorded during catheter treatment, as an extracted usage history. The server device 1 also compares the extracted usage history with the usage history of registered information, and if the consumables 62 used during catheter treatment do not match, it displays the extracted usage history or registered information of the mismatched consumables 62. This allows for a comparison of the usage and quantity of consumables 62 between the registered information and the extracted usage history. If there is no difference in the quantity used, the correct quantity can be determined, and if there is a difference, the cause of the difference can be identified, thus enabling more accurate management of the quantity of consumables 62.

[0086] This output screen 91 allows users to easily create nursing record sections included in catheter records. Furthermore, regarding the quantity of consumables 62 such as drugs and medical devices used in catheter treatment, a more accurate quantity can be recorded by comparing the extracted usage history with the consumables management database 17.

[0087] [Embodiment 2] Figure 15 is a schematic diagram of a system according to the second embodiment of the present disclosure. The system according to this embodiment includes an information processing device 1, an information processing terminal 2, an electronic medical record server device 3, a generation server device 4, and equipment in a catheter operating room 6. The hardware configuration of the system according to the second embodiment of the present disclosure is the same as that of the first embodiment except that it has an electronic medical record server device 3, so a description of the configuration other than the electronic medical record server device 3 will be omitted.

[0088] Figure 16 is a block diagram showing an example configuration of the electronic medical record server device 3. The electronic medical record server device 3 can be an information processing device composed mainly of electronic circuits using semiconductor circuit elements. The electronic medical record server device 3 has a control unit 31, a communication unit 32, a reading unit 33, and a storage unit 34. The reading unit 33 can read a portable storage medium 35. The components of the control unit 31, communication unit 32, reading unit 33, and storage unit 34 are connected to each other so as to be able to communicate with each other by a bus 39 or the like. Except for the contents stored in the storage unit 34, each of these components can be configured the same as the information processing device (server device) 1 in Figure 2, so redundant explanations are omitted. Note that the electronic medical record server device 3 may have other configurations, such as not having a reading unit 33, as in the case of server device 1.

[0089] The storage unit 34 stores the medical record database 36. The medical record database 36 stores the patient's medical record information. The medical record information includes information such as the diagnosis entered by the doctor during the examination, and various test results are stored along with the date and time. Alternatively, the medical record database 36 may be stored in the storage unit 14 of the server device 1 without providing an electronic medical record server device 3. In this case, the server device 1 includes the functions of the electronic medical record server device 3.

[0090] In the second embodiment, the process of creating and displaying catheter treatment reports can be represented by a flowchart similar to the example in Figure 9 of the first embodiment, so redundant explanations are omitted. Figure 17 is a flowchart showing an example of the catheter treatment report creation process according to the second embodiment. In the catheter treatment report creation process according to the second embodiment, the server device 1 acquires records from the consumables management database 17 (step S51). The process in step S51 is the same as the process in step S31 of the first embodiment, so redundant explanations are omitted.

[0091] Next, the server device 1 determines whether vital data exists (step S52). Here, vital data may include blood pressure, pulse rate, and oxygen saturation, or any or all of them. If the server device 1 determines that vital data exists (step S52: YES), it saves a note indicating that vital data exists (step S53).

[0092] After completing the process in step S53, or if the server device 1 determines that there is no vital data (step S52: NO), the server device 1 determines whether there is an audio file (step S55). If the server device 1 determines that there is an audio file (step S55: YES), it saves an extracted usage history, which is obtained by extracting the use and usage time of the consumable 62 from the information based on the audio (step S56).

[0093] The acquisition of the extracted usage history is the same as in Figure 10 (step S37) of the first embodiment, so redundant explanations will be omitted. In this embodiment, the extracted usage history is acquired based on an audio file, but as in Figure 10 of the first embodiment, the extracted usage history may also be acquired from an image (video) file. In this embodiment, the extracted usage history is obtained by extracting the use and time of use of the consumable 62 from the audio, but it may also be possible to save each procedure and other events that occurred during catheter treatment, along with the time the procedure was performed, from the audio (or video).

[0094] Furthermore, if information indicating the presence of a lesion is detected from the audio, the date and time the lesion was detected and the details of the lesion are saved in text format (step S57). Here, the audio-based information may be the audio itself or the audio converted into text. The lesion may also include plaque or hematoma.

[0095] After completing the process in step S57, or if the server device 1 determines that there is no audio file (step S55: NO), the server device 1 determines whether there is an image file (step S58). Here, the image file may be either a still image or a moving image. If the server device 1 determines that there is an image file (step S58: YES), it analyzes the image file, and if a lesion is detected, it saves the date and time of detection and the type of lesion in text format (step S59).

[0096] For lesion detection, a dedicated image analysis learning model that has been pre-trained on images of lesions treated with catheters can be used. The dedicated image analysis learning model may be stored in server device 1, or it may be stored in an information processing device connected to network 5, etc. The lesions may include plaque or hematoma.

[0097] After completing the process in step S59, or if the server device 1 determines that there are no image files (step S58: NO), the server device 1 retrieves the patient's medical record information from the medical record database 36 of the electronic medical record server device 3 (step S61). The medical record information may include tomographic images from the previous catheter treatment. Subsequently, the server device 1 creates a prompt (step S62).

[0098] In addition to what is explained using Figure 12, the prompts include, for example, "4. If there are lesions, please describe the condition of the lesions in the 'Report on Lesions, etc.' section. If there is information on the same location from past treatments or examinations, please compare and explain." Such descriptions allow for output comparing the lesions detected from audio or images with past information stored in, for example, medical record information. In this configuration, the "Report on Lesions, etc." is generated as part of the catheter treatment report.

[0099] When server device 1 creates a prompt, it inputs the created prompt into language model 45, and from language model 45 obtains a report on catheter treatment, including nursing records and reports on lesions, as well as the usage status of consumables 62 (step S63). Here, as in the first embodiment, when obtaining the catheter treatment report and extracted usage history from language model 45, generation server device 4 or server device 1 may obtain and refer to similar past reports (Figure 11).

[0100] The server device 1 compares the extracted usage history with the records in the acquired consumables management database 17, obtains the difference in the usage status of the consumables 62 (step S64), and terminates the catheter treatment report creation process. Here, in the second embodiment as well, a process of acquiring and referring to similar reports may be performed, similar to the process of the generation server device 4 in Figure 11 of the first embodiment.

[0101] As described above, the server device 1 acquires images taken during catheter treatment and provides the language model 45 with the images and the date and time of acquisition of the images to generate a report on the catheter treatment, including reports on lesions, etc. The images taken here may include angiography images. This allows users such as doctors to check not only nursing records but also lesions, etc., detected from the images by the learning model, etc.

[0102] Furthermore, the server device 1 acquires registration information, including the usage history of consumables 62 used in catheter treatment, and generates a catheter treatment report by providing the language model 45 with the registration information and a command to create a catheter treatment report. As a result, a catheter treatment report based on the usage history of consumables 62 recorded by reading by the consumable code reader 61 can be obtained, allowing users to create catheter treatment reports more easily and accurately. Here, consumables 62 may include balloons and stents.

[0103] Figure 18 shows an example of the catheter treatment report output screen 92 according to the second embodiment. The catheter treatment report output screen 92 is a screen that the terminal device 2 displays on the display unit 26 based on information transmitted from the server device 1 to the terminal device 2. As shown in this figure, the catheter treatment report output screen 92 has a nursing record display area 921, a consumable quantity confirmation area 922, a confirmation button 926, and a lesion report area 925.

[0104] The nursing record display area 921 is an area that displays the contents of the nursing record (catheter treatment report) acquired by the server device 1, similar to the output screen 91 in Figure 14. It differs from the output screen 91 in Figure 14 in that it includes entries other than the record of consumables 62, such as "ACT test performed." As described above, if the audio or video file is analyzed and saved along with the time the procedure or other event occurred during catheter treatment, the server device 1 or the generating server device 4 may add or supplement entries other than the record of consumables 62 to the nursing record. In this case, the nursing record will be updated chronologically for each procedure or other event that occurred, along with the entry regarding the use of consumables 62.

[0105] The consumable quantity confirmation area 922, like the consumable quantity confirmation area 912 in Figure 14, has a drug usage area 923 and a medical device usage area 924. The drug usage area 923, the audio / image file playback button 9231 for drug use, the recording by the consumable code reader 9232, the medical device usage area 924, the audio / image file playback button 9241 for medical device use, the recording by the consumable code reader 9242, and the confirmation button 926 each have the same functions and content as the corresponding areas in Figure 14, so redundant explanations are omitted.

[0106] Furthermore, the output screen 92 in Figure 18 differs from the output screen 91 in Figure 14 in that it has a lesion / other reporting area 925. The lesion / other reporting area 925 is an area that displays the content output by the language model 45 in response to the prompt, such as "4. If there are any lesions, please describe the condition of the lesion in the 'Reporting Lesions / Others' section. If there is information on the same location from past treatments or examinations, please compare and explain."

[0107] The lesion reporting area 925 is displayed as part of the catheter treatment report. The lesion reporting area 925 displays lesions detected from audio or images. It also displays information comparing the lesion with past information stored in the medical record, for example. For example, in Figure 18, it displays, "Compared to the previous IVUS image in the medical record, there is a shadow in the IVUS image that may be a hematoma," prompting the user, such as a physician, to confirm whether it is a hematoma.

[0108] As described above, a report on the catheter treatment is generated by feeding the images obtained during catheter treatment to an image analysis learning model, detecting lesions, or recordings related to lesions in audio during catheter treatment, along with the date and time the images or content related to lesions were recorded, and feeding these to a language model 45. This allows users such as doctors to check not only nursing records but also lesions detected from images by the learning model, etc.

[0109] Furthermore, the server device 1 generates a report on catheter treatment by providing the electronic medical record information of the patient undergoing catheter treatment to the language model 45. This allows users, such as doctors, to review reports on lesions, etc., by referring to past information on the site where the lesion was found.

[0110] Furthermore, the server device 1 acquires registration information, including the usage history of consumables 62 used in catheter treatment, and generates a catheter treatment report by providing the language model 45 with the registration information and a command to create a catheter treatment report. As a result, a catheter treatment report based on the usage history of consumables 62 recorded by reading by the consumable code reader 61 can be obtained, allowing users to create catheter treatment reports more easily and accurately.

[0111] Furthermore, using output screens 91 or 92, users can easily create, for example, nursing record sections included in catheter records. In addition, regarding the quantity of consumables 62 such as drugs and medical devices used in catheter treatment, a more accurate quantity can be recorded by comparing the extracted usage history with the consumables management database 17.

[0112] In the above-described configuration, the server device 1, terminal device 2, electronic medical record server device 3, and generation server device 4 are described as being composed of different information processing devices, but some or all of them may be composed of a single information processing device.

[0113] In the above configuration, program 16 is executed on server device 1, but part or all of program 16 may be executed on terminal device 2, electronic medical record server device 3, or generation server device 4. Also, any or all of the functions of terminal device 2, electronic medical record server device 3, and generation server device 4 may be executed on server device 1. Furthermore, program 16 can be referred to as a program product, software, or software product, which may be provided on a recording medium or distributed via a communication network.

[0114] The forms of this disclosure are illustrative in all respects and not restrictive. The scope of the invention is not limited to those shown in the above disclosure but is shown by the claims, and all modifications within the meaning and scope of the equivalents of the claims are intended.

[0115] Furthermore, the sequences shown in each embodiment described above are not limited, and within a reasonable scope, the order of each processing step may be changed, and multiple processes may be executed in parallel. The processing entity for each process is not limited, and within a reasonable scope, the processing of each device may be executed by other devices.

[0116] The matters described in each embodiment can be combined with each other. Furthermore, the independent and dependent claims described in the claims can be combined with each other in any combination, regardless of the form of reference. In addition, although the claims do not use the form of a multi-claim that further references a multi-claim (multi-multi-claim), it may be a combination that uses the form of a multi-multi-claim that references all higher-level claims.

[0117] 1. Information Processing Device (Server Device) 11. Control Unit 12. Communication Unit 13. Reading Unit 14. Storage Unit 15. Portable Storage Medium 16. Program (Program Product) 17. Consumables Management Database 18. Catheter Treatment Report Database 19. Bus 2. Information Processing Terminal (Terminal Device) 3. Electronic Medical Record Server Device 4. Generation Server Device 5. Network 6. Catheter Operation Room 61. Consumables Code Reader 62. Consumables 63. Microphone 64. Camera 65. Vital Sign Measuring Device 66. Device Connection Terminal 91. Output Screen 911. Nursing Record Display Area 912. Consumables Quantity Confirmation Area 913. Drug Usage Area 9131. Audio / Image File Playback Button for Drug Use 9132. Recording by Consumables Code Reader 914. Medical Device Usage Area 9141. Audio / Image File Playback Button for Medical Device Use 9142. Recording by Consumables Code Reader 916 Confirmation button 92 Output screen 921 Nursing record display area 922 Consumable quantity confirmation area 923 Medication usage area 9231 Audio / image file playback button for medication use 9232 Recording by consumable code reader 924 Medical device usage area 9241 Audio / image file playback button for medical device use 9242 Recording by consumable code reader 925 Lesion / symptom reporting area 926 Confirmation button

Claims

1. A program that obtains registration information including the usage history of consumables used in catheter treatment, and causes a computer to execute a process to generate a report on the catheter treatment by providing the registration information and a command to create a report on the catheter treatment to a language model.

2. The program according to claim 1, which acquires images taken during the catheter treatment and generates the report by providing the images and the date and time of acquisition of the images to the language model.

3. The program according to claim 2, which generates a report of the catheter treatment by providing the captured images, including an angiography image, to the language model.

4. The program according to claim 1, which generates the report by providing the electronic medical record information of the patient undergoing the catheter treatment, or vital data obtained during the catheter treatment, to the language model.

5. The program according to claim 1, which generates the report by providing the registration information of the consumables, including balloons and stents, to the language model.

6. The program according to claim 1, which generates a report of the catheter treatment by providing the image captured during the catheter treatment to an image analysis learning model, the content related to the lesion recorded in the audio during the catheter treatment, along with the date and time on which the image captured or the content related to the lesion was recorded, to the language model.

7. The program according to claim 1, which generates a report of catheter treatment by extracting reports with the same treatment name from a database in which the contents of past reports are stored and providing them to the language model.

8. The program according to claim 1, which stores the date and time when the identification information of the consumables is read at any of the following times: when managing them as inventory, when using them, or when disposing of them, and the identification information, together with inventory, use, or disposal, as registration information.

9. The program according to claim 1, which extracts and stores as an extraction usage history the names and quantities of the consumables used, based on audio or images recorded during catheter treatment.

10. The program according to claim 9, which compares the extracted usage history and the usage history of the registered information, and displays the extracted usage history or registered information of the consumables used during the catheter treatment if they do not match.

11. An information processing method for generating a report on catheter treatment by acquiring registration information including the usage history of consumables used in catheter treatment, and providing the registration information and a command to create a report on the catheter treatment to a language model.

12. An information processing device comprising a control unit, wherein the control unit acquires registration information including the usage history of consumables used in catheter treatment, and generates a report of the catheter treatment by providing the registration information and a command to create a report of the catheter treatment to a language model.

Images