Blood bag management system

Abstract

To efficiently distribute blood bags. [Solution] The blood bag management system comprises multiple client terminals installed in each medical institution where blood bags with RFID media attached are stored, and a management server that stores unique information stored on the RFID media, information regarding the demand for blood bags at the medical institution, and location information of the medical institution. When the management server receives request data from a client terminal requesting a specific blood bag, it selects a blood bag that matches the request, selects the client terminal installed in the medical institution with the shortest delivery distance to the first medical institution from among the client terminals where the selected blood bag is registered, generates interrupt delivery data to execute delivery to the first medical institution, and stores as an interrupt delivery history that the selected blood bag has been delivered from the medical institution with the shortest delivery distance to the first medical institution to the first medical institution.

Description

Technical Field

[0001] The present invention relates to a blood bag management system.

Background Art

[0002] Patent Document 1 discloses a deployment system configured to procure parts from a warehouse such that the transportation time of the parts can be minimized when a stockout of the parts occurs.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Conventionally, in the management of blood bags, a method has been adopted in which blood bags are centralized and stored in a hub facility (blood center). However, there is a problem that a large amount of equipment investment is required to maintain and manage the hub facility.

[0005] In addition, in the method of centralized storage of blood bags in one place, there is a high risk that the stored blood bags will become unusable during a power outage or a natural disaster. Not only natural disasters, but also due to traffic conditions, etc., there is also a risk that it will be difficult to transport blood bags to the medical institutions that requested them.

[0006] In addition, unlike articles such as clothing and repair parts, individual management of blood bags is essential.

[0007] Therefore, it has been difficult to apply the deployment system disclosed in Patent Document 1 to the management of blood bags in the medical field.

[0008] Therefore, the present invention aims to reduce the risk of being unable to deliver blood bags and to efficiently distribute blood bags. [Means for solving the problem]

[0009] According to one aspect of the present invention, a plurality of client terminals are installed in each of the medical institutions where blood bags with RFID media attached are stored, and a management server stores unique information stored in the RFID media attached to the blood bag, information about the blood sealed in the blood bag, information about the demand for the blood bags at the medical institution, and location information of the medical institution, wherein the management server generates delivery data for executing delivery based on the information about the demand for the blood bags and the location information, and transmits it to each of the plurality of client terminals, and the management server is installed in one of the plurality of client terminals at the first medical institution. A blood bag management system is provided which, upon receiving request data from a client terminal requesting a specific blood, selects a blood bag that matches the information about the specific blood, selects a client terminal installed at the medical institution with the shortest delivery distance to the first medical institution from among the client terminals where the selected blood bag is registered, generates interrupt delivery data to deliver the selected blood bag to the first medical institution, transmits it to the selected client terminal, and stores as an interrupt delivery history that the selected blood bag has been delivered from the medical institution with the shortest delivery distance to the first medical institution to the first medical institution. [Effects of the Invention]

[0010] According to one aspect of the present invention, delivery data for delivering blood bags is generated based on information regarding the demand for blood bags and location information of medical institutions, and transmitted to a client terminal. This reduces the risk of being unable to deliver blood bags and allows for efficient distribution of blood bags compared to storing and managing blood bags in one location. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram illustrating a blood bag management system according to an embodiment of the present invention. [Figure 2] Figure 2 is a diagram illustrating the configuration of a client terminal installed at a blood center and a reader connected to the client terminal. [Figure 3] Figure 3 illustrates the storage list stored on the client terminal. [Figure 4] Figure 4 is a configuration diagram illustrating the management server. [Figure 5] Figure 5 illustrates the management list created on the management server. [Figure 6] Figure 6 illustrates the changes made to the management list on the management server. [Figure 7] Figure 7 is a flowchart illustrating the first process for generating delivery data on the management server. [Figure 8] Figure 8 is a flowchart illustrating the second process for generating delivery data on the management server. [Figure 9] Figure 9 is a flowchart illustrating the process of updating the management list on the management server. [Modes for carrying out the invention]

[0012] The forms described below are not limited to those shown in the brief description of the drawings.

[0013] A first aspect of one aspect of the present invention comprises a plurality of client terminals installed in each of the medical institutions where blood bags with RFID media attached are stored, and a management server which stores unique information stored in the RFID media attached to the blood bags, information about the blood sealed in the blood bags, information about the demand for the blood bags at the medical institution, and location information of the medical institution, wherein the management server generates delivery data for performing delivery based on the information about the demand for the blood bags and the location information, and transmits it to each of the plurality of client terminals, and the management server is installed in the first of the plurality of client terminals at the medical institution. This blood bag management system receives request data from a client terminal requesting a specific blood type, selects a blood bag that matches the information about the specific blood type, selects a client terminal located at the medical institution with the shortest delivery distance to the first medical institution from among the client terminals where the selected blood bag is registered, generates interrupt delivery data to deliver the selected blood bag to the first medical institution, transmits it to the selected client terminal, and stores as an interrupt delivery history that the selected blood bag was delivered from the medical institution with the shortest delivery distance to the first medical institution.

