KR102136215B1 - Medical device management method and system thereof - Google Patents

Abstract

A medical device management method is provided. A control method of a system for managing medical devices according to the present invention includes: a step of allowing an agency terminal to obtain barcode information of a medical device for management of warehousing the medical device (S110); a step of allowing a server to register the medical device as inventory of the store terminal when obtaining the barcode information of the medical device from the store terminal (S120); a step of allowing the store terminal to transmit provisional release information for the medical device to a hospital to the server (S130); and a step of allowing the server to register the medical device as hospital inventory (S140).

Description

MEDICAL DEVICE MANAGEMENT METHOD AND SYSTEM THEREOF}

The present invention relates to a medical device management method and system.

Medical practice is an activity related to human life, and its importance cannot be said. Therefore, a person who can perform a medical action is strictly limited, and furthermore, medical devices used to perform a medical action are also strictly managed.

It is a reality that medical devices are managed differently from general items due to their specificity. Specifically, even in products that perform the same function, various products exist according to detailed standards (length, width, thickness, etc.), and all existing products must be managed without fail, so the types of items subject to management vary. .

In addition, since the medical device should be used immediately in a situation necessary for a hospital, there is a problem that it cannot be used immediately when necessary when stored in an agency selling medical devices. Therefore, most medical devices are entrusted to the hospital, and after the medical devices are used, sales processing is performed afterwards.

Due to the specificity of the above-described medical device, there is a need for a method and system for managing the medical device, grasping inventory, and replacing the medical device according to the stock.

Registered Patent Publication No. 10-1886172 (2018.08.01)

The problem to be solved by the present invention is to provide a medical device management method and system.

The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the following description.

A method of controlling a system for managing a medical device according to an aspect of the present invention for solving the above-described problem includes: obtaining a bar code information of the medical device by a dealer terminal for managing medical device receipt (S110); When the server obtains barcode information of the medical device from the agency terminal, registering the medical device as inventory of the agency terminal (S120); Transmitting, by the agency terminal, runaway information to run the medical device to the hospital (S130); And the server, registering the medical device as inventory of the hospital (S140).

At this time, the control method, the server, registering a plurality of medical devices as inventory of the hospital (S210); The server, receiving information about the medical device existing in the hospital from the dealer terminal (S220); Comparing information on a plurality of medical devices registered in the inventory and information on medical devices received from the agency terminal, obtaining information on medical devices used by the hospital (S230); have.

In this case, the barcode information may include stock keeping unit (SKU) information, medical device standard code information, and shelf life information.

At this time, the control method, the server, when receiving data indicating that the medical device is used, deleting the medical device from the hospital inventory (S310); Generating a transaction statement for the deleted medical device (S320); And transmitting the generated transaction statement to the agency and the hospital (S330).

At this time, the deleting step (S310), the medical device, when the medical device is opened, generating the medical device opening signal (S311); Transmitting, by the medical device, the data including the opened signal to the server (S312); The server deleting the medical device from the hospital inventory (S313); It may include.

At this time, the opening signal is generated by an opening signal generating device including a pressure sensor and a communication unit, and the opening signal generating device may be attached to an opening of the medical device.

At this time, the control method, the server, obtaining a shelf life of the medical device based on the barcode information (S410); The server, in the hospital, obtaining a first usage history for the same medical device as the medical device (S420); The server, in a plurality of hospitals, obtaining a second usage history for the same medical device as the medical device (S430); Determining a possibility of replacing the medical device based on the shelf life of the medical device, the first usage history, and the second usage history (S440); And if the replaceability is greater than a preset criterion, the server transmits a message proposing to replace the medical device to the agency terminal (S450); The history of use for the medical device includes the expiration date of the medical device, when the medical device is received at the hospital, when the medical device is used, and when the medical device is used. Can.

At this time, determining the possibility of replacing the medical device (S440) comprises: obtaining data for a plurality of hospitals using the medical device (S441); Clustering data for the obtained plurality of hospitals (S442); Of the plurality of clusters obtained through the clustering, obtaining a cluster associated with the hospital (S443); And determining a possibility of replacing the medical device based on usage history information of at least one hospital corresponding to the obtained cluster (S444). It may include.

Other specific matters of the present invention are included in the detailed description and drawings.

According to various embodiments of the present disclosure described above, the present invention can effectively manage a medical device.

The effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description.

