Medical information processing device

The medical image processing apparatus effectively identifies and follows up with patients requiring care by detecting abnormalities in test results and excluding those with canceled issues, ensuring timely medical treatment.

JP7745378B2Active Publication Date: 2025-09-29CANON MEDICAL SYST CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021123900
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-07-29
Publication Date
2025-09-29
Estimated Expiration
2041-07-29

AI Technical Summary

Technical Problem

Existing systems fail to efficiently identify patients who require follow-up care based on test results, leading to potential worsening of their condition due to inadequate timely medical treatment.

Method used

A medical image processing apparatus with an identification unit, detection units, and determination units to identify follow-up candidates, detect abnormalities in test results, and set appropriate follow-up targets by excluding patients with canceled abnormalities from the follow-up list.

Benefits of technology

Ensures timely medical treatment by identifying and following up with patients who need it, thereby preventing their conditions from worsening.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007745378000001
    Figure 0007745378000001
  • Figure 0007745378000002
    Figure 0007745378000002
  • Figure 0007745378000003
    Figure 0007745378000003
Patent Text Reader

Abstract

To provide a medical information processing device that identifies a patient for whom examination as to whether treatment is provided at proper timing should be continuously followed.SOLUTION: In a notification server 50 that identifies a patient for whom examination as to whether treatment is provided at proper timing should be continuously followed, a candidate identification function 551 identifies a follow candidate which is the candidate for the patient to be followed. A first abnormality detection function 552 detects abnormality from a first inspection result pertaining to the follow candidate patient. A second abnormality detection function 553 detects abnormality from a second inspection result pertaining to the follow candidate patient that was generated at a later time than the first inspection result. An exclusion setting function 554 determines whether or not to exclude the patient from the follow candidate, on the basis of the treatment records of the follow candidate patient, when abnormality of the patient is detected from the second inspection result. A follow subject setting function 556 sets a patient not excluded from the follow candidate by the first determination unit to be the subject to be followed.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The embodiments disclosed in the present specification and drawings relate to a medical information processing device.

[0002] Conventionally, various tests are performed on patients. However, if the patient is not treated according to the test results, the patient's condition may worsen. Therefore, patients need to receive medical treatment at the appropriate time.

[0003] However, it would be cumbersome to set all patients as subjects for follow-up, which requires continuous investigation to check whether treatment is being provided at an appropriate time. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-018705 Summary of the Invention [Problem to be solved by the invention]

[0005] One of the problems to be solved by the embodiments disclosed in this specification and the drawings is to identify patients who should be followed. 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 below can also be positioned as other problems. [Means for solving the problem]

[0006] A medical image processing apparatus according to an embodiment includes an identification unit, a first detection unit, a second detection unit, a first determination unit, and a setting unit. The identification unit identifies a follow-up candidate who is a candidate for a follow-up target patient. The first detection unit detects an abnormality from a first test result for the follow-up candidate patient. The second detection unit detects an abnormality from a second test result for the follow-up candidate patient that was generated earlier than the first test result. The first determination unit: The first test result and The second test result Different If an abnormality is detected, the setting unit determines whether to exclude the patient from the follow-up candidate based on the medical records of the patient of the follow-up candidate. The setting unit sets the patient who was not excluded from the follow-up candidate by the first determination unit as the follow-up target. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a notification system according to this embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the notification server according to this embodiment. [Figure 3] FIG. 3 is a flowchart showing an example of a test result notification process executed by the notification server according to this embodiment. [Figure 4] FIG. 4 is a flowchart showing an example of a reservation notification process executed by the notification server according to this embodiment. [Figure 5] FIG. 5 is a flowchart showing an example of a drug notification process executed by the notification server according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the medical image processing device according to this embodiment will be described with reference to the drawings. In the following embodiments, parts with the same reference numerals perform similar operations, and redundant description will be omitted as appropriate.

[0009] (Present embodiment) FIG. 1 is a block diagram showing an example of the configuration of a notification system 1 according to this embodiment. The notification system 1 includes a Hospital Information System (HIS) 10, a Radiology Information System (RIS) 20, a Picture Archiving and Communication System (PACS) 30, a Laboratory Information System (LIS) 40, and a notification server 50. Each system and device is connected to each other so as to be able to communicate with each other via a network 60. The configuration shown in FIG. 1 is an example, and the number of each system and device may be changed as desired. Devices not shown in FIG. 1 may also be connected to the network 60.

[0010] The hospital information system 10, the radiology department information system 20, the medical image management system 30, the clinical test information system 40, and the notification server 50 are realized by computer devices such as servers and workstations.