[0014] According to a first aspect of a certain embodiment of the present invention, a management server that stores unique information stored on an RFID medium, information regarding the demand for blood bags at a medical institution, and location information of the medical institution generates delivery data for delivering blood bags based on the information regarding the demand for blood bags and the location information of the medical institution, transmits it to a client terminal, and stores as an interrupt delivery history that the selected blood bags were delivered to the first medical institution from the medical institution with the shortest delivery distance to the first medical institution.

[0015] Therefore, according to the first aspect of the embodiments of the present invention, by using the generated delivery data, blood bags can be shared with each other even when they are distributed to each medical institution. This reduces the risk that blood bags cannot be delivered when they are stored and managed in one place, and enables the efficient circulation of blood bags. In addition, by storing the interrupt delivery history, the management server can prevent the creation and transmission of interrupt delivery data from looping for one blood bag due to the same request being generated from multiple client terminals for a specific blood bag.

[0016] A second aspect of an embodiment of the present invention includes a plurality of client terminals installed in each medical institution where blood bags with RFID media attached are stored, the unique information stored in the RFID media attached to the blood bags, the information regarding the blood enclosed in the blood bags, the information regarding the demand for the blood bags in the medical institutions, and a management server that stores the location information of the medical institutions. The management server generates delivery data for executing delivery based on the information regarding the demand for the blood bags and the location information, and transmits it to each of the plurality of client terminals. When the management server receives request data for requesting specific blood from a client terminal provided in a first medical institution among the plurality of client terminals, it selects a blood bag that matches the information regarding the specific blood, and selects a client terminal installed in a medical institution with the shortest delivery time to the first medical institution among the client terminals where the selected blood bag is registered. The management server generates interrupt delivery data for executing the delivery of the selected blood bag to the first medical institution and transmits it to the selected client terminal, and stores as an interrupt delivery history that the selected blood bag has been delivered from the medical institution with the shortest delivery time to the first medical institution to the first medical institution. This is a blood bag management system.

[0017] According to a second aspect of an embodiment of the present invention, when the management server receives request data for requesting specific blood from a first medical institution, interrupt delivery data for executing the delivery of the specific blood from the medical institution with the shortest delivery time is generated, transmitted to the client terminal, and the selected blood bag is delivered from the medical institution with the shortest delivery time to the first medical institution, which is stored as an interrupt delivery history.

[0018] Therefore, according to the second aspect of the embodiment of the present invention, by using the generated interrupt delivery data, the blood bag can be efficiently circulated. In addition, the management server can prevent the creation and transmission of interrupt delivery data from looping for one blood bag due to the same request from a plurality of client terminals for a specific blood bag by storing the interrupt delivery history.

[0019] A third aspect of an embodiment of the present invention is the blood bag management system according to the first or second aspect, wherein when the management server sets the use schedule of the specific blood bag in the extracted client terminal, the management server selects the next candidate client terminal, generates interrupt delivery data for executing the delivery of the specific blood bag to the first medical institution, and transmits the interrupt delivery data to the next candidate client terminal.

[0020] According to a third aspect of an embodiment of the present invention, when the management server receives request data for requesting a specific blood bag from a first medical institution, if the use schedule of the specific blood bag is set in the extracted medical institution with the shortest delivery distance or delivery time, interrupt delivery data for executing the delivery of the specific blood bag from the next candidate medical institution is generated.

[0021] Therefore, according to the third aspect of the embodiment of the present invention, by using the generated interrupt delivery data, the blood bag can be efficiently circulated.

[0022] A fourth aspect of a certain embodiment of the present invention is a blood bag management system according to any one of the first to third embodiments, wherein the information relating to the demand for the blood bags includes information relating to the past usage of the blood bags and information relating to the forecast of usage.

[0023] According to a fourth aspect of a certain embodiment of the present invention, delivery data is generated based on information regarding the past usage of blood bags and information regarding usage predictions.

[0024] Therefore, according to a fourth aspect of the present invention, blood bags can be efficiently distributed by using delivery data generated based on information regarding the actual usage of blood bags and information regarding usage predictions.