1 and 2 is a system diagram for explaining a medical device management system according to an embodiment of the present invention.
3 is a flowchart illustrating a method of registering a medical device as a hospital inventory according to an embodiment of the present invention.
4 is a flowchart illustrating a method of grasping a medical device used by a hospital according to an embodiment of the present invention.
5 is a flowchart illustrating a method of deleting a used medical device from a hospital inventory and generating a transaction statement for the deleted medical device according to an embodiment of the present invention.
6 is a flowchart illustrating a method of determining a used medical device according to an embodiment of the present invention.
7 is a flowchart illustrating a method of replacing a medical device considering a shelf life of the medical device according to an embodiment of the present invention.
8 is a flowchart illustrating a method of determining a replaceability according to an embodiment of the present invention.
9 is a block diagram illustrating the configuration of an apparatus according to an embodiment of the present invention.
10 is an exemplary view for explaining a method of attaching an opening signal generating apparatus according to an embodiment of the present invention.

Advantages and features of the present invention, and methods for achieving them will be clarified with reference to embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments allow the disclosure of the present invention to be complete, and are common in the technical field to which the present invention pertains. It is provided to fully inform the skilled person of the scope of the present invention, and the present invention is only defined by the scope of the claims.

The terminology used herein is for describing the embodiments and is not intended to limit the present invention. In the present specification, the singular form also includes the plural form unless otherwise specified in the phrase. As used herein, “comprises” and/or “comprising” does not exclude the presence or addition of one or more other components other than the components mentioned. Throughout the specification, the same reference numerals refer to the same components, and “and/or” includes each and every combination of one or more of the components mentioned. Although "first", "second", etc. are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are only used to distinguish one component from another component. Therefore, it goes without saying that the first component mentioned below may be the second component within the technical spirit of the present invention.

Unless otherwise defined, all terms (including technical and scientific terms) used in this specification may be used in a sense that can be commonly understood by those skilled in the art to which the present invention pertains. In addition, terms that are defined in a commonly used dictionary are not ideally or excessively interpreted unless specifically defined.

The term "part" or "module" as used in the specification means a hardware component such as software, FPGA or ASIC, and "part" or "module" performs certain roles. However, "part" or "module" is not meant to be limited to software or hardware. The "unit" or "module" may be configured to be in an addressable storage medium or may be configured to reproduce one or more processors. Thus, as an example, “part” or “module” means components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, Includes procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, database, data structures, tables, arrays and variables. The functionality provided within components and "parts" or "modules" can be combined into a smaller number of components and "parts" or "modules" or into additional components and "parts" or "modules" Can be further separated.

The spatially relative terms “below”, “beneath”, “lower”, “above”, “upper”, and the like are shown in the figure as one figure. It can be used to easily describe a correlation between a component and other components. The spatially relative terms should be understood as terms including different directions of components in use or operation in addition to the directions shown in the drawings. For example, if a component shown in the drawing is turned over, a component described as "below" or "beneath" of another component will be placed "above" of the other component. Can. Thus, the exemplary term “below” can include both the directions below and above. The component can also be oriented in other directions, so that spatially relative terms can be interpreted according to the orientation.

In the present specification, the computer means all kinds of hardware devices including at least one processor, and may be understood as a meaning encompassing a software configuration operating in a corresponding hardware device according to an embodiment. For example, a computer may be understood as meaning including, but not limited to, a smartphone, a tablet PC, a desktop, a laptop, and user clients and applications running on each device.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Each step described in this specification is described as being performed by a computer, but the subject of each step is not limited thereto, and according to an embodiment, at least some of the steps may be performed in different devices.

1 and 2 is a system diagram for explaining a medical device management system according to an embodiment of the present invention.

As shown in FIG. 1, the medical device management system may include a medical device 10, a server 20, and an agency terminal 30.

The medical device 10 may be worn at an agency or hospital. At this time, the medical device may include a barcode indicating its own information. The information of the medical device may be transmitted to the agency terminal 30 or the server 20 and registered as inventory of the agency or hospital.

The medical device 10 in the present invention includes various medical devices. In one embodiment, the medical device according to the present invention may include a medical device disclosed in the provisions regarding medical device items and product grades notified to the Ministry of Food and Drug Safety. Accordingly, the medical device 10 in the present invention may include instruments and machines, medical supplies, dental materials, in vitro diagnostic reagents, and the like. However, of course, the medical device 10 in the present invention may include various other medical devices, and may be applied differently for each country.

On the other hand, the medical device 10 in the present invention may mean the medical device itself, but, of course, can be understood as a configuration including a packaging material for packaging a medical device.

