Medical device management system

Abstract

Appropriate management will be implemented for medical devices whose installation location is changed. [Solution] A medical device management device 10 acquires medical device information relating to a medical device and manages the medical device, and the medical device management device 10 includes a management unit 31 that, when the installation facility of a medical device is changed, acquires source information indicating the installation facility before the change and destination information indicating the installation facility after the change as medical device information and stores them in a storage unit 22.

Description

Technical Field

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

[0002] Conventionally, technologies for efficient use of products such as pharmaceuticals have been developed. For example, Patent Document 1 discloses a system including a consignment 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 listed in the immovable pharmaceutical matching system based on the usage file uploaded to the purchasing store terminal and the immovable inventory file etc. uploaded to the consignment 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. And 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] Furthermore, in order to reduce the amount of medical equipment that is discarded without being used and to realize the efficient use of medical equipment, efforts are being made to buy, sell, or move medical equipment between facilities that use it infrequently and those that use it frequently. There is a need for technology that can properly manage medical equipment whose installation location changes in this way.

[0006] This disclosure aims to provide a medical device management system that can appropriately manage medical devices whose installation location is changed. [Means for solving the problem]

[0007] A medical device management device relating to one aspect of this disclosure is: A medical device management device that acquires medical device information relating to medical devices and manages said medical devices, When the installation location of the medical device is changed, the system includes a management unit that acquires and stores in the storage unit medical device information, including source information indicating the installation location before the change and destination information indicating the installation location after the change. [Effects of the Invention]