[0025] A fifth aspect of a certain embodiment of the present invention is a blood bag management system according to any one of the first to fourth embodiments, wherein each of the plurality of client terminals is connected to a storage unit equipped with a communication unit for the RFID medium, and the unique information is collected from the RFID medium of the blood bag stored in the storage unit.

[0026] According to a fifth aspect of a certain embodiment of the present invention, the client terminal is connected to a storage unit equipped with a communication unit for an RFID medium attached to a blood bag, so that the client terminal can detect when a blood bag is taken in or out of the storage unit.

[0027] Therefore, according to a fifth aspect of the present invention, when generating delivery data, inventory information of blood bags can be efficiently obtained, thereby enabling efficient distribution of blood bags.

[0028] A blood bag management system according to an embodiment of the present invention will be described below with reference to the drawings.

[0029] [Blood bag management system] <System Configuration> Figure 1 is a schematic diagram illustrating a blood bag management system 1 according to an embodiment of the present invention.

[0030] As shown in Figure 1, the blood bag management system 1 is a system configured by interconnecting client terminals 11, 21, 31, and 41 installed at the blood center 10 and medical institutions 20, 30, and 40, respectively, with a management server 50 for centralized management of these client terminals, via a network NW.

[0031] The blood bag P has an RFID label L attached to it, which is an RFID medium equipped with an antenna pattern and IC device compatible with RFID (Radio Frequency Identification) technology that transmits and receives information via contactless communication, and has an adhesive layer.

[0032] The contents of blood bag P include various types such as whole blood, red blood cells, plasma, and platelets, each with a different expiration date. Each RFID label L stores unique information, which allows for the identification of blood bag P.

[0033] In the blood bag management system 1, the blood centers 10, medical institutions 20, 30, and 40 registered in the blood bag management system 1 can equalize any surplus or shortage of blood bag P inventory by distributing blood bag P between them based on the blood bag P distribution data generated by the management server 50.

[0034] <Client terminal> Next, client terminals 11, 21, 31, and 41 will be described. Since the same client terminal can be used for blood center 10 and medical institutions 20, 30, and 40, client terminal 11 will be described below.

[0035] Figure 2 is a diagram illustrating the configuration of a client terminal 11 installed at the blood center 10 and a reader device 12 connected to the client terminal 11.

[0036] As shown in Figure 2, the client terminal 11 includes an input unit 111 that receives input from the operator, a display unit 112 that displays information for operation and delivery data of blood bags P, a processing unit 113, and a storage unit 114.

[0037] Furthermore, the client terminal 11 includes a connection interface 115 for connecting to a reader 12 for acquiring information from the blood bag P, and a network interface 116 for connecting to a network NW wirelessly or via a wired connection.

[0038] In this embodiment, the network NW is the so-called internet.

[0039] The input unit 111 and the display unit 112 may be an integrated touch panel.

[0040] The processing unit 113 is comprised of a CPU and controls the input unit 111, the display unit 112, the connection interface 115, and the network interface 116.

[0041] Furthermore, the processing unit 113 executes a program stored in the storage unit 114 to create a storage list that links the unique information of the RFID label L acquired by the reader 12 with information for identifying the client terminal 11. The storage list will be described later.

[0042] The memory unit 114 includes a ROM for storing various control programs and RAM as a work area for the CPU, and the memory unit 114 stores a storage list created by the processing unit 113.

[0043] The storage unit 114 can be an HDD (Hard Disk Drive) or an SSD (Solid State Drive), etc.

[0044] The client terminal 11 is connected via a connection interface 115 to a reader 12 that reads the RFID label L attached to the blood bag P.

[0045] As shown in Figure 2, in this embodiment, the reader 12 is a device in which a communication unit 122 for communicating with the RFID label L attached to the blood bag P is installed in a storage unit 121 that holds the blood bag P at a predetermined temperature.

[0046] The RFID label L used in this embodiment is a passive RFID that generates an induced electromotive force by receiving radio waves transmitted from the communication unit 122 of the reader 12. As an example, wireless communication using radio waves in the UHF band (frequency 860-960MHz) is used.

[0047] Therefore, the communication unit 122 can read the unique information of the blood bag from the RFID label L attached to the blood bag P stored in the storage unit 121.

[0048] By activating the communication unit 122 when the door of the storage unit 121 is opened or closed, unique information about the blood bags P stored in the storage unit 121 can be obtained.

[0049] In this embodiment, the IC device of the RFID label L stores the unique information (ID) of the RFID label L attached to the blood bag P.