[0011] The hospital information system 10 stores schedule information 11 and electronic medical record information 12. The schedule information 11 is information that records a patient's medical treatment schedule, such as a history of past visits to the hospital and future visits the patient plans to make. In other words, the schedule information 11 includes information for identifying the patient and the patient's schedule. The electronic medical record information 12 is information that records the progress of the patient's medical treatment. For example, the electronic medical record information 12 includes information for identifying the patient, the name of the disease the patient has, the name of the prescribed medication, the treatment period, and the like. The electronic medical record information 12 is an example of a medical record.

[0012] The radiology information system 20 stores imaging order information 21 and image interpretation report information 22. The imaging order information 21 is information ordering an examination by imaging. The image interpretation report information 22 is information containing findings by a doctor or other medical professional who interpreted image information 31 captured by a medical image diagnostic device. The image interpretation report information 22 also contains information for identifying a medical professional such as a doctor who ordered imaging by the medical image diagnostic device.

[0013] The medical image management system 30 stores image information 31. The image information 31 includes images captured by a medical image diagnostic device. The medical image diagnostic device is, for example, an X-ray CT (Computed Tomography) device, an MRI (Magnetic Resonance Imaging) device, an X-ray diagnostic device, an ultrasound diagnostic device, or the like. The image information 31 complies with the DICOM (Digital Imaging and Communications in Medicine) standard.

[0014] The clinical test information system 40 stores clinical test order information 41, clinical test result information 42, and clinical test report information 43. The clinical test order information 41 is information for ordering a clinical test. The clinical test result information 42 is information showing the results of the clinical test. The clinical test report information 43 is information containing findings on the clinical test results. Furthermore, the clinical test order information 41, clinical test result information 42, and clinical test report information 43 contain information for identifying the medical professional, such as a doctor, who ordered the clinical test.

[0015] The notification server 50 is a server device that notifies the patient of the follow-up target according to their condition. The notification server 50 is an example of a medical information processing device. More specifically, the notification server 50 identifies candidate patients to be followed. A follow-up target is a target for which continuous investigation is conducted to determine whether medical treatment is being provided at an appropriate time. For example, the notification server 50 has little need to set a minor illness such as a cold or a minor injury as a follow-up target. Therefore, the notification server 50 identifies follow-up candidates who are candidates for patients to be followed from among patients with illnesses or injuries that have been set in advance.

[0016] The notification server 50 also determines whether the test results of the follow-up candidate patient contain an abnormality. If the test results contain an abnormality, the notification server 50 also determines whether the medical records, such as the electronic medical record information 12, contain information to cancel the detected abnormality. For example, even if an abnormal shadow is detected by mammography, if the shadow is dense breast tissue, the patient does not suffer from breast cancer or other conditions. In such cases, the electronic medical record information 12 records information indicating that the abnormal shadow is dense breast tissue and therefore no problem is diagnosed. For example, the notification server 50 detects the information indicating the diagnosis that there is no problem as information to cancel the abnormality. The notification server 50 then determines to exclude the patient from the follow-up candidates.

[0017] The notification server 50 also sets patients who have not been excluded from the follow-up candidates as follow-up targets. The notification server 50 then follows up with medical professionals such as doctors in charge of the patients who are the follow-up targets, the patients themselves, and people related to the patients. For example, the notification server 50 sends emails or the like indicating the content of the follow-up.

[0018] Next, the notification server 50 will be described.

[0019] 2 is a block diagram showing an example of the configuration of the notification server 50 according to this embodiment. The notification server 50 includes an NW (network) interface 510, an input interface 520, a display 530, a storage circuit 540, and a processing circuit 550.

[0020] The NW interface 510 is connected to the processing circuit 550, and controls the transmission and communication of various data between the processing circuit 550 and each device connected via the network 60. For example, the NW interface 510 is realized by a network card, a network adapter, a NIC (Network Interface Controller), or the like.

[0021] The input interface 520 is connected to the processing circuit 550 and converts input operations received from an operator (medical professional) into electrical signals and outputs the electrical signals to the processing circuit 550. Specifically, the input interface 520 converts the input operations received from the operator into electrical signals and outputs the electrical signals to the processing circuit 550. For example, the input interface 520 may be realized by a trackball, a switch button, a mouse, a keyboard, a touchpad that performs input operations by touching the operation surface, a touchscreen that integrates a display screen and a touchpad, a non-contact input circuit using an optical sensor, a voice input circuit, or the like. Note that in this specification, the input interface 520 is not limited to those that include physical operation components such as a mouse and a keyboard. For example, 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 is also included as an example of the input interface 520.

