Medical information processing apparatus, medical information processing system, and medical information processing program

Abstract

To easily grasp a license range of medical data.SOLUTION: A medical information processing apparatus according to an embodiment comprises: a receiving unit that receives a search condition for searching for medical data including at least one of opinion data related to a doctor's opinion and medical image data, and the purpose of use of the medical data; a searching unit that, on the basis of the search condition received by the receiving unit, refers to a database that manages the medical data and license information related to a license for the medical data in association with each other, and searches for the medical data; an allocation unit that, on the basis of the license information associated with the medical data searched for by the searching unit and the purpose of use received by the receiving unit, allocates the medical data searched for by the searching unit; and a presentation unit that presents information based on the result of the allocation performed by the allocation unit.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The embodiments disclosed in this specification and the drawings relate to a medical information processing device, a medical information processing system, and a medical information processing program. [Background technology]

[0002] Conventionally, when preparing reports such as radiology reports or papers, doctors may use similar case searches, findings searches, etc. to search for medical data such as medical image data and findings data, and use the searched medical data to prepare the report or paper. When using medical data to prepare a report or paper in this way, the doctor obtains permission to use the data from the patient who is the provider of the medical data. In addition, when medical data with permission to use from a patient is used, a system exists for notifying the patient that the medical data has been used.

[0003] In recent years, doctors may want to use medical data for various purposes other than writing reports and papers, such as using it as learning data when training a learning model, or as reference images in pre-processing of images when performing image analysis with an analysis application, etc. However, since the scope of the license for medical data is often limited, doctors must check the scope of the license for medical data, and if they use the medical data outside the scope of the license, they must re-contract with the patient to agree on the scope of use of the medical data.

[0004] In addition, within the scope of the license, there are cases where a hospital wishes to search for or use medical data acquired by other departments of the hospital or medical data acquired by other hospitals, but the data cannot be used without the patient's knowledge, so the patient must be notified that the medical data has been used. However, while a mechanism for notifying patients that their medical data has been used can be applied to patients of the hospital, it is difficult to apply this to patients of other hospitals whose contact information is not managed, so it is difficult to notify patients of other hospitals that their medical data has been used. Therefore, it is desirable to make it easier to re-contract with patients and notify patients that their medical data has been used, as well as to make it easier to understand the scope of the license for medical data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2004-102863 A [Patent Document 2] JP 2021-101299 A [Patent Document 3] JP 2016-167190 A Summary of the Invention [Problem to be solved by the invention]

[0006] One of the problems to be solved by the embodiments disclosed in this specification and the drawings is to make it possible to easily understand the scope of the license for use of medical data. However, the problems to be solved by the embodiments disclosed in this specification and the drawings are not limited to the above problem. Problems corresponding to the effects of each configuration shown in the embodiments described later can also be positioned as other problems. [Means for solving the problem]

[0007] A medical information processing device according to an embodiment includes a reception unit that receives search conditions for searching for medical data including at least one of findings data related to a doctor's findings and medical image data, and an intended use of the medical data, a search unit that searches for the medical data by referring to a database that associates and manages the medical data with license information related to a license for use of the medical data, based on the search conditions received by the reception unit, a distribution unit that distributes the medical data searched by the search unit based on the license information associated with the medical data searched by the search unit and the intended use received by the reception unit, and a presentation unit that presents information based on the distribution result of the distribution unit. [Brief description of the drawings]

[0008] [Figure 1] 1 is a block diagram showing an example of the arrangement of a medical information processing system according to a first embodiment. [Diagram 2] FIG. 4 is a diagram showing an example of management data according to the first embodiment. [Diagram 3] 1 is a block diagram showing an example of the arrangement of a medical image processing apparatus according to a first embodiment. [Figure 4] FIG. 4 is a flowchart illustrating the contents of a presentation process executed by the medical image processing apparatus according to the first embodiment. [Diagram 5] FIG. 2 is a view showing an example of an input screen displayed on a display of the medical image processing apparatus according to the first embodiment. [Figure 6] 4 is a diagram showing an example of a medical data list generated in the medical image processing apparatus according to the embodiment. [Figure 7] FIG. 2 is a view showing an example of a presentation screen displayed on a display of the medical image processing apparatus according to the first embodiment. [Figure 8] FIG. 4 is a flowchart illustrating the contents of a providing process executed by the medical image processing apparatus according to the first embodiment. [Figure 9] FIG. 4 is a view showing an example of license confirmation information generated in the medical information processing apparatus according to the first embodiment. [Figure 10]FIG. 2 is a diagram showing an example of provided data provided by the medical image processing apparatus according to the first embodiment. [Figure 11] FIG. 4 is a flowchart illustrating the contents of a notification process executed by the medical image processing apparatus according to the first embodiment. [Figure 12] 4 is a diagram showing an example of information indicating that medical data generated in the medical image processing apparatus according to the first embodiment has been used. FIG. [Figure 13] FIG. 4 is a flowchart illustrating the contents of a billing process executed in the medical image processing apparatus according to the first embodiment. [Figure 14] FIG. 11 is a block diagram showing an example of the configuration of a medical information processing system according to a second embodiment. [Figure 15] FIG. 11 is a diagram showing an example of management data according to the second embodiment. [Figure 16] FIG. 13 is a block diagram showing an example of the configuration of a medical information processing apparatus according to Modification 1. [Figure 17] FIG. 11 is a flowchart illustrating the content of a point giving process executed by the medical information processing device according to the first modification. [Figure 18] FIG. 13 is a diagram showing another example of an input screen displayed on the display of the medical image processing device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of a medical information processing device, a medical information processing system, and a medical information processing program will be described with reference to the drawings. In the following description, components having substantially the same functions and configurations are denoted by the same reference numerals, and repeated description will be given only when necessary.

[0010] [First embodiment] FIG. 1 is a block diagram showing a configuration example of a medical information processing system 1 according to the first embodiment. As shown in FIG. 1, the medical information processing system 1 according to this embodiment is configured to include a database 10, a doctor terminal 30, a medical data storage device 50A of a facility A, a medical data storage device 50B of a facility B, a medical information processing device 70, and a patient terminal 90. As shown in FIG. 1, the doctor terminal 30, the medical data storage device 50A of the facility A, and the medical information processing device 70 are communicatively connected to each other via an intra-hospital network NW1 using a dedicated line within the hospital. Also, as shown in FIG. 1, the database 10, the medical data storage device 50A of the facility A, the medical data storage device 50B of the facility B, the medical information processing device 70, and the patient terminal 90 are communicatively connected to each other via a network NW2 using a public line such as the Internet. Furthermore, in the example shown in FIG. 1, the doctor terminal 30, the medical data storage device 50A, and the medical information processing device 70 are provided in a facility A of a medical institution such as a hospital or a clinic. The medical data storage device 50B is provided in a facility B of a medical institution such as a hospital or clinic different from the facility A, and the database 10 is provided in an information management facility different from the facilities A and B.

[0011] The database 10, the doctor terminal 30, the medical data storage device 50A of facility A, the medical data storage device 50B of facility B, the medical information processing device 70, and the patient terminal 90 may be communicably connected to each other via a network of public lines such as the Internet. In the example shown in FIG. 1, the database 10 is provided in an information management facility, but the location where the database 10 is provided is not limited to the information management facility. In other words, the location where the database 10 is provided is arbitrary, and the database 10 may be provided in facility A or facility B. In the following, when the medical data storage device 50A of facility A and the medical data storage device 50B of facility B are expressed without distinction, they are simply referred to as "medical data storage device 50".

[0012] The database 10 manages medical data and license information from a plurality of facilities in association with each other. Specifically, the database 10 according to this embodiment manages medical data and license information from facilities A and B in association with each other. The database 10 according to this embodiment does not store medical data itself, but stores management data that associates and manages information about the storage destination of the medical data with the license information, thereby managing the medical data and the license information in association with each other.