[0050] A printable area is formed on the surface of the RFID label L, and blood bag information, including the type of blood bag P, the volume of blood bag P, the blood type of the blood sealed in the blood bag P, the expiration date, and other blood-related information necessary in a medical setting, may be printed on the RFID label L as text or a two-dimensional code using a printer capable of printing on the RFID label L.

[0051] In this embodiment, the IC device of the RFID label L may be capable of writing not only unique information (ID) but also the blood bag information and information regarding the planned use of the blood bag P as described above.

[0052] According to the RFID label L, the blood bag P to which the RFID label L is attached can be identified based on the unique information stored in the built-in IC device.

[0053] For example, the reader 12 detects the opening and closing of the storage unit 121, and activates the communication unit 122 at the moment when a blood bag P is inserted into or removed from the storage unit 121, thereby acquiring unique information from the RFID labels L of the blood bags P stored in the storage unit 121.

[0054] The reader 12 transmits unique information obtained from multiple RFID labels L to the client terminal 11. If a medical institution is not equipped with a reader 12 that includes a storage unit 121 and a communication unit 122, medical personnel may use a designated reader to read the two-dimensional code or IC device when placing the blood bag P in the storage unit.

[0055] On the client terminal 11, a process is executed to generate a storage list or to update a storage list based on the unique information of the acquired RFID label L.

[0056] Figure 3 illustrates the storage list stored on the client terminal 11.

[0057] As shown in Figure 3, the storage list associates the unique information (ID) of the RFID label L with information about the blood bag, including the type of blood bag P, the volume of blood bag P, the blood type of the blood sealed in the blood bag P, the expiration date, and other blood-related information necessary in the medical setting, along with information to identify the client terminal 11 (blood center 10) (e.g., location information). The storage list is stored in the memory unit 114.

[0058] In the storage list, some information, such as blood bag information, may be manually entered by the operator using the client terminal 11.

[0059] On the client terminal 11, the inventory of blood bags P stored in the storage unit 121 can be detected by executing a process to generate a storage list or a process to update the storage list.

[0060] The process of generating or updating the storage list may be performed each time blood bag information is transmitted from the reader 12 to the client terminal 11, or it may be performed periodically.

[0061] If the client terminal is installed in a medical institution, it can send request data to the management server 50 requesting a specific blood bag P that is in demand at the medical institution.

[0062] <Management Server> Next, we will describe the management server 50. Figure 4 is a configuration diagram illustrating the management server 50.

[0063] The management server 50 comprises a processing unit 151, a storage unit 152, and a network interface 153 for connecting to the network NW shown in Figure 1.

[0064] The processing unit 151 is comprised of the CPU.

[0065] The memory unit 152 includes ROM for storing various control programs and RAM as the CPU's work area. An HDD or SSD can be used as the memory unit 152.

[0066] In this embodiment, the management server 50 may include an input unit for receiving input from the operator and a display unit for displaying information for operation.

[0067] The management server 50 can, for example, perform machine learning using a so-called AI (Artificial Intelligence) system built into the processing unit 151 and the storage unit 152.

[0068] The management server 50 obtains storage lists from the blood center 10 or each of the medical institutions 20, 30, and 40 at predetermined times, and creates a management list for managing the blood bags P held by the facilities connected to the blood bag management system 1 based on the storage lists sent from the client terminals 11, 21, 31, and 41.

[0069] The creation of the management list by the management server 50 is implemented in the processing unit 151 as a management list creation module 154.

[0070] Figure 5 illustrates the management list created in the management list creation module 154. Figure 6 illustrates the management list that has been modified in the management list creation module 154.

[0071] The management lists shown in Figures 5 and 6 include the type of blood bag P, the volume of blood bag P, the blood type of the blood sealed in the blood bag P, the expiration date, information about the blood needed at the medical site (including status information such as planned use of blood bag P, in transit or preparing for transit), information to identify the medical institution (e.g., location information), status information, and a transfer flag. This information is associated with the unique information (ID) of the RFID label L and stored in the storage unit 152.

[0072] Furthermore, the memory unit 152 also stores information about multiple client terminals 11, 21, 31, and 41 installed in each medical institution where blood bags P with RFID labels L attached are stored, as well as unique information stored on the RFID labels L, information regarding the demand for blood bags P at medical institutions 20, 30, and 40, and location information of medical institutions 20, 30, and 40.

[0073] The management server 50 can generate delivery data for blood bags P by performing machine learning using an AI system. The generation of delivery data by the management server 50 is implemented in the processing unit 151 as a delivery data generation module 155.

