KR102595947B1 - Medical device software sharing device and method - Google Patents

Abstract

Receive software information and meta information about medical devices, group meta information based on filter information, classify software information according to grouped meta information, extract filter information corresponding to requested information, and filter the extracted A medical device software sharing device is provided that extracts meta information grouped according to information and extracts software information corresponding to meta information selected among the grouped meta information.

Description

Medical device software sharing device and method {MEDICAL DEVICE SOFTWARE SHARING DEVICE AND METHOD}

The present invention relates to an apparatus and method for sharing medical device software, and more specifically, to an apparatus and method for sharing medical device software.

Conventional medical devices and healthcare-related software (applications, algorithms, etc.) are generally distributed and sold independently through the manufacturer or seller's own platform.

Therefore, a specific organization may have a monopoly on some medical software, and in this case, end-users of medical devices may have limited opportunities to select diverse and high-quality software. This may lead to limitations in opportunities and may result in a lack of development and expansion of medical-related software through competition and improvement through feedback from end users.

Additionally, because it is difficult for end users to access various software, there is very little software that can be directly experienced compared to the speed of software development, and there is also very little software used in medical settings. Accordingly, there may be a disadvantage in that the speed of development of medical device software is slowed down. Moreover, this phenomenon is a disadvantage that can have a negative impact on patients who need to experience a better level of medical benefits through high-quality medical device software.

Public Patent Publication No. 10-2019-0113446 (2019.10.08.)

The technical problem to be solved by the present invention is to provide a medical device software sharing device and method for registering software created to drive a medical device and sharing or selling the registered software.

One aspect of the present invention includes a communication unit that receives software information and meta information about a medical device from a registrant terminal and receives request information for the software information from a purchaser terminal; Group the meta information based on preset filter information, classify the software information according to the grouped meta information, extract filter information corresponding to the request information, and extract meta information grouped according to the extracted filter information. a classification unit for extraction; and an extraction unit that extracts meta information selected from the purchaser terminal among the grouped meta information and extracts software information corresponding to the selected meta information.

Additionally, the software information may be source code generated to control the medical device or connection information with the source code stored in the registrant terminal.

Additionally, the meta information may include public information provided to the purchaser terminal according to the request information and selection information provided based on a disclosure request transmitted from the purchaser terminal.

In addition, when a provision request signal for the selection information is transmitted from the registrant terminal, the communication unit transmits the provision request signal to the purchaser terminal to obtain a provision acceptance signal or provision rejection signal for the selection information from the purchaser terminal. Signals can be transmitted.

In addition, when the allowable modification range for the software information is set by the registrant terminal, the communication unit receives evaluation information according to a modification command input for the allowable modification range to the purchaser terminal, and the classification unit, The number of purchaser terminals that delivered the evaluation information can be counted, and the grouped meta information can be listed in order of the number of counted evaluation information.

In addition, the filter information includes part information indicating the body part with which the medical device is in contact, function information indicating the operation method of the medical device and technology used in the medical device, purpose information indicating the purpose of use of the medical device, It may include authentication information indicating whether the medical device or the software information has been certified by an official organization, and rating information indicating the classification of the medical device.

Another aspect of the present invention is a method of sharing medical device software in a medical device software sharing device, comprising: a communication unit receiving software information and meta information about a medical device from a registrant terminal; The communication unit receiving request information for the software information from the purchaser terminal; A classifier grouping the meta information based on preset filter information and classifying the software information according to the grouped meta information; the classification unit extracting filter information corresponding to the request information and extracting meta information grouped according to the extracted filter information; and extracting meta information selected from the purchaser terminal among the grouped meta information by an extraction unit, and extracting software information corresponding to the selected meta information.

Additionally, the software information may be source code generated to control the medical device or connection information with the source code stored in the registrant terminal.

Additionally, the meta information may include public information provided to the purchaser terminal according to the request information and selection information provided based on a disclosure request transmitted from the purchaser terminal.

In addition, when a provision request signal for the selection information is transmitted from the registrant terminal, the communication unit transmits the provision request signal to the purchaser terminal to obtain a provision acceptance signal or provision rejection signal for the selection information from the purchaser terminal. Signals can be transmitted.

In addition, when the allowable modification range for the software information is set by the registrant terminal, the communication unit receives evaluation information according to a modification command input for the allowable modification range to the purchaser terminal, and the classification unit, The number of purchaser terminals that delivered the evaluation information can be counted, and the grouped meta information can be listed in order of the number of counted evaluation information.