[0022] The display 530 is connected to the processing circuit 550 and displays various information and image data output from the processing circuit 550. For example, the display 530 is realized by a liquid crystal display, a CRT (Cathode Ray Tube) display, an organic EL display, a plasma display, a touch panel, or the like.

[0023] The storage circuitry 540 is connected to the processing circuitry 550 and stores various data. The storage circuitry 540 also stores various programs that are read and executed by the processing circuitry 550 to realize various functions. For example, the storage circuitry 540 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, a hard disk, an optical disk, or the like.

[0024] The memory circuitry 540 stores notification destination information 541. The notification destination information 541 has information indicating the notification destination of each patient. For example, the notification destination information 541 has the email address of the patient and the email address of the doctor in charge of treating the patient. Note that the notification destination information 541 is not limited to an email address, and may be an account of a social networking service (SNS) or other information.

[0025] The processing circuit 550 controls the overall operation of the notification server 50. The processing circuit 550 includes, for example, a candidate identification function 551, a first anomaly detection function 552, a second anomaly detection function 553, an exclusion determination function 554, a schedule acquisition function 555, a follow target setting function 556, and a notification function 557. In the embodiment, each processing function performed by the components of the candidate identification function 551, the first anomaly detection function 552, the second anomaly detection function 553, the exclusion determination function 554, the schedule acquisition function 555, the follow target setting function 556, and the notification function 557 is stored in the storage circuit 540 in the form of a computer-executable program. The processing circuit 550 is a processor that reads and executes the program from the storage circuit 540 to realize the function corresponding to each program. In other words, the processing circuit 550, after reading each program, has the functions shown in the processing circuit 550 of FIG. 2.

[0026] 2 has been described as realizing the candidate identification function 551, the first anomaly detection function 552, the second anomaly detection function 553, the exclusion determination function 554, the schedule acquisition function 555, the follow target setting function 556, and the notification function 557 by a single processor, but it is also possible to combine multiple independent processors to configure the processing circuit 550 and have each processor execute a program to realize the function. Also, in FIG. 2, it has been described as realizing the single storage circuit such as the storage circuit 540 storing the program corresponding to each processing function, but it is also possible to configure multiple storage circuits to be distributed and have the processing circuit 550 read out the corresponding program from each storage circuit.

[0027] The term "processor" used in the above description refers to a circuit such as a CPU (Central Processing Unit), a GPU (Graphical Processing Unit), 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 functions by reading and executing a program stored in the memory circuit 540. Note that instead of storing a program in the memory circuit 540, the processor may be configured so that the program is directly embedded in its circuitry. In this case, the processor realizes its functions by reading and executing the program embedded in its circuitry.

[0028] The candidate identification function 551 identifies follow-up candidates who are candidates for patients to be followed up. The candidate identification function 551 is an example of an identification unit. More specifically, the candidate identification function 551 identifies, as follow-up candidates, patients whose medical records include information indicating a diagnosis result of a set injury or illness or a possibility of the set injury or illness. For example, when the candidate identification function 551 detects information indicating a diagnosis of a set injury or illness or a possibility of the set injury or illness, information indicating that a medication prescribed for the set injury or illness has been prescribed, or information indicating that a test to be performed for the set injury or illness has been ordered from the medical records, the candidate identification function 551 sets the corresponding patient as a follow-up candidate.

[0029] The first abnormality detection function 552 detects abnormalities from the first test results for a follow-up candidate patient. The first abnormality detection function 552 is an example of a first detection unit. Here, the first test is a test on the patient. For example, the first test may be a clinical test or an image diagnosis test. The first test result is the result of the first test. That is, the first test result may be clinical test result information 42, which is the test result of the clinical test, clinical test report information 43, which has findings from the test result of the clinical test, image information 31 captured by a medical image diagnostic device, radiology report information 22, which has findings on the image information 31, or other information.

[0030] That is, the first abnormality detection function 552 detects abnormalities from the first test results, such as the clinical test result information 42, the clinical test report information 43, the image information 31, and the radiology report information 22. An abnormality is an injury or illness, or the possibility of a set injury or illness. For example, the first abnormality detection function 552 detects abnormal shadows, abnormal values ​​in the test results, or text indicating an injury or illness from the first test results. The first abnormality detection function 552 may also detect abnormalities from first test results for a follow-up candidate patient that do not have a log indicating that the first test results have been viewed. This is because if the first test results have already been viewed by a medical professional such as a doctor, there is little point in the first abnormality detection function 552 detecting an abnormality again.

[0031] The second abnormality detection function 553 detects abnormalities from second test results that were generated earlier than the first test results for the follow-up candidate patient. The second abnormality detection function 553 is an example of a second detection unit. That is, the second abnormality detection function 553 detects abnormalities from second test results that indicate the test results of a second test that was performed earlier than the first test.

