Ophthalmological medical data processing program and ophthalmological medical data processing device

Abstract

To provide an ophthalmic medical data processing program and an ophthalmic medical data processing device capable of storing medical data by being appropriately associated with a patient.SOLUTION: A control part preliminarily identifies a patient of an object of acquiring medical data, and stores a patient identification log showing a date / time of identifying the patient and the identified patient in a storage device. The control part stores the medical data acquired in a state with the patient identified in advance in association with the identified patient in the storage device. The control part acquires information showing the date / time when data is acquired about unprocessed data which has not undergone storage processing associated with the patient yet in the acquired medical data. The control part identifies the patient identified when the unprocessed data is acquired as a patient of an object of acquiring the unprocessed data in an ex-post manner. The control part stores the unprocessed data in association with the patient identified in an ex-post manner in the storage device.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present disclosure relates to an ophthalmological medical data processing program and an ophthalmological medical data processing device for processing ophthalmological medical data. [Background technology]

[0002] Various techniques have been proposed for presenting data useful for medical treatment to a user (e.g., a doctor or an assistant). For example, the device described in Patent Document 1 stores OCT data obtained by an imaging device in association with the patient from whom the data was obtained. The user observes the progress of the lesion from changes in the multiple OCT data stored in association with the patient. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-104535 A Summary of the Invention [Problem to be solved by the invention]

[0004] A method for storing acquired medical data by linking it to a patient from whom the medical data is acquired is considered. For example, when a patient from whom the medical data is acquired is specified in advance and medical data of the specified patient is generated, the generated medical data is usually considered to be appropriately linked to the patient. However, when an abnormality occurs in the ophthalmology medical data processing device or the operating environment of the device, the generated medical data may not be linked to the patient even if the patient is specified in advance. In this case, the user needs to identify the patient from whom the medical data is acquired and link it to the medical data. In addition, if there is no information for identifying the patient, the medical data may have to be discarded without identifying the patient. Therefore, a technology is desired for appropriately linking medical data to the patient and storing it even if some abnormality occurs.

[0005] A typical object of the present disclosure is to provide an ophthalmology medical data processing program and an ophthalmology medical data processing device that are capable of appropriately linking medical data to patients and storing the medical data. [Means for solving the problem]

[0006] An ophthalmology medical data processing program provided by a typical embodiment of the present disclosure is an ophthalmology medical data processing program executed in an ophthalmology medical data processing device that processes medical data indicating at least one of the results of ophthalmological examination, photography, and examination performed on a patient, and the ophthalmology medical data processing program is executed by a control unit of the ophthalmology medical data processing device, thereby performing a pre-identification step of identifying a patient from whom medical data is to be acquired in advance, a log storage step of storing in a storage device a patient identification log that is a log indicating the date and time when the patient was identified in the pre-identification step and the identified patient, a medical data acquisition step of acquiring medical data, and a medical data acquisition step of acquiring medical data acquired in a state where the patient has been identified in advance in the pre-identification step. The ophthalmology medical data processing device executes a normal storage step of linking the medical data acquired in the medical data acquisition step to the identified patient and storing it in the storage device, a post-identification step of identifying a patient as a target for acquiring unprocessed data, which is medical data acquired in the medical data acquisition step that has not yet been subjected to storage processing linked to a patient, and a post-identification step of linking the unprocessed data to the patient identified in the post-identification step and storing it in the storage device, in which in the post-identification step, information indicating the date and time when the unprocessed data was acquired is acquired, and based on the patient identification log, the patient identified in the pre-identification step at the time when the unprocessed data was acquired is identified as the patient as a target for acquiring the unprocessed data.