In addition, the filter information includes part information indicating the body part with which the medical device is in contact, function information indicating the operation method of the medical device and technology used in the medical device, purpose information indicating the purpose of use of the medical device, It may include authentication information indicating whether the medical device or the software information has been certified by an official organization, and rating information indicating the classification of the medical device.

According to one aspect of the present invention described above, by providing a medical device software sharing device and method, software created to drive a medical device can be registered, and the registered software can be shared or sold.

1 is a schematic diagram of a medical device software sharing system including a medical device software sharing device according to an embodiment of the present invention.
Figure 2 is a control block diagram of a medical device software sharing device according to an embodiment of the present invention.
Figure 3 is a block diagram showing the process by which the classification unit of Figure 2 classifies software information.
Figure 4 is a block diagram showing the process of extracting meta information by the classification unit of Figure 2.
Figure 5 is a block diagram showing the process of extracting software information by the extraction unit of Figure 2.
Figure 6 is a flowchart of a method for sharing medical device software according to an embodiment of the present invention.

The detailed description of the present invention described below refers to the accompanying drawings, which show by way of example specific embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different from one another but are not necessarily mutually exclusive. For example, specific shapes, structures and characteristics described herein may be implemented in one embodiment without departing from the spirit and scope of the invention. Additionally, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the detailed description that follows is not intended to be taken in a limiting sense, and the scope of the invention is limited only by the appended claims, together with all equivalents to what those claims assert, if properly described. Similar reference numbers in the drawings refer to identical or similar functions across various aspects.

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

1 is a schematic diagram of a medical device software sharing system including a medical device software sharing device according to an embodiment of the present invention.

The medical device software sharing system 1 (hereinafter referred to as the sharing system) is a medical device software sharing device 100 that receives software information and meta information about the medical device 10 from the registrant terminal 200 and sends it to the purchaser terminal 300. It may be arranged to provide.

Here, the medical device 10 may refer to an instrument or device provided to perform tests, surgeries, procedures, etc. on a patient's disease or condition. In addition, the medical device 10 may further include an instrument or device provided for health management purposes.

Accordingly, software information may mean source code written to drive the medical device 10, etc. Through this, the medical device 10 applies software information and automatically performs examinations, surgeries, procedures, etc. on the patient's disease or disease, or the medical device 10 applies software information to the patient by medical personnel. Tests, surgeries, procedures, etc. for diseases or conditions may be performed.

For example, software information may be obtained by capturing the patient's affected area using magnetic resonance imaging (MRI), computed tomography (CT) images, X-ray images, and ultrasound images. and can be generated to predict the patient's condition based on the captured information.

In this way, software information can be generated to perform tests, surgeries, procedures, etc. for various diseases or conditions.

In this regard, the software information may be either source code generated to control the medical device or connection information with the source code stored in the registrant terminal 200.

Accordingly, the medical device software sharing device 100 can receive software information, either source code or connection information, from the registrant terminal 200 and store it.

Here, the connection information may be prepared to indicate an accessible path to the source code stored in the registrant terminal 200. For example, connection information may indicate a link based on a protocol, etc.

In this regard, the medical device software sharing device 100 may be arranged to convert the connection information into a preset standard protocol when connection information is received from the registrant terminal 200.

Accordingly, the medical device software sharing device 100 can convert different connection information transmitted from the registrant terminal 200 using different protocols into the same protocol format, and through this, the medical device software sharing device 100 Can perform registration of software information and meta information in various terminal devices.

In addition, the medical device software sharing device 100 can determine the protocol through which an arbitrary signal is transmitted from the purchaser terminal 300, and accordingly, the medical device software sharing device 100 transmits the connection information to the purchaser terminal 300. It can also be converted to the protocol used and transmitted.

Meanwhile, meta information may be information representing software information and the medical device 10 to which the software information is applied.

For example, meta information may include country information, registrant information, authentication information, rating information, permission information, sales information, promotional information, usage information, document information, security information, structure information, and performance information.

Here, country information may mean the country of the registrant or the country in which the software information was created, registrant information may mean information of the individual, organization, company, etc. who created or registered the software information, and authentication information may refer to the medical device information. (10) Alternatively, it may indicate whether software information has been certified by an official organization.