[0074] In this embodiment, the delivery data generation module 155 generates delivery data for delivering blood bags P to each of the client terminals 11, 21, 31, and 41, based on information regarding the demand for blood bags P and location information of medical institutions.

[0075] Furthermore, the management server 50 calculates the minimum number of blood bags P required for each blood center 10 or each medical institution 20, 30, and 40 based on the usage history of each blood center 10 or each medical institution 20, 30, and 40, and generates or updates delivery data to maintain a predetermined inventory level.

[0076] In other words, the delivery data generation module 155 uses machine learning by an AI system to determine, based on information regarding the demand for blood bags P and the location information of medical institutions, how many blood bags P should be stored at which medical institution among the blood center 10 or each of the medical institutions 20, 30, and 40.

[0077] Based on the derived results, the delivery data generation module 155 generates delivery data for delivering blood bags P so that the required number of blood bags P are stored at the blood center 10 or at each of the medical institutions 20, 30, and 40.

[0078] Furthermore, the management server 50 can generate delivery data in the management list so that blood bags P with approaching expiration dates are used preferentially.

[0079] Furthermore, if there are blood bags P that are nearing the end of their lifespan, the management server 50 can decide whether to dispose of the blood bags P or transfer them to another medical institution, based on the transportation costs to transport them to a nearby medical institution and the availability of the blood bags P based on past usage records.

[0080] Furthermore, when the management server 50 receives request data for a specific blood bag P from a client terminal installed at the first medical institution among the multiple client terminals 11, 21, 31, and 41, it selects the blood bag P corresponding to the specific blood bag P from the management list and changes the status information of the blood bag P to "in transit" (see Figures 5 and 6). By changing the status information of the blood bag P while it is in transit, it is possible to prevent duplicate delivery data from being created for a single blood bag P. Also, once delivery is complete, the location information in the status information is rewritten to that of the medical institution to which it was delivered (see Figures 5 and 6).

[0081] In this embodiment, by changing the status information of the blood bag P during delivery, for example, if a medical institution attempts to remove a blood bag P that has been set to be in delivery from the storage unit 121, a warning sound may be emitted or the blood bag P set to be in delivery may be prevented from being removed.

[0082] The management server 50 selects the medical institution with the shortest delivery distance to the first medical institution from among the medical institutions where the selected specific blood bag P is stored, and generates interrupt delivery data to the client terminal installed at the selected medical institution to execute the delivery of the specific blood bag to the first medical institution.

[0083] In the above explanation, "interrupt delivery data" refers to data that instructs the delivery of blood bags that have been delivered from blood center 10 to medical institutions 20, 30, and 40, respectively, and have become part of the medical institutions' inventory, for transfer to other medical institutions.

[0084] In other words, for example, if the first medical institution is medical institution 40 in Figure 1, and medical institution 40 receives request data from the management server 50 requesting a blood bag P of blood type AB, the management server 50 extracts the medical institutions that store blood bag P of blood type AB from the management list. As an example, let's assume that medical institutions 20 and 30 are extracted.

[0085] Next, the management server 50 selects the medical institution 40 that has the shortest delivery distance. In this case, let's assume that medical institution 30 is selected. The management server 50 generates interrupt delivery data to deliver the AB blood bag P to medical institution 40, that is, to execute the delivery via route R1, and sends it to the client terminal 31 installed at medical institution 30.

[0086] When a blood bag P of type AB is delivered to the medical institution 40, the management server 50 detects the corresponding blood bag P in the storage unit 121 of the medical institution 40, and updates the management list to indicate that the blood bag P is in the inventory of the medical institution 40.

[0087] In another configuration, when the management server 50 receives request data for a specific blood bag P from a client terminal installed at the first medical institution among multiple client terminals 11, 21, 31, and 41, it selects a blood bag P corresponding to the specific blood bag P from the management list. Then, it selects the medical institution that has the shortest delivery time to the first medical institution from among the medical institutions where the selected specific blood bag P is stored, and generates interrupt delivery data to the client terminal installed at the selected medical institution to execute the delivery of the specific blood bag to the first medical institution.

[0088] In other words, for example, if the first medical institution is medical institution 20 in Figure 1, when medical institution 20 requests a blood bag P of blood type A from the management server 50 among medical institutions 20, 30, and 40, the management server 50 extracts the medical institutions that have blood bag P of blood type A stored from the management list. As an example, let's assume that blood center 10 and medical institution 40 are extracted.

[0089] The management server 50 then selects the medical institution that will have the shortest delivery time to the medical institution 20. In this case, let's assume that the blood center 10 is selected. The management server 50 generates interrupt delivery data to deliver the blood bag P of blood type A to the medical institution 20, that is, to execute the delivery via route R2, and sends it to the client terminal 11 installed at the blood center 10.