[0007] An ophthalmology medical data processing device provided by a typical embodiment of the present disclosure is an ophthalmology medical data processing device that processes medical data indicating at least any one of the results of ophthalmological examination, photography, and examination performed on a patient, and a control unit of the ophthalmology medical data processing device performs a pre-identification step of identifying a patient from whom medical data is to be acquired in advance, a log storage step of storing in a storage device a patient identification log that is a log indicating the date and time when the patient was identified in the pre-identification step and the identified patient, a medical data acquisition step of acquiring medical data, and linking the medical data acquired in the pre-identification step when the patient has been identified in advance to the identified patient. The method executes a normal storage step of storing the unprocessed data in the storage device while linking the unprocessed data to the patient, a post-identification step of identifying a patient from among the medical data acquired in the medical data acquisition step, the patient being a target of unprocessed data, which is medical data that has not yet been subjected to storage processing linked to a patient, and a post-identification step of storing the unprocessed data in the storage device while linking the unprocessed data to the patient identified in the post-identification step.In the post-identification step, information indicating the date and time when the unprocessed data was acquired is acquired, and based on the patient identification log, the patient who was identified in the pre-identification step at the time when the unprocessed data was acquired is identified as the patient from which the unprocessed data is to be acquired.

[0008] According to the ophthalmological medical data processing program and the ophthalmological medical data processing device according to the present disclosure, medical data is appropriately linked to a patient and stored. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a schematic configuration of an ophthalmological medical data processing system 1. FIG. [Diagram 2] 4 is a flowchart of a normal storage process executed by the ophthalmological medical data processing device 10. [Diagram 3] FIG. 2 is a diagram showing an example of a patient information display screen 30. [Figure 4] FIG. 13 is a diagram illustrating a data configuration of a patient identification log. [Diagram 5]13 is a flowchart of a post-storage process executed by the ophthalmological medical data processing apparatus 10. [Figure 6] FIG. 13 is a diagram showing an example of a specific result confirmation screen 40. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] <Summary> The ophthalmology medical data processing device exemplified in the present disclosure processes medical data indicating the results of at least one of ophthalmology examinations, photography, and consultations performed on a patient. The control unit of the ophthalmology medical data processing device executes a pre-identification step, a log storage step, a medical data acquisition step, a normal storage step, a post-identification step, and a post-storage step.

[0011] In the pre-identification step, the control unit pre-identifies a patient from whom medical data is to be acquired. In the log storage step, the control unit stores in the storage device a patient identification log, which is a log showing the date and time when the patient was identified in the pre-identification step and the identified patient. In the medical data acquisition step, the control unit acquires medical data. In the normal storage step, the control unit stores in the storage device medical data acquired in a state in which the patient was identified in advance in the pre-identification step, linked to the identified patient. In the post-identification step, the control unit acquires information showing the date and time when the data was acquired for unprocessed data that has not yet been subjected to storage processing linked to the patient among the medical data acquired in the medical data acquisition step. The control unit post-identifies the patient identified in the pre-identification step at the time when the unprocessed data was acquired as the patient from whom the unprocessed data is to be acquired. In the post-identification step, the control unit stores in the storage device the unprocessed data linked to the patient identified in the post-identification step.

[0012] According to the technology disclosed herein, even if the medical data cannot be linked to a patient due to some abnormality, the patient who was identified at the time the medical data was acquired can be identified later based on the date and time information indicated by the patient identification log and the information indicating the date and time when the medical data was acquired. Therefore, the medical data is appropriately linked to the patient and stored.

[0013] In addition, the date and time information in the present disclosure is not limited to information indicating a date and time, as long as it is information that can identify the time before and after the date and time. For example, information indicating the elapsed time from a specific timing may be used as the date and time information.

[0014] A specific method for identifying a patient from whom medical data is to be acquired in advance may be appropriately selected. For example, in the advance identification step, the control unit may input an instruction from a user to identify a patient via an operation unit or the like, and identify the patient in advance according to the input instruction. The control unit may also identify the patient in advance by reading an identifier (such as a barcode) for identifying the patient.

[0015] A specific method for storing medical data in association with a patient can also be selected as appropriate. For example, the control unit may link the medical data to a patient by including information for identifying the patient (e.g., a patient ID, etc.) in the data name when storing the medical data. In addition, the control unit may link the medical data to a patient by saving the medical data in a folder for a specified patient among multiple folders provided for each patient.

