Medical device management system

Abstract

To enable the efficient use of medical devices. [Solution] The medical device management device 10 includes an input receiving unit 21 that receives input operations from multiple users regarding medical devices, a matching processing unit 32 that matches demanders who wish to add medical devices with suppliers who wish to supply medical devices, and a management unit 31 that, after matching by the matching processing unit 32, determines whether the process for exchanging medical devices between the demander and the supplier has been carried out normally, based on the content of the input operations regarding the exchange of medical devices by at least one of the demander and the supplier.

Description

Technical Field

[0001] The present disclosure relates to a medical device management apparatus.

[0002] Conventionally, technologies for efficiently using products such as pharmaceuticals have been developed. For example, Patent Document 1 discloses a system including a selling store terminal, a purchasing store terminal, and an immovable pharmaceutical matching server. In this system, the immovable pharmaceutical matching server generates information indicating order candidates for immovable pharmaceuticals by the purchasing store terminal among the immovable pharmaceuticals offered to the immovable pharmaceutical matching system based on the usage amount file uploaded to the purchasing store terminal and the immovable inventory file etc. uploaded to the selling store terminal, and transmits it to the purchasing store terminal. Then, when the purchasing store terminal logs in to the web site of the immovable pharmaceutical matching system, order candidates for immovable pharmaceuticals by the purchasing store terminal are displayed on the purchasing store terminal.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, medical devices such as electrode pads of defibrillators have a set expiration date. In facilities with high usage frequency such as fire departments, there is a high possibility that medical devices will be used before the expiration date, while in facilities with low usage frequency such as schools, medical devices may be discarded without being used until the expiration date.

[0005] Therefore, a technology that can support the exchange of medical devices between facilities with low usage frequency and facilities with high usage frequency and realize the efficient use of medical devices is desired.

[0006] This disclosure aims to provide a medical device management device that can enable the efficient use of medical devices. [Means for solving the problem]

[0007] A medical device management device relating to one aspect of this disclosure is: An input reception unit that receives input operations from multiple users regarding medical devices, A matching processing unit that matches a customer who wishes to add the medical device with a supplier who wishes to supply the medical device, among the multiple users mentioned above. The system includes a management unit that, after matching by the matching processing unit, determines whether the process for exchanging the medical device between the user and the supplier has been carried out correctly, based on the content of the input operations for exchanging the medical device by at least one of the user and the supplier. [Effects of the Invention]

[0008] This disclosure enables the efficient use of medical devices. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is a block diagram showing the configuration of a management system comprising a server according to an embodiment of this disclosure. [Figure 2] Figure 2 shows an example of a user table stored in the server's memory. [Figure 3] Figure 3 shows an example of a manufacturing table stored in the server's memory. [Figure 4] Figure 4 shows an example of a delivery table stored in the server's memory. [Figure 5] Figure 5 shows an example of an installation table stored in the server's memory. [Figure 6] Figure 6 is a sequence diagram illustrating the flow of electrode pad exchange between the consumer and the supplier. [Figure 7]Figure 7 shows an example of a demand entry table stored in the server's memory. [Figure 8] Figure 8 shows an example of a supply entry table stored in the server's memory. [Figure 9] Figure 9 shows an example of a replacement management table stored in the server's memory. [Figure 10] Figure 10 shows an example of a usage table stored in the server's memory. [Figure 11] Figure 11 is a table showing an example of the relationship between medical device information acquired by the management department, the registration table, and the registration timing. [Modes for carrying out the invention]

[0010] [Management System] Hereinafter, a server 10, which is an example of a medical device management device related to this disclosure, will be described with reference to drawings. Figure 1 is a block diagram showing the configuration of a management system 100 equipped with the server 10 according to an embodiment of this disclosure.

[0011] Referring to Figure 1, the management system 100 includes, for example, a server 10 for managing medical devices, a user terminal (terminal device) 11, a vendor terminal 12, and a management terminal 13. The user terminal 11 is used by users (users), such as personnel at the medical device installation facility. The vendor terminal 12 is used by the medical device manufacturer. The management terminal 13 is used by administrators, such as personnel in the sales management department of the medical device manufacturer.

[0012] Server 10 is connected to each of the user terminals 11, vendor terminals 12, and management terminals 13 via a communication network 16 so that they can communicate with each other. More specifically, Server 10 comprises a communication unit (input receiving unit) 21, a storage unit 22, and an information processing unit 23. The information processing unit 23 includes a management unit 31, a matching processing unit 32, and a notification unit 33.

