JP2005165648A - Cooperative diagnostic system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a plurality of medical doctors to efficiently perform a diagnosis in corporation with each other while protecting privacy. <P>SOLUTION: A request origin hospital 1 is provided with: a photographing device such as a fundus camera 2; and a requesting doctor terminal 3 for recording a photographed image and test information and patient information or the like and making a request to another diagnostician. Patient information registered at the time of accepting the patient is stored in a patient information database 4, and the database 4 is connected to the fundus camera 2 and the requesting doctor terminal 3. The requesting doctor terminal 3 of the request origin hospital 1 is connected through a network such as a LAN or the Internet to a management server 5 having various databases. Diagnosticians terminals 6A, 6B and 6C for remote diagnosticians A, B and C are connected to the management server 5, and may be connected to referral doctor terminals 7D and 7E for referral doctors D and E. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a cooperative diagnosis apparatus in which a plurality of doctors cooperate to make a diagnosis.

  Conventionally, when a patient performs a medical examination at a medical examination center, a fundus photograph is generally taken using a fundus camera together with a urine test, a blood test, an inquiry, and the like. If there is no ophthalmologist in the same facility, the photographed fundus image is requested to make a primary diagnosis with the contracted ophthalmologist. In that case, the requesting hospital, which is the screening center, requires many administrative procedures such as preparation of test data sheets, sending and collecting fundus photos and diagnostic reports, and calculation and payment of diagnostic fees. Time and effort are required.

  In order to solve these problems, some hospitals use non-mydriatic fundus cameras to take pictures of the fundus of diabetic patients, mail the film taken to an ophthalmologist, and interpret and diagnose retinopathy Is entrusted.

  Further, as described in Patent Document 1, a method of requesting diagnosis from another doctor using a computer terminal connected to a network is also disclosed.