[0016] In the medical data acquisition step, the control unit may acquire medical data from an ophthalmic device that performs at least one of the examination and photography of the subject's eye. In the post-identification step, the control unit may identify a patient from whom the unprocessed data is to be acquired based on information on the date and time when the unprocessed data was generated in the ophthalmic device. For example, it is also possible to identify a patient from whom the unprocessed data is to be acquired based on the date and time when the ophthalmic medical data processing device acquired the unprocessed data from the ophthalmic device. However, if a discrepancy occurs between the date and time when the ophthalmic device generated the unprocessed data and the date and time when the ophthalmic medical data processing device acquired the unprocessed data from the ophthalmic device due to a network malfunction or the like, it may not be possible to accurately identify a patient from whom the unprocessed data is to be acquired. In contrast, by referring to information on the date and time when the ophthalmic device generated the unprocessed data, a patient from whom the unprocessed data is to be acquired is more accurately identified.

[0017] However, in the post-identification step, the patient from whom the unprocessed data is to be acquired may be identified based on information on the date and time when the ophthalmic medical data processing device acquires the unprocessed data from the ophthalmic device. In this case, even if a procedure is adopted in which the patient from whom the medical data is to be acquired is identified after the medical data is generated in advance by the ophthalmic device, the patient from whom the medical data is to be acquired can be identified post-identification. In addition, the medical data is not limited to the examination data or image data generated by the ophthalmic device. For example, the medical data may be a patient's chart data, etc., created in response to an instruction input by a user.

[0018] The control unit may execute a determination result notifying step of notifying a user of the result identified by the patient for which the unprocessed data is to be acquired in the post-identification step. In the post-storing step, when a signal indicating that the notified result has been confirmed is input by the user, the unprocessed data may be stored in association with the identified patient. In this case, the possibility that the unprocessed data is associated with a wrong patient is appropriately suppressed.

[0019] When there are a plurality of unprocessed data, the control unit may notify the user of the results of the patient identification in the post-identification step for each of the plurality of unprocessed data collectively. In this case, the user can efficiently check the patient identification results for the plurality of unprocessed data.

[0020] The control unit may further execute a confirmation step. In the confirmation step, when the unprocessed data is image data and image data previously associated with a patient identified based on the patient identification log exists, the control unit confirms the patient identification result based on the patient identification log based on the comparison result between the unprocessed data and past image data of the patient identified based on the patient identification log. In this case, the accuracy of the patient identification result performed based on the patient identification log is appropriately confirmed based on the comparison result with the image data previously stored. Thus, the patient from which the unprocessed data is to be obtained is more accurately identified.

[0021] The specific method of the confirmation step may be appropriately selected. For example, the control unit may acquire the similarity between the unprocessed data and the past image data by known image processing or a mathematical model trained according to a machine learning algorithm. The control unit may confirm whether the patient identification result based on the patient identification log is accurate or not depending on whether the acquired similarity is equal to or greater than a threshold. The control unit may also display both the unprocessed data and the past image data on the display unit. The control unit may confirm whether the patient identification result based on the patient identification log is accurate or not depending on whether an instruction indicating that the subjects of the unprocessed data and the past image data are the same is input by the user.

[0022] In the pre-identification step, the control unit may identify in advance whether the eye from which the medical data is to be acquired is the left or right eye, together with the patient from which the medical data is to be acquired. In the post-identification step, the control unit may acquire information indicating whether the unprocessed data is data for the left or right eye. The control unit may identify the patient from which the unprocessed data is to be acquired from among the multiple patients whose left and right information identified in the pre-identification step matches the left and right information for the unprocessed data. In this case, the accuracy of identifying the patient is further improved by referring to the information on the left and right eyes.

[0023] <Embodiment> Hereinafter, one typical embodiment of the present disclosure will be described with reference to the drawings. First, an example of a system configuration of an ophthalmological medical data processing system 1 in this embodiment will be outlined with reference to Fig. 1. The ophthalmological medical data processing system 1 of this embodiment includes an ophthalmological medical data processing device 10 and an ophthalmological device 20.

[0024] The ophthalmological medical data processing device 10 processes various medical data. In this embodiment, a personal computer (hereinafter, referred to as "PC") installed in a medical institution is used as the ophthalmological medical data processing device 10. However, the ophthalmological medical data processing device 10 is not limited to a PC. For example, a smartphone or a tablet terminal may be used as the ophthalmological medical data processing device 10. A server may be used as the ophthalmological medical data processing device 10 separately from or together with the PC. In this case, the server may be, for example, a server of a manufacturer that provides a cloud service (a so-called cloud server), or a server other than a cloud server (for example, a server of a manufacturer that provides an ophthalmological medical data processing program, etc.). A plurality of terminals may work together to function as the ophthalmological medical data processing device 10. For example, a scanner that captures an image and a PC connected to the scanner may work together to function as the ophthalmological medical data processing device 10.