[0013] Here, the medical data includes at least one of the findings data related to the doctor's findings and medical image data. The findings data includes at least one of the findings on the image, the findings on the interview, and the findings on the examination, and the patient information of the patient corresponding to the findings. The patient information includes at least one of the patient's name, patient ID, date of birth, sex, medical history, case name, and vital information including at least one of the height, weight, pulse, and biochemical information. The medical image data includes, for example, a medical image and associated information associated with the medical image. The associated information includes at least one of the patient's name, patient ID, date of birth, sex, image type, imaging site, case name, and vital information including at least one of the height, weight, pulse, and biochemical information.

[0014] The license information is information regarding the license for use of the medical data. As will be described in detail later, the license information includes at least one of the permitted scope of the medical data, the scope of use of the medical data, and the scope of disclosure of the medical data.

[0015] The contents of the management data stored in the database 10 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of management data according to the first embodiment. As shown in Fig. 2, a plurality of management data MD1, MD2, and MD3 are stored in the database 10 for each medical data. Hereinafter, when there is no need to distinguish between the management data, they will simply be referred to as management data MD.

[0016] In the management data MD, items and contents for the items are associated with each other. The management data MD includes, as items, a facility / company, a reliability, a role, a management device, a name, an access source, a use destination, a purpose of use, a contact, information on the number of uses, a disclosure period (a period of use), and, as permission contents (contents of permission for use), a permission range, a usable range, and a disclosure range. The management data MD according to this embodiment is data registered for each medical data.

[0017] The facility / company is an item of information related to the name of the facility or company where the medical data is stored. Taking the management data MD1 shown in Figure 2 as an example, facility B is registered in the content of the facility / company item of the management data MD1.

[0018] The reliability is an item of information regarding the reliability of a facility that uses medical data. The reliability in this management data MD is set, for example, so that a facility has a high reliability when an electronic contract is made with a patient. This reliability is, for example, a score such as a 5-point or 10-point rating. Taking the management data MD1 shown in FIG. 2 as an example, the contents of the reliability item in the management data MD1 indicate that, on a 10-point rating, the reliability of facility B is 9 and the reliability of facility C is 5. This reliability includes authentication information. The authentication information is information regarding authentication when a facility registered with this reliability accesses medical data managed in this management data MD.

[0019] The role is an item related to the role of the user who can access the medical data, that is, an item related to the usage authority of the medical data. For example, the contents of the role item are registered as "guest" indicating a guest user, "general" indicating a general user, "administrator" indicating a data administrator, etc. Taking the management data MD1 shown in Fig. 2 as an example, "general" is registered as the contents of the role item of the management data MD1.

[0020] The management device is an item of information about a device that manages medical data, that is, a device that stores medical data. Specifically, the contents of the management device item include information such as the IP address and MAC address of the device that stores the medical data.

[0021] The name is an item of information about the name of the medical data. Therefore, the content of the name item is registered with a file name, etc. The management device and name are information about the storage destination of the medical data.

[0022] The access source is an item of information about the terminal that operates the search. For example, the contents of the access source item include terminal identification information, such as the IP address or MAC address, of the terminal that accessed the medical data by the search.

[0023] The destination of use is an item of information about the terminal that uses the medical data. For example, the contents of the destination of use item include identification information of the terminal that used (sent) the medical data, such as the IP address or MAC address.

[0024] The purpose of use is an item of information regarding the user's purpose of use when using medical data. The contents of the purpose of use item are registered as the user's purpose of use when using medical data, such as a paper, AI, or findings. The purpose of use may also include the name of an application or service used when using the medical data. The content of the purpose of use item in the management data MD1 shown in FIG. 2 is registered as a paper. In other words, it is indicated that the medical data managed in the management data MD1 was used for a paper.

[0025] The contact information is information about the contact of the patient related to the medical data. For example, the contents of the contact information item include the patient's telephone number, email address, etc. Of course, the contents of the contact information item may include both the patient's telephone number and email address.

[0026] The use count information is information about the number of times the medical data has been used. In this embodiment, the use count information is included in the management data MD, so that the use count information is associated with the medical data.

[0027] The disclosure period (usage period) is an item of information about the period during which medical data can be used. For example, the contents of the disclosure period item include the date, number of years, months, or days during which the medical data can be used. The contents of the disclosure period item in the management data MD1 shown in FIG. 2 include the date indicating the period during which the medical data can be used.

[0028] The permission contents are items of information regarding the license for use of the medical data. For example, the permission contents include information regarding the license scope of the medical data, the scope of use of the medical data, and the scope of disclosure of the medical data. The permission contents correspond to the license information in this embodiment.

[0029] The permission range is an item of information regarding the type of medical data for which use is permitted. Images are registered as the content for the permission range item in the management data MD1 shown in FIG. 2. That is, it is shown that permission to use images is granted in the medical data managed by the management data MD1. Note that the content registered in the permission range is not limited to images. For example, the content registered in the permission range may be findings, etc.

[0030] The usable range is an item of information regarding the usable range of medical data. The usable range of medical data authorized by the patient is registered as the content for the usable range. The content for the usable range item in the management data MD1 shown in FIG. 2 is registered as a paper. In other words, this indicates that the medical data managed in the management data MD1 can be used for a paper. Note that the content registered in the usable range is not limited to a paper. For example, it can be a paper, AI, findings, etc.

[0031] The disclosure range is an item of information indicating the range of information that can be disclosed to the user among the information in the medical data that can identify an individual. The information that can identify an individual is, for example, information such as the patient's name, patient ID, date of birth, gender, and case name. For this reason, for example, the content of the disclosure range registers the range of information that can be disclosed to the user, such as the patient's name and patient ID. Age and gender are registered as the disclosure range in the management data MD1 shown in FIG. 2. In other words, it indicates that age and gender are disclosed to the user among the information in the medical data that can identify an individual.

[0032] In addition, the management data MD according to the present embodiment includes the facility / company, the reliability, the role, the management device, the name, the access source, the destination, the purpose of use, the contact information, the number of uses information, the disclosure period (use period), and the permission content (license content) including the permission range, the usable range, and the disclosure range of data, but the items included in the management data MD are arbitrary. For example, the management data MD may include items other than the facility / company, the reliability, the role, the management device, the name, the access source, the destination, the purpose of use, the contact information, the number of uses information, the disclosure period (use period), and the permission content (license content) including the permission range, the usable range, and the disclosure range of data. The management data MD may also include only some of the items of the facility / company, reliability, role, management device, name, access source, destination, purpose of use, contact information, number of uses information, disclosure period (use period), and permission content (license content), such as permission range, usable range, and data disclosure range. For example, the reliability may not be included in the management data MD and may be managed in a table or the like that associates the facility name with the reliability, and only either the facility / company or the management device may be included in the management data MD. Furthermore, the permission content may not include the disclosure range. Furthermore, the number of uses information may not be included in the management data MD.

[0033] The doctor terminal 30 is a terminal used by a doctor. For example, in this embodiment, the doctor terminal 30 accepts input of search conditions for searching medical data and the purpose of use of the medical data. In addition, the doctor terminal 30 transmits the accepted search conditions and the purpose of use to the medical information processing device 70 via the hospital network NW1. The doctor terminal 30 is, for example, an electronic medical record terminal or a terminal for creating an interpretation report. The doctor terminal 30 is, for example, a mobile terminal such as a smartphone or a tablet PC, or a terminal such as a personal computer used by a doctor. In the example shown in FIG. 1, one doctor terminal 30 is connected to the hospital network NW1, but the number of doctor terminals 30 connected to the hospital network NW1 is not limited to this. That is, the number of doctor terminals 30 is arbitrary, and multiple doctor terminals 30 may be connected to the hospital network NW1.