The server 20 is a configuration for managing the medical device 10. Specifically, the server 20 may receive information on the medical device from the medical device 10 or the agency terminal 30 to manage the medical device. At this time, the information on the medical device includes information on the medical device itself, such as the type, quantity, and expiration date of the medical device, and further includes information on the location of the medical device and the actual owner of the medical device. It can be a concept.

The server 20 according to an embodiment of the present invention may be configured as a single server as well as a plurality of servers as needed, and may be a concept including a cloud server.

The agency terminal 30 is configured to transmit the information of the medical device 10 to the server 20. The agency terminal 10 may obtain information such as a barcode included in the medical device 10 and transmit it to the server 20 or register it as inventory of the agency. Dealer terminal 10 is a smart phone (smartphone), tablet PC (tablet personal computer), mobile phone (mobile phone), video phone, e-book reader (e-book reader), desktop PC (desktop PC), laptop PC ( laptop PC), a netbook computer (netbook computer), a workstation (workstation), a server, a personal digital assistant (PDA), and a portable multimedia player (PMP).

Meanwhile, as illustrated in FIG. 2, the medical device management system may further include a hospital terminal 40. The hospital terminal 40 is configured to acquire information on whether to use the medical device 10 worn in the hospital. The hospital terminal 40 does not need to be owned by the hospital, and may be a terminal owned by an agency or a terminal owned by an administrator of the server 20 as needed.

3 is a flowchart illustrating a method of registering a medical device as a hospital inventory according to an embodiment of the present invention.

In step S110, the agency terminal 30 may acquire barcode information of the medical device. At this time, the barcode information may include various information. In one embodiment, the barcode information may include country code information, manufacturer code information, product list code information, and check digits. Further, the barcode information may include stock keeping unit (SKU) information, medical device-specific identification code information (UDI), and shelf life information. SKU stands for inventory management code, and it is an identification management code used to facilitate tracking of individual products for inventory management purposes. UDI is information that can grasp the entire cycle information from production to distribution of medical devices, and can be linked to a database in which medical device information is stored. Needless to say, the barcode may be a one-dimensional barcode or a two-dimensional barcode.

In step S120, the server 20 may register the medical device 10 as inventory of the agency terminal. Specifically, the server 20 may register the medical device 10 as the stock of the agency by receiving information that the medical device is to be registered as the stock of the agency from the agency terminal 30.

In step S130, the agency terminal 30 may transmit the runaway information to the server 20. In this case, the provisional runaway may mean a delivery method in which the medical device 10 is temporarily registered as stock in the hospital before the process of transferring the device according to the transaction of the medical device 10 and generating a transaction statement and transferring the transaction price. Even if the medical device 10 is run away, since the transaction is not completed, there is a need for the agency to manage the medical device 10.

In step S140, the server 20 may register the medical device 10 as a hospital inventory. At this time, registering the medical device 10 as the stock of the hospital means that the medical device 10 that has been run away is stored in the hospital.

4 is a flowchart illustrating a method of grasping a medical device used by a hospital according to an embodiment of the present invention.

In step S210, the server 20 may register a plurality of medical devices as hospital inventory. That is, each of the medical devices described in FIG. 2 may be registered as a hospital inventory. According to an embodiment, the server 20 may manage medical devices in a single hospital, but of course, may manage medical devices in each of a plurality of hospitals.

In step S220, the server 20 may receive medical device information of the hospital. At this time, the medical device information may include information on the number of medical devices currently present in the hospital.

In one embodiment, the medical device 10 may include radio frequency identification (RFID). The server 20 may receive medical device information through RFID, and determine the number of medical devices 10 currently present in the hospital.

In step S230, the server 20 may obtain medical device information used by the hospital. That is, the server 20 compares the quantity of the medical devices 10 registered as stocks of the hospital through the runaway process and the quantity of the medical devices 10 actually present in the hospital, and the quantity of the medical devices 10 used. Can judge.

5 is a flowchart illustrating a method of deleting a used medical device from a hospital inventory and generating a transaction statement for the deleted medical device according to an embodiment of the present invention.

In step S310, when the server 20 acquires the medical device 10 usage data, the server 20 may delete the medical device from the hospital inventory. That is, as described in FIG. 4, the server 20 may determine the quantity of the medical device 10 used through a method of checking the quantity of the medical device 10 existing in the hospital, but described in FIG. 5 As described above, data using the medical device 10 may be acquired through various methods, and the quantity of the medical device 10 used based on the medical device 10 usage data may be determined.