In addition, the grade information may indicate the classification of the medical device 10, which is determined according to the time of contact with the human body, the degree of invasiveness, whether medicine or energy is delivered to the patient, and whether it has a biological effect on the patient. It can indicate whether the device is permitted to be imported or sold, and sales information can indicate the price and availability period of software information.

Additionally, promotional information may refer to information such as advertisements for the medical device 10 or software information, usage information may indicate how to use the medical device 10 or software information, and document information may refer to medical device ( 10) Alternatively, it may include a certificate for software information, etc.

Additionally, security information may indicate the security level of software information, structural information may indicate the structure, parts, elements, etc. of the medical device 10, and performance information may indicate the performance or specifications of the medical device 10. It may be information representing .

At this time, the performance information may include learning information used for software information, verification information for software information, accuracy information, clinical trial information, and supporting information such as papers and patents.

For example, if there is a process of generating a learning model from software information through machine learning, etc., learning information may include body parts, types of images, image processing techniques, etc. that appear in the images used in the process of creating the learning model. may include.

For example, learning information may include information such as wrist region, X-ray image, feature point extraction technique, and image registration technique based on feature points.

In this regard, the meta information may include public information provided to the purchaser terminal according to the request information and selection information provided based on the disclosure request transmitted from the purchaser terminal.

At this time, public information may mean information set to be made public or private, and optional information may mean information set to be made public or private by the registrant. Accordingly, selection information may be provided separately upon the buyer's request.

For example, public information may include country information, registrant information, certification information, rating information, licensing information, sales information, and promotional information, and optional information may include usage information, documentation information, security information, structure information, and performance information. may include.

Meanwhile, the registrant terminal 200 may be prepared to allow the registrant to register software information and meta information in the medical device software sharing device 100, and as such, the registrant terminal 200 can be used in a personal computer, server, portable terminal device, etc. It may include various devices.

As such, the registrant terminal 200 may be a terminal device of a producer who produces the medical device 10 or software information or a seller who distributes and sells it. Accordingly, the medical device software sharing device 100 may be used by a plurality of different registrants. Software information and meta information can be received and registered from the terminal 200.

In addition, the purchaser terminal 300 may be provided so that the purchaser receives software information and meta information registered in the medical device software sharing device 100, and as such, the purchaser terminal 300 can be used as a personal computer, server, or portable terminal. It may include various devices such as devices.

In this regard, the medical device software sharing device 100 may be provided in various service forms such as a web server format, cloud, or on-premise, and in this case, the purchaser terminal 300 The web page provided by the medical device software sharing device 100 can be accessed through various devices.

At this time, when transmitting software information and meta information to the purchaser terminal 300, the medical device software sharing device 100 may transmit part or all of the software information and meta information so that the purchaser cannot identify it, which means that the medical device The software sharing device 100 can be understood as applying a data anonymization technique to some or all of the software information and meta information.

Here, the data anonymization technique can be understood as a technique of encrypting and sharing the part that requires confidentiality when sharing confidential data.

Hereinafter, the medical device software sharing device 100 according to an embodiment of the present invention will be described in detail.

Figure 2 is a control block diagram of a medical device software sharing device according to an embodiment of the present invention.

The medical device software sharing device 100 may include a communication unit 110, a classification unit 120, a storage unit 130, and an extraction unit 140.

Additionally, the medical device software sharing device 100 may be implemented with more components than those shown in FIG. 2 or may be implemented with fewer components. Alternatively, the medical device software sharing device 100 may integrate at least two components provided in the medical device software sharing device 100 into one component, so that one component may perform a complex function. Hereinafter, the above-described components will be described in detail.

The communication unit 110 may be connected to the registrant terminal 200 through a wired or wireless network. Accordingly, the communication unit 110 may provide information to the registrant terminal 200 or receive information from the registrant terminal 200. there is.

Additionally, the communication unit 110 may be connected to the purchaser terminal 300 through a wired or wireless network, and accordingly, the communication unit 110 provides information to the purchaser terminal 300 or transmits information from the purchaser terminal 300. You can receive it.

The classification unit 120 may classify meta information transmitted from the registrant terminal 200 based on preset filter information.

To this end, the classification unit 120 can compare information appearing from meta information and filter information, and through this, the classification unit 120 can extract and group meta information corresponding to the filter information.