[0034] The medical data storage device 50 stores medical data. The medical data storage device 50A according to this embodiment transmits the stored medical data to the doctor terminal 30 and the medical information processing device 70 via the intra-hospital network NW1, and transmits the stored medical data to the database 10 via the network NW2. The medical data storage device 50B according to this embodiment transmits the stored medical data to the database 10 via the network NW2. For example, the medical data storage device 50 is composed of an image server such as a PACS (Picture Archiving and Communication System). In the example shown in FIG. 1, for example, the medical data storage device 50A of the facility A stores medical data generated in the facility A and / or medical data acquired from the facility B, and the medical data storage device 50B of the facility B stores medical data generated in the facility B and / or medical data acquired from the facility A.

[0035] 1 in this embodiment, two medical data storage devices 50A of facility A and medical data storage device 50B of facility B are connected to the network NW2, but the number of medical data storage devices 50 connected to the network NW2 is not limited to this. That is, the number of medical data storage devices 50 connected to the network NW2 is arbitrary, and for example, one medical data storage device 50 may be connected to the network NW2, or three or more medical data storage devices 50 may be connected to the network NW2.

[0036] The medical information processing device 70 is a device that receives search conditions for searching medical data and the intended use of the medical data, searches for medical data based on the search conditions, distributes the searched medical data based on the intended use, and presents information based on the distribution result to the user. Specifically, the medical information processing device 70 receives search conditions for searching medical data and the intended use of the medical data transmitted from the doctor terminal 30 via a communication interface 77 described later, or receives search conditions for searching medical data and the intended use of the medical data via an input interface 71 described later, searches for medical data based on the search conditions, distributes the searched medical data based on the intended use, and presents information based on the distribution result.

[0037] The medical information processing device 70 is, for example, a computer such as a PC (Personal Computer) or a server device. Although the medical information processing device 70 according to the present embodiment is installed in the facilities of a medical institution such as a hospital or a clinic, the location where the medical information processing device 70 is installed is not limited thereto. In other words, the location where the medical information processing device 70 is installed is arbitrary, and may be installed in, for example, a cloud environment or the like.

[0038] The patient terminal 90 is a terminal used by a patient. The patient terminal 90 is a terminal owned by the patient, such as a mobile terminal such as a smartphone or a tablet PC, or a personal computer. In this embodiment, the patient terminal 90 receives, for example, license confirmation information transmitted from the medical information processing device 70 and information indicating that medical data has been used, and transmits usability information to the medical information processing device 70.

[0039] The license confirmation information is information regarding confirmation of license to use medical data. This license information includes, for example, information such as the contents of medical data that the doctor wants to use and the doctor's purpose of use. The license confirmation information may also include information other than the contents of medical data that the doctor wants to use and the doctor's purpose of use.

[0040] The information indicating that the medical data has been used is usage data information or a message indicating that the medical data has been used. The usage data information includes, for example, the contents of the medical data used, the usage of the medical data, and information on the facility that used the medical data. Note that the usage data information may include information other than the contents of the medical data used, the usage of the medical data, and the facility that used the medical data, and it is sufficient that the usage data information includes at least one of the contents of the medical data used, the usage of the medical data, and the facility that used the medical data. The message indicating that the medical data has been used is a message such as "medical data has been used." Note that the contents of the message are not limited to this. In other words, the contents of the message are arbitrary.

[0041] The usability information is information regarding whether or not the medical data can be used in response to confirmation of permission to use the medical data. The usability information includes, for example, information regarding whether or not the medical data can be used, the usable range, and the disclosure range of the medical data. Note that the usability information may include information other than whether or not the medical data can be used, the usable range of the medical data, and the disclosure range of the medical data.

[0042] 1 in this embodiment, one patient terminal 90 is connected to the network NW2, but the number of patient terminals 90 connected to the network NW2 is not limited to this. That is, the number of patient terminals 90 is arbitrary, and multiple patient terminals 90 may be connected to the network NW2.

[0043] Next, the configuration of the medical information processing device 70 according to this embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the configuration of the medical information processing device 70 according to the first embodiment. As shown in Fig. 3, the medical information processing device 70 according to this embodiment is configured to include an input interface 71, a display 73, a memory circuitry 75, a communication interface 77, and a processing circuitry 79. The multiple elements constituting this medical information processing device 70 may be stored in one housing, or may be stored in a distributed manner in multiple housings.

[0044] The input interface 71 accepts various input operations from a user, converts the accepted input operations into electrical signals, and outputs the electrical signals to the processing circuit 79. The input interface 71 is realized by, for example, a mouse, a keyboard, a trackball, a manual switch, a foot switch, a button, a joystick, a touchpad that performs input operations by touching the operation surface, a touch screen in which a display screen and a touchpad are integrated, a non-contact input interface using an optical sensor, and a voice input interface. In this specification, the input interface 71 is not limited to an interface having physical operation parts such as a mouse and a keyboard. For example, an example of the input interface 71 also includes an electrical signal processing circuit that receives an electrical signal corresponding to an input operation from an external input device provided separately from the device and outputs the electrical signal to a control circuit.

[0045] The display 73 displays various information. For example, the display 73 displays a GUI (Graphical User Interface) for receiving various operations from a user. In this embodiment, the display 73 is configured by, for example, a liquid crystal display or a CRT (Cathode Ray Tube) display.

[0046] The storage circuitry 75 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, a hard disk, an optical disk, etc. In this embodiment, the storage circuitry 75 stores various information such as medical data transmitted from a database and medical data transmitted from the medical data storage device 50.

[0047] The communication interface 77 implements various information communication protocols according to the configuration of the intra-hospital network NW1 and the network NW2. The communication interface 77 realizes communication with other devices via the intra-hospital network NW1 and the network NW2 in accordance with these various protocols.

[0048] The processing circuitry 79 is an arithmetic circuit that performs various calculations, and is configured with a processor such as a CPU, a GPU, etc. The processing circuitry 79 according to this embodiment receives search conditions for searching medical data and the intended use of the medical data, searches for medical data by referring to the database 10, sorts the medical data according to the intended use, and displays information based on the sorting result.

[0049] Therefore, the processing circuit 79 according to this embodiment has a reception function 791, a search function 792, a calculation function 793, a distribution function 794, a presentation function 795, a first notification function 796, a conversion function 797, a second notification function 798, and a billing function 799. The reception function 791 corresponds to the reception unit according to this embodiment, the search function 792 corresponds to the search unit according to this embodiment, the calculation function 793 corresponds to the calculation unit according to this embodiment, the distribution function 794 corresponds to the distribution unit according to this embodiment, the presentation function 795 corresponds to the presentation unit according to this embodiment, the first notification function 796 corresponds to the first notification unit according to this embodiment, the conversion function 797 corresponds to the conversion unit according to this embodiment, the second notification function 798 corresponds to the second notification unit according to this embodiment, and the billing function 799 corresponds to the billing unit according to this embodiment.

[0050] In the embodiment shown in Fig. 3, the processing functions performed by the reception function 791, the search function 792, the calculation function 793, the allocation function 794, the presentation function 795, the first notification function 796, the conversion function 797, the second notification function 798, and the billing execution function 799 are stored in the storage circuitry 75 in the form of a program executable by a computer. The processing circuitry 79 is a processor that realizes a function corresponding to each program by reading and executing the program from the storage circuitry 75. In other words, the processing circuitry 79 in a state in which each program has been read has each function shown in the processing circuitry 79 in Fig. 3. In FIG. 3, it has been described that the reception function 791, search function 792, calculation function 793, allocation function 794, presentation function 795, first notification function 796, conversion function 797, second notification function 798, and billing execution function 799 are realized by a single processing circuit 79. However, it is also possible to configure the processing circuit 79 by combining a number of independent processors and realize these functions by each processor executing a program.