[0013] The communication unit 21 functions as an interface for the server 10 to communicate with external communication devices such as the user terminal 11, the operator terminal 12, and the management terminal 13. For example, assume that a user performs an input operation related to a medical device on the user terminal 11. In this case, the user terminal 11 transmits information indicating the input content by the user to the server 10. When the communication unit 21 in the server 10 receives the information transmitted from the user terminal 11, it outputs the information to the information processing unit 23.

[0014] The storage unit 22 is a means for storing various information, and is realized by, for example, a RAM (Random Access Memory), a ROM (Read Only Memory), a HDD (Hard Disk Drive), or the like.

[0015] The management unit 31 in the information processing unit 23 acquires information related to medical devices (hereinafter, also referred to as "medical device information"), and manages medical devices using the acquired medical device information. In the present embodiment, a case where the management unit 31 manages the electrode pads of an AED (automated external defibrillator) that performs electrocardiogram analysis and discharge treatment on a subject as an example of a medical device will be described.

[0016] Here, in facilities such as a fire department, the frequency of use of an AED is high, and there is a high possibility that the electrode pads will be used before the expiration date or replacement date. On the other hand, in facilities such as schools, the frequency of use of an AED is low, and the electrode pads may be discarded without being used until the expiration date or replacement date. Therefore, the electrode pads may be exchanged between facilities with a low frequency of use and facilities with a high frequency of use.

[0017] The management unit 31 of the server 10 according to the embodiment of the present disclosure acquires, for example, information related to the replacement of electrode pads, specifically, medical device information indicating the installation facility before replacement and the installation facility after replacement, and stores the acquired medical device information in the storage unit 22. Further, when the management unit 31 newly acquires medical device information, it registers the newly acquired medical device information in the storage unit 22 or changes the medical device information already stored in the storage unit 22.

[0018] In the information processing unit 23, the notification unit 33 notifies the administrator's management terminal 13 of the update of medical device information stored in the memory unit 22, for example, when the management unit 31 updates the medical device information.

[0019] The matching processing unit 32 in the information processing unit 23 matches customers who wish to add electrode pads with suppliers who wish to supply medical devices.

[0020] For example, suppose a user inputs information into the user terminal 11 indicating that they wish to add or receive electrode pads. In this case, the user terminal 11 transmits information indicating the user's input to the server 10. The matching processing unit 32 in the server 10 receives the above information transmitted from the user terminal 11 via the communication unit 21 and, based on this information, performs matching between a customer who wishes to add electrode pads and a supplier who wishes to supply electrode pads.

[0021] [Flow of electrode pad exchange between demanders and suppliers] (User registration) Each user who wishes to use the management system 100 registers to use the management system 100. For example, when a user enters user information such as their name (an example of medical device information) into the user terminal 11, the user terminal 11 sends the user information entered by the user to the server 10.

[0022] The storage unit 22 of the server 10 stores a user table in which user information is registered. Figure 2 shows an example of a user table stored in the storage unit 22 of the server 10. The user table contains, for example, user ID, username, email address, affiliation, and the address of the affiliation. Referring to Figures 1 and 2, when the management unit 31 of the server 10 receives user information transmitted from the user terminal 11 via the communication unit 21, it registers the user information in the user table shown in Figure 2.

[0023] (Registration for the manufacture and distribution of electrode pads) Furthermore, the electrode pad manufacturer registers information about the electrode pads. For example, suppose the manufacturer inputs manufacturing information (an example of medical device information) such as the manufacturing date of the electrode pads, delivery information (an example of medical device information) such as the recipient institution of the electrode pads, and installation information (an example of medical device information) such as the facility where the electrode pads are installed, into the vendor terminal 12. In this case, the vendor terminal 12 transmits the manufacturing information, delivery information, and installation information entered by the manufacturer to the server 10.

[0024] The storage unit 22 of server 10 stores a manufacturing table where manufacturing information for electrode pads is registered, a delivery table where delivery information is registered, and an installation table where installation information is registered.

[0025] Figure 3 shows an example of a manufacturing table stored in the storage unit 22 of the server 10. The manufacturing table registers, for example, the lot number of the electrode pads, the manufacturing date, the manufacturing location, the person in charge of manufacturing, the model name of the corresponding AED, and the expiration date. When the management unit 31 of the server 10 shown in Figure 1 receives manufacturing information transmitted from the vendor terminal 12 via the communication unit 21, it registers the manufacturing information in the manufacturing table, for example, as shown in (A) of Figure 3.