In this case, the usage data may include the above-described barcode information and data indicating that a medical device corresponding to the barcode information is used.

In one embodiment, the server 20 may determine whether the packaging of the medical device 10 has been opened to determine the quantity of the medical device 10 used. A detailed embodiment of this will be described later in FIG. 6.

In another embodiment, when the medical device 10 is a medical device including an electronic device, when the first power is supplied to the medical device 10, the server 10 may determine that the medical device 10 is used. have. For example, if the medical device 10 is a medical device that requires power supply, such as a diagnostic X-ray device, the medical device 10 is programmed to generate and transmit data to the server 20 when the communication unit and the first power supply are used. A memory storing the used data generation unit may be further included.

In yet another embodiment, the system can further include an access security system. Specifically, the medical device storage place inside the hospital includes an access security system, and the server 20 can control the access security system. In this case, the server 20 may determine whether or not a person has entered the medical device storage place through the access security system. When a person enters and exits the medical device storage area, the server 20 may receive information about the person who has access from the access security system. The server 20 may transmit information about the person who has entered and exited to the dealer terminal 30. The server 20 may receive a control signal requesting to provide information on the type and quantity of the medical device used to the person entering and exiting the agency terminal 30. The server 20 may receive information on the type and quantity of the used medical device from the hospital and provide it to the agency terminal 20.

As described above, when the system further includes an access security system, when a user whose user information is not registered enters a medical device storage place, information on this may be transmitted to a dealer terminal and a security company.

In step S320, the server 20 may generate a transaction statement for the deleted medical device 10. That is, the server 20 may determine that the deleted medical device 10 has been sold and generate a transaction statement for it. The server 20 may obtain price information for each medical device to generate a transaction statement. In one embodiment, when the medical device 10 does not have a price change (for example, when determining the price at the time of first runaway, the price of the medical device 10), the server 20 is medical to the agency or hospital A transaction statement may be generated based on price information when registering the inventory of the device 10. In another embodiment, if there is a price fluctuation in the medical device (for example, when the price at the time the medical device 10 is used in a hospital is set as the price of the medical device 10), the server 20 May generate a transaction statement based on the price of the medical device 10 at the time of obtaining the usage data.

In step S330, the server 20 may transmit the generated transaction statement to the agency and hospital. Of course, the server 20 may further include a transaction price transmission step according to the transaction specification.

In one embodiment, the transaction price can be transferred directly through the server 20. In another embodiment, the transaction price is transferred through a financial institution, and the server 20 may receive data about the transfer from the financial institution to complete the medical device 10 transaction process.

6 is a flowchart illustrating a method of determining a used medical device according to an embodiment of the present invention.

In step S311, when the medical device 10 is opened, the medical device 10 may acquire a signal for opening the medical device.

At this time, the opening signal may be obtained by the opening signal generating device 15 attached to the medical device 10. In one embodiment, the opening signal generating device may include at least one of a pressure sensor, a communication unit, a memory, and a processor.

The opening signal generating device will be described in detail with reference to FIG. 10. Specifically, when the pressure of the pressure sensor is equal to or less than a preset value, the unsealing signal generating device 15 may determine that the medical device 10 has been opened and transmit the unsealing signal to the server 20.

That is, in step S312, the medical device 10 may transmit the opening signal to the server 20.

At this time, the opening signal may include information about the medical device. In one embodiment, the opening signal may include barcode information.

In step S313, the server 20 may delete the medical device corresponding to the transmitted opening signal from the hospital inventory. That is, the server 20 may determine whether any medical device among the plurality of medical devices received in the hospital is opened based on information on the medical device included in the opening signal.

At this time, the opening signal generating device 15, as shown in Figure 10, may include a cover coupling portion (11,12) and the cover portion (13,14). The medical device 10 may be packaged by the lid coupling portions 11 and 12 covering the packaging box and the covering lid coupling portions 11 and 12 sealed with a tape or the like. At this time, the inner surfaces of the lid coupling portions 11 and 12 and the outer surfaces of the lid portions 13 and 14 may be in contact with each other, and the opening signal generating device 15 is outside the lid portions 13 and 14. It can be placed on the side.

In the state in which the packaging of the medical device 10 is completed, the inner surfaces of the lid coupling portions 11 and 12 and the outer surfaces of the lid portions 13 and 14 are in contact with each other, so that the pressure sensor receives a pressure of a constant intensity. do. However, when the medical device 10 is opened, the pressure sensed by the pressure sensor is lower than the sealed state. Therefore, when the pressure detected by the pressure sensor is lower than a preset value, the unsealing signal generating device 15 may determine that the medical device 10 is opened.