[0032] The second test is an examination performed on a patient. For example, the second test may be a clinical test or an examination using diagnostic imaging. The second test result is the result of the second test. That is, the second test result may be clinical test result information 42, which is the test result of the clinical test, clinical test report information 43, which contains findings from the test result of the clinical test, image information 31 captured by a medical image diagnostic device, radiology report information 22, which contains findings on the image information 31, or other information.

[0033] Here, if an abnormality is detected in the results of two tests conducted at different times, the notification server 50 sets the test as a follow-up target. Therefore, if the test contents or purposes of the two tests are different, there may be little point in detecting an abnormality in each test. For example, even if an abnormality is detected in the test results of a cancer test and an allergy test, there may be little correlation between them.

[0034] Therefore, the second test results may be limited to test results of the same type of test as the first test. For example, if the first test result is clinical test report information 43, the second abnormality detection function 553 may limit it to clinical test report information 43 for the second test result of a second test having the same test content as the first test. Alternatively, the second test results may be limited to test results of a test having the same purpose as the first test. For example, if the first test is a test for a specific disease, the second abnormality detection function 553 may limit the second test results to test results for the same disease as the first test. In other words, when the test content and test purpose of the second test are set, the second abnormality detection function 553 detects abnormalities from the second test results having the test content and test purpose identified by the first test result.

[0035] When an abnormality is detected in a patient from the second test results, the exclusion determination function 554 determines whether to exclude the patient from the follow-up candidate list based on the patient's medical record. The exclusion determination function 554 is an example of a first determination unit. More specifically, the exclusion determination function 554 determines to exclude a patient from the follow-up candidate list if the medical record, such as the electronic medical record information 12, contains abnormality cancellation information indicating that the abnormality should be canceled. The abnormality cancellation information is information that cancels the abnormality detected by the second abnormality detection function 553. For example, the abnormality cancellation information is a sentence or a numerical value that indicates a diagnostic result that determines that the abnormality is not a problem.

[0036] A specific example will be given. For example, the abnormality cancellation information is a diagnosis of a sequela with little chance of improvement. If the sequela with little chance of improvement continues for a certain period of time, the condition becomes normal and no longer corresponds to an abnormality. Also, if the sequela has little chance of improvement, the patient may not need to visit the hospital again. In such a case, the exclusion determination function 554 determines that the patient in question should be excluded from follow-up candidates, since there is no need to continuously check whether medical treatment is being provided.

[0037] Alternatively, the abnormality cancellation information may be a false positive diagnosis. For example, abnormal shadows may be observed in cases of dense breast tissue, but they are not breast cancer. In such cases, the patient does not need treatment and does not need to visit the hospital. Therefore, the exclusion determination function 554 determines to exclude from follow-up candidates patients whose medical records, such as the electronic medical record information 12, contain abnormality cancellation information indicating a false positive.

[0038] Alternatively, the abnormal cancellation information is information indicating that treatment has ended. For example, information indicating that treatment has ended may include a sentence indicating that treatment has ended, information indicating that a certain period of time has passed since the last medical record, information indicating that no medication was prescribed in the last medical consultation, or information indicating that the last medical record only included instructions to improve lifestyle habits. If treatment has ended, the patient does not need to visit the hospital. Therefore, the exclusion determination function 554 determines to exclude from follow-up candidates patients whose medical records include abnormal cancellation information indicating that treatment has ended.

[0039] The follow-up target setting function 556 sets, as a follow-up target, a patient who has not been excluded from the follow-up candidates by the exclusion determination function 554. The follow-up target setting function 556 is an example of a setting unit. In other words, the follow-up target setting function 556 sets, as a follow-up target, a follow-up candidate patient in which an abnormality has been detected by the first abnormality detection function 552 and the second abnormality detection function 553.

[0040] The schedule acquisition function 555 acquires the medical treatment schedule of the patient to be followed up. The schedule acquisition function 555 is an example of an acquisition unit. More specifically, the schedule acquisition function 555 acquires, for example, the medical treatment schedule included in the schedule information 11. For example, the medical treatment schedule is information indicating the scheduled date of the next hospital visit of the patient to be followed up. Or, the medical treatment schedule is information indicating the scheduled date when the medication prescribed to the patient to be followed up will run out.

[0041] Here, although the patient to be followed up needs to visit the hospital regularly, if they do not, there is a high possibility that their condition will worsen. Furthermore, if the patient to be followed up runs out of their prescribed medication and stops taking it without receiving a diagnosis, there is a high possibility that their condition will worsen. Therefore, the patient to be followed up will schedule a diagnosis when the date on which their prescribed medication is due to run out is approaching. Therefore, the schedule acquisition function 555 acquires the medical treatment schedule of the patient to be followed up.