[0025] The ophthalmological medical data processing device 10 includes a control unit 11 that performs various control processes, and a communication I / F 14. The control unit 11 includes a CPU 12 that is a controller responsible for control, and a storage device 13 that can store programs, data, and the like. The communication I / F 14 connects the ophthalmological medical data processing device 10 to external devices (e.g., an ophthalmological device 20, etc.) via a network 5. The ophthalmological medical data processing device 10 is also connected to an operation unit 16 and a display unit 17.

[0026] The storage device 13 stores an ophthalmology data processing program for executing at least a part of the ophthalmology data processing (see FIG. 2 and FIG. 5) described later. The storage device 13 also stores medical data linked to the patient. The medical data in this embodiment is data indicating at least one of ophthalmology examination, photography, and examination performed on the patient. As an example, in this embodiment, image data of the subject's eye photographed by the ophthalmology device (ophthalmology photography device) 20 (for example, at least one image data such as an OCT image, an SLO image, a fundus camera image, and a corneal endothelial cell photography image), examination data indicating the examination result of the subject's eye performed by the ophthalmology device (ophthalmology examination device) 20 (for example, at least one examination data such as an axial length, an eye refractive power, and an intraocular pressure), image data captured via a scanner connected to the ophthalmology data processing device 10, and patient chart data created by the user operating the operation unit 16 are processed as medical data.

[0027] In this embodiment, the case where medical data is stored in the storage device 13 built in the ophthalmological medical data processing device 10 is exemplified. However, the storage device in which the medical data is stored may be provided outside the ophthalmological medical data processing device 10. For example, the medical data may be stored in a server (including a cloud server) or an external hard disk. In this case, the ophthalmological medical data processing device 10 and the storage device may be connected by wireless communication (including a network such as the Internet) or wired communication.

[0028] The ophthalmic device 20 performs at least one of photographing and examining the subject's eye. For example, at least one of an OCT device, a scanning laser ophthalmoscope (SLO), a fundus camera, a corneal endothelial cell photographing device, an axial length measuring device, an eye refractive power measuring device, an intraocular pressure measuring device, and the like can be used as the ophthalmic device 20. The ophthalmic device 20 includes a control unit 21 that performs various control processes, and a communication I / F 24. The control unit 21 includes a CPU 22 that is a controller that manages control, and a storage device 23 that can store programs, data, and the like. The ophthalmic device 20 also includes an operation unit 26, a display unit 27, and a drive unit 28. The drive unit 28 includes various components necessary for the ophthalmic device 20 to perform at least one of photographing and examining the patient.

[0029] An example of ophthalmological data processing executed by the ophthalmological data processing device 10 of this embodiment will be described with reference to Figs. 2 to 6. The ophthalmological data processing device 10 of this embodiment can execute normal storage processing (see Fig. 2) and post-storage processing (see Fig. 5). In the normal storage processing, the patient from whom medical data is to be acquired is specified in advance, and medical data of the specified patient is acquired. The acquired medical data is stored in association with the patient specified in advance. Here, if an abnormality occurs in the ophthalmological data processing device 10 or the operating environment of the device (for example, the network 5, etc.) while the normal storage processing is being executed, the acquired medical data may remain as unprocessed data without being associated with the patient. In the post-storage processing, unprocessed data that has not yet been subjected to storage processing associated with the patient is appropriately associated with the patient and stored.

[0030] As described above, the ophthalmic medical data processing device 10 of this embodiment can process, as medical data, image data of the subject's eye photographed by the ophthalmic device (ophthalmic imaging device) 20, examination data showing the examination results of the subject's eye performed by the ophthalmic device (ophthalmic examination device) 20, and patient chart data, etc. In the following description, a case in which image data of the fundus of the subject's eye photographed by the ophthalmic device 20 is processed as medical data will be exemplified. The normal storage process and the post-storage process are executed by the CPU 12 of the ophthalmic medical data processing device 10 according to the ophthalmic medical data processing program stored in the storage device 13.