[0051] The reception function 791 is a function that receives search conditions for searching medical data and the intended use of the medical data. The search function 792 is a function that searches for medical data by referring to the database 10 based on the search conditions received by the reception function 791. The calculation function 793 is a function that calculates the degree of agreement between the medical data searched by the search function 792, the license information associated with the medical data searched by the search function 792, and the search conditions and the intended use.

[0052] The sorting function 794 is a function that sorts the medical data searched by the search function 792 based on the license information associated with the medical data searched by the search function 792 and the purpose of use accepted by the acceptance function 791. The presentation function 795 is a function that presents information based on the sorting result of the sorting function 794. The first notification function 796 is a function that notifies the patient of the license confirmation information.

[0053] The conversion function 797 is a function that converts the medical data based on the disclosure range of the medical data. The second notification function 798 is a function that notifies the patient of information indicating that the medical data has been used. The billing execution function 799 executes billing for the patient.

[0054] 4 is a flow chart for explaining the contents of the presentation process executed by the medical information processing device 70 according to the first embodiment. In this presentation process, search conditions for searching medical data and the intended use of the medical data are received, the medical data is searched for by referring to the database 10, the medical data is sorted according to the intended use, and information based on the sorting results is displayed. For example, this presentation process is a process that is executed when the search conditions and the intended use are received.

[0055] 4, first, the medical information processing device 70 receives search conditions and an intended use (step S11). The process of receiving the search conditions and the intended use is realized by a receiving function 791 in the processing circuitry 79. Specifically, the medical information processing device 70 receives, via the input interface 71, the search conditions for searching medical data and the intended use of the medical data.

[0056] In the above-mentioned step S11, the medical information processing device 70 receives the search conditions for searching medical data and the intended use of the medical data via the input interface 71, but is not limited to this. The medical information processing device 70 may receive the search conditions and the intended use transmitted from the doctor terminal 30 via the communication interface 77.

[0057] FIG. 5 is a diagram showing an example of an input screen displayed on the display 73 of the medical information processing device 70 according to the first embodiment. As shown in FIG. 5, the input screen SC1 according to this embodiment displays an image input box IB1 for receiving medical image data IM1, a text box TB1 for receiving a case name, and a text box TB2 for receiving a use purpose. That is, in the example shown in FIG. 5, the image input box IB1 and the text box TB1 receive medical image data IM1 and a case name as search conditions, and the text box TB2 receives a use purpose. In the example shown in FIG. 5, a chest X-ray image is input as a search condition in the image input box IB1, a pulmonary nodule is input as a text box TB1, and a paper is input as a use purpose in the text box TB2.

[0058] 5, the reception function 791 receives medical image data IM1 and a case name as search conditions, but the search conditions received by the reception function 791 are not limited to these. That is, the search conditions received by the reception function 791 are arbitrary, and for example, the search conditions may be either the case name or the medical image data IM1, or may include age, sex, and the like other than the case name and medical image data IM1.

[0059] Next, as shown in Fig. 4, the medical information processing device 70 searches for medical data (step S13). This process of searching for medical data is realized by the search function 792 in the processing circuit 79. Specifically, the medical information processing device 70 searches for medical data by referring to the database 10 based on the search conditions accepted by the reception function 791 in step S11. More specifically, in the example shown in Fig. 5, the reception function 791 accepts chest X-ray images and pulmonary nodules as search conditions, so the search function 792 causes the database 10 to acquire medical data from a storage destination based on the management data MD of the database 10, and compares the search conditions of chest X-ray images and pulmonary nodules with the contents of the medical data managed in the database 10 to search for medical data similar to the search conditions. Medical data similar to the search conditions may be, for example, medical data that includes the same case name and whose medical image data and / or finding data are similar to the search conditions, or medical data that does not include the same case name, i.e., medical data that includes similar or different case names and whose medical image data and / or finding data are similar to the search conditions.

[0060] 4, the medical information processing device 70 acquires the medical data and the license information (step S15). The process of acquiring the medical data and the license information is realized by the search function 792 in the processing circuitry 79. Specifically, the medical information processing device 70 acquires the medical data searched in step S13 and the license information associated with the medical data.

[0061] Next, as shown in FIG. 4, the medical information processing device 70 calculates the degree of agreement (step S17). This process of calculating the degree of agreement is realized by the calculation function 793 in the processing circuit 79. Specifically, the medical information processing device 70 calculates the degree of agreement based on the medical data and license information associated with the medical data searched in step S13 and acquired in step S15, and the search conditions and purpose of use accepted in step S11. More specifically, when the medical information processing device 70 accepts the purpose of use and the medical image data IM1 and case name as the search conditions in step S11, it compares the medical image and case name and purpose of use included in the medical image data IM1 as the search conditions with the medical image in the medical data and the case name included in the supplementary information of the medical image searched in step S13, and the usable range of the license information associated with the medical data, to calculate the degree of agreement. For example, the calculated degree of agreement is associated with the medical data searched by the search function 792 in step S13.

[0062] The method of calculating the degree of agreement is not limited to the case of comparing the medical image data, case name, and purpose of use as search conditions received by the reception function 791 with the medical image in the medical data searched in step S13, the case name included in the incidental information of the medical image, and the license information associated with the medical data. That is, the method of calculating the degree of agreement is arbitrary, and the degree of agreement may be calculated from the rate of agreement of each item of the incidental information by comparing each item of the incidental information of the medical image data received as the search condition and the incidental information of the searched medical image data. In this way, when comparing each item of the incidental information incidental to the medical image received as the search condition and the incidental information of the searched medical image data, the degree of agreement may be calculated using weighting according to the items defined in advance by a table or the like. For example, the degree of agreement may be calculated by defining weighting for each item such as the imaging site, the type of image such as CT or MRI, and age, calculating a coefficient from the defined weighting, and applying the calculated coefficient to the rate of agreement of each item of the incidental information. In addition, when weighting is used according to items defined in advance in a table or the like, the weighting may be set to be greater when the imaging area, image type such as CT or MRI, etc. match, when the ages are similar, or when the cases match.

[0063] 4, the medical information processing device 70 distributes the medical data (step S19). This process of distributing the medical data is realized by the distribution function 794 in the processing circuit 79. Specifically, the medical information processing device 70 distributes the medical data searched by the search function 792 in step S13 based on the purpose of use accepted by the reception function 791 in step S11 and the license information associated with the medical data searched by the search function 792 in step S13. More specifically, the distribution function 794 distributes the medical data searched by the search function 792 in step S13 into medical data with a license for the purpose of use and medical data without a license for the purpose of use based on the purpose of use accepted by the reception function 791 in step S11 and the license information associated with the medical data searched by the search function 792 in step S13. For example, if the intended use is a paper, the allocation function 794 allocates the searched medical data to medical data with a license for the intended use if the range of use in the license information for the medical data includes a paper, and allocates it to medical data without a license for the intended use if the range of use in the license information for the medical data does not include a paper.

[0064] 4, the medical information processing device 70 generates information based on the sorting result (step S21). The process of generating information based on the sorting result is realized by the sorting function 794 in the processing circuitry 79. Specifically, the medical information processing device 70 generates, for example, a medical data list to which the sorting result is added as information based on the sorting result of the sorting function 794.

[0065] FIG. 6 is a diagram showing an example of the medical data list LT1 generated in the medical information processing device 70 according to the present embodiment. As shown in FIG. 6, the medical data list LT1 in the present embodiment includes a patient ID, a patient name, a permission range, a usable range, and a search match degree. The search match degree included in this medical data list LT1 corresponds to the match degree calculated in step S17. In the example shown in FIG. 6, in the medical data list LT1, as a sorting result, hatching is added to medical data that has a use permission for the intended use, and hatching is not added to medical data that does not have a use permission for the intended use. In this way, the sorting function 794 generates the medical data list LT1 to which the sorting result is added as information based on the sorting result.

