+

WO2003096199A1 - Appareil, systeme et procede de traitement d'informations, support d'enregistrement et programme - Google Patents

Appareil, systeme et procede de traitement d'informations, support d'enregistrement et programme Download PDF

Info

Publication number
WO2003096199A1
WO2003096199A1 PCT/JP2003/005660 JP0305660W WO03096199A1 WO 2003096199 A1 WO2003096199 A1 WO 2003096199A1 JP 0305660 W JP0305660 W JP 0305660W WO 03096199 A1 WO03096199 A1 WO 03096199A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
information
identifier
target
diagnosis
Prior art date
Application number
PCT/JP2003/005660
Other languages
English (en)
Inventor
Satoshi Shimizu
Shinya Tanaka
Tsukasa Sako
Original Assignee
Canon Kabushiki Kaisha
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from JP2002132808A external-priority patent/JP2003323496A/ja
Priority claimed from JP2002170372A external-priority patent/JP3977153B2/ja
Application filed by Canon Kabushiki Kaisha filed Critical Canon Kabushiki Kaisha
Priority to AU2003230242A priority Critical patent/AU2003230242A1/en
Priority to EP03723239A priority patent/EP1506484A4/fr
Publication of WO2003096199A1 publication Critical patent/WO2003096199A1/fr
Priority to US10/969,790 priority patent/US7450742B2/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • G06F21/6254—Protecting personal data, e.g. for financial or medical purposes by anonymising data, e.g. decorrelating personal data from the owner's identification
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H30/00—ICT specially adapted for the handling or processing of medical images
    • G16H30/20—ICT specially adapted for the handling or processing of medical images for handling medical images, e.g. DICOM, HL7 or PACS