[0008] According to this disclosure, appropriate management can be carried out for medical devices whose installation facility is changed. [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. [Figure 12] Figure 12 shows an example of a search screen displayed on the user terminal when tracking electrode pads. [Figure 13] Figure 13 shows another example of a search screen displayed on the user terminal when tracking electrode pads. [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 communicably connected to each of user terminal 11, business operator terminal 12, and management terminal 13 via communication network 16. More specifically, server 10 includes a communication unit (input reception unit) 21, a storage unit 22, and an information processing unit 23. Information processing unit 23 includes a management unit 31, a matching processing unit 32, and a notification unit 33.

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

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

[0015] Management unit 31 in information processing unit 23 acquires information regarding a medical device (hereinafter, also referred to as "medical device information"), and performs management of the medical device using the acquired medical device information. In the present embodiment, the case where management unit 31 performs management of 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 usage frequency 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 usage frequency 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 usage frequency and facilities with a high usage frequency.

[0017] The management unit 31 of the server 10 according to the embodiment of this disclosure acquires, for example, medical device 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. In addition, when the management unit 31 acquires new medical device information, it registers the newly acquired medical device information in the storage unit 22 or modifies 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 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] Note that 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 server 10 has completed matching 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 (step S17).

[0041] Specifically, 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 pads, the management unit 31 registers the source information and destination information in the exchange management table.

[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 inputs information indicating that the payment has been made to terminal device 11B. In this case, terminal device 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 terminal device 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 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] As described above, server 10 acquires various information regarding the exchange of electrode pads between users and registers it in the corresponding table. Therefore, it can support the exchange of electrode pads between users.

[0062] [Electrode pad tracking] 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, for example, information indicating the demand ID, supply ID, entry date and time, person in charge, AED model name, email address of the user in charge, availability of spare pads, and transaction status of 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 server 10 can then output tracking results, such as the status of the electrode pads, by using the medical device information stored in the memory unit 22. A specific example of how the server 10 tracks the status of the electrode pads will be described below.

[0067] (Tracking the distribution route) Figure 12 shows an example of a search screen displayed on the user terminal 11 when tracking electrode pads. As shown in Figure 12, for example, when a user performs a predetermined operation on the user terminal 11 to track electrode pads, a search screen is displayed on the monitor of the user terminal 11.

[0068] The search screen displays a search box 41 for entering search terms and selection buttons 42 for selecting tracking items. In the example shown in Figure 12, as examples of selectable tracking items, selection button 42A for searching transaction status and selection button 42B for searching distribution route are displayed. Here, we assume that the user enters the lot number "AAA" into the search box 41 and selects selection button 42B on the user terminal 11.

[0069] In this case, the user terminal 11 shown in Figure 1 sends input information indicating the user's input to the server 10. When the management unit 31 of the server 10 receives the input information sent from the user terminal 11 via the communication unit 21, it refers to the medical device information stored in the storage unit 22 and extracts medical device information corresponding to the user's input.

[0070] Here, the management unit 31, for example, refers to the manufacturing table shown in Figure 3 to extract information indicating the manufacturing location and manufacturing date of the electrode pad with lot number "AAA". The management unit 31 also refers to the installation table shown in Figure 5 to extract information indicating the installation facility before the change and information indicating the installation facility after the change, if the installation facility for the electrode pad has been changed.

[0071] The management unit 31 then sends a list of extracted information to the user terminal 11 as search results corresponding to the user's input. When the user terminal 11 receives the search results sent from the server 10, it displays the contents of those search results on the search screen, for example.

[0072] In the example shown in Figure 12, the search results for the distribution route of an electrode pad with lot number "AAA" show that it was manufactured in "Tomioka" on January 1, 2014, installed at A City Board of Education First Elementary School on January 3, 2014, and then its installation location was changed to A City Fire Department East Station on November 7, 2023. By checking this information, users can understand the distribution route and installation period at each installation location for any given electrode pad.

[0073] Furthermore, if, for example, any issues are found with an electrode pad, it is possible to take preventative measures such as checking the condition of other electrode pads installed at the facility where the electrode pad was previously installed by examining the distribution route of the electrode pad. Additionally, by identifying the management conditions at the facility where the electrode pad was previously installed, it is possible to estimate the cause of the issues that arose.

[0074] (Tracking transaction status) Figure 13 shows another example of the search screen displayed on the user terminal 11 when tracking electrode pads. Here, it is assumed that the user enters the lot number "AAB" into the search box 41 and selects the select button 42A on the user terminal 11.

[0075] In this case, the user terminal 11 shown in Figure 1 sends input information indicating the user's input to the server 10. When the management unit 31 in the server 10 receives the input information sent from the user terminal 11 via the communication unit 21, it refers to the medical device information stored in the storage unit 22 and extracts medical device information corresponding to the user's input.

[0076] Here, the management unit 31 extracts information such as the current transaction status, demand ID, supply ID, matching date, expiration date, name and email address of the supplier's contact person (supplier), and installation facility for electrode pads with lot number "AAB". The management unit 31 then sends a list of the extracted information to the user terminal 11 as a search result corresponding to the user's input. When the user terminal 11 receives the search results sent from the server 10, it displays the contents of the search results on the search screen, for example.

[0077] In the example shown in Figure 13, the search results for the transaction status of an electrode pad with lot number "AAB" show that it is currently being shipped, the demand ID is "Demand 2", the supply ID is "Supply 2", the matching date is November 3, 2023, the expiration date is January 1, 2025, the supplier's name is "Koden Jiro", the recipient user's email address is "OOOO@XXXXX", and the installation facility is "Nishi Police Station". By checking this information, users can easily understand the shipping status, expiration date, and installation facility of the electrode pad.

[0078] Note that the search results shown in Figures 12 and 13 are just examples, and the management unit 31 in the server 10 can output various types of search results. The information to be output may be pre-configured in the management system 100, or it may be arbitrarily configured by the user or others.

[0079] For example, the management unit 31 may output search results showing a list of past replacement statuses of electrode pads installed within the same city. Alternatively, the management unit 31 may output comparative results of past electrode pad replacement statuses for each municipality. When such output is provided, the search results can be used to promote the municipalities' efforts toward the SDGs (Sustainable Development Goals).

[0080] Furthermore, for example, the management unit 31 may output a list of expiration dates or replacement dates for multiple electrode pads. The management unit 31 may also output the list sorted by the closest expiration date or closest replacement date. When such output is provided, users can easily identify, for example, which electrode pads should be replaced first.

[0081] Furthermore, for example, the management unit 31 may output a list of multiple electrode pads that are managed by the same administrator to the administrator's management terminal 13. When such output is provided, the administrator can easily check the status of each electrode pad that they are responsible for managing.

[0082] Furthermore, for example, the management unit 31 may output a list of multiple electrode pads manufactured at the same location. When such an output is provided, users can easily identify other electrode pads manufactured at the same location as the electrode pad in question if they find any issues with the electrode pad.

[0083] 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.

[0084] As described above, the server 10 according to the embodiment of this disclosure acquires medical device information and manages medical devices. When the installation facility of a medical device is changed, the management unit 31 of the server 10 acquires source information indicating the installation facility before the change and destination information indicating the installation facility after the change as medical device information and stores them in the storage unit 22.

[0085] This configuration allows medical device administrators to identify the facility from which the medical device was moved and the facility to which it was moved by checking the medical device information stored on server 10. For example, if any issues are found with the medical device, they can check the status of other medical devices installed at the previous installation facility or check the management status of medical devices at the previous installation facility. Thus, medical devices can be managed appropriately.

[0086] Furthermore, if the installation location of a medical device is changed, the management unit 31 of the server 10 adds the newly acquired relocation information to the medical device information of the medical device.

[0087] With this configuration, if the facility where a medical device is installed changes multiple times, administrators can keep track of the multiple facilities where the medical device has been installed in the past.

[0088] Furthermore, medical device information includes information regarding the manufacture of medical devices. With this configuration, for example, if any issues are found with a medical device, it is possible to check the manufacturing information of that medical device, such as its lot number, place of manufacture, date of manufacture, and manufacturer, to determine whether other medical devices manufactured under similar conditions are functioning correctly.

[0089] Furthermore, information regarding the manufacture of medical devices includes the expiration date of the medical devices. This configuration allows users to easily understand the expiration date of medical devices.

[0090] Additionally, medical device information includes information regarding the delivery of medical devices. With this configuration, for example, a user can check the delivery date and time of the medical device to understand the period during which the medical device was installed at the previous installation facility and the period during which it was installed at the current installation facility.

[0091] Furthermore, medical device information includes information about the installation location of the medical device within the facility where it is installed. This configuration allows, for example, administrators to easily confirm the installation location of medical devices within the facility where they are installed.

[0092] Furthermore, the matching processing unit 32 of server 10 matches demanders who wish to add medical equipment with suppliers who wish to supply medical equipment. The matching processing unit 32 also determines the facility corresponding to the supplier as the installation facility before the change, and the facility corresponding to the demander as the installation facility after the change.

[0093] In this way, by automatically matching demanders who wish to add medical equipment with suppliers who wish to supply medical equipment, the movement of medical equipment between facilities with low usage and facilities with high usage can be made more reliable. Furthermore, the server 10 can automatically determine the facility where the medical equipment was installed before the change and the facility where it will be installed after the change.

[0094] Furthermore, the medical device information includes information regarding the exchange of medical devices between the user and the supplier, as determined by the matching processing unit 32. This configuration allows, for example, medical device managers to identify both consumers and suppliers, as well as to track the dates on which matching took place and when medical devices were replaced.

[0095] Furthermore, medical device information includes information regarding the use of medical devices. This configuration allows, for example, medical device managers to track the date and time when medical devices are used.

[0096] Furthermore, information regarding the use of medical devices includes the frequency of their use. This configuration allows users to easily understand the frequency of medical device use.

[0097] Furthermore, if the medical device information stored in the memory unit 22 is updated, the notification unit 33 of the server 10 notifies a predetermined administrator of the update to the medical device information. This configuration allows administrators to quickly identify changes in the installation locations of medical equipment.

[0098] Furthermore, the communication unit 21 of the server 10 receives input operations from the user regarding medical devices. The management unit 31 then extracts one or more medical devices corresponding to the content of the input operation and outputs a list of medical device information for each extracted medical device.

[0099] With this configuration, for example, if a user specifies City A, a list of medical device information for each medical device installed in City A will be output. This allows the user to understand the status of each medical device in City A, such as its manufacturing, delivery, installation facilities, replacement, and usage, in a list format.

[0100] Furthermore, if medical devices are consumables, it is possible to verify whether changes to the installation facilities of such medical devices are being carried out efficiently. This can be used, for example, to promote each municipality's efforts toward the SDGs.

[0101] Furthermore, the server 10 is connected to a user terminal 11 operated by the user. The management unit 31 of the server 10 outputs the above list to the user terminal 11.

[0102] With this configuration, users can view a list of medical device information corresponding to their own input operations on a terminal device, even when they are away from the medical device management system.

[0103] The medical device in question is the electrode pads for an AED, which performs electrocardiogram analysis and discharge processing on the subject. This configuration allows for efficient management of electrode pads, which are consumable items.

[0104] 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]