[0026] Figure 4 shows an example of a delivery table stored in the storage unit 22 of the server 10. As shown in Figure 4, the delivery table registers, for example, the delivery ID, delivery date, delivery destination, installation facility, and delivery company for electrode pads. When the management unit 31 of the server 10 shown in Figure 1 receives delivery information transmitted from the vendor terminal 12 via the communication unit 21, it registers the delivery information in the manufacturing table, for example, as shown in Figure 4(A).

[0027] Figure 5 shows an example of an installation table stored in the storage unit of server 10. The installation table registers, for example, the lot number of the electrode pads, the delivery destination, the installation facility, the installation location at the installation facility, the replacement history, past delivery IDs (delivery history), and the installation facility history. When the management unit 31 of server 10 shown in Figure 1 receives installation information transmitted from the vendor terminal 12 via the communication unit 21, it registers the installation information in the installation table, for example, as shown in (A) of Figure 5.

[0028] (Matching demanders and suppliers) Figure 6 is a sequence diagram illustrating the flow of electrode pad exchange between the demander and the supplier. Here, User A on the fire department side is the demander of the electrode pads, and User B on the school side is the supplier of the electrode pads. In other words, User A wants additional electrode pads, and User B wants to exchange existing electrode pads that are nearing their expiration or replacement deadline for new ones.

[0029] (A) Entry processing Referring to Figures 1 and 6, first, let's assume that user A, the demander, inputs demand entry information into user terminal 11A indicating that they wish to add electrode pads. In this case, user terminal 11A transmits the input demand entry information (an example of medical device information) to server 10 (step S11).

[0030] Here, the storage unit 22 of the server 10 stores a demand entry table in which demand entry information is registered. Figure 7 shows an example of a demand entry table stored in the storage unit 22 of the server 10. The demand entry table stores, for example, the demand entry information ID (demand ID), the installation facility, the AED model name, the AED lot number, the expiration date or replacement date of the electrode pads, the replaceable range of the electrode pads, the desired delivery date of the electrode pads, the date and time the demand entry information was entered, and the user ID.

[0031] Referring again to Figures 1 and 6, when the management unit 31 of the server 10 receives the demand entry information transmitted from the user terminal 11A via the communication unit 21, it registers the demand entry information in the demand entry table (step S12).

[0032] Next, the notification unit 33 of the server 10 sends a notification (demand entry notification) to each user registered in the user table (see Figure 2) that new demand entry information has been registered (step S13). For example, the notification unit 33 simultaneously sends an email indicating the content of the newly registered demand entry information to each user's user terminal 11 via the communication unit 21.

[0033] Furthermore, the notification unit 33 may be configured to notify only users who meet certain conditions, such as users whose affiliated location falls within a predetermined range from the installation facility included in the demand entry information, or users who are associated with the fire station to which user A belongs, that new demand entry information has been registered.

[0034] Furthermore, suppose user B, the supplier, inputs supply entry information (an example of medical device information) into user terminal 11B indicating that they wish to receive electrode pads. In this case, user terminal 11B transmits the input supply entry information to server 10 (step S14).

[0035] Here, the storage unit 22 of the server 10 stores a supply entry table in which supply entry information is registered. Figure 8 shows an example of a supply entry table stored in the storage unit 22 of the server 10. The supply entry table stores, for example, the supply entry information ID (supply ID), the AED installation facility, the range in which electrode pads can be provided, the lot number of the electrode pads, the lot number of the AED, the date and time the supply entry information was entered, whether or not there are any electrode pads in stock other than the electrode pads scheduled to be supplied (hereinafter referred to as "spare pads"), and the user ID.

[0036] Referring again to Figures 1 and 6, when the management unit 31 of the server 10 receives the supply entry information transmitted from the user terminal 11B via the communication unit 21, it registers the supply entry information in the supply entry table (step S15).

[0037] The transmission of supply entry information (step S14) and the registration of supply entry information (step S15) may be performed before the transmission of demand entry information (step S11), the registration of demand entry information (step S12), and the notification of demand entry (step S13).

[0038] (B) Process from the start of the exchange to the completion of the exchange Next, the matching processing unit 32 of the server 10 performs matching between demanders and suppliers based on the demand entry table and supply entry table stored in the storage unit 22 (step S16).

[0039] Here, the storage unit 22 of the server 10 stores an exchange management table for managing the exchange status of electrode pads between matched demanders and suppliers. Figure 9 shows an example of an exchange management table stored in the storage unit 22 of the server 10. The exchange management table registers exchange management information (an example of medical device information) such as the matching ID, transaction status, transaction update date, demand ID, supply ID, matching date, payment status, and the installation status of electrode pads at the exchange destination.