[0066] The medical data list LT1 may include other information such as a case name. In the example shown in Fig. 6, the medical data with a license for the intended use is hatched as the sorting result, and the medical data without a license for the intended use is not hatched. However, the method of assigning the sorting result is not limited to this. In other words, the method of assigning the sorting result is arbitrary, and for example, different hues may be assigned to the medical data with a license for the intended use and the medical data without a license for the intended use as the sorting result.

[0067] In step S21, the sorting function 794 generates the medical data list LT1 to which the sorting result is added as information based on the sorting result, but is not limited to this. For example, the sorting function 794 may generate two medical data lists as information based on the sorting result: a licensed list including medical data with a license for the intended use, and an unlicensed list including medical data without a license for the intended use.

[0068] Next, as shown in Fig. 4, the medical information processing device 70 presents information based on the allocation result (step S23). This process of presenting information based on the allocation result is realized by the presentation function 795 in the processing circuitry 79. Specifically, the medical information processing device 70 presents the information based on the allocation result generated in step S21 on the display 73. Note that the information based on the allocation result is not limited to being presented on the display 73. In other words, the presentation destination of the information based on the allocation result is arbitrary, and the medical information processing device 70 may transmit the information based on the allocation result to the doctor terminal 30 via the communication interface 77 and present the information based on the allocation result on the display of the doctor terminal 30.

[0069] Fig. 7 is a diagram showing an example of a presentation screen displayed on the display 73 of the medical information processing device 70 according to the first embodiment. As shown in Fig. 7, the presentation screen SC2 according to this embodiment includes the case name and purpose of use, which are the search conditions received in step S11, and the medical data list LT1 generated as information based on the sorting result in step S21. On this presentation screen SC2, for example, a doctor can check the detailed contents of the medical data by selecting one of the medical data included in the medical data list LT1.

[0070] In step S23, information based on the allocation result is presented on the display 73, and the presentation process according to this embodiment is then terminated.

[0071] 8 is a flow chart for explaining the contents of the provision process executed by the medical information processing device 70 according to the first embodiment. In this provision process, when a use application for medical data is received from a doctor, and the medical data for which the use application is received is medical data with a use permission for the intended use, the medical data is provided to the doctor, and when the medical data for which the use application is received is medical data with no use permission for the intended use, the license confirmation information regarding the confirmation of the use permission for the medical data is notified to the patient, and when the use of the medical data is approved by the patient, the medical data is provided to the doctor. For example, this provision process is a process executed when a use application for medical data is received.

[0072] As shown in FIG. 8, first, the medical information processing device 70 judges whether or not an application to use medical data has been accepted (step S31). This process of judging whether or not an application to use medical data has been accepted is realized by the acceptance function 791 in the processing circuit 79. Specifically, the medical information processing device 70 judges whether or not an application to use medical data has been accepted from a doctor via the input interface 71. More specifically, the acceptance function 791 judges whether or not an application to use medical data in the medical data list LT1 provided in step S23 of the presentation process shown in FIG. 4 has been accepted from a doctor via the input interface 71. Then, if an application to use medical data has not been accepted (step S31: No), the medical information processing device 70 waits until an application to use medical data is accepted.

[0073] On the other hand, when an application for use of medical data is accepted (step S31: Yes), the medical information processing device 70 judges whether or not there is a license for the intended use (step S33). The process of judging whether or not there is a license for the intended use is realized by the first notification function 796 in the processing circuit 79. Specifically, the medical information processing device 70 judges whether or not there is a license for the intended use based on the intended use accepted in step S11 of the presentation process and the usable range in the license information associated with the medical data for which the application for use was accepted in step S31.

[0074] If there is no license for the intended use (step S33: No), that is, if an application for use of medical data without a license for the intended use is received, the medical information processing device 70 generates license confirmation information (step S35). The process of generating this license confirmation information is realized by the first notification function 796 in the processing circuit 79. Specifically, the medical information processing device 70 generates the license confirmation information based on the medical data for which the application for use was received in step S31 and the intended use received in step S11 of the presentation process.

[0075] 9 is a diagram showing an example of license confirmation information IF1 generated in the medical information processing device 70 according to the first embodiment. As shown in FIG. 9, license confirmation information IF1 according to this embodiment includes a medical image in the medical data, a purpose of use, and a facility name. Note that, although license confirmation information IF1 according to this embodiment includes a medical image, a purpose of use, and a facility name, the contents included in the license confirmation information are not limited to this. In other words, the contents included in license confirmation information IF1 are arbitrary, and for example, license information associated with medical data for which a usage application has been accepted may be included in license confirmation information IF1.

[0076] Next, as shown in FIG. 8, the medical information processing device 70 notifies the patient of the license confirmation information IF1 (step S37). The process of notifying the patient of the license confirmation information IF1 is realized by the first notification function 796 in the processing circuit 79. Specifically, the medical information processing device 70 notifies the patient of the license confirmation information IF1 generated in step S35 via the communication interface 77. More specifically, the first notification function 796 notifies the patient by transmitting the license confirmation information IF1 to the patient terminal 90 based on the contact information registered in the medical data management data MD. Note that if the contact information is not registered in the medical data management data MD or if the license confirmation information is not directly notified to the patient, the first notification function 796 may transmit the license confirmation information to a doctor terminal or the like of a facility or the like registered in the facility / company of the medical data management data MD via the network NW2, and notify the patient of the license information via the facility or the like.

[0077] Next, as shown in Fig. 8, the medical information processing device 70 judges whether or not the usability information has been received (step S39). The process of judging whether or not the usability information has been received is realized by the reception function 791 in the processing circuit 79. Specifically, the medical information processing device 70 judges whether or not the usability information has been received from the patient terminal 90 via the communication interface 77. Note that the usability information is not limited to being transmitted from the patient terminal 90, but may be transmitted from a doctor's terminal in the facility where the patient is visiting. Then, if the usability information has not been received (step S39: No), the medical information processing device 70 waits until the usability information is received.

[0078] On the other hand, when the usability information is received in step S39 (step S39: Yes), the medical information processing device 70 judges whether the medical data is usable or not (step S41). This process of judging whether the medical data is usable or not is realized by the first notification function 796 in the processing circuit 79. Specifically, the medical information processing device 70 judges whether the medical data is usable or not based on the usability of the medical data in the received usability information.

[0079] Then, in step S41, if the medical data cannot be used (step S41: No), the medical information processing device 70 notifies the doctor that the medical data cannot be used (step S43). This process of notifying the doctor that the medical data cannot be used is realized by the first notification function 796 in the processing circuit 79. Specifically, the medical information processing device 70 notifies the doctor that the medical data cannot be used via the display 73. Note that in step S43, the destination of the notification that the medical data cannot be used is not limited to the display 73 of the medical information processing device 70, and the notification may be sent to the doctor terminal 30 via the communication interface 77.

[0080] On the other hand, if the medical data can be used in step S41 (step S41: Yes), or if there is a license for the intended use in step S33 (step S33: Yes), the medical information processing device 70 converts the medical data (step S45). This process of converting the medical data is realized by the conversion function 797 in the processing circuit 79. Specifically, the medical information processing device 70 converts the medical data based on the disclosure range in the license information associated with the medical data. More specifically, the conversion function 797 converts the medical data based on the disclosure range so as to anonymize information that identifies an individual other than the contents included in the disclosure range. For example, if the disclosure range includes age and sex, the conversion function 797 converts the medical data by removing or filling in information such as a patient ID, a patient name, an imaging site, and a case name in the medical data, which is information that identifies an individual other than age and sex.