Here, the filter information may be information set to classify meta information according to a series of conditions. For example, the filter information may include part information, function information, purpose information, authentication information, and grade information.

At this time, the part information may refer to a body part that the medical device 10 touches, or the part information may further include a body part affected by the medical device 10.

Functional information may indicate the operation method of the medical device 10 or the technology used in the medical device 10. For example, functional information may be prepared to indicate ultrasound, infrared, X-ray, MRI, CT, etc.

Additionally, the purpose information may be prepared to indicate the purpose of use of the medical device 10. For example, the purpose information may be prepared to indicate cutting, extrusion, photography, etc.

Additionally, the authentication information may indicate whether the medical device 10 or software information has been certified by an official organization, and the rating information may indicate the classification of the medical device 10.

To this end, the classification unit 120 may create a classification model using artificial intelligence (AI) techniques such as machine learning.

Here, machine learning can be understood as a technique for generating a learning model based on a plurality of information to classify the plurality of information into one or more groups, and classifying arbitrary information based on the generated learning model. Likewise, machine learning is supervised learning, which creates a learning model so that arbitrary information can be classified according to a plurality of information classified by an administrator, analyzes the plurality of information itself, or performs a clustering process to create a learning model. This may include unsupervised learning, which creates a learning model, and semi-supervised learning, which creates a learning model by mixing supervised learning and unsupervised learning.

Accordingly, the classification unit 120 can generate a classification model by learning the relationship between a plurality of pre-prepared meta information and filter information, and through this, the classification unit 120 can classify the registrant terminal 200 based on the classification model. Meta information transmitted from can be grouped according to filter information.

The storage unit 130 may combine and store software information and meta information. In this case, the storage unit 130 may classify and store meta information grouped based on filter information.

The extraction unit 140 may extract software information requested from the purchaser terminal 300, and accordingly, the communication unit 110 may transmit the extracted software information to the purchaser terminal 300.

Figure 3 is a block diagram showing the process by which the classification unit of Figure 2 classifies software information.

Referring to Figure 3, the communication unit 110 may receive software information and meta information about the medical device 10 from the registrant terminal 200.

Accordingly, the classification unit 120 may group meta information based on preset filter information, and the classification unit 120 may classify software information according to the grouped meta information.

At this time, the storage unit 130 may classify and store grouped meta information based on filter information, and the storage unit 130 may combine and store software information and meta information.

Figure 4 is a block diagram showing the process of extracting meta information by the classification unit of Figure 2.

Referring to Figure 4, the communication unit 110 may receive request information for software information from the purchaser terminal 300.

Here, the request information can be generated to match the filter information, and for this purpose, the buyer terminal 300 can output filter information and receive selection of one or more filter information from the buyer.

Accordingly, the buyer terminal 300 may generate request information based on the filter information selected by the buyer.

For example, filter information may be created to include information such as legs, authentication completed, ultrasound, etc.

Accordingly, the classification unit 120 can extract filter information corresponding to the request information, and the classification unit 120 can extract meta information grouped according to the extracted filter information.

Meanwhile, the communication unit 110 can transmit the extracted meta information to the purchaser terminal 300, and in this case, the purchaser terminal 300 can receive grouped meta information.

Through this, the buyer terminal 300 can check one or more meta information according to the requested information, and the buyer terminal 300 can receive a selection of at least one meta information among one or more meta information according to the requested information from the buyer.

At this time, when the buyer terminal 300 selects meta information, it may be understood as proceeding with a purchase for the corresponding meta information.

In this regard, the buyer terminal 300 may receive a provision request signal for selection information among a plurality of information appearing from the meta information. In this case, the communication unit 110 may receive a provision request signal from the purchaser terminal 300. It can be received and delivered to the registrant terminal 200.

At this time, the communication unit 110 may further receive personal information of the purchaser terminal 300 and transmit it to the registrant terminal 200.

Through this, the registrant terminal 200 can receive a provision acceptance signal that accepts the provision of the selected information, or a provision rejection signal that rejects the provision of the selected information.

Accordingly, when receiving a provision acceptance signal from the registrant terminal 200, the communication unit 110 may transmit selection information regarding the provision acceptance signal to the purchaser terminal 300.

Figure 5 is a block diagram showing the process of extracting software information by the extraction unit of Figure 2.