[0040] Referring again to Figures 1 and 6, once the matching processing unit 32 completes the matching between the demander and the supplier, it registers exchange management information related to the matching, such as the matching ID and transaction status, in the exchange management table.

[0041] Furthermore, when the matching processing unit 32 matches user A and user B as described above, it determines the facility to which user B, the supplier, belongs, i.e., the installation facility included in the supply entry information, as the installation facility from which the electrode pads will be moved. The matching processing unit 32 also determines the facility to which user A, the demander, belongs, i.e., the installation facility included in the demand entry information, as the installation facility to which the electrode pads will be moved.

[0042] When the matching processing unit 32 determines the source and destination of the electrode pad, the management unit 31 registers the source information indicating the source and the destination information indicating the destination in the exchange management table (step S17).

[0043] The matching processing unit 32 then sends a matching notification to user terminal 11A of user A and user terminal 11B of user B via the communication unit 21, indicating that matching has been completed (step S18). At this time, the matching processing unit 32 sends, for example, source information to user terminal 11A along with the matching notification. The matching processing unit 32 also sends, for example, destination information to user terminal 11B along with the matching notification.

[0044] Next, the matching processing unit 32 bills user B for the system usage fee associated with the replacement of the electrode pads. Specifically, the matching processing unit 32, for example, sends billing information indicating the billing amount to user terminal 11B via the communication unit 21 (step S19). At this time, the system usage fee billed to user B is set to an amount lower than the purchase price of the electrode pads.

[0045] Suppose user B makes a payment for the system usage fee and enters information indicating that the payment has been made into user terminal 11B. In this case, user terminal 11B sends a payment completion notification to server 10 indicating the information entered by user B (step S20).

[0046] Next, when the management unit 31 in the server 10 receives the payment completion notification sent from the user terminal 11B via the communication unit 21, it registers today's date in the transaction update date column of the exchange management table, as shown in Figure 9(B), for example, and further updates the payment status column by adding the payment date (step S21).

[0047] Next, the management unit 31 refers to the supply entry table shown in Figure 8, for example, and sends a delivery instruction to the vendor terminal 12 via the communication unit 21 so that new electrode pads are delivered from the manufacturer to the installation facility registered by the supplier, user B (step S22). When the manufacturer confirms the delivery instruction sent from the server 10 to the vendor terminal 12, it delivers the new electrode pads to the installation facility indicated by the delivery instruction.

[0048] Furthermore, the manufacturer inputs, for example, manufacturing information, delivery information, and installation information for the delivered electrode pads into the vendor terminal 12. In this case, the vendor terminal 12 transmits the manufacturing information, delivery information, and installation information entered by the manufacturer to the server 10.

[0049] The management unit 31 in server 10 receives manufacturing information, delivery information, and installation information transmitted from vendor terminal 12 via the communication unit 21. The management unit 31 then registers the received manufacturing information in the manufacturing table (see (B) in Figure 3), the received delivery information in the delivery table (see (B) in Figure 4), and the received installation information in the installation table (see (B) in Figure 5) (step S23).

[0050] Next, the management unit 31 sends a delivery completion notification to the user terminal 11B via the communication unit 21, indicating that the delivery of the new electrode pads to the school to which the user belongs has been completed (step S24). After user B confirms the delivery completion notification sent from the server 10 to the user terminal 11B, user B takes the electrode pads to be replaced to the installation facility indicated by the destination information. Then, the electrode pads are handed over from user B to user A.

[0051] Next, suppose user A completes the replacement of the electrode pads handed over by user B and performs an operation to input replacement completion information to user terminal 11A to indicate that the replacement has been completed. In this case, when user terminal 11A receives the above input operation from user A, it sends a replacement completion notification to server 10 (step S25).

[0052] Furthermore, suppose user B completes the replacement of the electrode pads that have been newly delivered from the manufacturer and performs an operation to input replacement completion information to user terminal 11B to indicate that the replacement has been completed. In this case, when user terminal 11B receives the above input operation from user B, it sends a replacement completion notification to server 10 (step S26).

[0053] Next, when the management unit 31 of the server 10 receives the exchange completion notifications sent from user terminals 11A and 11B via the communication unit 21, it corrects the transaction status in the exchange management table to "Exchange Completed," as shown in Figure 9(C). The management unit 31 also enters today's date as the transaction update date in the exchange management table and updates the item for the installation status of the exchange destination by adding "Exchange Completed."