[0031] The normal storage process will be described with reference to Figs. 2 to 4. The normal storage process is executed while the ophthalmological medical data processing device 10 is operating. First, the CPU 12 judges whether or not an instruction to identify a patient from which medical data is to be acquired has been input (S1). In this embodiment, the user can input an instruction to identify a patient to the ophthalmological medical data processing device 10 by operating the operation unit 16. In this case, the user may input an instruction to identify a patient by selecting a patient from a patient list in which a plurality of patients are listed, from which the medical data is to be acquired. The user may input the ID or name of the patient. Also, an identifier (e.g., a barcode, etc.) for identifying the patient may be given to each patient. In this case, the CPU 12 may input an instruction to identify the patient by inputting an identifier read by an identifier reader. In this embodiment, together with the instruction to identify the patient, an instruction to specify whether the eye to be the subject of medical care (examination, photography, diagnosis, treatment, etc.) is the left eye, the right eye, or both eyes is also input. However, the information indicating the target eye may be specified based on past information regarding the specified patient. If an instruction to identify a patient has not been input (S1: NO), the process of S1 is repeated and the system enters a standby state.

[0032] When an instruction to identify a patient is input (S1: YES), the CPU 12 preliminarily identifies a patient and a target eye from which medical data is to be acquired in accordance with the input instruction. The CPU 12 causes the display unit 17 to display a patient information display screen 30 (see FIG. 3) including information on the identified patient (S2).

[0033] In the patient information display screen 30 illustrated in FIG. 3, information on the patient name, sex, target eye, and last examination date and time of the identified patient is displayed. As described above, the information on the target eye indicates which of the patient's left and right eyes is the eye that is the target of medical treatment. The information on the last examination date and time indicates the date and time when the patient was last examined. In addition, the patient information display screen 30 of this embodiment is provided with a last captured image display field 31, an image data import button 32, and an end button 33. If there is image data previously captured for the patient identified in S2, the past image is displayed in the last captured image display field 31. The image data import button 32 is operated by the user when a new image of the patient's eye to be examined is captured and saved by the ophthalmologic device 20. The end button 33 is operated by the user when the treatment for the patient identified at that time is to be ended (for example, when changing the patient, etc.).

[0034] Next, the CPU 12 stores in the storage device 13 a patient identification log, which is a log about the patient identification process executed in S2 (S3). FIG. 4 shows an example of the data configuration of the patient identification log. In the example shown in FIG. 4, information on the identification date and time, information on the identified patient, and information on the target eye are stored as the patient identification log each time the pre-identification process (S2) is executed. The information on the identification date and time indicates the date and time when the patient was identified in the pre-identification process. The information on the identified patient indicates the patient identified in the pre-identification process. The information on the target eye indicates whether the eye that is the target of treatment is the left eye, the right eye, or both eyes of the identified patient.

[0035] Next, the CPU 12 judges whether or not the medical data has been acquired (S5). In this embodiment, the ophthalmic device 20 captures an image of the subject's eye to generate image data, which is a type of medical data. The ophthalmic device 20 transmits the generated image data to the ophthalmic medical data processing device 10 via the network 5. In this embodiment, the image data is captured from the ophthalmic device 20 by the user operating an image data capture button 32 (see FIG. 3). Here, in this embodiment, information indicating the date and time when the image data was generated (captured) by the ophthalmic device 20 is added to the image data. It is also possible to change the method by which the ophthalmic medical data processing device 10 acquires the medical data. For example, the ophthalmic medical data processing device 10 may acquire the medical data via a storage medium (such as a USB memory) that is detachable from the device. The medical data may be transmitted and received via wired communication or the like.

[0036] If medical data has not been acquired (S5: NO), the process proceeds directly to S7. If medical data has been acquired (S5: YES), the CPU 12 associates the acquired medical data with the patient identified in S2 and stores the medical data in the storage device 13 (S6). For example, the CPU 12 may associate the medical data with the patient by including information for identifying the patient (e.g., a patient ID, etc.) in the data name when storing the medical data. The CPU 12 may also associate the medical data with the patient by saving the medical data in a folder for the identified patient out of multiple folders provided for each patient.