Definitions

  • the present invention relates to an information processing apparatus, an information processing system, an information processing method, a computer-readable storage medium storing a program for executing the method, and the program which are used for an apparatus or system for processing medical information (e.g., image data obtained by X-ray imaging and the like) in the medical field.
  • medical information e.g., image data obtained by X-ray imaging and the like
  • imaging diagnosis in the medical field indicates that image information obtained by X-ray imaging is output onto an X-ray film, and a doctor or the like observes (interprets) the film image through a radiograph viewer.
  • a general X-ray film is set to have a contrast corresponding to the density range of 1.0 to about 1.5 D in which the film image can be easily observed. For this reason, if imaging conditions slightly differ from desired conditions, overexposure or underexposure occurs, resulting in imposing adverse effects on imaging diagnosis by image interpretation.
  • Images on X-ray films are essentially analog images, which are used most frequently in imaging diagnosis and regarded important. In spite of this, however, these images have not been fit to the above comprehensive imaging diagnosis and have caused a bottleneck in computerization in the field of imaging diagnosis .
  • X-ray images are digitalized, X-ray images with stabler image quality can be saved, and various kinds of image processing can be done on the basis of , the digital data of such X-ray images.
  • image processing such as temporal difference processing can be performed, in which an X-ray image obtained by preceding X-ray imaging and an X-ray image obtained by current X-ray imaging are digitally positioned to each other, and the difference is obtained.
  • This operation is effective in terms of imaging diagnosis.
  • the above temporal difference processing function can be served on the Internet.
  • medical information variant kinds of medical information including X-ray images
  • intranet can be served on the Internet.
  • intranet information information inside the intranet
  • sending intranet information onto the Internet poses a problem in terms of external leakage. For this reason, when a service on the Internet is to be used, external leakage of intranet information must be minimized.
  • the present invention has been made to solve the above problems, and has as its object to provide an information processing apparatus, information processing system, and information processing method which can reliably prevent information leakage and reliably protect information, and a computer-readable storage medium storing a program for executing this operation, and the program.
  • information leakage from the information saving side is prevented, and identification of information between the information saving side and the information processing side is inhibited.
  • the information processing side is prevented from receiving information other than predetermined information.
  • an information processing apparatus which externally transfers target information to process the information, and' saves the processed information, comprising: storage means for storing second identification information corresponding to the target information in association with the target information to which first identification information is attached; first changing means for deleting the first identification information and adding the corresponding second identification information to the target information in the storage means; transfer means for externally transferring the target information processed by the first changing means; and saving means for saving the target information processed at an external transfer destination to which the information is transferred by the transfer means.
  • an information processing apparatus which is connected, through a network, to a requesting terminal which generates diagnosis request data and a diagnosing terminal which input diagnosis result data with respect to the diagnosis request data, comprising: first reception means for receiving, through the network, diagnosis request data to which a specific examination number is attached from the requesting terminal; conversion means for converting the examination number attached to the diagnosis request data into an examination request number; first transmission means for transmitting, to the diagnosing terminal through the network, the diagnosis request data to which the examination request number is attached; second reception means for receiving the diagnosis result data with respect to the diagnosis request data from the diagnosing terminal through the network; and second transmission means for inversely converting the examination request number attached to the diagnosis result data into the examination number and transmitting the diagnosis result data to the requesting terminal through the network.
  • Fig. 1 is a block diagram showing the arrangement of a data save processing system according to the first embodiment of the present invention
  • Fig. 2 is a block diagram showing the arrangement of a computer which reads out, from a computer-readable storage medium, a program for causing the computer to realize the function of the data save processing system according to the first embodiment of the present invention, and executes the program;
  • Fig. 3 is a view showing the arrangement of a system according to the second embodiment of the present invention;
  • Fig. 4 is a flow chart for explaining the flow of a diagnosis request according to the second embodiment of the present invention.
  • Fig. 5 is a view for explaining the flow of a diagnosis request job according to the second embodiment of the present invention
  • Fig. 6 is a view for explaining a diagnosis request form window according to the second embodiment of the present invention
  • Fig. 7 is a view for explaining a diagnosing doctor selection setting window according to the second embodiment of the present invention.
  • Fig. 8 is a view for explaining a diagnosis request list window according to the second embodiment of the present invention.
  • Fig. 9 is a view for explaining a diagnosis report window according to the second embodiment of the present invention.
  • Fig. 10 is a view for explaining a diagnosis report confirmation window according to the second embodiment of the present invention.
  • Fig. 11 is a view showing the arrangement of a system according to the third embodiment of the present invention.
  • the present invention is applied to a data save processing system 100 like the one shown in Fig. 1.
  • the data save processing system 100 is configured to prevent leakage of information from a data save device 200, inhibit data identification between the data save device 200 and a data processing device 300, and inhibit the data processing deice 300 from receiving data other than predetermined data.
  • a data processing - device which sends out data (target data including image data or the like obtained by X-ray imaging) from a data save device storing data existing in an intranet or the like and executes services on the Internet
  • the data save device issues a new identifier (second identifier) different from the identifier (first identifier such as a check ID) attached to the target data, and deletes supplementary information that poses a problem when it is leaked.
  • the data save device saves this new identifier together with the target data.
  • the data processing device performs data processing of the target data from the data save device, and returns the processed target data to the data save device. At this time, the data processing device attaches the new identifier to the target data when returning it to the data save device.
  • the data save device receives and saves the processed data from the data processing device. At the same time, on the basis of the new identifier attached to the processed data, the data save device searches for the original data (data before processing) of the processed data, and deletes the identifier (new identifier) which is stored in association with the searched data. This makes it possible to erase the association with the data.
  • the data save device issues a new identifier (third identifier) by using the new identifier issued at the time of data transmission to the data processing device and the current Greenwich time according to a specific algorithm, attaches it to the target data, and transmits the resultant data to the data processing device.
  • a new identifier third identifier
  • the data processing device determines whether the new identifier attached to the target data from the data save device is the identifier issued in a time zone with a specific time width before and after the current Greenwich time. This can prevent unspecified facilities from using services on the Internet.
  • the data save processing system 100 is designed such that the data save device 200 which manages and saves data such as medical information on the hospital side and the data processing device 300 which processes the data can communicate with each other through a communication line.
  • the data save device 200 is, for example, a device on an intranet in a hospital, and the data processing device 300 is a device on the Internet.
  • the communication line is typically one of the Internet, a LAN, a WAN, a telephone line, a dedicated digital line, an ATM, a frame relay line, a communication satellite line, a cable TV line, a data broadcast radio line, and the like or a so-called communication network realized by a combination of thereof and may have any arrangement as long as it allows data transmission/reception.
  • the data save device 200 includes a generated data reception unit 211, data management unit 212, first changing unit 213, transfer unit 214, reception unit 215, save unit 216, second changing unit 217, reference device transmission unit 218, first identifier generating unit 219, change recording unit 220, second identifier generating unit 221, third identifier generating unit 222, and Greenwich time acquisition unit 223.
  • the data processing device 300 includes an authentication unit 301, processed data transfer unit 302, data processing unit 303, and Greenwich time acquisition unit 304.
  • the first identifier generating unit 219 generates the first identifier
  • the first identifier becomes part of the supplementary information of the corresponding transfer data.
  • the second identifier generating unit 221 generates the second identifier different from the first identifier generated by the first identifier generating unit 219.
  • the change recording unit 220 stores (records) the second identifier generated, by the second identifier generating unit 221, as supplementary information of the transfer data saved in the data management unit 212.
  • the first changing unit 213 simultaneously deletes the first identifier from the supplementary information of the transfer data and generates transfer data (identifier-changed data) to which the second identifier is attached.
  • the transfer unit 214 transfers the transfer data (identifier-changed data) obtained by the first changing -unit 213 to the data processing device 300 side (Internet side) .
  • the reception unit 215 receives processed data from the data processing device 300.
  • the save unit 216 saves the data received by the reception unit 215 in the data management unit 212.
  • the third identifier generating unit 222 generates the third identifier based on the second identifier according to a specific algorithm.
  • the first changing unit 213 attaches the third identifier generated by the third identifier generating unit 222 to the supplementary information of the transfer data, and transfers the resultant data to the data processing device 300 through the transfer unit 214.
  • the authentication unit 301 receives the data transferred from the data save device 200 and compares the third identifier with the fourth identifier generated based on the second identifier of the received data according to the above algorithm in the data save device 200, thereby determining whether the fourth identifier coincides with the third identifier.
  • the external image generating device 201 outputs image data obtained by X-ray imaging.
  • the generated data reception unit 211 receives the image data output from the image generating device 201.
  • This image data is, for example, an image obtained by X-ray imaging, to which attribute information including information (patient information) about the patient subjected to the X-ray imaging, examination information, and the like is attached as supplementary information.
  • the first identifier generating unit 219 When the generated data reception unit 211 receives image data, the first identifier generating unit 219 generates, for the image data, a unique identifier (first identifier) in the data management unit 212, and adds the identifier to the image data.
  • the data save processing system 100 can use another mode of providing the first identifier depending on the facilities where the system is installed. This mode can be used on the precondition that the supplementary information of an image includes a check ID, and the check ID can be reliably used as a unique identifier in the data management unit 212 in operational facilities.
  • the first identifier generating unit 219 extracts this check ID from the supplementary information of the image and sets it as a unique identifier (first identifier) .
  • first identifier a unique identifier
  • the data management unit 212 saves the image data to which the first identifier is attached by the first identifier generating unit 219.
  • the data save device 200 is, for example, a device installed in a hospital.
  • the data save device 200 issues a new identifier, and at the same time deletes supplementary information that will cause a problem when it is leaked. This makes it possible to prevent data leakage.
  • the data save device 200 sequentially processes the data as transfer targets in the data management unit 212, and sends out them to the data processing device 300.
  • the second identifier different from the first identifier attached to the image data must be issued.
  • the second identifier generating unit 221 therefore issues the second identifier.
  • the change recording unit 220 records the second identifier, generated by the second identifier generating unit 221, as supplementary information of the target image data in the data management unit 212.
  • the first changing unit 213 reads out the target image data from the data management unit 212 and deletes the first identifier of the data. At the same time, the first changing unit 213 adds the second identifier to the data.
  • the first changing unit 213 also deletes, of the supplementary information of the target image data, information about the patient corresponding to the target image data and all information that specifies the data itself, and more specifically, patient information such as the patient name and patient ID, the examination date, the examination date and time, and the like.
  • the first changing unit 213 does not delete minimum necessary information required for image expression, e.g., the numbers of pixels corresponding to the width and height of the image.
  • the third identifier generating unit 222 generates the third identifier on the basis of the Greenwich time (processing time information) obtained by the Greenwich time acquisition unit 223 and the second identifier obtained by the second identifier generating unit 221.
  • the current Greenwich time is converted into an elapsed minute of 54,321 min (Mi) based on 2000 (year) - 01 (month) - 01 (day) , and the second identifier is 98765 (ID), the third identifier is given by
  • the first changing unit 213 attaches, to the target image data, the third identifier obtained by the third identifier generating unit 222 in this manner as supplementary information.
  • the transfer unit 214 sends out the target image data whose supplementary information is changed by the first changing unit 213 to the data processing device 300.
  • the data processing unit 303 performs data processing for the image data (target image data) transferred from the data save device 200, but returns the second identifier to the data save device 200 through the processed data transfer unit 302 without changing the second identifier which is attached to the processed data.
  • the data processing unit 303 saves the corresponding history information, second identifier, and supplementary information.
  • the authentication unit 301 discriminates whether the target image data is sent from an authentic request source (the data save device 200 side in this case) .
  • the authentication unit 301 executes discrimination processing (authentication processing) according to the algorithm used by the third identifier generating unit 222 of the data save device 200. At this time, the authentication unit 301 permits target image data that falls within two min before and after the Greenwich time in minutes obtained by the Greenwich time acquisition unit 304.
  • the authentication unit 301 regards the target image data as data from an authentic request source (the data save device 200 side in this case) .
  • the authentication unit 301 is configured to have a time margin. This is because correct times are not always set in both the data save device 200 and the data processing device 300, and a transfer time includes a delay time.
  • the authentication unit 301 Upon recognizing by the above authentication processing that the target image data is not authentic, the authentication unit 301 notifies the data processing unit 303 of the corresponding information (error occurrence) . As a consequence, the data processing unit 303 stops data processing.
  • the third party maliciously saves transmission/reception data flowing on a network and sends out the data to .
  • the data processing device
  • the data processing device 300 does not authenticate the data because of the difference in Greenwich time.
  • the target image data (processed data) that is recognized as authentic data by the authentication unit is recognized as authentic data by the authentication unit
  • the reception unit 215 receives the processed data from the data processing device 300.
  • the save unit 216 saves the processed data received by the reception unit 215 in the data management unit 212. After the data is completely saved in the save unit 216, the second changing unit 217 searches the data management unit 212 for data on the basis of the second identifier of the processed data.
  • the second changing unit 217 searches the data management unit 212 for the unprocessed target image data corresponding to the processed data, and deletes the second identifier attached to the target image data.
  • the second changing unit 217 adds partial information to the unprocessed target image data.
  • This information includes, for example, information about the patient corresponding to the target image data, and information that specifies the data itself, and more specifically, patient information such as the patient name and patient ID, the examination date, and the examination date and time.
  • patient information such as the patient name and patient ID, the examination date, and the examination date and time.
  • the identifiers attached to these image data and added data may be set in the header field of the image data or separately managed as a database.
  • Image data managed by the data management unit 212 e.g., image data subjected to data processing in the data processing device 300 in the above manner, is transmitted from the reference device transmission unit 218 to the image reference device 202.
  • the image reference device 202 displays the image data from the reference device transmission unit 218 for imaging diagnosis or the like.
  • the image reference device cannot obtain any information that indicates the execution of data processing in the data processing device 300 on the Internet side.
  • the object of the present invention is realized even by supplying a storage medium storing software program codes for realizing the functions of the data save device 200 or data processing device 300 according to the first embodiment to a system or apparatus, and causing the computer (or a CPU or MPU) of the system or apparatus to read out and execute the program codes stored in the storage medium.
  • the program codes read out from the storage medium realize the functions of this embodiment by themselves, and the storage medium storing the program codes constitutes the present invention.
  • a storage medium for supplying the program codes a ROM, flexible disk, hard disk, optical disk, magnetooptical disk, CD-ROM, CD-R, magnetic tape, nonvolatile memory card, or the like can be used.
  • Fig. 2 shows a function 600 of the above computer (data save device 200 or data processing device 300) .
  • a system bus 604 a CPU 601, a ROM 602, RAM 603, a keyboard controller (KBC) 605 for a keyboard (KB) 609, a CRT controller (CRTC) 606 for a CRT display (CRT) 610 serving as a display unit, a disk controller (DKC) 607 for a hard disk (HD) 611 and a flexible disk (FD) 612, and a network interface controller (NIC) 608 for connection to a network 620.
  • the CPU 601 collectively controls the respective components connected to the system bus 604 by executing software stored in the ROM 602 or HD 611 or software supplied from the FD 612.
  • the CPU 601 performs control to realize the operation of this embodiment by reading out and executing a processing program based on a predetermined processing sequence from the ROM 602, HD 611, or FD 612.
  • the RAM 603 functions as a main memory, work area, or the like for the CPU 601.
  • the KBC 605 controls instruction input from the KB 609, a pointing device (not shown), or the like.
  • the CRTC 606 controls display on the CRT 610.
  • the DKC 607 controls access to the HD 611 and FD 612 which store a boot program, various applications, edit files, user files, a network management program, a predetermined processing program in this embodiment, and the like.
  • the NIC 608 bidirectionally exchanges data with an apparatus or system on the network 620. As described above, according to the first embodiment, even if the data saving side (data save processing system 100) requests an external apparatus (data processing side (data processing device 300) ) to process data, leakage of data from the data saving side can be prevented.
  • the ID (second identifier) managed by on the data saving side is identical to the ID (second identifier) of the information received on the data processing side, the ID (second identifier) managed on the data saving side is deleted at the timing when the data processing side returns the data processing result to the data saving side. Even if, therefore, data are stored on the data processing side, the data processing side cannot determine in the subsequent processing which data corresponds to which data on the data saving side. This makes it possible to prevent data leakage and data analysis.
  • Using the third identifier generated by a specific algorithm allows the data processing side to authenticate data. Even if, therefore, data transferred on a network is stolen and maliciously re-transmitted afterward, since the data processing side performs authentication based on the Greenwich time, erroneous authentication can be prevented.
  • the data processing device 300 may be made to function as a server, and the data save processing system 100 may be made to function as a client which uses the server.
  • the "server” in this case means, in WWW system, a Web server which stores information such as HTML documents and images and transmits information through a network such as the Internet upon reception of a request from client software such as a Web browser, or an application server (or a Web application server) which has a function of receiving a request from a user through a network and serving as a mediator for processing in the database system or the like.
  • the "client” means a computer and software which use the functions and data provided from a server in a network.
  • this client corresponds to a computer connected to a network, a home personal computer, and a Web browser, viewer, or the like which operates on a computer.
  • the first embodiment and the second to fourth embodiments to be described below can implement various kinds of processing associated with medical work between a client and a server under the Web environment through the Internet.
  • the present invention is not limited to such an arrangement.
  • the present invention can be applied to any arrangement as long as it is in a computer network environment which provides a form in which various operation windows for executing processes associated with the services provided by a server can be displayed on the browser (viewer) of a client.
  • one doctor in making a diagnosis, one doctor generally examines one patient.
  • a doctor often requires a second opinion from another doctor or refers the patient to another hospital and entrusts a diagnosis to another doctor depending on the type of disease or the condition of the patient.
  • a diabetic patient visits a physician, it may be diagnosed that the patient may have diabetic retinopathy.
  • the patient preferably takes a medical examination from an ophthalmologist. If, however, no ophthalmology department exits within the same hospital facilities, the physician refers the patient to an ophthalmologist. In this case, the physician must write a letter of introduction and generate an examination data sheet and the like.
  • the physician needs also to communicate with the ophthalmologist to whom the patient is referred. This requires much time and effort. In addition, the patient must regularly visit the physician and ophthalmologist, respectively.
  • Using a network poses the problem that "a doctor on the requesting side can browse all the registered information, and hence information associated with patient's privacy, e.g., the name of the patient, date of birth, and address may leak.” This in turn poses, for example, the problem that "a doctor cannot entrust another doctor with a diagnosis for the sake of security protection of information, and hence cannot select an optimal diagnosing doctor.”
  • the second embodiment is wherein when a cooperate diagnosis is to be performed by using a network, privacy is ensured by assigning different IDs to the examination requesting side and the examining side and performing conversion between the two IDs.
  • Fig. 3 shows an example of the arrangement of a cooperative diagnosis system according to the second embodiment of the present invention.
  • Reference numeral 10 denotes a hospital on a requesting side, which includes a photographing apparatus 11 such as a fundus camera for photographing fundus images and a requesting doctor terminal 12 which records examination information, patient information, and the like together with photographed images to make a request to another doctor (diagnosing doctor) .
  • Patient information registered at the time of reception of patients is stored in a patient information database (DB) 13.
  • the patient information database 13 is connected to the photographing apparatus 11 and requesting doctor terminal 12. In photographing an image or requesting a diagnosis, therefore, patient information can be input by searching for patient information that has already been stored in a patient information database 13.
  • the requesting doctor terminal 12 can connect to a management server 20 through a network such as a LAN or the Internet.
  • the requesting doctor terminal 12 transmits processing target data such as a diagnosis request form to the management server 20 to register the data, thereby requesting another doctor to perform a diagnosis.
  • the management server 20 includes a diagnosis/treatment database storing various kinds of information associated with diagnoses, an order management database for managing diagnosis request orders, a diagnosing doctor database for managing registered doctor data, an accounting database for managing accounting to the requesting side/money distribution to the requested side, a requesting hospital database, and the like.
  • the registered hospital 10 on the requesting side, various types of terminals of diagnosing doctors 30A, 30B, and 30C, and the like can connect to the management server 20 through a network.
  • the management server 120 may be installed within the facilities of the hospital 10 on the requesting side or installed in facilities other than the hospital 10 on the requesting side which can be accessed through a public network such as the Internet.
  • the diagnosing doctors 30A, 30B, and 30C respectively have diagnosing doctor terminals 31A to 31C and can browse diagnosis requests imposed on themselves on their terminals, input diagnosis results, and register diagnosis result data by transmitting it to the management server 120 by accessing the management server 20 through a network.
  • a plurality of diagnosing doctors can share each of the diagnostic terminals 31A to 31C by making authentication using digital signatures, passwords, or the like. If an application used for a diagnosis is set as a Web-based application to allow execution of necessary processing such as request processing, browse processing, and diagnosis report processing by using a standard Web browser, a requested diagnosis can be processed from any kind of PC regardless of the type of terminal and OS, thus providing convenience.
  • the hospital on the requesting side issues a diagnosis request to a diagnosing doctor A (diagnosing doctor terminal 31A) with the highest priority level through the management server 20 (S10) .
  • the diagnosing doctor A makes a diagnosis (S20) by image interpretation and transmits a diagnosis result report from the diagnosing doctor terminal 31A to the requesting doctor terminal 12 in the hospital 10 on the requesting side through the management server 20.
  • the doctor on the requesting side confirms the received diagnosis result report by using the requesting doctor terminal 12 in the hospital 10 on the requesting side (S30) . With this operation, this examination is finished.
  • the doctor can issue a re-examination request from the diagnosing doctor terminal 31A to the requesting doctor terminal 12 in the hospital 10 on the requesting side through the management server 20.
  • the diagnosis request is canceled.
  • the requesting doctor terminal 12 in the hospital on the requesting side is then notified of the corresponding information.
  • images are photographed again and patient data is added and corrected in the hospital 10 on the requesting side, and a diagnosis request is issued again as a new examination request.
  • the diagnosis request generated in the hospital 10 on the requesting side in this manner is finished when a diagnosis report is made or the request is canceled to issue a re-examination request. Assigning priority levels to diagnosing doctors in consideration of the schedules, specialties, and the like of the doctors in this manner can reliably make diagnosis requests .
  • the management server 20 may automatically make a re-examination request and cancel the diagnosis request. This makes it possible to prevent the diagnosing doctor from stagnating in an examination.
  • Fig. 3 shows the steps of processing to be performed by the requesting doctor terminal 12 in the hospital on the requesting side, a diagnosing doctor using a diagnosing doctor terminal, and the management server .
  • an operator reads a patient's magnetic card with a magnetic card reader (not shown) connected to the photographing device 11, and inputs a patient ID.
  • the operator then inputs data concerning the patient with a data input unit mounted on the photographing device 11.
  • the patient data is constituted by personal information such as the name and address, diagnosis information such as sex, date of birth, weight, blood pressure, and medical history, and the like.
  • the operator may retrieve these data from the patient information database 13 connected to the photographing device 11 through a network by using the patient ID as a key, and input the retrieved data.
  • Proper photographing conditions are then set for the photographing device 11 to photograph fundus images of the patient.
  • the data of the fundus images photographed by the photographing device 11 are sent to the requesting doctor terminal 12 to be displayed on a diagnosis request form window like the one shown in Fig. 6.
  • diagnosis request form in addition to the image data sent from the photographing device 11, the following data are sent and displayed: the patient data input by the photographing device 11 and data concerning the image, e.g., the image number, photographing apparatus, photography date and time, and distinction between the left and right eyes.
  • An examination number is automatically issued for each diagnosis request so as to avoid overlapping within the hospital .
  • the doctor on the requesting side inputs request data, e.g., examination date and time, the name of a hospital, a hospital code, the name of a doctor in charge, an examination purpose, and the dead line of a diagnosis report, by using the requesting doctor terminal 12.
  • request data e.g., examination date and time
  • the doctor may input patient data by using the requesting doctor terminal 12 through this diagnosis request form window after image transfer instead of the photographing device 11.
  • a diagnosing doctor selection setting button in the diagnosis request form window Fig. 6
  • a diagnosing doctor selection setting window with a diagnosing doctor list is displayed, as shown in Fig. 7.
  • the diagnosing doctor list includes, for example, the priority levels, names, specialties, titles, and work schedules of diagnosing doctors.
  • the hospital 10 on the requesting side can set the priority levels of diagnosing doctors in advance in the diagnosing doctor database of the management server 20.
  • the priority levels of diagnosing doctors can be changed by using a priority level changing button in the diagnosing doctor selection setting window.
  • the priority levels can be changed in accordance with a patient case or in consideration of the schedules of displayed diagnosing doctors.
  • a diagnosis doctor can be added to or deleted from the diagnosing doctor list by operating diagnosing doctor add and delete buttons . As described above, a diagnosis request from the hospital 10 on the requesting side is given to a diagnosing doctor with the highest priority level.
  • the management server 20 searches the diagnosing doctor database to check the schedule of the diagnosing doctor with the highest priority level. If the schedule is not open for a predetermined period of time or more, the management server 20 displays, on the requesting doctor terminal 12, a window for allowing the doctor to select whether to request another doctor with the next highest priority level. This window displays, for example, a message like "Doctor XX cannot make any diagnosis report until December 16. Do you still want to request doctor XX to make a diagnosis? Or do you switch to doctor OO?" The requesting doctor in the hospital 10 on the requesting side determines a diagnosing doctor by selects one of the choices in this window by using the requesting doctor terminal 12.
  • diagnosis request form window After changing the settings associated with the diagnosing doctors or changing the settings in a range, in the diagnosis request form window, which is released to public, the doctor on the requesting side returns to the diagnosis request form window (Fig. 6) to click a diagnosis request button upon checking input request data and the like. As a consequence, the contents of the diagnosis request form (diagnosis request form data) are transmitted to the management server 20. With this operation, the diagnosis request job is finished.
  • the transmitted diagnosis request form data is stored in the diagnosis information database after it is confirmed in the management server 20 that there is no defect concerning data items in the contents.
  • a hospital code which is a number indicating the facilities of the hospital 10 on the requesting side is added to the examination number issued by the hospital 10 on the requesting side to generate a unique number on the management server 20. After it is confirmed that this number is not identical to any of the examination numbers that have already been registered, a new unique number is issued as an examination request number.
  • the management server 20 further registers the examination number of this examination and the examination request number in the order management database in association with each other. At the same time, data such as the occurrence date and time of the diagnosis request and the current status (wait for diagnosis) are recorded.
  • the management server 20 retrieves a diagnosing doctor with the highest priority level set in the diagnosing doctor selection list in association with this examination from the diagnosing doctor database.
  • the management server 20 makes contact with the retrieved diagnosing doctor (e.g., the diagnosing doctor A) by means such as e-mail transmission, indicating that a diagnosis request has been issued.
  • the management server 20 changes the setting of access level with respect to the diagnosis/treatment database to "browsing/reporting permitted" .
  • the diagnosing doctor A is made to know the generation of the diagnosis request through the diagnosing doctor terminal 31A, he/she accesses the management server 20 through the diagnosing doctor terminal 31A.
  • the management server 20 Upon authenticating the diagnosing doctor A by using the ID, password, electronic signature, and the like, the management server 20 displays a diagnosis request list window like the one shown in Fig. 8 on the diagnosing doctor terminal 31A. Note that authentication with a fingerprint, iris, or the like can make a strict check to prevent someone from browsing diagnosis/treatment data or making a diagnosis report by disguising himself/herself as the diagnosing doctor A.
  • a diagnosis report window like the one shown in Fig. 9 is displayed.
  • This diagnosis report window displays necessary data such as diagnosis request data, personal information of the patient, and image data, and allows the diagnosing doctor to input the result obtained by interpreting/diagnosing these displayed data in an diagnosis result entry field through the diagnosing doctor terminal 31A
  • the hospital 10 on the requesting side limits the contents in the diagnosis report window displayed on the diagnosing doctor terminal 31A with respect to the diagnosing doctor A to only items necessary for a diagnosis.
  • the diagnosing doctor A cannot therefore browse personal information such as the address and telephone number of the patient.
  • an examination number only the examination request number issued by the management server 20 is displayed, and no examination number in the hospital 10 on the requesting side is displayed with respect to the diagnosing doctor A. There is no chance of violation of privacy concerning personal information of the patient.
  • the hospital 10 on the requesting side can ensure privacy concerning personal information of a patient while disclosing only information necessary for a diagnosis to a diagnosing doctor.
  • the diagnosing doctor A can select re-examination request processing or report registration processing through the diagnosing doctor terminal 31A.
  • the diagnosing doctor A can cancel this diagnosis request and request the hospital 10 on the requesting side to perform re-photographing by clicking the re-examination request button.
  • the diagnosing doctor A inputs the diagnosis result in the result entry field and clicks the report register button, the data of the diagnosis report is transmitted to the management server 20. With this operation, the step for the diagnosis report is completed.
  • the diagnosing doctor browses image data, patient data, and the like in a diagnosis report window like the one shown in Fig. 9, and makes a diagnosis based on these data.
  • the diagnosing doctor then inputs the diagnosis result including the name of a disease, findings, and the like in the diagnosis result entry field.
  • the report register button is clicked, the input diagnosis result data is transmitted to the management server 20.
  • the management server 20 registers the diagnosis result data in the diagnosis/treatment database, and changes the status on the order management database to "end of diagnosis/wait for confirmation".
  • the management server 20 then notifies the requesting doctor terminal 12 in the hospital 10 on the requesting side by mail or the like that the diagnosis result has been reported.
  • the examination request number is inversely converted into the original examination number used to make the diagnosis request.
  • the requesting doctor terminal 12 in the hospital 10 on the requesting side accesses the management server 20.
  • a diagnosis report confirmation window like the one shown in Fig. 10 is displayed.
  • the doctor clicks the request source confirmation button upon confirming the contents of the diagnosis result the corresponding information is transmitted to the management server 20.
  • this diagnosis report confirmation window there is no need to inhibit the disclosure of information for security protection, and hence the examination number in the hospital 10 on the requesting side and personal information of the patient are displayed as in the case of the diagnosis request form window.
  • the diagnosis request number used by the diagnosing doctor is displayed in the diagnosis report confirmation window or the like on the requesting doctor terminal 12 side, together with the examination number, to specify the examination when it is necessary to make a direct contact with the diagnosing doctor by telephone or the like as in case of an emergency.
  • the management server 20 updates the examination status of the order management database to "end of examination”, registers the diagnosis report record in the diagnosing doctor database, and registers accounting/money distribution data in the accounting database. Finally, the management server 20 transmits e-mail indicating the completion of all operations for this examination to the requesting doctor terminal 12 in the hospital on the requesting side and the diagnosing doctor terminal of the diagnosing doctor who has made the diagnosis. With this operation, the examination is terminated. «Third Embodiment»
  • visitors A, B, and C e.g., patients
  • visitors A, B, and C e.g., patients
  • the management server 20 may manage a browsing count, access time, or the like and charge a visitor in accordance with the amount of use.
  • an examination is specified by using the examination number issued by the hospital 10 on the requesting side and the hospital code. If the unique number of an image which is used to make a diagnosis request, e.g., a DICOM image, is to be used, a study UID, which is a property of this image, can be used for the recognition of an examination at the time of registration. Since a study UID is always a unique value according to the DICOM specifications, this value can be used as a unique number on a management server 20 without being combined with a hospital code. Therefore, this number can be used after being converted into a unique examination request number on the management server.
  • a study UID is always a unique value according to the DICOM specifications
  • a plurality of doctors can efficiently and cooperatively make a diagnosis.
  • a hospital on the requesting side in particular, can make a diagnosis request to a doctor outside the hospital without disclosing any examination number used in the hospital to the doctor outside the hospital, thereby reliably ensuring security of private data such as personal information of a patient and a diagnosis result.
  • Each terminal and server described in each of the second to fourth embodiments is realized by the arrangement shown in Fig. 2.
  • the arrangement of the first embodiment can be applied to the cooperative diagnosis system according to the second to fourth embodiments. If, for example, the arrangement of the first embodiment is to be applied to the arrangement of the second embodiment, the function realized by the data save processing system 100 in Fig. 1 in the first embodiment is applied to the function realized by the requesting doctor terminal 12 and management server 20 in Fig. 2. The function realized by the data processing device 300 in Fig. 1 in the first embodiment is applied to each of the diagnosing doctor terminals 31A to 31C in Fig. 2 in the second embodiment. This makes it possible to realize a cooperative diagnosis while ensuring security of data in the first embodiment as well.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Medical Informatics (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Epidemiology (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)

Abstract

L'invention concerne un appareil de traitement d'informations qui transmet des informations cibles à un dispositif de traitement de données externe pour traiter ces informations, puis sauvegarde les informations traitées. Cet appareil comprend une unité de gestion de données qui enregistre des secondes informations d'identification correspondant aux informations cibles en association avec les informations cibles auxquelles des premières informations d'identification sont jointes. Une première unité de modification supprime les premières informations d'identification des informations cibles et ajoute aux informations cibles dans l'unité de gestion de données les secondes informations d'identification correspondantes. Une unité de transfert transmet les informations cibles traitées par la première unité de modification au dispositif de traitement de données externe.
PCT/JP2003/005660 2002-05-08 2003-05-06 Appareil, systeme et procede de traitement d'informations, support d'enregistrement et programme WO2003096199A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2003230242A AU2003230242A1 (en) 2002-05-08 2003-05-06 Information processing apparatus, information processing system, information processing method, storage medium, and program
EP03723239A EP1506484A4 (fr) 2002-05-08 2003-05-06 Appareil, systeme et procede de traitement d'informations, support d'enregistrement et programme
US10/969,790 US7450742B2 (en) 2002-05-08 2004-10-20 Information processing apparatus, information processing system, information processing method, storage medium, and program

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2002-132808 2002-05-08
JP2002132808A JP2003323496A (ja) 2002-05-08 2002-05-08 連携診断システム
JP2002-170372 2002-06-11
JP2002170372A JP3977153B2 (ja) 2002-06-11 2002-06-11 データ処理装置、データ処理システム、データ処理方法及びプログラム

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10/969,790 Continuation US7450742B2 (en) 2002-05-08 2004-10-20 Information processing apparatus, information processing system, information processing method, storage medium, and program

Publications (1)

Publication Number Publication Date
WO2003096199A1 true WO2003096199A1 (fr) 2003-11-20

Family

ID=29422373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2003/005660 WO2003096199A1 (fr) 2002-05-08 2003-05-06 Appareil, systeme et procede de traitement d'informations, support d'enregistrement et programme

Country Status (3)

Country Link
EP (1) EP1506484A4 (fr)
AU (1) AU2003230242A1 (fr)
WO (1) WO2003096199A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7350231B2 (en) 2001-06-06 2008-03-25 Yahoo ! Inc. System and method for controlling access to digital content, including streaming media
US7356838B2 (en) 2001-06-06 2008-04-08 Yahoo! Inc. System and method for controlling access to digital content, including streaming media
CN107330288A (zh) * 2017-07-10 2017-11-07 叮当（深圳）健康机器人科技有限公司 一种用药信息获取方法及装置
CN114451860A (zh) * 2022-01-27 2022-05-10 广东康软科技股份有限公司 一种基于深度学习的眼底病变诊断方法、系统及设备

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0855659A1 (fr) * 1997-01-22 1998-07-29 Lucent Technologies Inc. Système et méthode de browsage anonyme et personnalisé dans un réseau
JP2000041957A (ja) * 1998-07-29 2000-02-15 Matsushita Electric Works Ltd 健康管理システム
EP1026603A2 (fr) * 1999-02-02 2000-08-09 SmithKline Beecham Corporation Appareil et méthod de rendre de l'information anonyme
JP2001154984A (ja) * 1999-11-16 2001-06-08 Alchemedia Ltd ネットワークを介して伝送されるディジタル画像の著作権保護のための方法及びシステム
JP2001217827A (ja) * 2000-02-03 2001-08-10 Victor Co Of Japan Ltd プレーヤ端末及びコンテンツデータ伝送システム
JP2001309158A (ja) * 2000-04-26 2001-11-02 Matsushita Electric Ind Co Ltd 電子メールシステム
JP2002055919A (ja) * 2000-08-07 2002-02-20 Sony Corp 情報処理装置および情報処理方法、サービス提供システム、並びに記録媒体
JP2002189953A (ja) * 2000-12-21 2002-07-05 Hitachi Ltd 情報配信システムおよび情報配信端末

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7509280B1 (en) * 1997-11-24 2009-03-24 Clinlcomp International, Inc. Enterprise healthcare management system and method of using same
WO2002019222A1 (fr) * 2000-08-31 2002-03-07 Clinnet Solutions Llc Système de distribution d'information en relation avec la santé

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0855659A1 (fr) * 1997-01-22 1998-07-29 Lucent Technologies Inc. Système et méthode de browsage anonyme et personnalisé dans un réseau
JP2000041957A (ja) * 1998-07-29 2000-02-15 Matsushita Electric Works Ltd 健康管理システム
EP1026603A2 (fr) * 1999-02-02 2000-08-09 SmithKline Beecham Corporation Appareil et méthod de rendre de l'information anonyme
JP2001154984A (ja) * 1999-11-16 2001-06-08 Alchemedia Ltd ネットワークを介して伝送されるディジタル画像の著作権保護のための方法及びシステム
JP2001217827A (ja) * 2000-02-03 2001-08-10 Victor Co Of Japan Ltd プレーヤ端末及びコンテンツデータ伝送システム
JP2001309158A (ja) * 2000-04-26 2001-11-02 Matsushita Electric Ind Co Ltd 電子メールシステム
JP2002055919A (ja) * 2000-08-07 2002-02-20 Sony Corp 情報処理装置および情報処理方法、サービス提供システム、並びに記録媒体
JP2002189953A (ja) * 2000-12-21 2002-07-05 Hitachi Ltd 情報配信システムおよび情報配信端末

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1506484A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7350231B2 (en) 2001-06-06 2008-03-25 Yahoo ! Inc. System and method for controlling access to digital content, including streaming media
US7356838B2 (en) 2001-06-06 2008-04-08 Yahoo! Inc. System and method for controlling access to digital content, including streaming media
CN107330288A (zh) * 2017-07-10 2017-11-07 叮当（深圳）健康机器人科技有限公司 一种用药信息获取方法及装置
CN114451860A (zh) * 2022-01-27 2022-05-10 广东康软科技股份有限公司 一种基于深度学习的眼底病变诊断方法、系统及设备

Also Published As

Publication number Publication date
EP1506484A4 (fr) 2006-05-03
AU2003230242A1 (en) 2003-11-11
EP1506484A1 (fr) 2005-02-16

Similar Documents

Publication Publication Date Title
US7450742B2 (en) Information processing apparatus, information processing system, information processing method, storage medium, and program
US20050021375A1 (en) Cooperative diagnosis system
CN100581468C (zh) X射线图像拍摄装置和管理方法
US8428969B2 (en) System and method for tracking medical imaging quality
US7818041B2 (en) System and method for efficient diagnostic analysis of ophthalmic examinations
EP1410761A1 (fr) Sytème de diagnostique par imagerie médicale, et serveur fournissant des informations et procédé pour fournir des informations
US20050197860A1 (en) Data management system
US20020138301A1 (en) Integration of a portal into an application service provider data archive and/or web based viewer
JP2003323496A (ja) 連携診断システム
JP2004512579A (ja) 医療画像管理システム及び方法
US20050187787A1 (en) Method for payer access to medical image data
JP2005092706A (ja) 連携検査診断装置
JP2006085545A (ja) 医用連携診断システム
EP1506484A1 (fr) Appareil, systeme et procede de traitement d'informations, support d'enregistrement et programme
US20020019832A1 (en) System, method and recording medium for medical image management
JP2003303237A (ja) 連携診断システム
JP2005165648A (ja) 連携診断装置
JP2005196533A (ja) 連携診断装置
JP2017151584A (ja) 医療情報処理装置、プログラム及び医療情報管理システム
JP2004194759A (ja) 連携診断システム
JP6881628B2 (ja) 医療連携システム及び制御プログラム
US20140172451A1 (en) Systems and methods for medical information management
JPWO2019215782A1 (ja) 診断情報提供装置、方法及びシステム
US20020059300A1 (en) System, method and recording medium for centralized management of medical images
JP2005010884A (ja) 遠隔診断システム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 10969790

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2003723239

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003723239

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 2003723239

Country of ref document: EP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载