[0054] Furthermore, as shown in Figure 5(C), the management unit 31 updates the installation table by changing, for example, the delivery destination, installation facility, and installation location of the electrode pad with lot number "AAA" that is to be replaced (step S27). If the same electrode pad is moved multiple times, for example, the destination information is added to the installation facility history in the replacement management table.

[0055] The example shown in Figure 6 illustrates a case where the ratio of demanders to suppliers of electrode pads is 1:1, but the ratio of demanders to suppliers is not limited to 1:1. For example, if a demander wants to add multiple electrode pads, multiple suppliers may be matched for one demander.

[0056] (C) Use after replacement Each AED performs a self-test, for example, periodically, to diagnose whether it is functioning correctly, i.e., whether its condition is normal or abnormal. Each AED then transmits the results of the self-test (status information) to the server 10. In addition, if the electrode pads have been used, each AED transmits the self-test results along with the usage history of the electrode pads (an example of medical device information).

[0057] The storage unit 22 of the server 10 shown in Figure 1 stores a usage table for managing the usage status of electrode pads. Figure 10 shows an example of a usage table stored in the storage unit 22 of the server 10. The usage table registers medical device information such as the lot number and usage date of the electrode pads.

[0058] Referring again to Figure 1, when the management unit 31 of the server 10 receives the self-test result transmitted from the AED via the communication unit 21, it checks whether the self-test result includes the usage history of the electrode pads. If the self-test result includes the usage history of the electrode pads, the management unit 31 adds the lot number and usage date of the electrode pads to the usage table.

[0059] Furthermore, the management unit 31 may calculate the frequency of use of the electrode pads during a predetermined period based on the usage dates registered in the usage table. In this case, the management unit 31 can register information indicating the calculated frequency of use (an example of medical device information) in the usage table.

[0060] Furthermore, if the self-test results include the usage history of the electrode pads, the notification unit 33 of the server 10 may, for example, send the usage history to the management terminal 13 of the administrator responsible for sales management of the electrode pads.

[0061] Furthermore, if the self-test results include expiration date information such as the expiration date or replacement date of the electrode pads, the management unit 31 of the server 10 may, for example, register the expiration date information of the electrode pads in the usage table.

[0062] [Process to support electrode pad replacement] Figure 11 is a table showing an example of the relationship between medical device information acquired by the management unit 31, the registration table, and the registration timing. As shown in Figure 11, for example, information such as the lot number, manufacturing date, manufacturing location, manufacturing manager, AED model name, and expiration date of the electrode pads are registered in the manufacturing table at the time of manufacturing or after installation of the electrode pads.

[0063] Furthermore, information such as the delivery ID, delivery date, delivery location, and delivery person for each electrode pad is registered in the delivery table at the time of manufacture or after installation of the electrode pad. Similarly, information such as the installation date, installation location, installation person, and installation history for each electrode pad is registered in the installation table at the time of manufacture or after installation of the electrode pad.

[0064] Furthermore, for example, the user's user ID, username, email address, affiliation, and address are registered in the user table when the user registers. Additionally, information such as the demand ID, supply ID, entry date and time, person in charge, AED model name, electrode pad expiration or replacement deadline, replaceable range, email address of the user in charge, availability of spare pads, and transaction status of the electrode pads are registered in the demand entry table or supply entry table at the time of demand entry or supply entry.

[0065] Furthermore, for example, matching ID, matching date, transaction status, transaction update date, payment status, and exchange partner transaction status are registered in the exchange management table at the time of demand entry, supply entry, or completion of electrode pad exchange. Also, for example, information indicating the date of use of an electrode pad is registered in the usage table after the electrode pad has been used.

[0066] The management unit 31 in the server 10 can determine whether the electrode pad replacement process is being performed correctly by checking the content of the input operations to the user terminal 11 by the demander and the supplier, i.e., the medical device information stored in the storage unit 22. If the management unit 31 determines that the electrode pad replacement process is not being performed correctly, it will support the replacement of the electrode pads by operating as described below. The following describes specific examples of support for electrode pad replacement by the server 10.

[0067] (Example 1) When matching between demanders and suppliers is not completed Referring again to Figures 1 and 6, for example, suppose that the matching by the matching processing unit 32 (step S16) is not completed within a predetermined period of time from the start of the matching process. In such a case, the management unit 31 determines that the process related to the replacement of the electrode pads, in this case the matching between the demander and the supplier, has not been performed properly.

[0068] The management unit 31 then sends a notification (hereinafter referred to as a "proposal notification") to the user terminal 11 of the customer, which is the source of the demand entry information, suggesting, for example, that the range of replaceable electrode pads be expanded or that the purchase of new electrode pads be made available. This makes it possible to more reliably replace the electrode pads on the customer's side and avoid situations where the customer has to wait indefinitely for the electrode pads to be replaced.