[0081] Next, as shown in FIG. 8, the medical information processing device 70 provides the medical data (step S47). This process of providing the medical data is realized by the first notification function 796 in the processing circuit 79. Specifically, the medical information processing device 70 provides the medical data converted in step S45 to the doctor. More specifically, the medical information processing device 70 provides the medical data to the doctor by making the medical data converted in step S45 downloadable. Note that the medical information processing device 70 may provide the medical data to the doctor by transmitting the medical data to the doctor terminal 30 via the communication interface 77. In addition, hereinafter, the medical data provided to the doctor is also referred to as provided data, as necessary.

[0082] FIG. 10 is a diagram showing an example of the provided data provided by the medical information processing device 70 according to the first embodiment. As shown in FIG. 10, the provided data PD1 includes a medical image, findings, age, and sex. The provided data PD1 in the example shown in FIG. 10 is data including a chest X-ray image as a medical image, age "40", and sex "male". In the example shown in FIG. 10, the provided data PD1 includes a medical image, age, and sex, but the contents included in the provided data PD1 are not limited to this. For example, the provided data PD1 may include vital information including at least one of findings, weight, height, pulse, and biochemical information related to the results of a biochemical test, and medical history.

[0083] In step S47, the medical data is provided, or in step S43, the doctor is notified that the medical data is unusable, and the provision process according to this embodiment is terminated.

[0084] 11 is a flow chart for explaining the contents of the notification process executed by the medical information processing device 70 according to the first embodiment. In this notification process, when the medical data is used by a doctor, information on the number of times the medical data has been used is updated, information indicating that the medical data has been used is generated, and the information indicating that the medical data has been used is notified to the patient. For example, this notification process is a process that is executed when the medical data is used.

[0085] As shown in Fig. 11, first, the medical information processing device 70 determines whether or not the medical data has been used (step S51). This process of determining whether or not the medical data has been used is realized by the second notification function 798 in the processing circuit 79. Specifically, the medical information processing device 70 determines whether or not the medical data has been used by determining whether or not the medical data has been downloaded or whether or not the medical data has been used in accordance with its intended purpose. Then, in step S51, if the medical data has not been used (step S51: No), the medical information processing device 70 waits until the medical data is used.

[0086] On the other hand, if the medical data has been used in step S51 (step S51: Yes), the medical information processing device 70 transmits an instruction to update the use count information (step S53). This process of transmitting the instruction to update the use count information is realized by the second notification function 798 in the processing circuitry 79. Specifically, the medical information processing device 70 transmits an instruction to update the use count information included in the management data MD corresponding to the used medical data to the database 10 via the communication interface 77.

[0087] 11, the medical information processing device 70 generates information indicating that the medical data has been used (step S55). The process of generating the information indicating that the medical data has been used is realized by the second notification function 798 in the processing circuitry 79. Specifically, the medical information processing device 70 generates information indicating that the medical data has been used based on the used medical data.

[0088] Fig. 12 is a diagram showing an example of information indicating that medical data generated in the medical information processing device 70 according to the first embodiment has been used. As shown in Fig. 12, the information indicating that medical data according to this embodiment has been used is used data information IF2. In the example shown in Fig. 12, the used data information IF2 includes, as the contents of the used medical data, medical image data, the content of use "paper", and the name of the facility that used it, "facility A".

[0089] Next, as shown in FIG. 11, the medical information processing device 70 notifies the patient of information indicating that the medical data has been used (step S57). This process of notifying the patient of information indicating that the medical data has been used is realized by the second notification function 798 in the processing circuit 79. Specifically, the medical information processing device 70 notifies the patient of the use data information, which is information indicating that the medical data generated in step S55 has been used. More specifically, the second notification function 798 notifies the patient by transmitting the use data information IF2 to the patient terminal 90 based on the contact information registered in the medical data management data MD. Note that if the contact information is not registered in the medical data management data MD, or if the information indicating that the medical data has been used is not directly notified to the patient, the second notification function 798 may transmit information indicating that the medical data has been used to a doctor terminal or the like of a facility or the like registered in the facility / company of the medical data management data MD via the network NW2, and notify the patient of the information indicating that the medical data has been used via the facility.

[0090] In step S57, the patient is notified of information indicating that the medical data has been used, and the notification process according to this embodiment is then terminated.

[0091] 13 is a flow chart for explaining the contents of the billing process executed in the medical image processing device 70 according to the first embodiment. In this billing process, when the provided data is used, information on the number of uses is acquired, and billing is executed to the patient based on the acquired information on the number of uses. For example, this billing process is executed when the provided data is used.

[0092] As shown in Fig. 13, first, the medical information processing device 70 determines whether the medical data has been used (step S61). This process of determining whether the medical data has been used is realized by the billing execution function 799 in the processing circuit 79. Specifically, the medical information processing device 70 determines whether the medical data has been used by determining whether the medical data has been downloaded or whether the medical data has been used in accordance with its intended purpose. Then, in step S61, if the medical data has not been used (step S61: No), the medical information processing device 70 waits until the medical data is used.

[0093] On the other hand, if the medical data has been used in step S61 (step S61: Yes), the medical information processing device 70 acquires use count information (step S63). The process of acquiring the use count information is realized by the billing execution function 799 in the processing circuit 79. Specifically, the medical information processing device 70 acquires the use count information from the management data MD corresponding to the used medical data.

[0094] Next, as shown in FIG. 13, the medical information processing device 70 executes billing (step S65). This process of executing billing is realized by a billing execution function 799 in the processing circuit 79. Specifically, billing is executed for the patient based on the use count information acquired in step S63. More specifically, the billing execution function 799 calculates the billing amount by referring to a table that associates the use count with the billing amount, or by using a predetermined formula that calculates the billing amount from the use count, and executes billing for the patient. Here, executing billing for the patient refers to the doctor making a payment to the patient according to the billing amount.

[0095] In step S65, the charging is performed, and the charging process according to this embodiment is terminated.

[0096] As described above, according to the medical information processing system 1 of the first embodiment, the medical information processing device 70 receives search conditions for medical data and the purpose of use of the medical data, refers to the database 10 based on the received search conditions to search for medical data, and sorts the medical data based on the license information associated with the searched medical data and the received purpose of use of the medical data, and presents information based on the sorting results, so that it is possible to know whether the medical data is data that can be referred to and / or diverted. In other words, it is possible to easily know the scope of the license for use of the medical data.

[0097] In addition, when the medical information processing device 70 of this embodiment receives an application to use medical data that does not have a license for the intended use, it notifies the patient of license confirmation information, making it possible to obtain license from the patient as necessary.

[0098] In addition, the medical information processing device 70 of this embodiment notifies the patient of information indicating that the medical data has been used when the medical data has been used, thereby reducing the possibility that the medical data will be used without the patient's knowledge.

[0099] Furthermore, according to the medical information processing system 1 of this embodiment, the database 10 manages medical data stored in other facilities, and the medical information processing device 70 is capable of searching for medical data stored in other facilities when searching for medical data, so that medical data from one's own hospital and / or other hospitals can be easily used.

[0100] Furthermore, according to the medical information processing system 1 of this embodiment, permission to use medical data from patients is obtained via a network, making it possible for doctors to easily obtain permission to use medical data.

[0101] In the first embodiment described above, the database 10 may be configured using a database shared in a distributed manner by a plurality of nodes connected to the network NW2, specifically, using a blockchain. In this case, the concept of a node includes, for example, the medical data storage device 50A, the medical data storage device 50B, the medical information processing device 70, etc. In this way, by configuring the database 10 using a blockchain, it becomes difficult to tamper with the medical data and management data, and the security of the management of the medical data can be improved.

[0102] Second Embodiment In the above-mentioned first embodiment, the database 10 is connected to the network NW2 and manages medical data acquired at a plurality of facilities, such as facility A and facility B, connected to the network NW2, but the database 10 does not necessarily need to manage medical data from a plurality of facilities. Therefore, in the second embodiment, a medical information processing system 1 in which the database 10 manages medical data acquired at one facility will be described. The following describes the parts that are different from the above-mentioned first embodiment.