JP 2001-273365 A

  As described above, in the case of the method of sending a film by mail, it takes time to mail inspection data and fundus photographs necessary for diagnosis, and there is a risk that the film or report may be lost during the mailing. There is also. Furthermore, it is necessary to manage images such as films and the like together with patient data, examination data, and a report created by an ophthalmologist, and there is a problem that a great deal of work is required for office work.

  The results of this primary diagnosis are reported to the patient from the screening center, but for some patients diagnosed as requiring a secondary diagnosis, which is a close examination, along with the results, It is necessary to introduce facilities that can receive detailed workups. At that time, depending on the medical condition, the doctor at the requesting examination center considers the hospital with specialists in the field, the hospital with appropriate examination facilities, or the hospital visit, and the location close to the patient's address. The hospital to be subjected to a close examination is selected according to various conditions such as hospitals.

  In this case, there is a problem that administrative procedures such as investigation, contact and preparation of a letter of introduction, etc. are extremely troublesome.

  The object of the present invention is to solve the above-mentioned problems and enable efficient diagnosis in cooperation with a plurality of doctors without troublesome office procedures. An object of the present invention is to provide a cooperative diagnosis apparatus capable of automatically selecting an appropriate doctor for a patient determined to be necessary and notifying the requesting hospital of the information.

  In order to achieve the above object, a linked diagnosis apparatus according to the present invention comprises a database server storing medical information, primary diagnostic facility information, and secondary diagnostic facility information, a request terminal connected to the database server, and the database server A diagnostic terminal connected to the terminal, an examination data registration means for registering examination data from the request terminal in the database server, a display means for displaying the registered examination data on the diagnostic terminal, and a secondary diagnosis Diagnostic result data registration means for registering primary diagnosis result data including information indicating whether it is necessary in the database server, and the database server is predetermined for a patient who needs the secondary diagnosis in the primary diagnosis result data. The secondary diagnostic facility itself selects at least one secondary diagnostic facility from a plurality of secondary diagnostic facilities using conditions. Selecting means, and having a notifying means for notifying at least one secondary diagnostic facility information of the selected from the database server to the requesting terminal.

  The cooperative diagnosis apparatus according to the present invention includes a database server storing medical information, primary diagnosis facility information, and secondary diagnosis facility information, a request terminal connected to the database server, and a diagnosis server connected to the database server. A terminal, a priority registration means for registering the priority order of the secondary diagnosis facility in the database server for each request data and the inspection data by the requesting terminal, and the diagnostic terminal displaying the registered inspection data Test data display means, diagnostic result data registration means for registering primary diagnosis result data including information indicating whether secondary diagnosis is necessary or not in the database server, and secondary diagnosis is required in the primary diagnosis result data Secondary for selecting a secondary diagnostic facility according to the priority registered by the database server for the patient to be examined The cross-sectional facility automatic selection means, said database server; and a notifying means for notifying the requesting terminal information of the selected diagnosis facilities.

  According to the linked diagnosis device according to the present invention, a plurality of doctors can efficiently and reliably perform a diagnosis, specifically request slips, reports, bills, film exchanges, fee payments, Diagnosis can be made efficiently and efficiently without troublesome administrative procedures such as making a letter of introduction. In the primary diagnosis, an appropriate hospital can be selected and introduced to a patient who needs a more precise secondary diagnosis.

  FIG. 1 shows a configuration diagram of the embodiment. In a requesting hospital 1 such as an examination center, an imaging device of a fundus camera 2 for imaging a fundus image, examination information, patient information, and the like together with the captured image. It has a requesting medical terminal 3 for recording and making a request to another doctor or diagnostician. Further, the requesting hospital 1 is provided with a patient information database 4 which stores patient information registered at the time of patient reception. The database 4 is connected to the fundus camera 2 and the requesting medical terminal 3.

  The requesting medical terminal 3 of the requesting hospital 1 is connected to the management server 5 via a network such as a LAN or the Internet. The management server 5 manages an order management database for managing the order of diagnosis requests, a medical information database for managing diagnostic data, a requesting hospital database for managing data of the requesting hospital 1, and data of registered diagnostic doctors. It has a diagnostic doctor database, a referral hospital database for managing a referral hospital, and a charge database for managing charge / distribution.

  The management server 5 is connected to diagnostic medical terminals 6A, 6B, and 6C for remote diagnostic doctors A, B, and C. Furthermore, connection to referral medical terminals 7D and 7E for referral doctors D and E is possible. Although the management server 5 may be located in the facility of the requesting hospital 1 as in the embodiment, it is a facility that is located in a different location from the requesting hospital 1 and is accessible via a public network such as the Internet. There is no problem.

  Diagnostic physicians A, B, and C use diagnostic medical terminals 6A, 6B, and 6C, respectively, to access management server 5 via the network, browse diagnostic requests imposed on themselves, and enter diagnostic results Then, the diagnosis result data can be registered by transmitting to the management server 5.

  The diagnostic medical terminal 6 can be used by a plurality of diagnostic doctors sharing, for example, one diagnostic medical terminal 6 by confirming the identity of the diagnostic medical terminal 6 with an electronic signature or a password. In addition, by using a standard browser with the application used for diagnosis as a web base and performing necessary operations such as request, browsing, and diagnosis report, any diagnostic medical device can be used regardless of the type or OS of the diagnostic medical terminal 6 The requested diagnosis can be processed from the terminal 6 as well.

  The diagnosis result report entered by the diagnosis doctors A and the like includes information indicating whether or not a detailed examination as a secondary diagnosis is necessary. The referral doctor or diagnosis facility suitable for the patient is automatically selected from a plurality of referral doctors or diagnosis facilities registered in the referral doctor database in accordance with predetermined conditions such as the location of the patient.

  The referral doctors D and E have referral medical terminals 7D and 7E, respectively, and can access the management server 5 via the network in the same manner as the diagnostic doctors A, B, and C. By searching the database, it is possible to view patient data introduced to the patient from the requesting hospital 1. Further, when a close inspection is performed, the result of the close inspection is entered and transmitted to the management server 5, whereby the data of the close inspection result can be registered in the medical care information database.

  In addition, the referring doctor and the diagnosis doctor may be the same doctor. In this case, a single terminal can be used as both the diagnosis doctor terminal and the referral doctor terminal.

  FIG. 2 shows a flowchart of a primary diagnosis operation in which a plurality of doctors cooperate with each other using this cooperative diagnosis apparatus. First, in step S1, the requesting hospital 1 reads the patient's magnetic card via a data input device such as a magnetic card reader (not shown) connected to the fundus camera 2 to obtain the patient ID, name, gender, date of birth. Enter patient data such as weight, blood pressure. These data may be retrieved and input from the patient information database 4 connected to the network using the patient ID as a key. Subsequently, after adjusting the photographing conditions of the fundus camera 2, a fundus image of the patient is photographed. The fundus image captured by the fundus camera 2 is displayed on the request medical terminal 6 on a diagnosis request slip screen 11 as shown in FIG.

  This diagnosis request form screen 11 is input via the image data 12, request data 13, and fundus camera 2, together with the image taken by the fundus camera 2, the image number, the imaging device, the shooting date and time, and the left / right eye distinction Patient data 14 is also displayed. Further, on the diagnosis request slip screen 11, a diagnostic doctor selection setting button 15 and a diagnosis request button 16 are displayed, and an examination number is further displayed.

  In step S2, the requesting doctor of the requesting hospital 1 inputs request data 13 such as the hospital name, the name of the doctor in charge, the diagnosis purpose, and the diagnosis report deadline on the diagnostic doctor request form screen 11. Further, the patient data 14 may be input on this screen after the image transfer without being performed by the fundus camera 2. At this time, the patient data 14 can be added and corrected as necessary.

  Subsequently, when the diagnostic doctor selection setting button 15 on the diagnosis request form screen 11 is clicked, a diagnostic doctor selection setting screen 21 as shown in FIG. 4 is displayed. The diagnosis doctor list 22 on the setting screen 21 includes items such as the priority order of the requested diagnosis doctor, the name of the diagnosis doctor, the specialty, the job title, and the work schedule, and the diagnosis doctor list 22 includes the management server 5. Are managed in the diagnostic physician database. Further, on this setting screen 21, a diagnostic doctor add button 23, a diagnostic doctor delete button 24, a priority order change button 25, an apply button 26, and a cancel button 27 are displayed.

  The priority order of the diagnostic doctor can be set in advance in the diagnostic doctor database of the management server 5 by the requesting hospital 1. By clicking the priority order change button 25 on the setting screen 21, for example, The priority order can be changed according to the case or in consideration of the displayed diagnostician's schedule. It is also possible to add or delete a diagnostician to / from the diagnostician list 22 by clicking an add button 23 for a diagnostician and a delete button 24 for a diagnostician.

  Further, when the application button 26 is clicked after changing the setting on the setting screen 21 for selecting the diagnostician, the setting is returned to the diagnostic request form screen 11 and the changed setting is registered in the diagnostician database of the management server 5. Subsequent diagnostic requests are processed according to this condition. In order to return to the diagnosis request form screen 11 without determining the diagnosis doctor, the cancel button 27 is clicked. Note that this step can be omitted when there is no change in the settings relating to the diagnostician.

  In step S 3, when the diagnosis request button 16 is clicked on the diagnosis request form screen 11, data on the diagnosis request form screen 11 is transmitted to the management server 5. The transmitted data of the diagnosis request form screen 11 is registered in the medical care information database after it is confirmed in the management server 5 that there is no deficiency for each diagnosis item. When registering in the medical care information database, a unique number on the management server 5 is created by combining the hospital code, which is the number representing the facility of the requesting hospital 1, and the examination number issued at the requesting hospital 1. After confirming that this does not overlap with the already registered inspection, a new unique number is issued as the inspection request number.

  In step S4, the management server 5 registers the inspection number and the inspection request number in association with the order management database, and records them together with data such as the date and time of diagnosis request occurrence and the current diagnosis wait.

  Next, in step S5, the diagnosis doctor with the highest priority set in the diagnosis doctor list 22 for this examination is automatically searched in the diagnosis doctor database in the management server 5, and a diagnosis request is sent to the diagnosis doctor. At the same time, the access level setting for the medical information database is changed to “viewable / reportable”.

  For example, when the diagnosis doctor A is notified that a diagnosis request has occurred, the diagnosis doctor A accesses the management server 5 from the diagnosis medical terminal 6A in step S6. The management server 5 displays the diagnosis request list screen 31 as shown in FIG. 5 on the diagnostic medical terminal 6A after confirming the identity by means such as ID, password, and electronic signature. A diagnosis request list 32 and a display button 33 are displayed on the diagnosis request list screen 31. In addition, if it is confirmed using the fingerprint, iris, etc. that the diagnosis doctor A is himself, it will be more strict so that no other person will pretend to be the diagnosis doctor A to view medical data or make a diagnosis report. You can also check it.

  In step S7, when the diagnosis doctor A selects the requested diagnosis request from the diagnosis request list 32 and clicks the display button 33, a diagnosis report screen 41 as shown in FIG. 6 is displayed. In the diagnosis report screen 41, the image data 12, the request data 13, and the patient data 14 necessary for diagnosis can be displayed, and the result of interpretation / diagnosis based on the data displayed by the diagnostician A can be input. A diagnosis result entry field 42 is provided so that a disease name, findings, necessity of detailed examination, necessary fine examination items, and the like can be entered. Further, a re-inspection request button 43 and a report registration button 44 are displayed on the diagnosis report screen 41, and an inspection request number is further displayed.

  The data displayed for the diagnosing doctor A is limited to only items necessary for diagnosis by the requesting hospital 1 to protect the privacy of the patient. Personal information such as the patient's name, address, and telephone number is The diagnostician A cannot view it. Since only the examination request number issued in the management server 5 is displayed and the examination number at the requesting hospital 1 is not displayed to the diagnostician A, the privacy such as the personal information of the patient is not leaked. . As described above, the requesting hospital 1 can maintain privacy confidentiality such as personal information of patients while disclosing information necessary for diagnosis to the diagnostician A.

  In step S8, the diagnostician A performs report registration based on the information displayed on the diagnosis report screen 41. When the diagnosis doctor A inputs the result of the primary diagnosis, that is, the name of the disease, the findings, the necessity of the secondary examination, which is a detailed examination, and the like in the diagnosis result entry field 42, and clicks the report registration button 44, the diagnostic report The data of the screen 41 is transmitted to the management server 5, and the diagnostic report step is completed.

  In the management server 5, after confirming that there is no deficiency in the data of each item of the transmitted diagnosis report screen 41, the diagnosis result is registered in the medical information database, and “waiting for diagnosis” on the order management database is set to “diagnosis completed”. Change to / waiting for confirmation.

  Subsequently, in step S9, the management server 5 determines whether or not a close inspection is required by using the data on whether or not a close inspection is required in the diagnosis result entry field 42, and if a close inspection is required. Then, the process proceeds to step S10.

  In the referral hospital database in the management server 5, conditions such as the location, date of medical examination, and inspection equipment are registered for a plurality of diagnostic facilities or doctors performing a detailed examination. In step S10, using the predetermined conditions such as the examination equipment registered in the referral hospital database, the distance from the hospital, etc., from the data such as the detailed examination items in the diagnosis result entry column 42 by the diagnostician A and the patient's address, It is possible to automatically select the most suitable inspection facility. A plurality of hospitals may be selected.

  The referral hospital is not selected for examinations for which a close examination is not required in the result of the primary diagnosis by the diagnostician A. The management server 5 issues an access key for this inspection.

  Next, in step S11, the requesting hospital 1 is notified that the report of the primary diagnosis of the examination has been completed. At that time, the examination request number is reversely converted to the examination number used in the diagnosis request. In step S12, when the requesting doctor of the requesting hospital 1 receiving the diagnosis report mail accesses the management server 5 via the requesting doctor terminal 3, a diagnosis report confirmation screen 51 as shown in FIG. 7 is displayed. . The diagnosis report confirmation screen 51 displays a diagnosis result column 52, a re-diagnosis request button 53, and a request source confirmation button 54 together with the image data 12, the request data 13, the patient data 14, and the examination number.

  After confirming the contents of the diagnosis result, the requesting doctor clicks the request source confirmation button 54 in step S13, and the information is transmitted to the management server 5. In the diagnosis report confirmation screen 51, it is not necessary to keep information or the like private in order to maintain confidentiality. Like the diagnosis request form screen 11, the examination number of the requesting hospital 1 and the personal information of the patient are also displayed. Yes.

  For examinations that require close examinations, the management server 5 describes the recommended hospital selected from the referral hospital database, information on examination items, and examination access keys. Can be given in the form of a letter of introduction. Of course, the letter of introduction is not limited to a letter, and means such as e-mail may be used. In that case, by sending the same mail to the referral hospital as well as the patient, the referral hospital can be surely notified of the patient referral.

  In step S14, the management server 5 updates the status to the end of examination in the order management database and registers the result of the diagnosis report in the diagnostic doctor database. In step S15, the management server 5 charges the requesting doctor in the billing database, and diagnoses doctor A Register the distribution data for. Subsequently, in step S16, an e-mail notifying that the processing for the primary diagnosis of this examination has been completed is transmitted to the requesting hospital 1 and the diagnosing doctor A who made the diagnosis.

  FIG. 8 shows a flowchart of secondary diagnosis in which a plurality of doctors cooperate in diagnosis using this cooperative diagnosis system. First, along with the result of the primary diagnosis at the requesting hospital 1, the patient who required a close examination visits the referred hospital with a referral letter issued by the requesting hospital 1 and filled in with an access queue. In step S21, patient registration is performed.

  FIG. 9 shows a referral patient primary diagnosis result data examination screen 61 in which an access key input field 62 and a display button 63 are displayed. In step S <b> 22, when the referral doctor inputs the access key described in the referral letter in the access key input field 62 and clicks the display button 63 in the referral medical terminal 7, the access key is transmitted to the management server 5.

  Further, the screen for displaying the primary examination result data may be in a format such as an introductory patient detailed examination list screen 71 as shown in FIG. On this introduction patient detailed examination list screen 71, a list 72 of patients introduced by the management server 5 is displayed, and the status of each examination such as waiting for detailed examination, waiting for detailed examination / waiting confirmation, confirmed, etc. is also displayed. In addition, a display button 73 is provided.

  When the patient visits the hospital, the access key described in the letter of introduction is selected, and when the display button 63 is clicked, the access key is transmitted to the management server 5. In step S23, when the access key is received, the management server 5 confirms that the transmission source terminal and the introduction destination hospital of this examination match, and then introduces the result of the primary diagnosis of the diagnosis doctor A to the introduction doctor. It is displayed on the medical terminal 7. Even if the terminal is connected to the management server 5, the inspection data cannot be accessed without an access key and a terminal corresponding to the key, which is safe from the viewpoint of security.

  Upon receiving this access key, the management server 5 determines that the patient has come to the hospital according to the referral letter, charges the referral fee to the referral destination hospital using the billing database in step S24, and registers the distribution data in the requesting hospital 1. . By registering the billing / distribution data in this way, the requesting doctor can surely receive the referral fee from the referral destination hospital without any troublesome procedures when referring to another hospital. In addition, the referral hospital pays the referral fee only when the referred patient visits, and does not pay the referral fee for the patient who has been referred but did not visit.

  The requesting hospital 1 obtains an introduction fee by introducing a patient to a primary diagnosis diagnostician, and as a result, can perform a primary diagnosis with a low diagnostic fee. In addition, the diagnostician hopes to make many primary diagnoses in order to be introduced as a referral hospital for patients requiring detailed examination. Therefore, the diagnostic fee per case can be kept low.

  Subsequently, in step S25, a primary diagnosis result display screen 81 as shown in FIG. On the primary diagnosis result display screen 81, a fine examination report display button 82 is displayed together with the image data 12, the request data 13, the patient data 14, and the diagnosis result column 42.

  The primary diagnosis result display screen 81 displays the result of the primary diagnosis, the patient's personal data, and other examination data. However, there is no information that should be kept confidential because the patient is visiting here. All information is displayed. When the fine inspection report display button 82 is clicked, a fine inspection report screen 91 shown in FIG. 12 is displayed. On this fine inspection report screen 91, a fine inspection result entry column 92 and a fine inspection report registration button 93 are displayed together with the image data 12, the request data 13, the patient data 14, and the diagnosis result column 42.

  In step S26, for example, the referral doctor performs a fine examination such as fluorescent fundus photographing, and then in step S27, enters the result in the fine examination result entry field 92 of the fine examination report screen 91. By clicking the inspection report registration button 93, the data for the detailed inspection is transmitted.

  In step S29, the management server 5 confirms that there is no deficiency in the data, then registers the result of the detailed examination in the medical care information database, and changes the status on the order management data verse to the precision examination reported / waiting confirmation. . In step S30, the requesting doctor of the requesting hospital 1 is notified by e-mail or the like that the detailed examination has been completed.

  In step S31, the requesting doctor of the requesting hospital 1 that has received the notification of the completion of the detailed examination accesses the management server 5 via the requesting doctor terminal 3, thereby performing a detailed examination report confirmation form 101 as shown in FIG. Is displayed. On this detailed inspection report confirmation form screen 101, a reexamination request button 102 and a request source confirmation button 103 are displayed together with image data 12, request data 13, patient data 14, a diagnosis result entry field 42, and a detailed inspection result entry field 92. Has been.

  In step S <b> 32, when the requesting doctor confirms the result of the detailed examination and clicks the request source confirmation button 103, the information is transmitted to the management server 5. In step S33, when the management server 5 receives the input of the request source confirmation button 103, the management server 5 updates the status to the end of the detailed examination in the order management database, and registers the result of the detailed examination report in the referral hospital database in step S34. Then, the distribution data of the detailed inspection report fee is registered in the referral hospital using the accounting database.

  Finally, in step S35, an e-mail notifying that the processing for this detailed examination has been completed is transmitted to the diagnosing doctor who made the diagnosis with the requesting hospital 1 and the referral destination hospital, and the precision that is the secondary diagnosis. Inspection is terminated.

  The results of detailed examination can be searched and viewed as a medical database, which is useful for future diagnosis. Furthermore, it can be used as a database for developing a CAD (computer automatic diagnosis) algorithm for fundus images at the time of medical examination, such as the false positive rate of medical examination (primary examination), etc. .

  The introduction hospital selection conditions in the above-described embodiment are the conditions set in advance in the management server 5, but the request medical terminal 3 uses the introduction hospital selection condition setting screen 111 as shown in FIG. It can also be set as the structure which can set the selection conditions of a hospital or a doctor.

  The introduction hospital selection condition setting screen 111 includes a selection condition priority list 112, a condition addition button 113, a condition deletion button 114, a priority change button 115, an apply button 116, and a cancel button 117. The priority order of the selection conditions can be set. For example, depending on your preference and convenience, whether there are necessary inspection facilities, specialized fields suitable for the primary diagnosis results, distance between the patient's address and hospital, and whether there is a doctor who performed the primary diagnosis, etc. The priority order can be set for each requesting hospital.

  In the requesting medical terminal 3, after changing the priority order on the setting screen 111 for the referral hospital selection condition, when the apply button 116 is clicked, the data is registered in the referral hospital database of the management server 5, and thereafter the management server 5 The referral hospital to be selected is selected according to this condition.

  Further, the requesting hospital 1 can set the hospital to be selected by the management server 5 using the introduction hospital selection screen 121 as shown in FIG. On the introduction hospital selection screen 121, an introduction hospital list 122, a hospital addition button 123, a hospital deletion button 124, a priority order change button 125, an apply button 126, and a cancel button 127 are displayed. Priorities can be set according to the date of medical treatment at the referral hospital.

  In the requesting medical terminal 3, after changing the priority order on the introduction hospital selection screen 121, when the apply button 126 is clicked, the data is registered in the secondary diagnosis facility database of the management server 5, and thereafter the introduction performed by the management server 5 is performed. As for the selection of the hospital, the hospital with the highest priority is selected.