[0037] Next, the CPU 12 judges whether or not to end the treatment for the identified patient (S7). If the end button 33 (see FIG. 3) has not been operated and the treatment is not to be ended, the process returns to S5, and the processes of S5 to S7 are repeated. If the end button 33 is operated (S7: NO), the process returns to S1. Thereafter, if a new instruction to identify a patient is input (S1: YES), the treatment for the next patient is performed.

[0038] The post-event storage process will be described with reference to Fig. 5 and Fig. 6. As described above, in the post-event storage process, when there is unprocessed data for which storage process linked to a patient has not yet been performed, the data is linked to the patient and stored after the fact. The timing for executing the post-event storage process can be appropriately selected. For example, the post-event storage process may be executed when the power supply of the ophthalmology medical data processing device 10 is turned on, or when an abnormality in the device is resolved. In addition, the accident storage process may be executed repeatedly at regular intervals.

[0039] First, the CPU 12 judges whether or not unprocessed data exists (S11). In this embodiment, the unprocessed data refers to medical data acquired in S5 of the normal storage process (see FIG. 2) that has not yet been subjected to storage processing linked to a patient. As described above, unprocessed data may be generated when some abnormality occurs. If there is no unprocessed data (S11: NO), the process ends as it is.

[0040] If unprocessed data exists (S11: YES), the CPU 12 acquires date and time information indicating the date and time when the unprocessed data was acquired (S12). In particular, if the unprocessed data is acquired from the ophthalmic device 20, the CPU 12 acquires information on the date and time when the unprocessed data was generated in the ophthalmic device 20. In this case, even if there is a discrepancy between the date and time when the ophthalmic device 20 generated the unprocessed data and the date and time when the ophthalmic medical data processing device 10 acquired the unprocessed data from the ophthalmic device 20 due to a malfunction of the network 5 or the like, the patient from whom medical data is to be acquired can be easily and accurately identified in the process of S13 described later.

[0041] Next, based on the patient identification log (see FIG. 4) stored in the storage device 13 and the date and time information acquired in S12, the CPU 12 retroactively identifies the patient identified in S2 at the time when the unprocessed data was acquired (or generated) as the patient from whom the unprocessed data is to be acquired (S13). As shown in FIG. 4, from the date and time when a certain patient A was identified to the date and time when the next patient B was identified, patient A is identified as the patient from whom the medical data is to be acquired. In the example shown in FIG. 4, it can be seen that "Suzuki Taro" was identified as the patient from whom the medical data is to be acquired from 9:01 when "Suzuki Taro" was identified to 9:18 when "Yamada Hanako" was identified. It can also be seen that "Yamada Hanako" was identified as the patient from whom the medical data is to be acquired from 9:18 when "Yamada Hanako" was identified to 9:29 when "Sato Jiro" was identified. Therefore, by comparing the patient identification log with the date and time information of the unprocessed data, the patient identified at the time when the unprocessed data was acquired is appropriately identified. For example, if the date and time when the unprocessed data was acquired (generated) is 9:24, it is identified afterwards in S13 that the patient for whom the unprocessed data is to be acquired is "Yamada Hanako."

[0042] In addition, the unprocessed data of this embodiment includes information indicating whether the data is for the left eye or the right eye. As described above, the patient identification log (see FIG. 4) of this embodiment also includes information on the target eye (information indicating either the left eye, the right eye, or both eyes). The CPU 12 identifies the patient from whom the unprocessed data is to be acquired from among a plurality of patients, whose information on the target eye indicated by the patient identification log matches the information on the left and right eyes of the unprocessed data. This further improves the accuracy of identifying the patient.

[0043] Next, the CPU 12 causes the display unit 17 to display an identification result confirmation screen 40 (see FIG. 6) (S14). The identification result confirmation screen 40 is a screen for notifying the user of and allowing the user to confirm the result of identifying the patient for whom unprocessed data is to be acquired in the post-identification process (S13). In the example shown in FIG. 6, the date and time when the unprocessed data was acquired (generated) and information about the patient identified in S13 are displayed on the identification result confirmation screen 40. Therefore, the user can properly confirm whether the result of the post-identification process (S13) is accurate by understanding the displayed information.