[0042] The notification function 557 executes a notification according to the patient's condition. More specifically, the notification function 557 notifies the patient to be followed, who is set by the follow-up target setting function 556, that an appointment for medical treatment is to be made. The notification function 557 is an example of a notification unit.

[0043] The notification function 557 determines whether the patient to be followed has made an appointment for medical treatment based on the medical treatment schedule acquired by the schedule acquisition function 555. The notification function 557 is an example of a second determination unit. Then, the notification function 557 notifies the patient to make an appointment for medical treatment based on the determination result of whether the patient has made an appointment for medical treatment. For example, the notification function 557 notifies the patient to make an appointment for medical treatment if the patient to be followed has not made an appointment for medical treatment based on the determination result of whether the patient has made an appointment for medical treatment. In other words, the notification function 557 notifies the patient to make an appointment for medical treatment if there is no appointment for medical treatment within a certain period in the medical treatment schedule of the patient to be followed acquired by the schedule acquisition function 555. Here, the certain period may be a period set commonly for multiple people, a period set for each patient, or a period set according to the patient's condition.

[0044] Furthermore, based on the determination result of whether a medical appointment has been made, the notification function 557 notifies a patient to make a medical appointment if the patient being followed up and whose remaining prescribed medication is estimated to be below a threshold has not made a medical appointment. Here, a doctor or other medical professional prescribes medication along with the duration for which the medication will be taken. Therefore, the notification function 557 can estimate the remaining amount of prescribed medication based on the duration for which the medication will be taken and the current date and time. Therefore, the notification function 557 notifies a patient to make a medical appointment if the remaining prescribed medication is estimated to be below a threshold.

[0045] Specifically, when issuing a notification to a patient, the notification function 557 extracts the notification destination of the patient to be followed from the notification destination information 541. Then, the notification function 557 notifies the extracted notification destination to make an appointment for medical treatment.

[0046] Furthermore, if a patient being followed has an appointment, the notification function 557 notifies the patient of the appointment date and time. This allows the notification function 557 to remind the patient of the appointment date and time. In other words, it is possible to prevent the patient from forgetting to make an appointment.

[0047] In addition, the notification function 557 may notify content according to the situation, not limited to the patient being followed, when no behavioral history indicating that behavior according to the situation has been performed is stored.

[0048] For example, if an abnormality is detected from the first test result and the second test result, the notification function 557 notifies the doctor who ordered the first test for the patient set as the follow-up target by the follow-up target setting function 556 that an abnormality has been detected from the first test result and the second test result. Specifically, the notification function 557 extracts information that can identify the doctor who ordered the first test from the imaging order information 21 or the clinical test order information 41 that ordered the first test. The notification function 557 also extracts the notification destination of the doctor identified by the extracted information from the notification destination information 541. Then, the notification function 557 notifies the extracted notification destination that an abnormality has been detected from the first test result and the second test result.

[0049] The notification function 557 notifies the user to check the first test results when no abnormality is detected in the first test results or when an abnormality detected in the first test results is canceled. Specifically, the notification function 557 extracts information that can identify the doctor who ordered the first test from the imaging order information 21 or clinical test order information 41 that ordered the first test. The notification function 557 also extracts the notification destination of the doctor identified by the extracted information from the notification destination information 541. The notification function 557 then notifies the extracted notification destination to check the first test results.

[0050] When an abnormality is detected in the test results, the notification function 557 checks whether an abnormality is also detected in the test results of another test to confirm whether the test result is valid. When an abnormality is detected in the first test results, if there are no second test results and no order has been placed, the notification function 557 notifies that an test should be ordered. Specifically, the notification function 557 extracts information that can identify the physician who ordered the first test from the imaging order information 21 or clinical test order information 41 that ordered the first test. The notification function 557 also extracts the notification destination of the physician identified by the extracted information from the notification destination information 541. The notification function 557 then notifies the extracted notification destination that an order should be placed.

[0051] If an abnormality is detected in the first test results, there are no second test results, but an order for a test has been issued, the notification function 557 notifies the patient to explain the test results. Specifically, the notification function 557 determines whether the test results of the issued order have been explained to the patient. That is, the notification function 557 determines whether an action history indicating that the patient has been explained is recorded. If the test results have not been explained to the patient, the notification function 557 extracts information that can identify the doctor who ordered the test from the imaging order information 21 or clinical test order information 41. The notification function 557 also extracts the notification destination of the doctor identified by the extracted information from the notification destination information 541. The notification function 557 then notifies the extracted notification destination to explain the test results to the patient. This prevents the notification server 50 from leaving the patient without taking any action, such as explaining the test results, after the test. Therefore, the notification server 50 can prevent the patient's condition from worsening due to the patient not taking any action, such as explaining the test results, after the test.