It is a block diagram of an Example. It is a flowchart figure of a primary diagnosis request. It is explanatory drawing of a diagnosis request form screen. It is explanatory drawing of the setting screen of a diagnostician selection. It is explanatory drawing of a diagnosis request list screen. It is explanatory drawing of a diagnostic report screen. It is explanatory drawing of a diagnostic report confirmation note screen. It is a flowchart figure of a secondary diagnosis request. It is explanatory drawing of a referral patient primary diagnosis result data search screen. It is explanatory drawing of a referral patient detailed examination list screen. It is explanatory drawing of a primary diagnosis result display screen. It is explanatory drawing of a detailed inspection report screen. It is explanatory drawing of a detailed inspection report confirmation note screen. It is explanatory drawing of the setting screen of the introduction hospital selection conditions in another Example. It is explanatory drawing of the selection screen of the introduction hospital in other Example.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Request origin hospital 2 Fundus camera 3 Request medical terminal 4 Patient information database 5 Management server 6A, 6B, 6C Diagnostic medical terminal 7D, 7E Referral medical terminal 11 Diagnostic request form screen 12 Image data 13 Request data 14 Patient data 21 Diagnostic doctor selection Setting screen 31 Diagnosis request list screen 41 Diagnosis report screen 51 Diagnosis report confirmation letter screen 61 Referral patient primary diagnosis result data search screen 71 Referral patient detailed examination list screen 81 Primary diagnosis result display screen 91 Detailed examination report screen 101 Detailed examination Report Confirmation Screen 111 Referral Hospital Selection Condition Setting Screen 121 Referral Hospital Selection Screen