On the other hand, the opening signal generating device 15 according to the present disclosure can be implemented in various ways as needed. In one embodiment, the opening signal generating device 15 may include a light detection sensor (CDS) instead of a pressure sensor, and may be located inside the packaging box. That is, when the packaging box is made of a material capable of blocking light, the unpacking signal generating device 15 includes a light sensing sensor, and when the illuminance detected by the light sensing sensor is greater than or equal to a preset value, generates an unpacking signal. Can.

On the other hand, according to another embodiment of the present invention, the server 20 does not directly receive the opening signal generated by the opening signal generating device, but the hospital inside the medical device storage area where the medical device 10 is stored. The terminal 40 may receive the opening signal. The hospital terminal 40 may collect the opening signal and transmit it to the server 20. At this time, the hospital terminal 40 may include a communication unit for receiving the opening signal. The hospital terminal 40 may include only one-way communication unit Rx for receiving the opening signal, or may include a two-way communication unit Rx/Tx for transmitting the received opening signal to the server 20.

When the hospital terminal 40 includes only the one-way communication unit Rx for receiving the opening signal, the data stored in the hospital terminal 40 may be backed up to the server every predetermined period.

7 is a flowchart illustrating a method of replacing a medical device considering a shelf life of the medical device according to an embodiment of the present invention.

7 and 8, for convenience of explanation, a hospital for replacing a medical device according to the present invention is called a first hospital, and a medical device to be replaced is called a first medical device.

In step S410, the server 20 may obtain a shelf life of the first medical device. As described above, the shelf life of the first medical device may be included in barcode information.

If the shelf life of the first medical device is less than or equal to a specific period, the server 20 may transmit a message for replacing the medical device to the agency terminal 30. At this time, a specific period may be determined through various methods.

In one embodiment, by steps S420 to S450, the server 20 may determine the possibility of replacing the first medical device.

Specifically, in step S420, the server 20 may obtain a first usage history for the first medical device in the medical device management hospital. In this case, the first usage history may mean information about a situation where a hospital uses a medical device. Specifically, the first usage history may be a history of a shelf life of a medical device, a time when the medical device is received at the hospital, a time when the medical device is used, and a remaining shelf life at the time when the medical device is used.

In step S430, the server 20 may obtain a second usage history for the first medical devices in a plurality of hospitals. That is, the first use history obtained in step S420 is the use history of the first medical device in the first hospital, and the use history in step S430 is the first medical device in the plurality of hospitals handling the first medical device. It can mean usage history.

In step S440, the server 20 may determine the possibility of replacing the first medical device. Specifically, the server 20 may determine the possibility of replacing the first medical device based on at least one of the first usage history and the second usage history. In one embodiment, the server 20 acquires data on the remaining shelf life of the used medical device at the time the first medical device is used in the first hospital, and replaces the possibility of replacement based on the remaining shelf life. Can decide. That is, the replacement possibility may be determined based on the first usage history. For example, if the first medical device is used three times in the first hospital and the remaining shelf life is 1, 3, and 8 days at the time the first medical device is used, the server 20 has a remaining shelf life, respectively. The possibility of replacement can be determined based on the average number of days, which is 4 days. That is, if the expiration date of the first medical devices received in the first hospital is 4 days or less, the server 20 may determine that the corresponding first medical device should be replaced. However, in order to determine the possibility of replacement, various methods such as the median value and the mode value may be used as well as using the average value of the remaining shelf life. Alternatively, the server 20 may determine a replacement possibility by adding a weight to the remaining shelf life and calculating an average. For example, when the first medical device is used in a situation in which the shelf life is 1 to m days remaining, the server 20 assigns a first weight to the corresponding first medical device and has a shelf life of m to n days remaining. If the first medical device is used, the second weight is assigned to the first medical device, and if the first medical device is used when the expiration date is n days to l days, the third weight is applied to the first medical device. It can be assigned, and the possibility of replacement can be reviewed based on the assigned weight. In an embodiment, the first to third weights may be exponential functions or output values for natural exponential functions. For example, the weight may be an output value at y=a*e^x+b. In this case, the first weight may be a*e^m+b, the second weight may be a*e^n+b, and the third weight may be a*e^l+b.

In another embodiment, the server 20 acquires data on the remaining expiration date of the used medical device at the time when the first medical device is used in a plurality of hospitals, and is replaceable based on the remaining expiration date. Can decide. That is, the possibility of replacement may be determined based on the second usage history. As a method of determining the replaceability, a method of determining the replaceability using the first usage history described above may be used.