[0044] Furthermore, the identification result confirmation screen 40 in this embodiment displays an approval button 41, a manual save button 42, and a data discard button 43. The approval button 41 is operated by the user when the patient identified later in S13 is correct. The manual save button 42 is operated by the user when the user manually (i.e., by operating the operation unit 16) re-identifies the patient and saves the unprocessed data. The data discard button 43 is operated by the user when the unprocessed data is to be discarded.

[0045] Furthermore, if image data (hereinafter referred to as "past image data") previously linked and stored exists for the patient identified in the post-identification process (S13) (S15: YES), an image comparison screen 50 (see FIG. 6) is displayed on the display unit 17 (S16). The image comparison screen 50 is a screen for allowing the user to compare unprocessed data with past image data. As shown in FIG. 6, the image comparison screen 50 of this embodiment is displayed on the display unit 17 together with the identification result confirmation screen 40. In the image comparison screen 50, unprocessed data 51 and past image data 52 are displayed side by side. Therefore, the user can more appropriately confirm the accuracy of the patient identification result performed based on the patient identification log by comparing the unprocessed data 51 with the past image data 52.

[0046] The CPU 12 determines whether the approval button 41 has been operated (S18). In other words, in S18, it is determined whether a signal indicating that the result of the post-identification process (S13) has been confirmed has been input by the user. If the approval button 41 has been operated (S18: YES), the CPU 12 associates the unprocessed data with the patient identified in the post-identification process (S13) and stores the unprocessed data in the storage device 13 (S19).

[0047] If the approval button 41 has not been operated (S18: NO), it is determined whether the manual save button 42 has been operated (S21). If the manual save button has been operated (S21: YES), the CPU 12 associates the unprocessed data with a specific patient and stores it in the storage device 13 in accordance with an instruction input by the user via the operation unit 16 (S22).

[0048] If the manual save button 42 has not been operated (S21: NO), it is determined whether the data discard button 43 has been operated (S24). If the data discard button 43 has not been operated (S24: NO), the process returns to S18, and the processes of S18 to S24 are repeated. If the data discard button 43 has been operated (S24: YES), the unprocessed data is discarded (S25), and the process ends.

[0049] The technology disclosed in the above embodiment is merely an example. Therefore, it is possible to change the technology exemplified in the above embodiment. For example, it is possible to execute only a part of the technology exemplified in the above embodiment. Specifically, in the above embodiment, the information of the target eye included in the patient identification log is referred to together with the information of the identification date and time, and then the post-identification process (S13) is executed. However, even if the information of the target eye is not referred to, it is possible to identify the patient from whom the unprocessed data is obtained after the fact.

[0050] In the above embodiment, the result of the post-event identification process (S13) is confirmed to be accurate by accepting an instruction input by the user while both the unprocessed data and the past image data are displayed on the display unit 17. However, the method for confirming the result of the post-event identification process based on the comparison result of the image data can also be changed. For example, the CPU 12 may obtain the similarity between the unprocessed data and the past image data by using known image processing or a mathematical model trained according to a machine learning algorithm. The CPU 12 may confirm whether the result of the post-event identification process (S13) is accurate depending on whether the obtained similarity is equal to or greater than a threshold value.

[0051] 6, the result of the post-identification process for one unprocessed data is displayed. However, when there are multiple unprocessed data, the CPU 12 may display the results of the post-identification process executed for each of the multiple unprocessed data together on the display unit 17. In this case, the user can efficiently check the results of the post-identification process for the multiple unprocessed data.

[0052] The process of identifying a patient in S2 of FIG. 2 is an example of a "pre-identification step". The process of storing a patient identification log in S3 of FIG. 2 is an example of a "log storage step". The process of acquiring medical data in S5 of FIG. 2 is an example of a "medical data acquisition step". The process of storing medical data by linking it to a patient in S6 of FIG. 2 is an example of a "normal storage step". The process of identifying a patient in S13 of FIG. 5 is an example of a "post-identification step". The process of storing unprocessed data by linking it to a patient in S14 to S19 of FIG. 5 is an example of a "post-storage step". The process of notifying a user of the result of the post-identification process in S14 of FIG. 5 is an example of an "identification result notification step". The process of confirming the result of the post-identification process in S16 and S18 of FIG. 5 is an example of a "confirmation step". [Explanation of symbols]