[0090] Furthermore, the management server 50 can also select the medical institution with the shortest delivery distance or the shortest delivery time, depending on the situation.

[0091] Furthermore, if a client terminal installed at a medical institution selected based on the shortest distance or shortest time has a scheduled use for the requested specific blood bag P, the management server 50 selects a second-choice client terminal and generates interrupt delivery data to deliver the specific blood bag P to the first medical institution at the second-choice client terminal.

[0092] In Figure 1, for example, medical institution 30 is selected as a medical institution capable of delivering blood bag P of blood type AB as requested by medical institution 40.

[0093] However, if medical institution 30 has scheduled to use blood bag P of blood type AB, or if the status information of blood bag P is set to "in transit", the management server 50 selects medical institution 20 which also stores blood bag P of blood type AB, generates interrupt delivery data to deliver blood bag P of blood type AB to medical institution 40, that is, to execute delivery via route R3, and sends it to the client terminal 21 installed at medical institution 20.

[0094] <First process for generating delivery data> Figure 7 is a flowchart illustrating the first process for generating delivery data in the management server 50.

[0095] As an example, let's consider a case where the management server 50 receives request data from a medical institution 40 requesting a blood bag P of type AB, and ultimately, the medical institution 30 delivers the blood bag P to the medical institution 40.

[0096] In step S1, the management server 50 receives request data from a client terminal 41 installed at medical institution 40 among the medical institutions 20, 30, and 40, requesting a blood bag P of type AB.

[0097] In step S2, the management server 50 performs a search process for the management list.

[0098] In step S3, once all data containing blood bag information for blood bag P of type AB has been extracted from the management list, the process proceeds to step S4.

[0099] In step S4, the management server 50 selects the medical institution from the extracted medical institutions 20 and 30 that has the shortest delivery distance to medical institution 40.

[0100] In step S5, when medical institution 30 is selected, the management server 50 generates interrupt delivery data to deliver the AB blood bag P to medical institution 40 and sends it to the client terminal 31 installed at medical institution 30.

[0101] Through the above process, the operator of the client terminal 31 that received the interrupt delivery data can arrange for the delivery of the AB blood bag P to the medical institution 40.

[0102] <Second process for generating delivery data> Figure 8 is a flowchart illustrating the second process for generating delivery data in the management server 50.

[0103] As an example, let's consider a case where the management server 50 receives request data from medical institution 40 requesting a blood bag P of type AB, and, taking into account the planned use, ultimately delivers the blood bag P from medical institution 20 to medical institution 40.

[0104] Steps S11 through S14 are the same. Specifically, when the management server 50 receives request data for type AB blood bag P from a client terminal 41 installed at the medical institution 40, it executes a search process for the management list and extracts all data from the management list that contain blood bag information related to type AB blood bag P.

[0105] The management server 50 selects medical institution 30 from the extracted medical institutions 20 and 30 as the medical institution with the shortest delivery distance to medical institution 40.

[0106] In the second process, in step S15, the management server 50 searches for the scheduled use of blood bag P of blood type AB. If the extracted blood bag P has a scheduled use, the management server 50 selects a medical institution 20 that also stores blood bag P of blood type AB.

[0107] In the following step S16, the management server 50 generates interrupt delivery data to deliver the blood bag P of blood type AB to the medical institution 40 and sends it to the client terminal 21 installed at the medical institution 20.

[0108] According to the above process, the operator of the client terminal 21 that received the interrupt delivery data can arrange for the delivery of the AB blood bag P to the medical institution 40. Furthermore, according to the second process, there will be no disruption to medical activities at the medical institution 30.

[0109] In the second process described above, for example, when delivery data is generated for delivering blood bags P from medical institution 20 to medical institution 40, the management server 50 updates the status information of blood bags P in the management list from "Inventory at medical institution 20" to "Inventory at medical institution 40". In Figures 5 and 6, this corresponds to the update of the status information for the ID-3100 blood bags.

[0110] However, if a request data for the blood bag P is sent to the management server 50 from another medical institution, it is possible that the blood bag P, which should be delivered from medical institution 20 to medical institution 40 at the request of medical institution 40 and used at medical institution 40, may be delivered to another medical institution. Therefore, to prevent this, a limit may be set on the number of times the blood bag P can be delivered from one medical institution to another, as part of the status information.

[0111] Figure 9 is a flowchart illustrating the process of updating the management list on the management server 50.