[0069] Furthermore, the management unit 31 may, for example, re-notify the user terminal 11 of each user registered in the user table (see Figure 2) of the demand entry information. This increases the likelihood of finding a supplier by re-soliciting suppliers of electrode pads.

[0070] Furthermore, for example, suppose that matching by the matching processing unit 32 has not been completed between the time the demand entry information is registered in the demand entry table (see Figure 7) and the time when a predetermined period (e.g., 3 months) has elapsed. In such a case as well, the management unit 31 can similarly perform at least one of the following: send a proposal notification to the demander's user terminal 11, and re-notify each user's user terminal 11 of the demand entry information.

[0071] Furthermore, for example, suppose that the matching process by the matching processing unit 32 has not yet completed when the period until the expiration or replacement deadline for the electrode pads registered in the demand entry table reaches a predetermined period (e.g., 6 months). In such a case as well, the management unit 31 can similarly perform at least one of the following: send a proposal notification to the demander's user terminal 11, and re-notify each user's user terminal 11 of the demand entry information.

[0072] Furthermore, if the management unit 31 finds that matching has not been completed when the period until the expiration or replacement deadline for the electrode pad has reached a predetermined time, it may delete the demand entry information corresponding to the electrode pad from the demand entry table. In this case, the management unit 31 sends an email to the user terminal 11 of the demander informing them that the electrode pad cannot be replaced and urging them to purchase a new electrode pad. Alternatively, the timing for deleting the demand entry information may be automatically set when the demand entry information is registered.

[0073] (Example 2) If the system usage fee is not paid Furthermore, for example, suppose that the payment completion notification (step S20) has not been received by the server 10 between the matching (step S16) and the end of a predetermined period. That is, suppose that the payment date, etc., has not been registered in the payment status column of the exchange management table shown in Figure 9. In such a case, the management unit 31 determines that the process related to the replacement of the electrode pads, in this case the payment of the system usage fee, has not been carried out properly.

[0074] The management unit 31 then sends a payment reminder email to the supplier's user terminal 11, which is the recipient of the payment request. This prevents delays in replacement due to non-payment of system usage fees and ensures reliable replacement of electrode pads.

[0075] Furthermore, if payment of the system usage fee is not made within a specified period following the sending of the above-mentioned reminder email, the management unit 31 may, for example, cancel the matching between the demander and the supplier. If the management unit 31 cancels the matching, it will, for example, send a notification to the user terminals 11 of both the demander and the supplier that the matching has been canceled. This allows the demander, upon receiving the notification, to take appropriate action, such as purchasing new electrode pads.

[0076] Furthermore, the management unit 31 may be configured to cancel the matching without sending the aforementioned reminder email.

[0077] The matching processing unit 32 may perform a new matching operation if the matching operation is canceled by the management unit 31. This makes it possible to more reliably replace electrode pads on the customer side.

[0078] (Example 3) When the electrode pads are not supplied by the supplier Furthermore, for example, suppose that between the matching (step S16) and the end of a predetermined period, the server 10 receives a payment completion notification (step S20), but does not receive a replacement completion notification (step S25) from the user terminal 11 of the demander. That is, suppose that in the replacement management table shown in Figure 9, the payment date and other information are registered in the payment status column, but "replacement completed" is not registered in the transaction status column. In such a case, the management unit 31 determines that the process related to the replacement of the electrode pads, in this case the delivery of the electrode pads from the supplier to the demander, has not been carried out properly.

[0079] The management unit 31 then sends a reminder email to the supplier's user terminal 11, for example, to encourage them to bring in the electrode pads. This prevents delays in replacement due to failure to bring in electrode pads from the supplier to the customer, and ensures reliable replacement of electrode pads.

[0080] Furthermore, if the electrode pads are not delivered to the customer by the specified period following the sending of the reminder email, the management unit 31 may, for example, cancel the matching between the customer and the supplier. In this case, for example, the administrator of the management system 100 may process a refund of the system usage fee already paid to the supplier.

[0081] Furthermore, for example, suppose that the server 10 has not received a replacement completion notification (step S25) between the time the delivery information is registered in the delivery table (see Figure 4) (step S23) and the time when a predetermined period has elapsed. In such a case, the management unit 31 will similarly send a reminder email to the supplier's user terminal 11 to urge them to bring in the electrode pads.