[0053] 1. Ophthalmology medical data processing system 5. Network 10. Ophthalmology medical data processing device 12 CPU 20 Ophthalmological equipment 40 Specific result confirmation screen 50 Image comparison screen

Claims

1. An ophthalmology medical data processing program executed in an ophthalmology medical data processing device that processes medical data indicating at least one result of an ophthalmology examination, photography, and examination performed on a patient, comprising: The ophthalmological medical data processing program is executed by a control unit of the ophthalmological medical data processing device, A pre-identification step of pre-identifying patients whose medical data are to be acquired; a log storage step of storing in a storage device a patient identification log which is a log indicating the date and time when the patient was identified in the advance identification step and the identified patient; A medical data acquisition step of acquiring medical data; a normal storage step of storing, in the storage device, medical data acquired in a state in which the patient is previously identified in the pre-identification step, in association with the identified patient; a post-identification step of identifying a patient from which unprocessed data is to be acquired, the unprocessed data being medical data that has not yet been subjected to storage processing linked to the patient, among the medical data acquired in the medical data acquisition step; a post-storage step of storing the unprocessed data in the storage device in association with the patient identified in the post-identification step; and causing the ophthalmological medical data processing device to execute the above steps; In the post-identification step, information indicating a date and time when the raw data was acquired is acquired; An ophthalmological medical data processing program, characterized in that, based on the patient identification log, a patient who was identified in the pre-identification step at the time the unprocessed data was acquired is identified as the patient for whom the unprocessed data is to be acquired.

2. 2. An ophthalmological medical data processing program according to claim 1, In the medical data acquisition step, medical data is acquired from an ophthalmologic apparatus that performs at least one of an examination and an image capturing of the subject's eye, An ophthalmologic medical data processing program, characterized in that in the post-identification step, a patient from whom the unprocessed data was to be obtained is identified based on information on the date and time when the unprocessed data was generated in the ophthalmologic device.

3. 3. An ophthalmologic medical data processing program according to claim 1, The post-storage step includes: a determination result notifying step of notifying a user of a result that a patient from whom the unprocessed data is to be acquired has been identified in the post-identification step, An ophthalmological medical data processing program characterized in that, when a signal indicating that the notified results have been confirmed is input by a user, the unprocessed data is stored in association with the identified patient.

4. 4. An ophthalmologic medical data processing program according to claim 1, An ophthalmologic medical data processing program characterized in that, when the unprocessed data is image data and image data previously linked and stored to the patient identified based on the patient identification log exists, a confirmation step is further executed to confirm the identification result of the patient based on the patient identification log based on the comparison result between the unprocessed data and the past image data of the patient identified based on the patient identification log.

5. 1. An ophthalmology medical data processing device for processing medical data indicative of results of ophthalmic examinations, photographs, and / or consultations performed on a patient, comprising: The control unit of the ophthalmological medical data processing device A pre-identification step of pre-identifying patients whose medical data are to be acquired; a log storage step of storing in a storage device a patient identification log which is a log indicating the date and time when the patient was identified in the advance identification step and the identified patient; A medical data acquisition step of acquiring medical data; a normal storage step of storing, in the storage device, medical data acquired in a state in which the patient is previously identified in the pre-identification step, in association with the identified patient; a post-identification step of identifying a patient from which unprocessed data is to be acquired, the unprocessed data being medical data that has not yet been subjected to storage processing linked to the patient, among the medical data acquired in the medical data acquisition step; a post-storage step of storing the unprocessed data in the storage device in association with the patient identified in the post-identification step; Run In the post-identification step, acquiring information indicating a date and time when the unprocessed data was acquired; an ophthalmological medical data processing device that identifies, based on the patient identification log, a patient who was identified in the pre-identification step at the time when the unprocessed data was acquired as a patient for which the unprocessed data is to be acquired.

Images