Referring to Figure 5, the classification unit 120 can extract filter information corresponding to the request information, and the classification unit 120 can extract meta information grouped according to the extracted filter information. You can.

Through this, the buyer terminal 300 can check one or more meta information according to the requested information, and the buyer terminal 300 can receive a selection of at least one meta information among one or more meta information according to the requested information from the buyer.

Accordingly, the communication unit 110 can receive selected meta information or a signal representing the corresponding meta information from the purchaser terminal 300.

At this time, the extraction unit 140 may extract meta information selected from the purchaser terminal 300 among the grouped meta information, and the extraction unit 140 may extract software information corresponding to the selected meta information.

Accordingly, the communication unit 110 can transmit the extracted software information to the purchaser terminal 300. Through this, the purchaser terminal 300 can perform tests, experiments, and operations on the delivered software information.

In this regard, the medical device software sharing device 100 receives from the registrant terminal 200 an environment required for purchaser testing, experimentation, and verification for software information whose authentication information appears in an unauthenticated state among the meta information. In this case, the purchaser terminal 300 may receive an environment required for testing, experimentation, and verification from the medical device software sharing device 100.

Through this, the user can use the software information delivered from the medical device software sharing device 100 for testing, experimentation, verification, and research.

Meanwhile, the allowable modification range for software information may be set in advance by the registrant terminal 200. Here, the allowable modification range may mean the scope in which modification of the source code indicated from software information is possible.

In this case, the buyer terminal 300 can output the allowable modification range set in the delivered software information so that the purchaser can identify it, and accordingly, the purchaser terminal 300 inputs a command to modify the allowable modification range from the purchaser. You can receive it.

Accordingly, the buyer terminal 300 can receive evaluation information from the buyer. Here, the evaluation information may include revision details according to the revision order and the buyer's opinion on the revision order.

At this time, the evaluation information may further include personal information of the purchaser terminal 300, etc.

In this case, the purchaser terminal 300 can transmit evaluation information to the medical device software sharing device 100, and the communication unit 110 can receive the evaluation information from the purchaser terminal 300.

At this time, the classification unit 120 can control the delivered evaluation information to be combined and stored with software information, and the storage unit 130 can combine the delivered evaluation information with software information and store it.

In this regard, the classification unit 120 may store evaluation information transmitted from different purchaser terminals 300 by combining it with the corresponding software information. At this time, the classification unit 120 may transmit the evaluation information combined with the software information. The number of purchaser terminals 300 can be counted.

In this case, when extracting meta information grouped according to request information, the classification unit 120 may list the grouped meta information in order of the largest number of evaluation information.

Accordingly, the buyer terminal 300 can output the grouped meta information in the order of the largest number of evaluation information.

Additionally, when transmitting software information, the communication unit 110 can further transmit evaluation information, and accordingly, the communication unit 110 can receive re-evaluation information about the evaluation information from the purchaser terminal 300.

At this time, the re-evaluation information may be set to indicate the level, grade, score, etc. of the evaluation information. In one embodiment, the re-evaluation information may be set to indicate any one score from 1 to 5.

In this regard, the classification unit 120 may combine and store the re-evaluation information with the evaluation information. At this time, the classification unit 120 may store the re-evaluation information combined with the evaluation information when the number and score of the re-evaluation information combined with the evaluation information exceed each threshold. , software information can be corrected based on the corresponding evaluation information.

At this time, correcting the software information based on the evaluation information can be understood as correcting the modification details shown from the evaluation information to the software information.

Figure 6 is a flowchart of a method for sharing medical device software according to an embodiment of the present invention.

The medical device software sharing method according to an embodiment of the present invention is carried out on substantially the same configuration as the medical device software sharing device 100 shown in FIG. 1, and therefore has the same configuration as the medical device software sharing device 100 shown in FIG. The same reference numerals will be assigned to elements, and repeated descriptions will be omitted.

The medical device software sharing method includes the steps of receiving software information and meta information about the medical device (600), receiving request information for software information (610), and classifying software information according to the meta information (620). , It may include extracting filter information corresponding to the request information, extracting meta information grouped according to the extracted filter information (630), and extracting software information corresponding to the meta information (640).

The step 600 of receiving software information and meta information about the medical device may be a step in which the communication unit 110 receives software information and meta information about the medical device 10 from the registrant terminal 200.

The step 610 of receiving request information for software information may be a step in which the communication unit 110 receives request information about software information from the purchaser terminal 300 .

