Medical device safety management method and a server performing the method
The method and server system leverage patient and device location information to automate medical device safety management, addressing integration and record-keeping inefficiencies, thereby reducing costs and improving management efficiency.
Patent Information
- Application Number
- KR1020230074762
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-06-12
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-06-12
AI Technical Summary
Current medical device safety management systems face challenges in integrating device information due to non-standardized interface specifications, leading to inefficiencies, record omissions, and reactive management methods that fail to provide historical data, resulting in increased costs and time consumption.
A method and server system that utilize patient and medical device location information to automatically generate and update usage information, determining safety status based on device information, order information, and providing real-time safety management.
Enables efficient and automated medical device safety management, reducing costs and time, minimizing failures, and improving management efficiency by providing accurate safety status updates.
Smart Images

Figure 112023064155853-PAT00003_ABST
Abstract
Description
Technology Field
[0001] An embodiment of the present invention relates to a method for managing the safety of a medical device and a server for performing the method. Background Technology
[0002] The recent advancement of information and communication technology (ICT) is accelerating the digitization of medical information. Many hospitals worldwide are adopting Health Information Technology (HIT)-based Electronic Health Record (EHR) systems, and extensive research is being conducted on medical standardization, such as standard protocols for interoperability between medical information systems and standard medical terminology systems.
[0003] Along with the digitization of medical information, attempts are being made to digitize the monitoring of medical device safety management. Problems with medical devices used in hospitals have a direct or indirect impact on patient safety. Furthermore, since medical devices often include many expensive components that can cause significant financial damage to hospitals, the safety management of medical devices is a critical and essential task.
[0004] However, as medical devices are manufactured by various companies, management methods may vary by manufacturer even for devices performing the same function. Furthermore, since the interface specifications required for management are not standardized, it is difficult to integrate medical device information and build a single database for management. Consequently, traditionally, medical device management departments within hospitals kept records for each device, or the suppliers of the devices performed individual inspections.
[0005] Conventional medical device safety management relies primarily on manual or computerized records, which can lead to record omissions and make retrieving records difficult. Consequently, there has been a problem with reduced safety management capabilities through history tracking. Furthermore, conventional management methods are reactive, recording information only after an incident occurs; thus, they could not provide users with historical information regarding the condition of the medical device before use. As a result, there were issues with significant time and cost consumption in medical device management.
[0006] Furthermore, within the existing medical device safety management system, safety information regarding medical devices issued by the government or medical organizations was disseminated to each medical institution through documents and electronic postings, leading to problems such as long delays or omissions in delivering the information to end users.
[0007] Furthermore, when multiple identical medical devices are housed in a single medical space, medical device managers must identify which devices are used more frequently or are outdated to determine whether to replace parts or the devices themselves. However, conventional usage assessment techniques calculate usage based on medical staff prescription information and the quantity of collected data; consequently, it is impossible to obtain usage data for each device regarding the actual time the device was applied to a patient. Consequently, there is no way to determine operating time other than inspecting multiple devices individually, rendering these methods impractical in actual medical settings. As a result, when a medical device malfunction is identified, replacing parts for multiple devices simultaneously leads to wasted costs and reduced management efficiency. The problem to be solved
[0008] The present invention aims to solve the aforementioned problems and / or limitations by providing a medical device safety management method that enables automatic medical device safety management using patient location information and medical device location information, and a server that performs the method.
[0009] However, these tasks are exemplary and do not limit the scope of the invention. means of solving the problem
[0010] One embodiment of the present invention provides a medical device safety management method comprising: a step of obtaining location information of a patient using a patient device; a step of obtaining location information of medical devices from a plurality of medical devices; a step of generating usage information of a matching medical device matched with the patient using the patient's location information and the location information of the medical devices; a step of updating device information of the matching medical device that has been stored using the generated usage information; and a step of verifying the safety of the matching medical device according to the device information of the matching medical device and providing the safety of the matching medical device to a user.
[0011] In one embodiment of the present invention, the method further includes the step of obtaining the patient's order information prescribed to the patient, and the step of generating usage information of the matching medical device may generate the usage information of the matching medical device using the patient's location information, the location information of the medical device, and the patient's order information.
[0012] In one embodiment of the present invention, the patient's order information may include at least one of treatment order information, test order information, and medication order information prescribed to the patient.
[0013] In one embodiment of the present invention, the step of generating usage information of the matching medical device may include: a step of determining a medical device included within a preset range based on the patient's location information; a step of determining the matching medical device among the medical devices included within the preset range using the patient's order information; and a step of generating usage information of the determined matching medical device.
[0014] In one embodiment of the present invention, the safety of the matching medical device may be determined based on the number of times the device information of the matching medical device is used.
[0015] In one embodiment of the present invention, the safety of the matching medical device may be determined based on the usage time of the device information of the matching medical device.
[0016] In one embodiment of the present invention, the safety of the matching medical device may be determined based on the management records of the matching medical device.
[0017] In one embodiment of the present invention, the safety of the matching medical device may be determined based on safety information of the device information of the matching medical device.
[0018] One embodiment of the present invention provides a computer-readable recording medium having a program for performing the aforementioned methods recorded thereon.
[0019] Another embodiment of the present invention provides a medical device safety management server comprising a memory storing at least one program, a patient device, a plurality of medical devices, a communication unit transmitting and receiving data with a medical system server, and at least one processor that determines the safety status of the medical device and provides it to a user by executing the at least one program, wherein the memory comprises instructions for the at least one processor to execute the steps of: obtaining location information of the patient from the patient device; obtaining location information of the medical device from a plurality of medical devices; generating usage information of a matching medical device matched with the patient using the patient's location information and the location information of the medical device; updating device information of the matching medical device stored using the generated usage information; and verifying the safety status of the matching medical device according to the device information of the matching medical device and providing the safety status of the matching medical device to a user.
[0020] Other aspects, features, and advantages other than those described above will become clear from the following drawings, claims, and detailed description of the invention. Effects of the invention
[0021] According to the means for solving the problem of the present invention described above, the embodiments of the present invention enable automatic safety management of medical devices by utilizing patient location information and medical device location information, thereby enabling automation of medical device safety management and making it easier to perform safety management of medical devices.
[0022] In addition, the embodiments of the present invention can reduce the cost and time of medical device safety management, reduce medical device failures, and reduce the cost of repair or replacement of medical devices, thereby enabling safer and more efficient safety management of medical devices.
[0023] Of course, the scope of the present invention is not limited by these effects. Brief explanation of the drawing
[0024] FIG. 1 is a schematic diagram illustrating a medical device safety management system according to one embodiment of the present invention. FIG. 2 is a block diagram schematically illustrating a medical device safety management server according to one embodiment of the present invention. FIG. 3 is a flowchart illustrating a medical device safety management method according to one embodiment of the present invention. Figure 4 is a diagram illustrating the medical device safety management method of Figure 3. FIG. 5 is a flowchart illustrating a method for generating usage information of a matching medical device according to an embodiment of the present invention. Specific details for implementing the invention
[0025] Hereinafter, the following embodiments will be described in detail with reference to the attached drawings. When describing with reference to the drawings, identical or corresponding components are given the same reference numerals, and redundant descriptions thereof will be omitted.
[0026] Since the embodiments are capable of various modifications, specific embodiments are illustrated in the drawings and described in detail in the detailed description. The effects and features of the embodiments and the methods for achieving them will become clear by referring to the details described below in conjunction with the drawings. However, the embodiments are not limited to those disclosed below and can be implemented in various forms.
[0027] In the drawings, parts unrelated to the explanation have been omitted to clearly explain the invention, and similar parts throughout the specification have been given similar reference numerals.
[0028] In the following embodiments, terms such as first, second, etc. are used not in a limiting sense, but for the purpose of distinguishing one component from another.
[0029] In the following embodiments, singular expressions include plural expressions unless the context clearly indicates otherwise.
[0030] In the following examples, terms such as "include" or "have" mean that the features or components described in the specification are present, and do not preclude the possibility that one or more other features or components may be added.
[0031] Where an embodiment can be implemented differently, a specific process sequence may be performed differently from the order described. For example, two processes described consecutively may be performed substantially simultaneously or proceed in the reverse order of the description.
[0032] In the following embodiments, when a part is described as being "connected" to another part, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other elements interposed between them.
[0033] FIG. 1 is a schematic diagram illustrating a medical device safety management system (1) according to one embodiment of the present invention, and FIG. 2 is a block diagram schematically illustrating a medical device safety management server (100) according to one embodiment of the present invention.
[0034] Referring to FIGS. 1 and 2, a medical device safety management system (1) according to one embodiment of the present invention may include a medical device safety management server (100), a patient device (200), a plurality of medical devices (300), and a medical system server (400). The medical device safety management server (100), the patient device (200), the plurality of medical devices (300), and the medical system server (400) may be connected to each other through a network (500) to transmit and receive data.
[0035] A medical device safety management system (1) according to one embodiment of the present invention may have a medical device safety management server (100) receive location information of a patient and location information of each medical device from a patient device (200) and a plurality of medical devices (300), generate usage information of a matching medical device matched with a patient, and verify the safety status of the matching medical device and provide it to a user. In addition, the medical device safety management system (1) may collect the safety management status of each medical device using the usage information of the matching medical device and provide it to a user.
[0036] The patient device (200) is a digital device that includes a function to communicate with the medical device safety management server (100), and may refer to various devices that transmit location information of a patient visiting the hospital to the medical device safety management server (100). Here, the patient's location information refers to real-time information, and the patient device (200) can collect the patient's location information using various location tracking methods and transmit it to the medical device safety management server (100).
[0037] In one embodiment, the patient device (200) may be a smartphone, tablet PC, etc. carried by the patient, and the patient's personal mobile terminal may be used. In another embodiment, the patient device (200) may be a wearable device such as a smart watch, smart band, smart ring, smart necklace, etc.
[0038] In another embodiment, the patient device (200) may be a hospital device, such as a patient bed, treatment table, or operating table assigned to the patient, which is provided to remain continuously while the patient uses the medical device. If the patient device (200) is a hospital device, the hospital device may be equipped with a first location information module capable of acquiring location information and communicating with a medical device safety management server (100). In this case, the first location information module may be implemented as separate hardware and embedded or externally mounted on the patient device (200), but is not limited thereto.
[0039] However, the patient device (200) is not limited to the above-described embodiment, and may be provided in a form in which a first position information module is attached to a device in which the relative position to the patient is fixed while the patient is using the medical device, and various modifications are possible.
[0040] The medical device (300) is a medical device in a hospital requiring safety management and may include a function to communicate with the medical device safety management server (100) and transmit location information of the medical device (300) to the medical device safety management server (100). Here, the location information of the medical device (300) refers to real-time information, and the medical device (300) may collect location information of the medical device using various location tracking methods and transmit it to the medical device safety management server (100).
[0041] A plurality of medical devices (300) may include various types of medical devices and may include multiple medical devices of the same type. At this time, the communication method or data signal system may differ for each medical device, but the medical device safety management server (100) can communicate with each medical device (300) and collect location information of each medical device (300).
[0042] In one embodiment, a plurality of medical devices (300) may include a second location information module capable of acquiring location information and communicating with a medical device safety management server (100). The second location information module may be implemented as separate hardware and embedded or externally mounted in each of the plurality of medical devices (300), but is not limited thereto.
[0043] The medical system server (400) is a server on the hospital side and can store and manage patient information. Patient information may include patient personal information, diagnostic information, and order information, and the order information may include treatment order information, test order information, and medication order information prescribed to the patient. Patient information stored in the medical system server (400) may be information stored in the medical system server (400) by the patient's medical staff.
[0044] A medical device safety management server (100), a patient device (200), a plurality of medical devices (300), and a medical system server (400) of a medical device safety management system (1) according to one embodiment of the present invention may be connected to a network (500).
[0045] The connection method of the network (500) is not limited and refers to a comprehensive data communication network that enables each network constituent entity shown in FIG. 1 to communicate smoothly with each other. The communication method of the network (500) may include not only a communication method utilizing a communication network that the network (500) may include, but also short-range wireless communication between devices.
[0046] For example, the network (500) includes a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and combinations thereof, and may include wired internet, wireless internet, and mobile wireless communication networks. Additionally, wireless communication may include, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth Low Energy, ZigBee, WFD (Wi-Fi Direct), UWB (ultra wideband), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), but is not limited thereto.
[0047] Referring to FIG. 2, a medical device safety management server (100) according to one embodiment of the present invention may include a communication unit (110), a processor (120), and a memory (130). The medical device safety management server (100) illustrated in FIG. 2 illustrates only the components related to the present embodiment to prevent the features of the present embodiment from being obscured. Therefore, a person skilled in the art related to the present embodiment will understand that other general-purpose components may be included in addition to the components illustrated in FIG. 2.
[0048] The medical device safety management server (100) may be implemented as a computer device or multiple computer devices that communicate with a patient device (200), multiple medical devices (300), and a medical system server (400) via a network (500) to provide commands, codes, files, content, services, etc. For example, the medical device safety management server (100) may provide a file for installing an application to a user terminal (not shown) connected via the network (500). In this case, the user terminal may install the application using the file provided by the server.
[0049] Additionally, the user may access the medical device safety management server (100) under the control of an operating system (OS) included in the user terminal and at least one program (e.g., a browser or an installed application) to receive services or content provided by the medical device safety management server (100). As another example, the medical device safety management server (100) may establish a communication session for data transmission and reception and route data transmission and reception with the user terminal through the established communication session.
[0050] The medical device safety management server (100) can generate medical device safety management information and provide the generated medical device safety management information to the user. Specifically, the medical device safety management server (100) can store and manage patient information and medical device information collected and transmitted from a patient device (200), a plurality of medical devices (300), and a medical system server (400). In addition, the medical device safety management server (100) can determine a medical device that matches the patient based on the acquired patient information and medical device information, generate usage information of the matching medical device, and update the device information of the matching medical device. In addition, the medical device safety management server (100) can verify the safety status of the matching medical device based on the device information of the matching medical device and provide the safety status of the matching medical device to the user.
[0051] The communication unit (110) can obtain location information of the patient and location information of the medical devices provided by the patient device (200) and the plurality of medical devices (300). The communication unit (110) functions as a communication module using wired or wireless communication and can receive location information transmitted from the patient device (200) and the plurality of medical devices (300). The communication unit (110) may include a configuration for communicating with the patient device (200) and the plurality of medical devices (300) through the network (500) shown in FIG. 1.
[0052] The communication unit (110) can communicate with a medical system server (400) in addition to the patient device (200) and a plurality of medical devices (300). The communication unit (110) can obtain patient order information prescribed to the patient from the medical system server (400).
[0053] Additionally, the communication unit (110) can provide the result data processed by the processor (120) to a user terminal or a medical system server (400).
[0054] The processor (120) may include any type of device capable of processing data and may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Instructions may be provided to the processor (120) by memory (130) or a communication unit (110). For example, the processor (120) may be configured to execute instructions received according to program code stored in a recording device such as memory (130).
[0055] For example, a processor (120) may refer to a data processing device embedded in hardware having a physically structured circuit to perform a function expressed by code or instructions included in a program. Examples of such data processing devices embedded in hardware may include a microprocessor, a central processing unit (CPU), a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., but the scope of the present invention is not limited thereto.
[0056] Memory (130) is a computer-readable recording medium and may include a non-perishable permanent mass storage device such as RAM (random access memory), ROM (read only memory), and a disk drive. Additionally, the memory (130) may store an operating system and at least one program code (e.g., code for a browser installed and running on a user terminal or the aforementioned application). These software components may be loaded from a computer-readable recording medium separate from the memory (130) using a drive mechanism. This separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, disk, tape, DVD / CD-ROM drive, or memory card. In another embodiment, the software components may be loaded into the memory (130) via a communication unit (110) rather than a computer-readable recording medium. For example, at least one program may be loaded into memory (130) based on a program (e.g., the application described above) that is installed by files provided through a network (500) by developers or a file distribution system that distributes installation files for applications.
[0057] At least one program code for controlling a patient device (200), a plurality of medical devices (300), or a medical system server (400) may be stored in the memory (130). Additionally, at least one program code for generating safety information of a medical device from location information obtained from the patient device (200) and the plurality of medical devices (300) may be stored.
[0058] The memory (130) can perform the function of temporarily or permanently storing data processed by the medical device safety management server (100). When the medical device safety management server (100) is connected to multiple patient devices (200), the memory (130) can compress and encrypt the data for each patient and store and manage it. Additionally, the memory (130) can store and manage device information for multiple medical devices (300) for each medical device.
[0059] The medical device safety management server (100) may further include an input / output interface (not shown). The input / output interface may be a means for interfacing with an input / output device. For example, the input device may include a device such as a keyboard or a mouse, and the output device may include a device such as a display for displaying a communication session of an application. As another example, the input / output interface may be a means for interfacing with a device in which the functions for input and output are integrated into one, such as a touchscreen.
[0060] As a more specific example, the processor (120) of the medical device safety management server (100) may display a service screen or content related to medical device safety information on a display through an input / output interface while processing instructions of a computer program loaded into memory (130).
[0061] Meanwhile, although the present specification describes the medical device safety management server (100) on the premise that it is provided separately from the medical system server (400), the medical device safety management server (100) may be provided with the same configuration as the medical system server (400). That is, the medical device safety management server (100) may be provided in the medical system server (400) and may be constructed as a single server.
[0062] Below, with reference to the drawings, a medical device safety management method performed on a medical device safety management server (100) is described.
[0063] FIG. 3 is a flowchart illustrating a medical device safety management method according to an embodiment of the present invention, FIG. 4 is a diagram for explaining the medical device safety management method of FIG. 3, and FIG. 5 is a flowchart illustrating a method for generating usage information of a matching medical device according to an embodiment of the present invention.
[0064] Referring to FIGS. 3 to 5, a medical device safety management method according to one embodiment of the present invention includes the steps of obtaining patient location information (S100), obtaining location information of a plurality of medical devices (S200), generating usage information of a matching medical device matched with a patient using the patient location information and the medical device location information (S300), updating device information of a matching medical device stored using the generated usage information (S400), checking the safety status of the matching medical device according to the device information of the matching medical device and providing the safety status of the matching medical device to a user (S500), and may further include the step of obtaining patient order information prescribed to the patient (S600).
[0065] First, a medical device safety management method according to one embodiment of the present invention obtains patient location information using a patient device (200) (S100).
[0066] The patient device (200) may be a mobile device or wearable device carried by the patient, or a hospital device such as a patient bed where the patient stays while using the medical device (300). In one embodiment, the patient device (200) may include a position measurement module (e.g., a GPS module, an inertial measurement unit (IMU), etc.) to obtain the patient's position information.
[0067] Here, the patient's location information may be location information measured in real-time or periodically by the patient device (200). The patient stays in a hospital, such as in a hospital room, treatment room, operating room, emergency room, intensive care unit, or intensive care unit, and uses a medical device. During the use of the medical device, the patient device (200) is carried by the patient or placed adjacent to the patient. At this time, the patient device (200) can measure the location in real-time or periodically, and the location information measured by the patient device (200) can be assumed to be the patient's location.
[0068] Meanwhile, a medical device safety management server (100) according to one embodiment of the present invention communicates with a patient device (200) through a communication unit (110) and can receive location information of the patient transmitted by the patient device (200).
[0069] Next, location information of each medical device is obtained from a plurality of medical devices (300) (S200).
[0070] The medical device (300) may be a medical device in a hospital where safety management is required. For example, the medical device (300) may include monitoring devices such as a mobile monitor, a cardiac output monitor, a pulse oximeter, and an end-tidal carbon dioxide partial pressure monitor, respiratory devices such as a ventilator, a drug infusion device, a defibrillator, ECMO, a hemodialysis device, etc. Meanwhile, the multiple medical devices (300) may include various types of medical devices, and may include multiple medical devices of the same type with the same model.
[0071] In one embodiment, each medical device (300) may include a position measurement module (e.g., a GPS module, an inertial measurement unit (IMU), etc.) to measure position information. Here, the position information measured by each medical device (300) may be position information measured in real time or periodically.
[0072] The communication unit (110) of the medical device safety management server (100) can receive location information measured from each medical device (300) and obtain location information of multiple medical devices. At this time, the medical device location information may be measured at the same frequency as the patient's location information.
[0073] The communication unit (110) can match the patient's location information and the medical device's location information at the same time interval based on the patient's location information, and can transmit the matched patient's location information and the medical device's location information to the processor (120). Meanwhile, the step of obtaining the patient's location information (S100) and the step of obtaining the medical device's location information (S200) from the medical device safety management server (100) can be performed simultaneously.
[0074] Next, using the patient's location information and the medical device's location information, usage information of the medical device matched with the patient is generated (S300).
[0075] The processor (120) can identify medical devices included within a pre-set range (A) centered on the patient's location by using the patient's location information and the medical device's location information. Specifically, as shown in FIG. 4, the processor (120) can identify medical devices (301, 302, 303, 304) included within the pre-set range (A) among a plurality of medical devices (300) that have transmitted location information.
[0076] At this time, the pre-set range (A) may be a designated area where the medical device used by the patient is placed. In one embodiment, the pre-set range (A) may be set within a radius of 1m centered on the location of the patient, which is the location of the patient device (200).
[0077] Next, the processor (120) can determine a matching medical device that is matched to a patient among medical devices (301, 302, 303, 304) included within a pre-set range (A) by using the device information of the previously stored medical device. Here, a matching medical device refers to a medical device used for a patient among a plurality of medical devices.
[0078] Here, the device information of the medical device refers to information related to the medical device stored in the medical device safety management server (100). For example, the device information of the medical device may include basic information such as the name, identification information, manufacturer, manufacturing number, version, model number, affiliation, installation location, and risk class of the medical device stored in the medical device safety management server (100) by the user, management records such as failure history, inspection history, repair history, and recall history, and safety letter information distributed by government agencies or medical organizations. In addition, the device information of the medical device may include medical device usage information and medical device safety information generated and stored by the medical device safety management server (100).
[0079] If multiple medical devices (301, 302, 303, 304) exist within a pre-set range (A), the processor (120) can search for medical devices of the same type (303, 304) using the device information of the medical devices. Subsequently, among the medical devices of the same type (303, 304) found, the medical device (303) located closer to the patient and the medical devices (301, 302) for which no medical devices of the same type were found are determined as matching medical devices.
[0080] At this time, the determination of which medical device among the searched medical devices of the same type (303, 304) is located closer to the patient can be made by comparing the distance (d1, d2) from the patient using the location information of the medical devices of the same type (303, 304).
[0081] That is, the processor (120) can determine different types of medical devices that are located within a pre-set range (A) from the patient and are positioned adjacent to the patient as matching medical devices for the patient by using the patient's location information and the medical device's location information.
[0082] Next, generate usage information for the determined matching medical device.
[0083] Since the matched medical device assigned to a patient is a medical device presumed to be used by the patient, usage information at the current time of use by the patient is generated. The usage information of the matched medical device may include the user's identification information, date and time of use, and the number of uses, and may also include the duration of use.
[0084] The above number of uses may be determined from the number of times the matching medical device is matched to a patient, and each time it is matched to a patient, it may be counted as one use. The above usage time may be calculated from the time the matching medical device is matched to a patient until the time the matching medical device goes out of a pre-set range (A). In another embodiment, the above usage time may be a time modified by user feedback input.
[0085] The matching medical device that matches the patient is a medical device requiring safety management monitoring, and can be classified into medical devices requiring monitoring of the number of uses and medical devices requiring monitoring of the usage time. Examples of medical devices requiring monitoring of usage time include drug infusion devices, ECMO, and hemodialysis devices, where the actual operating time after power is turned on is important, including consumables such as motors. Accordingly, for medical devices requiring monitoring of usage time, it may be important to generate usage information that includes the usage time. The processor (120) can determine whether the matching medical device requires monitoring of usage time by using the device information of the medical device, and if it is determined to be a medical device requiring monitoring of usage time, it can generate usage information that includes the usage time.
[0086] Next, the device information of the previously stored matching medical device is updated using the generated usage information (S400).
[0087] The processor (120) can manage the usage information of the matching medical device by updating the previously stored device information of the matching medical device using the usage information of the matching medical device. That is, when the medical device is matched with a patient, the processor (120) can update the device information by integrating the newly generated usage information with the previously stored device information, and save the updated new device information as the device information of the matching medical device.
[0088] Next, the safety of the matching medical device is checked based on the device information of the matching medical device, and the safety of the matching medical device is provided to the user (S500).
[0089] Here, the device information of the matching medical device used to verify the safety of the matching medical device may be the previously stored device information of the matching medical device, rather than the information updated in step S400. That is, the processor (120) can provide the user with the safety status of the matching medical device at a stage prior to using the matching medical device. Specifically, in the case where a medical device located away from the patient approaches the patient and is placed within a pre-set range (A), the processor (120) can immediately verify the safety status of the matching medical device using the previously stored device information of the matching medical device when the medical device enters the pre-set range (A) and is matched with the patient, and provide the verified safety status of the matching medical device to the user.
[0090] However, the present invention is not limited thereto, and the device information of the matching medical device used to verify the safety of the matching medical device may be the information updated in step S400. The processor (120) can verify the safety of the matching medical device based on the updated device information of the matching medical device and can provide the verified safety of the matching medical device to the user.
[0091] The medical device safety management server (100) can provide the user with information regarding the safety status of a verified matching medical device through the matching medical device. For example, the medical device may be equipped with at least one notification device, and the processor (120) may be connected to the notification device to provide a notification corresponding to the safety status of the matching medical device in various ways, such as light, vibration, or a message. At this time, the notification may be visual feedback provided on a display included in the medical device, or auditory feedback through sound.
[0092] In one embodiment, the medical device may be provided with at least one light-emitting element, and the processor (120) may control the light-emitting element to provide a notification (e.g., green, orange, red) corresponding to the safety status of the medical device (e.g., normal, caution, danger).
[0093] Additionally, the processor (120) may provide safety information of the medical device to the user when the safety status of the medical device is confirmed to be dangerous or cautionary. When the user confirms a notification corresponding to caution or danger through the medical device's notification device, the user may access the medical device safety management server (100) through a user terminal, etc., and may check medical device safety information such as failure history, malfunction history, and usage information of the medical device stored in the medical device safety management server (100).
[0094] Meanwhile, the safety status of the matching medical device may be calculated based on management records such as usage information, failure history, inspection history, repair history, and recall history among the previously stored or updated device information of the matching medical device. The calculated safety status of the matching medical device may be stored in the medical device safety management server (100) as medical device safety information.
[0095] In another embodiment, the safety of the matching medical device may be determined based on the number of uses among the device information of the matching medical device. The processor (120) may determine the safety of the matching medical device by checking the number of uses of the matching medical device that has been stored or updated and comparing it with the number of uses of a pre-set safety range.
[0096] In another embodiment, the safety of the matching medical device may be determined based on the usage time among the device information of the matching medical device. The processor (120) may determine the safety of the matching medical device by checking the usage time of the matching medical device that has been stored or updated and comparing it with the time of a pre-set safety range.
[0097] In another embodiment, the safety of the matching medical device may be determined based on safety letter information among the device information of the matching medical device. The medical device safety management server (100) may receive safety letter information distributed by government agencies or medical organizations, and the processor (120) may determine the safety of the matching medical device based on the received safety letter information.
[0098] Specifically, the processor (120) can determine the safety status of the matching medical device based on the failure history of the matching medical device. If the number of failures exceeds a pre-set safety range, the processor (120) can determine the safety status of the medical device as a dangerous state or a caution state.
[0099] Additionally, the processor (120) may determine whether the matching medical device is safe based on the risk level of the equipment group to which the matching medical device belongs.
[0100] Meanwhile, if the safety status of the confirmed matching medical device does not correspond to a safe state, the processor (120) can generate usage information corresponding to the dangerous state of the matching medical device and update the device information of the matching medical device using the generated usage information.
[0101] The safety status of the matching medical device provided to the user may include grade information corresponding to the risk grade or management grade of the medical device. Here, the risk grade of the medical device is a grade indicating the degree of risk of the medical device, and the management grade of the medical device is a grade indicating the degree to which the medical device requires management. The processor (120) can determine the risk grade of the medical device and also determine the management grade of the medical device by evaluating the risk level for each medical device based on the device information of each medical device.
[0102] Specifically, the processor (120) can determine a risk level or a management level based on usage information generated by matching the medical device information with a patient. The medical device safety management server (100) can provide the determined risk level or management level to the user, and the risk level provided to the user can help the user decide whether to continue using the medical device or stop using it, and the management level can enable the user to identify medical devices that require management.
[0103] Meanwhile, the medical device safety management server (100) may further include a learning unit trained to evaluate the safety of a matching medical device. The learning unit may be an artificial neural network trained to determine a matching medical device using the patient's location information and the medical device's location information, and to evaluate the safety of the matching medical device using the device information of the matching medical device. In this case, the artificial neural network may be trained by machine learning or deep learning techniques. As an example, the artificial neural network may be a neural network based on a Convolutional Neural Network (CNN) model. In this case, the CNN model may be a layered model used to extract features of input data by alternately performing a plurality of computation layers (Convolutional Layer, Pooling Layer). However, the present invention is not limited thereto, and it is understood that any artificial neural network for learning the criteria for evaluating the safety of a medical device may be used.
[0104] Meanwhile, a medical device safety management method according to one embodiment of the present invention may further include a step (S600) of obtaining patient order information prescribed to a patient. The step of obtaining patient order information (S600) may be performed simultaneously with the step of obtaining patient location information (S100) and the step of obtaining medical device location information (S200), but is not limited thereto.
[0105] The patient's order information may include treatment order information, test order information, and medication order information prescribed to the patient, and may be entered and stored in the medical system server (400) by the patient's medical staff. The communication unit (110) of the medical device safety management server (100) can communicate with the medical system server (400) to obtain the patient's order information transmitted by the medical system server (400).
[0106] In one embodiment, the processor (120) can determine a matching medical device and generate usage information using the patient's location information, the location information of the medical device, and the patient's order information. Specifically, as illustrated in FIG. 5, the step of generating usage information of a matching medical device using the patient's order information may include a step of determining a medical device included within a pre-set range based on the patient's location information (S310), a step of determining a matching medical device among the medical devices determined using the patient's order information (S320), and a step of generating usage information of the determined matching medical device (S330).
[0107] First, the processor (120) identifies a medical device included within a pre-set range (A) centered on the patient's location using the patient's location information and the medical device's location information (S310).
[0108] Next, using the patient's order information, a matching medical device corresponding to the patient's order information is determined among the medical devices included within a pre-set range (A) (S320).
[0109] The processor (120) can select different types of medical devices placed adjacent to the patient among the medical devices included within a pre-set range (A), and determine a matching medical device by matching them with the patient's order information. Since the order information includes a medical doctor's prescription related to the use of a specific medical device, the processor (120) can determine only the medical device corresponding to the order information among the selected medical devices as the matching medical device using the order information.
[0110] Next, usage information for the determined matching medical device is generated (S330).
[0111] The processor (120) can generate usage information including the number of uses and / or usage time of the determined matching medical device.
[0112] Meanwhile, in emergency situations, the patient's order information may be entered into the medical system server (400) after the patient's use of the medical device is finished. In this case, the processor (120) may check the order information entered after the user's treatment and generate usage information for the medical device corresponding thereto.
[0113] If the medical device safety management server (100) further includes a learning unit that is trained to evaluate the safety of a matching medical device, the learning unit may be trained to determine the matching medical device using the patient's location information, the medical device's location information and the patient's order information, and to evaluate the safety of the matching medical device using the device information of the matching medical device.
[0114] Meanwhile, the medical device safety management server (100) may provide medical device safety management information to the user at the user's request or periodically. The medical device safety management information may include the safety status of the medical device, the number of times the medical device is used, the usage time, the breakdown history, inspection history, repair history, etc. At this time, the processor (120) may calculate the items included in the medical device safety management information into a score and provide it to the user.
[0115] Additionally, the medical device safety management server (100) can generate inspection plans and repair plans for medical devices using medical device safety management information, and can provide notifications related to the medical device inspection plans and repair plans to the user. Additionally, the medical device safety management server (100) can calculate failure rates and expected lifespans for each medical device, and can generate a medical device safety management guide that includes these.
[0116] The medical device safety management method and medical device safety management server (100) according to embodiments of the present invention can automatically generate usage information of the medical device using patient location information and medical device location information, and derive safety information of the medical device using this, thereby enabling automation of medical device safety management and efficient safety management. In addition, the cost and time consumed in medical device safety management can be significantly reduced, and the failure rate of the medical device can be reduced, thereby reducing the cost used for repair and replacement of the medical device.
[0117] The embodiments may also be implemented in the form of a recording medium containing computer-executable instructions, such as program modules executed by a computer. A computer-readable medium may be any available medium accessible by a computer and includes both volatile and non-volatile media, and both removable and inremovable media. Additionally, a computer-readable medium may include both computer storage media and communication media. A computer storage medium includes both volatile and non-volatile, removable and inremovable media implemented by any method or technique for storing information, such as computer-readable instructions, data structures, program modules, or other data. A communication medium typically includes computer-readable instructions, data structures, other data of modulated data signals such as program modules, or other transmission mechanisms, and includes any information transmission medium.
[0118] Additionally, in this specification, "part" may be a hardware component, such as a processor or circuit, and / or a software component executed by a hardware component, such as a processor.
[0119] As such, the present invention has been described with reference to an embodiment illustrated in the drawings, but this is merely illustrative, and those skilled in the art will understand that various modifications and variations of the embodiments are possible therefrom. Accordingly, the true technical scope of protection of the present invention should be determined by the technical spirit of the appended claims. Explanation of the symbols
[0120] 1 : Medical Device Safety Management System 100 : Medical device safety management server 200 : Patient device 300 : Medical device 400: Medical System Server 500 : Network
Claims
Claim 1 A method for managing the safety of a medical device, comprising: a step of obtaining location information of the patient using a patient device; a step of obtaining location information of the medical device from a plurality of medical devices; a step of generating usage information of a matching medical device matched with the patient using the location information of the patient and the location information of the medical device; a step of updating device information of the matching medical device that has been stored using the generated usage information; and a step of immediately determining the safety status of the matching medical device based on device information of the matching medical device that has been stored prior to the update when the matching medical device is matched with the patient, and providing the determined safety status of the matching medical device to a user terminal distinct from the patient device, wherein if the safety status is confirmed to be caution or danger, providing safety information of the matching medical device including at least one of failure history, malfunction history, and usage information of the matching medical device to the user terminal. Claim 2 A medical device safety management method according to claim 1, further comprising the step of obtaining the patient’s order information prescribed to the patient; wherein the step of generating usage information of the matching medical device generates usage information of the matching medical device using the patient’s location information, the location information of the medical device, and the patient’s order information. Claim 3 A method for managing the safety of a medical device according to claim 2, wherein the patient's order information includes at least one of treatment order information, test order information, and medication order information prescribed to the patient. Claim 4 A method for managing the safety of a medical device according to claim 2, wherein the step of generating usage information of the matching medical device comprises: a step of identifying a medical device included within a pre-set range based on the patient's location information; a step of determining the matching medical device among the medical devices included within the pre-set range using the patient's order information; and a step of generating usage information of the determined matching medical device. Claim 5 A medical device safety management method according to claim 1, wherein the safety of the matching medical device is determined based on the number of times the device information of the matching medical device is used. Claim 6 A medical device safety management method according to claim 1, wherein the safety of the matching medical device is determined based on the usage time of the device information of the matching medical device. Claim 7 A medical device safety management method according to claim 1, wherein the safety of the matching medical device is determined based on the management records of the matching medical device. Claim 8 A medical device safety management method according to claim 1, wherein the safety of the matching medical device is determined based on safety letter information of the matching medical device. Claim 9 A computer-readable recording medium having a program recorded thereon for performing a method according to any one of claims 1 to 8. Claim 10 A memory for storing at least one program; a communication unit for transmitting and receiving data with a patient device, a plurality of medical devices, and a medical system server; and at least one processor that determines the safety status of the medical device by executing the at least one program and provides it to a user terminal; wherein the memory comprises the step of the at least one processor obtaining location information of the patient from the patient device; the step of obtaining location information of the medical device from a plurality of medical devices; the step of generating usage information of a matching medical device matched with the patient using the patient's location information and the location information of the medical device; and the step of updating the previously stored device information of the matching medical device using the generated usage information. A medical device safety management server characterized by including instructions to execute the step of: immediately determining the safety status of the matching medical device based on device information of the matching medical device stored prior to the update when the matching medical device is matched with the patient; providing the determined safety status of the matching medical device to a user terminal distinct from the patient device; and, if the safety status is confirmed to be caution or danger, providing safety information of the matching medical device, including at least one of failure history, malfunction history, and usage information of the matching medical device, to the user terminal.
Citation Information
Patent Citations
The method and appartus for scheduling of medical device based on medical device characteristics and medical personnel operation experience
KR1020230043401A