[0112] When the management server 50 generates delivery data for the blood bag P based on the request (step S5 or S16), it changes the status information to "in transit" as step S21.

[0113] When the management server 50 detects the blood bag P in the storage unit 121 of the destination medical institution (step S22: Yes), in step S23, it changes the location information in the status information of the management list to the destination medical institution and sets the transfer flag from 0 to 1 (see ID-3100 in Figures 5 and 6).

[0114] When the management server 50 searches for a requested blood bag P, it searches for blood bags P with the transfer flag set to 0. This prevents a blood bag P that should be used at a designated medical institution from being transferred to another medical institution. In other words, it prevents a loop of interrupt delivery data creation and transmission for a single blood bag P that occurs when multiple client terminals request the same specific blood bag P.

[0115] [Effects and Effects] According to the blood bag management system 1 of the present invention, the management server 50 generates delivery data for leveling the inventory of blood bags P at medical institutions based on unique information stored in the RFID label L, information on the demand for blood bags P at medical institutions such as the blood center 10 and medical institutions 20, 30, and 40, and location information of the medical institutions.

[0116] Each medical institution can use the delivery data generated on the management server 50 to exchange blood bags P with each other, even if they are stored in a distributed manner at each medical institution. This reduces the risk of blood bags becoming undeliverable due to centralized storage and management in one location, and enables the efficient distribution of blood bags.

[0117] Furthermore, this allows blood bags P, which were previously discarded without being used in medical institutions, to be efficiently distributed among medical institutions registered in the blood bag management system 1, thereby reducing the amount of blood bags P that are wasted.

[0118] Furthermore, since the distribution of blood bags P, which previously relied solely on blood center 10 as its base, can now be conducted among medical institutions 20, 30, and 40—a so-called ad-hoc distribution model—convenience is improved in terms of both delivery time and transportation costs.

[0119] Furthermore, according to the blood bag management system 1, if a situation arises where the number of blood bags P being handled at a medical institution such as the blood center 10, medical institutions 20, 30, and 40 is about to exceed the storage space capacity, the management server 50 can search for a medical institution with available storage space and send delivery data specifying the transfer destination to a client terminal located at the medical institution whose storage space capacity is being exceeded.

[0120] In this way, the blood bag management system 1 can comprehensively manage the inventory status of blood bags in the region where the medical institutions it manages are located, and can coordinate the delivery of blood bags P.

[0121] According to the blood bag management system 1 of this embodiment, when the management server 50 receives request data from a first medical institution requesting a specific blood bag P, it can generate interrupt delivery data instructing the medical institution with the shortest delivery distance to deliver the requested blood bag P, and transmit this data to a client terminal located at the relevant medical institution.

[0122] Furthermore, according to the blood bag management system 1, when the management server 50 receives request data from a first medical institution requesting a specific blood bag P, it can generate interrupt delivery data to deliver the requested blood bag P from the medical institution with the shortest delivery time and send it to a client terminal located at the relevant medical institution.

[0123] Thus, according to the blood bag management system 1, in order to instruct deliveries to equalize the surplus or shortage of inventory at each of the blood centers 10 and medical institutions 20, 30, and 40, in addition to the normally generated delivery data, when an urgent request is issued, interrupt delivery data is used to execute the delivery of blood bags P, taking into account the delivery time or delivery distance, thereby enabling the efficient distribution of blood bags.

[0124] The management server 50 can deliver blood bag P from a medical institution that does not have a scheduled use if a client terminal installed at a medical institution selected based on the shortest distance or shortest time has a scheduled use for the requested specific blood bag P. Therefore, even if there is a request for a blood bag P with high urgency, it will not disrupt medical activities at other medical institutions.

[0125] [Other embodiments] Although this embodiment has been described above, the above embodiment is merely one example of how the present invention can be applied, and it is not intended to limit the technical scope of the present invention to the specific configuration of the above embodiment.

[0126] The network NW may be the so-called internet, or it may be a proprietary network built for, for example, the blood bag management system 1.

[0127] The functions of the management list creation module 154 and the delivery data generation module 155 in the management server 50 may be provided in an AI system (cloud AI) built on the network NW. In this case, the management server 50 can receive the management list or delivery data as a result via the network NW by accessing the cloud AI built on the network NW.

[0128] For example, the demand for blood bags could be predicted by considering not only information between medical institutions but also weather conditions and upcoming events near medical institutions, and delivery data for blood bags could be generated based on the prediction results. This would allow for measures such as predicting increased demand due to disasters and moving blood bags to disaster-prone areas.