Claims (5)

  A database server storing medical information, primary diagnostic facility information, secondary diagnostic facility information, a requesting terminal connected to the database server, a diagnostic terminal connected to the database server, and test data from the requesting terminal Inspection data registration means for registering in the database server, display means for displaying the registered inspection data on the diagnostic terminal, and primary diagnosis result data including information indicating whether secondary diagnosis is necessary or not. And at least one of a plurality of secondary diagnosis facilities using a predetermined condition for the patient for which the secondary diagnosis is required in the primary diagnosis result data. Secondary diagnosis facility automatic selection means for selecting a secondary diagnosis facility, and the selected from the database server Linkage diagnostic apparatus characterized by having a notifying means for notifying at least one information of the secondary diagnosis facilities to the requesting terminal.   The cooperative diagnosis apparatus according to claim 1, wherein the requesting terminal has a secondary diagnosis facility selection condition setting unit capable of setting the predetermined condition.   Whether the predetermined condition is a diagnostic facility that has performed a primary diagnosis for the patient, or whether it is a diagnostic facility capable of performing secondary diagnostic items required in the patient's primary diagnosis result data Or at least one of the geographical conditions such as the distance between the patient address and the diagnostic facility, or the hospital visit time.   A database server storing medical information, primary diagnostic facility information, and secondary diagnostic facility information, a requesting terminal connected to the database server, a diagnostic terminal connected to the database server, and the requesting terminal including test data Priority registration means for registering the priority order of secondary diagnosis facilities in the database server for each requesting facility, inspection data display means for the diagnosis terminal to display the registered inspection data, and secondary diagnosis are required A diagnostic result data registration means for registering primary diagnosis result data including information indicating whether or not to the database server, and the database server for a patient in an examination that requires a secondary diagnosis in the primary diagnosis result data, Secondary diagnosis facility automatic selection means for selecting a secondary diagnosis facility according to the registered priority order, and the data Susaba linkage diagnostic apparatus characterized by having a notifying means for notifying the requesting terminal information of the selected diagnosis facilities.   The linkage diagnosis apparatus according to claim 1, wherein the database server has a charging database.

Images