[0052] Next, various processes executed by the notification server 50 will be described.

[0053] 3 is a flowchart showing an example of a test result notification process executed by the notification server 50 according to this embodiment. The test result notification process notifies the patient of the test results and sets the patient to be followed up.

[0054] The candidate identification function 551 determines whether or not a certain period of time has passed since the previous process (step S11). If the certain period of time has not passed (step S11; No), the candidate identification function 551 waits.

[0055] When a certain period of time has passed (Step S11; Yes), the candidate identification function 551 identifies follow-up candidates who are candidates for patients to be followed (Step S12). That is, the candidate identification function 551 identifies patients with a specific injury or illness or patients at risk of a specific injury or illness as follow-up candidates.

[0056] The first abnormality detection function 552 determines whether or not the first test results for the follow-up candidate patient include an abnormality (step S13). If the first test results do not include an abnormality (step S13; Yes), the notification function 557 notifies the medical professional, such as the doctor who ordered the first test, that the first test results should be checked (step S14). That is, the notification function 557 notifies the medical professional's email address, SNS account, etc., based on the notification destination information 541, that the first test results should be checked.

[0057] If the first test result contains an abnormality (step S13; No), the second abnormality detection function 553 determines whether the second test result for the same patient as the first test result is stored (step S15).

[0058] If the second test result is stored (step S15; Yes), the second abnormality detection function 553 determines whether or not the second test result contains an abnormality (step S16).

[0059] If the second test result does not contain an abnormality (step S16; Yes), the notification function 557 proceeds to step S14. For example, the notification function 557 notifies that an abnormality was detected in the first test result but not in the second test result, and therefore the first test result should be checked.

[0060] If the second test results contain an abnormality (step S16; No), the exclusion determination function 554 determines whether the medical records, such as the electronic medical record information 12, of the follow-up candidate patient in whom the abnormality was detected contain abnormality cancellation information to cancel the patient (step S17).

[0061] If the abnormality cancellation information is included (step S17; Yes), the notification function 557 proceeds to step S14. For example, the notification function 557 detects an abnormality from the first test result and the second test result, but notifies that the first test result should be checked because the abnormality cancellation information is included.

[0062] If the abnormality cancellation information is not included (step S17; No), the notification function 557 notifies that an abnormality has been detected from the first test result and the second test result. That is, the notification function 557 notifies the medical professional of the abnormality detection to the medical professional's email address, SNS account, etc. (step S18).

[0063] The follow-up target setting function 556 sets the follow-up candidate patient in whom abnormalities are detected from the first test result and the second test result as a follow-up target (step S19).

[0064] If the second test result is not stored in step S15 (step S15; No), the notification function 557 determines whether an order for a test has been placed (step S20). That is, the notification function 557 determines whether the clinical test order information 41 and the imaging order information 21 are stored.

[0065] If an order for the test has not been issued (step S20; No), the notification function 557 notifies the medical professional, such as the doctor who ordered the first test, that an order for the test will be placed (step S23).

[0066] If an order for a test has been issued (step S20; Yes), the notification function 557 determines whether the test results of the test performed in response to the issued order have been explained to the patient (step S21). That is, the notification function 557 determines whether an action history indicating that the test results have been explained to the patient is stored. If the test results have been explained to the patient (step S21; Yes), the notification server 50 ends the process.

[0067] If the test results have not been explained to the patient (step S21; No), the notification function 557 notifies the medical professional, such as the doctor who issued the test order, that the test results should be explained to the patient (step S22).

[0068] With the above, the notification server 50 ends the test result notification process.

[0069] 4 is a flowchart showing an example of reservation notification processing executed by the notification server 50 according to this embodiment. The reservation notification processing is processing for notifying a patient to be followed when the patient has not yet made a medical appointment.

[0070] The schedule acquisition function 555 acquires the medical treatment schedule from the electronic medical record information 12 of the patient to be followed up (step S31).

[0071] The notification function 557 determines whether or not there is no medical treatment scheduled (step S32). That is, the notification function 557 determines whether or not the patient to be followed is visiting a hospital. For example, the notification function 557 determines whether or not there is no medical treatment scheduled within a certain period of time since the last medical treatment.

[0072] If there is no medical appointment scheduled (step S32; Yes), the notification function 557 notifies the patient to be followed to obtain a medical appointment schedule (step S33). That is, the notification function 557 notifies the patient to obtain a medical appointment schedule via an email address, an SNS account, or the like of the patient based on the notification destination information 541.