[0129] In this embodiment, in addition to the HF and UHF bands, applicable contactless communication bands can also include the LF band (frequency 135 kHz or less) as a band that enables NFC by electromagnetic induction, and the microwave band (frequency 2.45 GHz) as a band that enables wireless communication by radio waves.

[0130] In this embodiment, the search for blood bags P may be set to the time that the medical institution can wait for the blood bags P, rather than the "expiration date." Even if the management server 50 can extract blood bags P from the management list, it can exclude medical institutions that will not be able to use them in time, enabling efficient delivery.

[0131] In this embodiment, although not shown in Figure 1, a mobile terminal that can connect to the management server 50 may be provided at the blood collection site, allowing the management list to be updated based on the blood collection schedule or the type of blood collected. This makes it possible to deliver the blood bags P directly from the blood collection site to medical institutions that require them.

[0132] Furthermore, the management server 50 may determine, based on the predicted demand, how much "plasma" or "platelets" to produce from the stored blood.

[0133] The management server 50 may, taking into account the demand for blood bags P, execute a process to send emails requesting blood donations to people who are likely to donate blood. This makes blood collection more efficient compared to broad-area advertising with no specific target audience or street-corner blood donation solicitation activities, and reduces the cost of blood collection.

[0134] The management server 50 may issue data related to special incentives to blood donors of blood types in high demand. This makes it possible to secure blood types that are in short supply early. The management server 50 may also periodically send blood donation requests to registered email addresses. [Explanation of Symbols]

[0135] 1. Blood bag management system 10. Blood Center (Medical Institution) 11 Client terminals 12. Reader 20, 30, 40 Medical Institutions (Medical Institutions) 21, 31, 41 Client terminals 50 Management Server 111 Input Section 112 Display section 113 Processing Unit 114 Storage section 115 Connection Interfaces 116 Network Interfaces 121 Storage Department 122 Communication Unit NW Network P Blood bag L RFID label (RFID medium)

Claims

1. Multiple client terminals are installed in each medical institution where blood bags with RFID media attached are stored, A management server that stores unique information stored on the RFID medium attached to the blood bag, information about the blood sealed in the blood bag, information about the demand for the blood bag at the medical institution, and location information of the medical institution, Equipped with, The management server generates delivery data for executing the delivery based on information regarding the demand for the blood bags and the location information, and transmits it to each of the multiple client terminals. The aforementioned management server When a request data for a specific blood sample is received from one of the multiple client terminals located at the first medical institution, A blood bag that matches the information about the specific blood is selected. From among the client terminals to which the selected blood bags are registered, select the client terminal installed at the medical institution that is closest in delivery distance to the first medical institution. Generate interrupt delivery data for delivering the selected blood bags to the first medical institution, and transmit it to the selected client terminal. The system records as an interrupt delivery history that the selected blood bags were delivered to the first medical institution from the medical institution with the shortest delivery distance to the first medical institution. Blood bag management system.

2. Multiple client terminals are installed in each medical institution where blood bags with RFID media attached are stored, A management server that stores unique information stored on the RFID medium attached to the blood bag, information about the blood sealed in the blood bag, information about the demand for the blood bag at the medical institution, and location information of the medical institution, Equipped with, The management server generates delivery data for executing the delivery based on information regarding the demand for the blood bags and the location information, and transmits it to each of the multiple client terminals. The aforementioned management server When a request data for a specific blood sample is received from one of the multiple client terminals located at the first medical institution, A blood bag that matches the information about the specific blood is selected. From among the client terminals to which the selected blood bags are registered, select the client terminal installed at the medical institution with the shortest delivery time to the first medical institution. Generate interrupt delivery data for delivering the selected blood bags to the first medical institution, and transmit it to the selected client terminal. The system records, as an interrupt delivery history, that the selected blood bags were delivered to the first medical institution from the medical institution with the shortest delivery time to the first medical institution. Blood bag management system.

3. A blood bag management system according to claim 1 or 2, The aforementioned management server If the extracted client terminal has a scheduled use of the specific blood bag, the system selects the next-choice client terminal, generates interrupt delivery data to deliver the specific blood bag to the first medical institution, and sends it to the next-choice client terminal. Blood bag management system.

4. A blood bag management system according to claim 1 or 2, The information regarding the demand for the blood bags includes information regarding the past usage and forecasts for the use of the blood bags. Blood bag management system.

5. A blood bag management system according to claim 1 or 2, Each of the aforementioned client terminals is connected to a storage unit equipped with a communication unit for the RFID medium. The unique information of the blood bag is collected from the RFID medium of the blood bag stored in the storage unit. Blood bag management system.

Images