[0082] The reminder email sent to the supplier's user terminal 11 may include input fields for the scheduled date and time of bringing in the electrode pads. When the supplier enters the scheduled date and time in the input field, the supplier's user terminal 11 sends the information indicating the entered scheduled date and time to the server 10. The management unit 31 in the server 10 then registers the information sent from the user terminal 11 in the storage unit 22.

[0083] In such a case, if the electrode pads are not delivered to the customer by the time a predetermined period has elapsed from the scheduled delivery date and time entered by the supplier, the management unit 31 may cancel the matching between the supplier and the customer. In this case, the management unit 31 will, for example, bill the supplier for the difference between the purchase price of the new electrode pads that have been delivered to the supplier and the system usage fee that the supplier has already paid.

[0084] (Example 4) Checking the connection of the new electrode pads Furthermore, suppose the server 10 receives a self-test result from the AED to which the replaced electrode pads have been attached. In this case, the management unit 31 in the server 10 checks the self-test result to determine whether the replaced electrode pads have been properly connected to the AED.

[0085] The management unit 31 then determines, for example, that the electrode pads are not properly connected to the AED, and sends, for example, an email or other message indicating how to connect the electrode pads to the AED to the user terminal 11 at the facility where the AED is installed. This allows support for users who are unfamiliar with connecting electrode pads.

[0086] Furthermore, for example, suppose that the server 10 has not received a self-test result from the AED to which the replaced electrode pads have been attached during the period between the update of the replacement management table (see Figure 9) (step S27) and the expiration of a predetermined period. In such a case as well, the management unit 31 can similarly send, for example, an email indicating how to connect the electrode pads to the AED to the user terminal 11 at the facility where the AED is installed.

[0087] (Example 5) Processing that takes into account the presence or absence of spare pads Furthermore, the management unit 31 may be configured to perform processing that takes into account whether or not the supplier of the electrode pads has spare electrode pads. For example, if the supplier has spare pads, the management unit 31 sends an email to the supplier's user terminal 11 prompting the delivery of the electrode pads to the customer, along with a matching notification (step S18).

[0088] On the other hand, if the supplier does not have spare pads, the management unit 31 does not send an email prompting the customer to hand over the electrode pads when sending the matching notification (step S18). Then, for example, after the delivery of the new electrode pads to the supplier is completed, the management unit 31 sends an email to the supplier's user terminal 11 prompting the customer to hand over the electrode pads, along with a delivery completion notification (step S24). This prevents a situation where the supplier's facility does not have electrode pads.

[0089] As illustrated in Examples 1 to 5 above, the management unit 31 in the server 10 checks the status of electrode pad replacement in real time by verifying the medical device information registered in the storage unit 22, and takes action according to the status. This supports the process of replacing medical devices and enables the efficient use of medical devices.

[0090] In this embodiment, the medical device managed by the management system 100 is described as an AED electrode pad, but the medical device managed by the management system 100 is not limited to an electrode pad. For example, the medical device may be a consumable item other than an electrode pad, such as a probe attached to the subject when measuring SpO2, which has an expiration date or replacement date.

[0091] As described above, the communication unit 21 of the server 10 according to the embodiment of this disclosure receives input operations from multiple users regarding medical devices. The matching processing unit 32 of the server 10 matches demanders who wish to add medical devices with suppliers who wish to supply medical devices. Furthermore, after the matching by the matching processing unit 32, the management unit 31 of the server 10 determines whether the process for exchanging medical devices between the demander and the supplier has been carried out correctly, based on the content of the input operations regarding the exchange of medical devices by at least one of the demander and the supplier.

[0092] This configuration allows for the detection of failures in the exchange of medical devices between consumers and suppliers, thereby ensuring that medical device exchanges are carried out more reliably.

[0093] Furthermore, if the management unit 31 of the server 10 determines that the process for exchanging medical devices between the demander and the supplier is not being carried out properly, the matching processing unit 32 will perform a new matching. This configuration allows for more reliable replacement of medical devices.

[0094] Furthermore, the management unit 31 of the server 10 can obtain an exchange completion notification indicating that the medical device has been delivered from the supplier to the customer. If the management unit 31 has not obtained an exchange completion notification after a predetermined time has elapsed since the matching process by the matching processing unit 32, it determines that the process related to the exchange of the medical device has not been carried out properly.

[0095] In this way, a configuration that detects whether the medical device has not been delivered from the supplier to the consumer after matching can support more reliable exchange of medical devices.