[0105] 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. A medical device management device that acquires medical device information relating to medical devices and manages said medical devices, A medical device management device comprising a management unit that, when the installation facility of the medical device is changed, acquires and stores in a storage unit medical device information, including source information indicating the installation facility before the change and destination information indicating the installation facility after the change.

2. The medical device management device according to claim 1, wherein the management unit adds the newly acquired relocation information to the medical device information of the medical device when the installation facility of the medical device is changed.

3. The medical device management device according to claim 1 or claim 2, wherein the medical device information includes information relating to the manufacture of the medical device.

4. The medical device management device according to claim 3, wherein the information relating to the manufacture of the medical device includes the expiration date of the medical device.

5. The medical device management device according to claim 1 or claim 2, wherein the medical device information includes information relating to the delivery of the medical device.

6. The medical device management device according to claim 1, wherein the medical device information includes information regarding the installation location of the medical device at the installation facility.

7. The medical device management device further includes 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. The matching processing unit determines the facility corresponding to the supplier as the installation facility before the change, and determines the facility corresponding to the demander as the installation facility after the change, as described in claim 1 or 2.

8. The medical device management device according to claim 7, wherein the medical device information includes information relating to the exchange of the medical device between the user and the supplier as determined by the matching processing unit.

9. The medical device management device according to claim 1 or claim 2, wherein the medical device information includes information regarding the use of the medical device.

10. The medical device management device according to claim 9, wherein the information relating to the use of the medical device includes the frequency of use of the medical device.

11. The aforementioned medical device management device further, A medical device management device according to claim 1 or 2, further comprising a notification unit that notifies a predetermined administrator of the update of the medical device information stored in the memory unit when the medical device information is updated.

12. The aforementioned medical device management device further, The medical device is equipped with an input receiving unit that receives input operations from the user, The medical device management device according to claim 1 or 2, wherein the management unit extracts one or more medical devices corresponding to the content of the input operation and outputs a list of medical device information for each of the extracted medical devices.

13. The aforementioned medical device management device is connected to a terminal device operated by the user. The medical device management device according to claim 10, wherein the management unit outputs the list to the terminal device.

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

Images