Furthermore, it is needless to say that the possibility of replacement can be determined based on both the first usage history and the second usage history. In this case, the server 20 may weight the first replaceability determined using the first usage history and the second replacement possibility determined using the second usage history, and the weight assigned to the first replacement possibility It may be higher than the weight assigned to the second replacement possibility section.

In step S450, the server 20 may transmit a medical device replacement message to the dealer terminal 30 if the possibility of replacing the medical device is greater than a preset criterion.

8 is a flow chart for explaining in detail a method for determining the possibility of replacement according to an embodiment of the present invention.

In step S441, the server 20 may acquire data for a plurality of hospitals. In this case, the data for the plurality of hospitals may include data on the type of hospital, data on the location of the hospital, data on the distribution of diseases of patients visiting the hospital, data on the main medical field of the hospital, and the like. .

In step S442, the server 20 may cluster data for a plurality of hospitals.

That is, even if it is a plurality of hospitals using the same first medical device, the use condition of the first medical device may be different depending on the type of hospital. For example, the primary medical device, the secondary hospital, and the tertiary hospital may have different amounts of the first medical device, the timing of use, and the amount of use. Alternatively, the amount of the first medical device, the time of use, the amount of use, etc. may be different depending on the location of the hospital, the distribution of diseases of the patient visiting the hospital, and the like. Accordingly, the server 20 may classify a plurality of hospitals by clustering the plurality of hospitals based on various data on the plurality of hospitals.

In step S443, the server 20 may acquire a cluster related to the first hospital among clusters generated by clustering. That is, the server 20 may determine whether the first hospital is the most similar to a hospital cluster among a plurality of hospital clusters generated for a plurality of hospitals.

In step S444, the server 20 may determine the possibility of replacement based on the usage history of the hospital corresponding to the obtained cluster.

Meanwhile, the above-described clustering may be performed by an artificial intelligence model. The server 20 according to an embodiment of the present invention includes a processor, and the processor may include a data learning unit and a data determining unit.

The data learning unit may train the data recognition model to have a criterion for clustering user data. The data learning unit applies a plurality of hospital data and first hospital data as training data to the data recognition model to cluster hospital data or to determine which hospital cluster is the most similar to the first hospital, a data recognition model having a judgment criterion You can create

In one embodiment, the data learning unit may generate or train a data recognition model using the above-described various hospital data as learning data. In this case, the hospital data may include data on the type of hospital, data on the location of the hospital, data on disease distribution of patients visiting the hospital, data on the main medical field of the hospital, and the like.

The data determination unit may determine the type of hospital using the hospital data as recognition data. The data determination unit may determine the type of hospital from the predetermined recognition data using the learned data recognition model. The data determination unit may determine or estimate a predetermined situation based on the predetermined recognition data by obtaining predetermined recognition data according to a preset criterion and applying the acquired recognition data as an input value to the data recognition model.

In addition, the result value output by applying the obtained recognition data to the data recognition model as an input value may be used to update the data recognition model.

At least a portion of the data learning unit and the data determining unit and at least a portion of the data determining unit may be implemented as a software module or manufactured in at least one hardware chip and mounted on the electronic device. For example, at least one of the data learning unit and the data determination unit may be manufactured in the form of a dedicated hardware chip for artificial intelligence (AI), or an existing general-purpose processor (eg, CPU or application processor) or graphics It may be manufactured as part of a dedicated processor (for example, a GPU) and mounted on various electronic devices described above. At this time, the dedicated hardware chip for artificial intelligence is a dedicated processor specialized in probabilistic computation, and has higher parallel processing performance than conventional general-purpose processors, so it can rapidly process computational tasks in the field of artificial intelligence such as machine learning. When the data learning unit and the data determination unit are implemented as a software module (or a program module including an instruction), the software module is a computer-readable non-transitory computer readable media. Can be stored in. In this case, the software module may be provided by the OS or may be provided by a predetermined application. Alternatively, some of the software modules may be provided by the OS, and some of the software modules may be provided by a predetermined application.

Meanwhile, the data learning unit may further include a data acquisition unit, a pre-processing unit, a learning data selection unit, a model learning unit, and a model evaluation unit. The data acquisition unit is configured to acquire learning data according to a specific purpose. The pre-processing unit is a component for pre-processing data acquired by the obtaining unit in a predefined format.