[0073] If a medical appointment is scheduled (step S32; No), the notification function 557 determines whether the current date and time is before the medical appointment date (step S34). If it is before the medical appointment date (step S34; Yes), the notification function 557 notifies the patient being followed of the scheduled medical appointment date (step S35).

[0074] If it is after the appointment date for medical treatment (step S34; No), the notification function 557 notifies the patient to be followed up to obtain a medical treatment schedule (step S36).

[0075] With the above, the notification server 50 ends the reservation notification process.

[0076] 5 is a flowchart showing an example of a drug notification process executed by the notification server 50 according to this embodiment. The drug notification process is a process for notifying a patient when the remaining amount of a drug prescribed to the patient being followed is estimated to be equal to or less than a threshold.

[0077] The notification function 557 determines whether the remaining amount of the prescribed drug is estimated to be equal to or less than a threshold based on the electronic medical record information 12 of the patient to be followed (step S41). In other words, the notification function 557 determines whether the remaining period until the end of the period for which the drug was prescribed is equal to or less than a threshold. If the remaining amount of the drug is estimated to be greater than the threshold (step S41; No), the notification function 557 waits.

[0078] If it is estimated that the remaining amount of medicine is less than the threshold (Step S41; Yes), the schedule acquisition function 555 acquires the medical treatment schedule from the electronic medical record information 12 of the patient to be followed up (Step S42).

[0079] The notification function 557 determines whether or not there is no medical treatment scheduled (step S43). That is, the notification function 557 determines whether or not there is no medical treatment scheduled until the last day of the period for which the medicine is prescribed.

[0080] If there is no medical appointment scheduled (step S43; Yes), the notification function 557 notifies the patient to be followed to obtain a medical appointment schedule in order to receive a drug prescription (step S44). That is, the notification function 557 notifies the patient to obtain a medical appointment schedule via an email address, an SNS account, or the like based on the notification destination information 541.

[0081] If a medical appointment is scheduled (step S43; No), the notification function 557 determines whether the current date and time is before the medical appointment date (step S45). If it is before the medical appointment date (step S45; Yes), the notification function 557 notifies the patient being followed of the scheduled medical appointment date (step S46).

[0082] If it is after the scheduled medical appointment date (step S45; No), the notification function 557 notifies the patient to acquire a medical appointment schedule in order to receive a prescription for medicine (step S47).

[0083] With the above, the notification server 50 ends the medication notification process.

[0084] As described above, the notification server 50 according to this embodiment identifies patients who are candidates for follow-up. The notification server 50 detects abnormalities from the first and second test results of the patient who is a candidate for follow-up. The notification server 50 also determines whether to exclude a patient in whom an abnormality has been detected from the list of candidates for follow-up, based on whether information for canceling the abnormality is included in the patient's medical records, such as the electronic medical record information 12. The notification server 50 then sets patients who have not been excluded from the list of candidates for follow-up as patients to be followed. In this way, the notification server 50 excludes patients whose medical records, such as the electronic medical record information 12, record abnormality cancellation information from the list of patients to be followed, thereby enabling the notification server 50 to identify patients to be followed.

[0085] In this way, the notification server 50 notifies the patient being followed to obtain a medical appointment schedule if the patient does not have a medical appointment scheduled. This allows the patient to receive medical treatment as appropriate. Therefore, medical professionals such as doctors can use the time of the medical treatment to explain test results, schedule subsequent tests, and prescribe medications. As a result, patients are less likely to be left untreated. Therefore, the notification server 50 can prevent the patient's condition from worsening.

[0086] (Variation) In this embodiment, the exclusion determination function 554 has been described as excluding patients whose medical records, such as the electronic medical chart information 12, contain abnormality cancellation information from the follow-up candidates. However, when the medical records contain abnormality cancellation information, the exclusion determination function 554 may determine that a patient who was excluded from the follow-up candidates is a follow-up candidate if a set condition is met. For example, the set condition may be that a set period has elapsed since the abnormality cancellation information was recorded in the medical record, or that an abnormality has been detected in the test results.

[0087] For example, if a set period has passed since the abnormality cancellation information was recorded in the medical record, the exclusion determination function 554 determines that the abnormality cancellation information is invalid. That is, the exclusion determination function 554 determines that the patient is a follow-up candidate. If the set period has passed, the patient may have newly developed an illness. Therefore, the exclusion determination function 554 determines that the abnormality cancellation information is invalid.