[0103] FIG. 14 is a block diagram showing an example of the configuration of a medical information processing system 1 according to the second embodiment, and corresponds to FIG. 1 in the first embodiment described above. As shown in FIG. 14, the medical information processing system 1 according to this embodiment is configured to include a database 10a, a doctor terminal 30, a medical data storage device 50a, a medical information processing device 70, and a patient terminal 90. As shown in FIG. 14, in the medical information processing system 1 according to the second embodiment, the database 10a, the doctor terminal 30, the medical data storage device 50a, and the medical information processing device 70 are communicatively connected to each other via an intra-hospital network NW1 using a dedicated line in the hospital. Also, as shown in FIG. 14, in the medical information processing system 1 according to the second embodiment, the medical data storage device 50a, the medical information processing device 70, and the patient terminal 90 are communicatively connected to each other via a network NW2 using a public line such as the Internet.

[0104] The database 10a according to this embodiment manages medical data of one facility and license information associated with the medical data in association with each other. Specifically, the database 10a according to this embodiment manages medical data of facility A in association with license information. This database 10a at least stores management data that manages information related to the storage destination of medical data in facility A in association with license information, thereby managing the medical data in association with license information.

[0105] FIG. 15 is a diagram showing an example of management data according to the second embodiment, and corresponds to FIG. 2 in the first embodiment described above. As shown in FIG. 15, in the management data MDa, items and contents for the items are associated with each other, similar to the management data MD in the first embodiment described above, and the items include a facility / company, a reliability, a role, a management device, a name, an access source, a use destination, a purpose of use, a contact, information on the number of uses, a disclosure period (use period), and permission contents (license contents) including a permission range, a usable range, and a disclosure range. The management data MDa according to this embodiment is also data registered for each medical data, similar to the management data MD according to the first embodiment.

[0106] The facility / company field is an item of information related to the name of the facility or company where the medical data is stored. Since the database 10a according to this embodiment manages the medical data of facility A, facility A is registered in the content of the facility / company field of the management data MD1a shown in FIG.

[0107] The reliability is an item related to the reliability of the facility that uses the medical data. As with the facility / company items described above, the database 10a according to this embodiment manages medical data of facility A, so the contents of the item in the management data MD1a shown in FIG. 15 indicate that the reliability of facility A is 8. Note that this reliability may include authentication information. The authentication information is information related to authentication when accessing medical data managed in this management data MDa from a facility registered with this reliability.

[0108] Other items of the management data MDa are similar to those of the management data MD in the first embodiment described above, and therefore a description thereof will be omitted.

[0109] The medical data storage device 50a stores medical data such as medical image data and findings data. The medical data storage device 50a according to this embodiment transmits the stored medical data to the doctor terminal 30 and the medical information processing device 70 via the hospital network NW1. For example, the medical data storage device 50a is configured with an image server such as a PACS (Picture Archiving and Communication System). In the example shown in FIG. 15, for example, the medical data storage device 50a stores medical data generated in facility A.

[0110] The configurations and functions of the doctor terminal 30, the medical information processing device 70, and the patient terminal 90 are similar to those of the first embodiment described above, and therefore will not be described.

[0111] As described above, according to the medical information processing system 1 of the second embodiment, the database 10a manages medical data acquired at one facility, the medical information processing device 70 can search for medical data stored at the facility when searching for medical data, and the medical information processing device 70 accepts search conditions for medical data and the purpose of use of the medical data, refers to the database 10a based on the accepted search conditions to search for medical data, and sorts the medical data based on the license information associated with the searched medical data and the accepted purpose of use of the medical data, and presents information based on the sorting result, so that it is possible to know whether the medical data is data that can be referred to and / or can be diverted. In other words, the content of the license for the medical data can be easily understood.

[0112] In the second embodiment described above, the database 10a is configured to be connected to the intra-hospital network NW1, but this is not limited thereto. The database 10a may be configured to be included in the medical data storage device 50a, or may be configured to be included in the storage circuitry 75 of the medical information processing device 70.

[0113] [Modification 1 of the first and second embodiments] The medical information processing device 70 of the first and second embodiments described above charges the patient based on the number of times the medical data is used, but instead of charging the patient, it is also possible to give points to the patient based on the number of times the medical data is used. A case where this modification is applied to the first embodiment will be described as Modification 1, but this modification can also be applied to the second embodiment described above.

[0114] 16 is a block diagram showing an example of the configuration of a medical information processing device 70 according to the first modification, and corresponds to FIG. 3 in the first embodiment. As shown in FIG. 16, the medical information processing device 70 according to this modification is configured by providing a processing circuitry 79 with a point-giving function 800 instead of a billing execution function 799. This point-giving function 800 is a function that is realized by the processing circuitry 79 reading and executing a program stored in the storage circuitry 75. This point-giving function 800 corresponds to the point-giving unit in the first modification.

[0115] Fig. 17 is a flow chart for explaining the content of the point allocation process executed by the medical information processing device 70 according to the first modification, and corresponds to Fig. 13 in the first embodiment. As shown in Fig. 17, steps S61 and S63 of the point allocation process according to this modification are similar to the billing execution process shown in Fig. 13 in the first embodiment.

[0116] After this step S63, the medical information processing device 70 assigns points (step S71). This process of assigning points is realized by the point assigning function 800 in the processing circuit 79. Specifically, the medical information processing device 70 assigns points to the patient based on the use count information acquired in step S63. More specifically, the point assigning function 800 calculates the number of points by referring to a table in which the number of uses is associated with the number of points, or by using a predetermined formula for calculating the number of points from the number of uses, and assigns the points to the patient. In this step S71, the points are assigned to the patient, and the point assigning process according to this embodiment is terminated. In this way, it is also possible to assign points to the patient instead of charging the patient.

[0117] [Other Modifications of the First and Second Embodiments] In the above-mentioned first and second embodiments, each process is described using the case where the purpose of use accepted by the reception function 791 is a thesis as an example, but the purpose of use accepted by the reception function 791 is not limited to a thesis. For example, image analysis may be accepted as the purpose of use accepted by the reception function 791. The use in this image analysis is a case where, when performing image analysis by AI such as an analysis application on a medical image, medical data is used to determine whether an accurate result can be obtained by analyzing the medical image before the image analysis is performed. More specifically, in an analysis application that analyzes how much blood is flowing in a coronary artery when a medical image of a coronary artery is input, the medical image and the analysis result included in the medical data are used to compare whether an accurate analysis result can be obtained by inputting the medical image into the analysis application from the viewpoint of dust, noise, and artifacts. That is, in this case, the medical data includes information on the analysis result of the image analysis. In this way, even if the medical data is used before the image analysis is performed, permission to use may be obtained from the patient, and when the medical data is used in step S57 of the presentation process, information indicating that the medical data has been used may be notified to the patient.

[0118] Also, in the first and second embodiments described above, for example, AI may be accepted as the intended use accepted by the reception function 791. That is, medical data may be used as learning data (teacher data) for training an AI (learning model). In this way, when medical data is used as learning data (teacher data) for training an AI, and when the medical data is used for AI training, information indicating that the medical data has been used may be notified to the patient. Alternatively, in the presentation process in the first embodiment described above, when the intended use "AI training" is accepted and a search for medical data is performed, information indicating that the medical data has been searched may be notified to the patient.

[0119] In the first and second embodiments described above, for example, a referral letter may be accepted as the purpose of use accepted by the reception function 791. That is, medical data may be used when presenting information in place of a referral letter to other medical facilities instead of a referral letter. Here, the information in place of a referral letter is a medical image with accompanying information in the case of medical image data, and is patient information and findings in the case of findings data. Note that, when the information in place of a referral letter includes both medical image data and findings data, the findings in the findings data may be linked to the medical image data. In this way, when it is desired to present information in place of a referral letter and to use medical data, usage permission confirmation information may be generated and notified to the patient.