The learning data selection unit may select data necessary for learning from data acquired by the learning data acquisition unit or data pre-processed by the learning data preprocessing unit. The selected training data may be provided to the model training unit. The learning data selection unit may select learning data necessary for learning from acquired or preprocessed data according to a preset selection criterion. In addition, the learning data selection unit may select learning data according to a preset selection criterion by learning by the model learning unit.

The model learning unit is configured to train a data judgment model using learning data. Specifically, when a plurality of pre-built data recognition models exist, the model learning unit may determine, as a data recognition model to learn, a data recognition model having a high relationship between input learning data and basic learning data. In this case, the basic learning data may be pre-classified for each type of data, and the data recognition model may be pre-built for each type of data. For example, the basic training data is classified into various criteria such as the region where the training data is generated, the time when the training data is generated, the size of the training data, the genre of the training data, the creator of the training data, and the type of object in the training data. It may be. The model evaluation unit is configured to improve the results of the data judgment model.

At least one of the above-described data acquisition unit, pre-processing unit, learning data selection unit, model learning unit, and model evaluation unit may be implemented as a software module or manufactured in the form of at least one hardware chip and mounted on an electronic device. For example, at least one of a data acquisition unit, a pre-processing unit, a training data selection unit, a model learning unit, and a model evaluation unit may be manufactured in the form of a dedicated hardware chip for artificial intelligence (AI), or existing It may be manufactured as part of a general-purpose processor (for example, a CPU or application processor) or a graphics-only processor (for example, a GPU), and may be mounted in various electronic devices described above.

In addition, the data determination unit may further include a data acquisition unit, a pre-processing unit, an input data selection unit, a recognition result providing unit, and a model update unit. The data acquisition unit is configured to acquire input data. The pre-processing unit is a component for pre-processing data acquired by the obtaining unit in a predefined format. The input data selection unit is configured to select data necessary for recognition among pre-processed data. The recognition result providing unit is configured to receive data selected from the input data. The model updating unit is configured to update the data judgment model based on the evaluation of the recognition result provided from the recognition result providing unit. At least one of the above-described data acquisition unit, pre-processing unit, input data selection unit, recognition result providing unit, and model update unit may be implemented as a software module or manufactured in the form of at least one hardware chip and mounted on the electronic device. For example, at least one of a data acquisition unit, a pre-processing unit, a training data selection unit, a model learning unit, and a model evaluation unit may be manufactured in the form of a dedicated hardware chip for artificial intelligence (AI), or existing It may be manufactured as part of a general-purpose processor (for example, a CPU or application processor) or a graphics-only processor (for example, a GPU), and may be mounted in various electronic devices described above.

Also, the data judgment model may be constructed in consideration of the application field of the recognition model, the purpose of learning, or the computer performance of the device. The data judgment model may be, for example, a model based on a neural network. The data judgment model can be designed to simulate a human brain structure on a computer. The data judgment model may include a plurality of network nodes having weights, which simulate neurons of a human neural network. A plurality of network nodes may each form a connection relationship so that neurons simulate synaptic activity of sending and receiving signals through synapses. The data judgment model may include, for example, a neural network model or a deep learning model developed from a neural network model. In the deep learning model, a plurality of network nodes may be located at different depths (or layers) and exchange data according to a convolutional connection relationship.

For example, a model such as a deep neural network (DNN), a recurrent neural network (RNN), or a bidirectional recurrent deep neural network (BRDNN) may be used as a data determination model, but is not limited thereto.

9 is a block diagram illustrating the configuration of an apparatus according to an embodiment of the present invention.

The processor 102 may include one or more cores (not shown) and a connection passage (for example, a bus) that transmits and receives signals to and from a graphic processing unit (not shown) and/or other components. .

The processor 102 according to an embodiment performs the methods described with respect to FIGS. 1 to 8 by executing one or more instructions stored in the memory 104.

For example, the processor 102 obtains new learning data by executing one or more instructions stored in memory, and uses the trained model to perform tests on the acquired new learning data, and the test results and labeling. Extracts the first learning data obtained by the obtained information with an accuracy equal to or greater than a predetermined first reference value, deletes the extracted first learning data from the new learning data, and extracts the new learning data from which the extracted learning data is deleted. By using it, the trained model can be trained again.

On the other hand, the processor 102 is a RAM (Random Access Memory, not shown) and a ROM (Read-Only Memory) that temporarily and/or permanently stores signals (or data) processed inside the processor 102. , Not shown). In addition, the processor 102 may be implemented in the form of a system on chip (SoC) including at least one of a graphic processing unit, RAM, and ROM.