[0096] Furthermore, the management unit 31 of the server 10 can obtain a payment completion notification indicating that payment has been made for the replacement of the medical device. If the management unit 31 has not obtained a payment completion notification after a predetermined time has elapsed since the matching by the matching processing unit 32, it will determine that the process related to the replacement of the medical device has not been carried out properly.

[0097] This configuration allows for more reliable collection of usage fees for the system provided by server 10.

[0098] Furthermore, the management unit 31 of the server 10 will also output a notification to the customer proposing the purchase of a new medical device if, after a predetermined period has elapsed since the matching process by the matching processing unit 32 began, the matching of a customer with a supplier has not been completed.

[0099] This configuration helps to avoid situations where consumers have to wait indefinitely for medical equipment replacements, thereby encouraging the purchase of new medical equipment.

[0100] Furthermore, the management unit 31 of the server 10, if a predetermined period of time has elapsed since the start of matching by the matching processing unit 32 and the matching of suppliers to demanders has not been completed, will output a notification to multiple users soliciting the supply of medical devices.

[0101] In this way, by soliciting requests from multiple users for supply, the likelihood of finding a supplier can be increased.

[0102] Furthermore, the medical devices managed by server 10 are the electrode pads of an AED, which performs electrocardiogram analysis and discharge processing on the patient. This configuration allows for efficient management of electrode pads, which are consumable items.

[0103] Furthermore, the management unit 31 of the server 10 acquires status information indicating the connection status of the electrode pads to the AED, and determines whether the connection of the electrode pads to the AED is normal based on the status information.

[0104] In this situation, when electrode pads are exchanged between the user and the supplier, there is a possibility that someone unfamiliar with the procedure for connecting electrode pads to an AED may perform the connection. In response to this, as described above, by determining whether the electrode pads have been connected to the AED correctly, it is possible to provide support such as detecting and notifying of any connection abnormalities.

[0105] Although embodiments of this disclosure have been described above, the technical scope of this application should not be interpreted as being limited by the description of these embodiments. These embodiments are examples, and it will be understood by those skilled in the art that various modifications of the embodiments are possible within the scope of the invention described in the claims. The technical scope of this application should be determined based on the scope of the invention described in the claims and the scope of its equivalents. [Explanation of Symbols]

[0106] 10: Server (Medical device management device), 11, 11A, 11B: User terminal (terminal device), 12: Vendor terminal, 13: Management terminal, 16: Communication network, 21: Communication unit (Input reception unit), 22: Storage unit, 23: Information processing unit, 31: Management unit, 32: Matching processing unit, 33: Notification unit, 41: Search box, 42, 42A, 42B: Selection buttons, 100: Management system

Claims

1. An input reception unit that receives input operations from multiple users regarding medical devices, A matching processing unit that matches a customer who wishes to add the medical device with a supplier who wishes to supply the medical device, among the multiple users mentioned above. A medical device management device comprising: a management unit that, after matching by the matching processing unit, determines whether the process for exchanging the medical device between the user and the supplier is being carried out normally, based on the content of the input operations for exchanging the medical device by at least one of the user and the supplier.

2. If the management unit determines that the process for exchanging the medical device between the user and the supplier is not being carried out properly, the matching processing unit performs a new match, as described in claim 1.

3. The management unit is capable of obtaining a notification of completion of the exchange indicating that the medical device has been delivered from the supplier to the customer. The medical device management device according to claim 1 or 2, wherein the management unit determines that the process for replacing the medical device has not been performed properly if it has not received the replacement completion notification at a predetermined time after matching by the matching processing unit.

4. The management department is able to obtain a payment completion notice indicating that payment has been made for the replacement of the medical device. The medical device management device according to claim 1 or 2, wherein the management unit determines that the process for replacing the medical device has not been carried out properly if it has not received the payment completion notification at a predetermined time after matching by the matching processing unit.

5. The medical device management device according to claim 1 or 2, wherein the management unit further outputs a notification to the customer proposing the purchase of a new medical device if, at a predetermined time after the start of matching by the matching processing unit, the matching of the customer with the supplier has not been completed.

6. The medical device management device according to claim 1 or 2, wherein the management unit further outputs a notification to the multiple users soliciting the supply of the medical device if, at a predetermined time elapsed since the start of matching by the matching processing unit, the matching of the supplier to the demander has not been completed.

7. The medical device management device according to claim 1 or claim 2, wherein the medical device is an electrode pad for a defibrillator that performs electrocardiogram analysis and discharge processing on a subject.

8. The medical device management device according to claim 7, further comprising: the management unit acquiring status information indicating the connection status of the medical device to the defibrillator, and determining whether the connection of the medical device to the defibrillator is normal based on the status information.

Images