The step 620 of classifying software information according to meta information may be a step in which the classification unit 120 groups meta information based on preset filter information and classifies software information according to the grouped meta information.

In the step 630 of extracting filter information corresponding to the request information and extracting meta information grouped according to the extracted filter information, the classification unit 120 extracts filter information corresponding to the request information and extracts the extracted filter information. This may be a step of extracting meta information grouped according to.

In the step 640 of extracting software information corresponding to meta information, the extraction unit 140 extracts meta information selected from the purchaser terminal 300 among the grouped meta information and extracts software information corresponding to the selected meta information. This may be a step.

Although the above has been described with reference to embodiments, those skilled in the art will understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the following patent claims. You will be able to.

1: Medical device software sharing system
10: Medical devices
100: Medical device software sharing device
200: Registrant terminal
300: Buyer terminal

Claims (12)

a communication unit that receives software information and meta information about the medical device from the registrant terminal and receives request information for the software information from the purchaser terminal;
Group the meta information based on preset filter information, classify the software information according to the grouped meta information, extract filter information corresponding to the request information, and extract meta information grouped according to the extracted filter information. a classification unit for extraction; and
An extraction unit extracting meta information selected from the purchaser terminal among the grouped meta information and extracting software information corresponding to the selected meta information,
The meta information is,
Contains public information provided to the purchaser terminal according to the request information and selection information provided based on a disclosure request transmitted from the purchaser terminal,
The Department of Communications,
When a provision request signal for the selection information is transmitted from the purchaser terminal, a medical device transmits the provision request signal to the registrant terminal and receives a provision acceptance signal or provision rejection signal for the selection information from the registrant terminal. Device software sharing device.
The method of claim 1, wherein the software information is:
A medical device software sharing device that is source code generated to control the medical device or connection information with the source code stored in the registrant terminal.
delete delete According to paragraph 1,
The Department of Communications,
When an allowable modification range for the software information is set by the registrant terminal, evaluation information according to a modification command input for the allowable modification range is delivered to the purchaser terminal,
The classification department,
A medical device software sharing device that counts the number of purchaser terminals that delivered the evaluation information and lists the grouped meta information in order of the number of counted evaluation information.
The method of claim 1, wherein the filter information is:
Part information indicating the body part with which the medical device is in contact, function information indicating the operating method of the medical device and technology used in the medical device, purpose information indicating the purpose of use of the medical device, and information about the medical device or the software. A medical device software sharing device that includes authentication information indicating whether an official organization has certified and rating information indicating a classification of the medical device.
In a method of sharing medical device software in a medical device software sharing device,
A step where the communication department receives software information and meta information about the medical device from the registrant terminal;
The communication unit receiving request information for the software information from the purchaser terminal;
A classifier grouping the meta information based on preset filter information and classifying the software information according to the grouped meta information;
the classification unit extracting filter information corresponding to the request information and extracting meta information grouped according to the extracted filter information; and
A step of extracting meta information selected from the purchaser terminal among the grouped meta information by an extraction unit, and extracting software information corresponding to the selected meta information,
The meta information is,
Contains public information provided to the purchaser terminal according to the request information and selection information provided based on a disclosure request transmitted from the purchaser terminal,
The Department of Communications,
When a provision request signal for the selection information is transmitted from the purchaser terminal, a medical device transmits the provision request signal to the registrant terminal and receives a provision acceptance signal or provision rejection signal for the selection information from the registrant terminal. How to share device software.
The method of claim 7, wherein the software information is:
A method of sharing medical device software, which is source code generated to control the medical device or connection information with the source code stored in the registrant terminal.
delete delete The method of claim 7, wherein the communication unit,
When an allowable modification range for the software information is set by the registrant terminal, evaluation information according to a modification command input for the allowable modification range is delivered to the purchaser terminal,
The classification department,
A method of sharing medical device software, counting the number of purchaser terminals that delivered the evaluation information, and listing the grouped meta information in order of the number of counted evaluation information.
The method of claim 7, wherein the filter information is:
Part information indicating the body part with which the medical device is in contact, function information indicating the operating method of the medical device and technology used in the medical device, purpose information indicating the purpose of use of the medical device, and information about the medical device or the software. A method of sharing medical device software, including certification information indicating whether an official organization has certified and rating information indicating a classification of the medical device.

Images