[0088] Furthermore, the exclusion determination function 554 determines that the abnormality cancellation information is invalid if the number of times an abnormality is detected in the test results is equal to or greater than the threshold number. In other words, the exclusion determination function 554 determines that the patient is a follow-up candidate. If the number of times an abnormality is detected is equal to or greater than the threshold number, the patient is likely to be suffering from some kind of disease. Therefore, the exclusion determination function 554 determines that the abnormality cancellation information is invalid.

[0089] In this way, the exclusion determination function 554 determines that the abnormality cancellation information is invalid when the set conditions are met, and sets the patient as a follow-up target. In other words, a patient is set as a follow-up target when there is room for doubt about the abnormality cancellation information. Then, the patient set as a follow-up target is notified to obtain a medical treatment schedule. Therefore, since the patient receives medical treatment, the exclusion determination function 554 can prevent the patient's injury or illness from being overlooked.

[0090] According to at least one of the embodiments described above, it is possible to identify patients to be followed up.

[0091] Although several embodiments have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, and combinations of embodiments can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0092] 1. Notification System 10 Hospital Information System (HIS) 11 Schedule Information 12 Electronic medical record information 20 Radiology Information Systems (RIS) 21 Imaging order information 22 Image interpretation report information 30 Medical Image Management Systems (PACS: Picture Archiving and Communication Systems) 31 Image information 40 Laboratory Information System (LIS) 41 Clinical Test Order Information 42 Clinical test result information 43 Clinical Test Report Information 50 Notification Server 541 Notification Information 550 Processing Circuit 551 Candidate Identification Function 552 First abnormality detection function 553 Second abnormality detection function 554 Exclusion Judgment Function 555 Schedule Acquisition Function 556 Follow target setting function 557 Notification function

Claims

1. an identification unit that identifies follow-up candidates who are candidates for patients to be followed; a first detection unit that detects abnormalities from a first test result of the follow-up candidate patient; a second detection unit that detects abnormalities from second test results generated earlier than the first test results for the follow-up candidate patient; a first determination unit that, when an abnormality is detected from the first test result and the second test result, determines whether or not to exclude the patient from the follow-up candidate based on a medical record of the patient of the follow-up candidate; a setting unit that sets the patient who has not been excluded from the follow-up candidates by the first determination unit as a follow-up target; A medical information processing device comprising:

2. The first determination unit determines to exclude the patient whose medical record includes abnormality cancellation information indicating that the abnormality is canceled from the follow-up candidate. The medical information processing device according to claim 1 .

3. The first determination unit determines to exclude the patient whose medical record includes the abnormality cancellation information indicating a false positive from the follow-up candidate. The medical information processing device according to claim 2 .

4. The first determination unit determines to exclude the patient whose medical record includes the abnormality cancellation information indicating that treatment has ended from the follow-up candidate. The medical information processing device according to claim 2 .

5. When the abnormality cancellation information is included in the medical record, the first determination unit determines that the patient who was excluded from the follow-up candidates is the follow-up candidate on condition that a set condition is satisfied. The medical information processing device according to claim 2 .

6. the identification unit identifies, as the follow-up candidate, the patient in the medical record that includes information indicating a diagnosis result that the patient has the set injury or illness or is at risk of the set injury or illness; The medical information processing device according to any one of claims 1 to 5.

7. The system further includes a notification unit that notifies the patient to be followed that an appointment for medical treatment has been made, the notification unit being configured to notify the patient to be followed by the patient. The medical information processing device according to any one of claims 1 to 6.

8. an acquisition unit that acquires a medical treatment schedule of the patient to be followed; a second determination unit that determines whether the patient to be followed up has made an appointment for medical treatment based on the medical treatment schedule, the notification unit notifies the user to make an appointment for medical treatment based on a determination result as to whether or not the user has made an appointment for medical treatment. The medical information processing device according to claim 7 .

9. the notification unit notifies the patient to make an appointment for medical treatment if the patient to be followed up has not made an appointment for medical treatment based on a determination result as to whether or not the patient has made an appointment for medical treatment. The medical information processing device according to claim 8 .

10. the notification unit notifies the patient to make an appointment for medical treatment when the patient to be followed up, whose remaining amount of prescribed medicine is estimated to be equal to or less than a threshold, has not made an appointment for medical treatment based on the determination result of whether or not an appointment for medical treatment has been made; The medical information processing device according to claim 8 .

Citation Information

Patent Citations

  • Accurate follow-up visit system and method based on patient individual disease condition database

    CN107066792A

  • Disease control program and disease control system

    JP2015018466A

  • Medical image processing device, image formation method and image formation program

    JP2020018705A

  • Information management device, information management system, and information management program

    JP2021056958A

  • Automatic Generation of User and Non-User Cohorts for The Estimation of Drug's Effect from Longitudinal Observational Data

    US20200005907A1