The memory 104 may store programs (one or more instructions) for processing and controlling the processor 102. Programs stored in the memory 104 may be divided into a plurality of modules according to functions.

The steps of a method or algorithm described in connection with an embodiment of the invention may be implemented directly in hardware, a software module executed by hardware, or a combination thereof. The software modules may include random access memory (RAM), read only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, hard disk, removable disk, CD-ROM, or It may reside on any type of computer readable recording medium well known in the art.

The components of the present invention may be implemented as a program (or application) to be executed in combination with a hardware computer, and stored in a medium. The components of the present invention can be implemented in software programming or software components, and similarly, embodiments include C, C++, including various algorithms implemented in a combination of data structures, processes, routines or other programming components. , Can be implemented in programming or scripting languages such as Java, assembler, etc. Functional aspects can be implemented with algorithms running on one or more processors.

The embodiments of the present invention have been described above with reference to the accompanying drawings, but those skilled in the art to which the present invention pertains may be implemented in other specific forms without changing the technical spirit or essential features of the present invention. You will understand. Therefore, it should be understood that the above-described embodiments are illustrative in all respects and not restrictive.

10: medical device
20: Server
30: dealer terminal
40: hospital terminal

Claims (10)

In the control method of the system for medical device management,
The dealer terminal, obtaining the barcode information of the medical device for the management of medical device wear (S110);
When the server obtains barcode information of the medical device from the agency terminal, registering the medical device as inventory of the agency terminal (S120);
Transmitting, by the agency terminal, runaway information to run the medical device to the hospital (S130); And
The server includes the step of registering the medical device as inventory of the hospital (S140);
The control method,
When the server receives data indicating that the medical device is used, deleting the medical device from the hospital inventory (S310);
Generating a transaction statement for the deleted medical device (S320); And
Further comprising the step of transmitting the generated transaction statement to the agency and the hospital (S330);
The deleting step (S310),
Generating, by the medical device, an opening signal for the medical device when the medical device is opened (S311);
Transmitting, by the medical device, the data including the opened signal to the server (S312);
The server deleting the medical device from the hospital inventory (S313); Including,
The control method,
Obtaining, by the server, a shelf life of the medical device based on the barcode information (S410);
The server, in the hospital, obtaining a first usage history for the same medical device as the medical device (S420);
The server, in a plurality of hospitals, obtaining a second usage history for the same medical device as the medical device (S430);
Determining a possibility of replacing the medical device based on a shelf life of the medical device, the first usage history, and the second usage history (S440); And
If the replaceability is greater than a preset criterion, the server transmits a message proposing to replace the medical device to the agency terminal (S450); Including,
Determining the possibility of replacing the medical device (S440),
Obtaining data for a plurality of hospitals using the medical device (S441);
Clustering data for the obtained plurality of hospitals (S442);
Of the plurality of clusters obtained through the clustering, obtaining a cluster associated with the hospital (S443); And
Determining a replacement possibility of the medical device based on usage history information of at least one hospital corresponding to the obtained cluster (S444); Including,
The replaceability is determined based on the weight of any one of the first weight, the second weight, and the third weight determined based on the first usage history, but the first weight has a shelf life of 1 day to m days remaining. In the situation, the weight is for the case where the medical device is used, and the second weight is the weight for the case where the medical device is used in a situation where the shelf life is m days to n days remaining, and the third weight is for the shelf life. It is a weight for the case where the medical device is used in a situation where n days to l days remain,
The barcode information includes SKU (stock keeping unit) information, medical device standard code information, and shelf life information,
The history of use for the medical device is characterized in that it is a history of the expiration date of the medical device, when the medical device is received at the hospital, when the medical device is used, and when the medical device is used, and when the medical device is used.
The opening signal,
It is generated by an opening signal generating device including a pressure sensor and a communication unit,
The opening signal generating device,
Characterized in that attached to the opening of the medical device,
The opening signal generating device, the control method, characterized in that disposed on the outer surface of the lid portion of the packaging container implemented so that the inner surface of the lid coupling portion and the outer surface of the lid contact each other. According to claim 1,
The control method,
The server registering a plurality of medical devices as inventory of the hospital (S210);
The server, receiving information about the medical device existing in the hospital from the dealer terminal (S220);
Controlling further comprising the step of obtaining information on medical devices used by the hospital by comparing information on a plurality of medical devices registered with the inventory and information on medical devices received from the agency terminal (S230). Way.

delete delete delete delete delete delete delete delete

Images