[0120] The databases 10 and 10a of the first and second embodiments described above may store the medical data itself. By storing the medical data itself in the databases 10 and 10a, the medical information processing device 70 can search for the medical data without needing to obtain the medical data from the medical data storage devices of each facility.

[0121] The databases 10 and 10a of the first and second embodiments described above can also manage terminal information related to accessible terminals. In this case, the management data MD and MDa include terminal information related to terminals that can access the medical data. In addition, when the management data MD and MDa include terminal information, when searching for medical data in step S13 in the presentation process of FIG. 4, the medical data may be prevented from being accessed from a terminal that is not registered in the terminal information of the management data MD and MDa. Alternatively, even if the medical data can be searched for in step S13 in the presentation process of FIG. 4, when an application for use of medical data in the management data MD that has passed the disclosure period is accepted in step S31 in the provision process of FIG. 8, the medical information processing device 70 may generate use permission confirmation information and notify the patient of the information in step S33 in the provision process of FIG. 8, assuming that there is no permission to use the medical data.

[0122] This terminal information may be manually registered by the user, or may be automatically added to the management data MD, MDa when it is determined in step S41 of the provision process of FIG. 8 that the medical data is usable.

[0123] Furthermore, the medical image processing apparatus 70 according to the above-described first and second embodiments may limit the storage of the medical data provided in step S47 in the providing process of FIG.

[0124] Furthermore, the medical information processing apparatus 70 according to the first and second embodiments described above can also restrict the search for medical data whose disclosure period in the management data MD has passed. In this case, for example, when searching for medical data in step S13 in the presentation process of Fig. 4, the search function 792 in the processing circuitry 79 refers to the disclosure period in the management data MD and restricts the search for medical data whose disclosure period in the management data MD has passed so as not to search for medical data whose disclosure period in the management data MD has passed.

[0125] Furthermore, even if it is possible to search for medical data for which the disclosure period in the management data MD has passed, when the medical information processing device 70 of the first and second embodiments described above receives an application to use medical data for which the disclosure period in the management data MD has passed in step S31 of the provision process of Figure 8, it may generate license confirmation information in step S33 of the provision process of Figure 8, determining that there is no license to use the medical data, and notify the patient of this.

[0126] The license confirmation information may also include the reliability of the facility that uses the medical data. Specifically, the medical information processing apparatus 70 according to the first and second embodiments described above may obtain the reliability from the management data MD corresponding to the medical data for which a use application has been accepted in step S35 of the provision process of FIG. 8, and generate the license confirmation information by including the reliability in the license confirmation information. By generating the license confirmation information including the reliability in this manner, the license confirmation information including the reliability is notified to the patient in step S37 of the provision process of FIG. 8. This allows the patient to use the reliability included in the license confirmation information as a criterion for determining whether or not to permit the use of medical data.

[0127] Moreover, instead of the image input box IB1 into which the medical image data IM1 is input, the input screen SC1 may display a text box for accepting text input related to findings. Fig. 18 is a diagram showing another example of the input screen displayed on the display 73 of the medical information processing device 70. For example, in step S11 in the presentation process of Fig. 4, "There are nodules in two places in the lungs" may be input as text input related to findings into the text box TB3 displayed on the input screen SC1 and accepted as a search condition. That is, instead of medical image data, text input related to findings may be accepted as a search condition.

[0128] The term "processor" used in the above description means a circuit such as a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)). The processor realizes its function by reading and executing a program stored in the memory circuit 75. Instead of storing a program in the memory circuit 75, the processor may be configured to directly incorporate the program in the circuit. In this case, the processor realizes its function by reading and executing the program incorporated in the circuit. The processor is not limited to being configured as a single processor circuit, and may be configured as one processor by combining multiple independent circuits to realize its function. Furthermore, the multiple components in FIG. 3 and FIG. 16 may be integrated into one processor to realize its function.

[0129] Although several embodiments have been described above, these embodiments are presented only as examples and are not intended to limit the scope of the invention. The novel device and method described in this specification can be implemented in various other forms. In addition, various omissions, substitutions, and modifications can be made to the forms of the device and method described in this specification without departing from the spirit of the invention. The appended claims and their equivalents are intended to include such forms and modifications that fall within the scope and spirit of the invention. [Explanation of symbols]

[0130] 1... medical information processing system, 10... database, 30... doctor terminal, 50, 50a... medical data storage device, 70... medical information processing device, 71... input interface, 73... display, 75... memory circuit, 77... communication interface, 79... processing circuit, 90... patient terminal, 791... reception function, 792... search function, 793... calculation function, 794... allocation function, 795... presentation function, 796... first notification function, 797... conversion function, 798... second notification function, 799... charging execution function, 800... point allocation function

Claims

1. a reception unit that receives search conditions for searching medical data including at least one of doctor's findings and medical image data, and a purpose of use of the medical data; a search unit that searches for the medical data by referring to a database that associates and manages the medical data with license information regarding a license for the medical data based on the search conditions received by the reception unit; a distribution unit that distributes the medical data searched by the search unit based on the license information associated with the medical data searched by the search unit and the purpose of use accepted by the acceptance unit; a presentation unit that presents information based on a distribution result of the distribution unit; A medical information processing device comprising:

2. The medical information processing device according to claim 1 , further comprising a calculation unit that calculates a degree of agreement between the medical data searched by the search unit and license information associated with the medical data searched by the search unit, and the search conditions and the intended use.

3. 2. The medical information processing device according to claim 1, wherein the allocation unit allocates the medical data searched by the search unit into medical data with a license for the intended purpose and medical data without a license for the intended purpose based on the intended purpose accepted by the acceptance unit and the license information associated with the medical data searched by the search unit.

4. The medical information processing device according to claim 1 , further comprising a first notification unit that, when an application for use of the medical data is accepted that does not have a license for the intended use, notifies a patient of license confirmation information regarding confirmation of the license for the medical data.

5. The medical image processing apparatus according to claim 4 , wherein the license confirmation information includes a reliability of a facility that uses the medical data.

6. the license information includes a disclosure scope of the medical data, The medical information processing apparatus according to claim 1 , further comprising a conversion unit that converts the medical data based on the range of disclosure.

7. The medical image processing apparatus according to claim 1 , further comprising a second notification unit that, when the medical data has been used, notifies a patient of information indicating that the medical data has been used.

8. The medical image processing apparatus according to claim 1 , wherein the medical data is associated with use count information regarding the number of times the medical data has been used.

9. The medical information processing apparatus according to claim 8 , further comprising a billing execution unit that executes billing for a patient based on the use count information.

10. The medical information processing device according to claim 8 , further comprising a point giving unit that gives points to the patient based on the number of times of use information.

11. The medical information processing device according to claim 1 , wherein the database is configured using a blockchain.

12. a database for managing medical data including at least one of doctor's findings and medical image data, and license information regarding the license for the medical data in association with each other; a reception unit that receives search conditions for searching the medical data and a purpose of use of the medical data; a search unit that searches for the medical data by referring to the database based on the search conditions accepted by the accepting unit; a distribution unit that distributes the medical data searched by the search unit based on the license information associated with the medical data searched by the search unit and the purpose of use accepted by the acceptance unit; a presentation unit that presents information based on a distribution result of the distribution unit, A medical information processing device; A medical information processing system comprising:

13. receiving search conditions for searching medical data including at least one of findings data related to a doctor's findings and medical image data, and a purpose of use of the medical data; searching for the medical data based on the received search conditions by referring to a database that associates and manages the medical data with license information regarding a license for the medical data; sorting the searched medical data based on the license information associated with the searched medical data and the accepted purpose of use; presenting information based on a result of the sorting; A medical information processing program that causes a computer to execute the above.

Images