JP2011181025A - Medical cooperation system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve security of medical examination information data shared in a medical cooperation system. <P>SOLUTION: In a regional medical cooperation system 100, a center server 1 transmits a confirmation request for user registration information of a cooperation destination doctor, to the terminal device of a cooperation source doctor before giving a user ID to the cooperation destination doctor and, when receiving an approval notification for the user registration information of the cooperation destination doctor from the terminal device of the cooperation source doctor, gives a user ID to the cooperation destination doctor to store the user ID in a storage part 13 together with the user registration information registered by the cooperation destination doctor. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a medical cooperation system.

  In recent years, with the development of medical technology, a framework for regional medical cooperation in which a plurality of medical facilities such as hospitals and clinics having specific functions cooperate to treat patients is becoming widespread.

  Medical information data such as medical image data, sample examination data, electronic medical record data, and interpretation reports are shared between medical facilities that are linked. Since medical information data is highly confidential information related to patient privacy, it is extremely important to prevent leakage of medical information data.

  Therefore, for example, Patent Literature 1 has a member information table in which the names and facility IDs of medical facilities and interpretation organizations that are members are stored, and the transmitted facility ID of each member is the facility in the member information table. A radiogram interpretation data management apparatus is described that determines whether access is from a member by collating with an ID, and permits access if the access is from a member.

JP 2008-29419 A

  By the way, in a system that issues a user ID to an accessible member and uses it for user authentication, such as the above-mentioned Patent Document 1, a user ID is normally issued based on user registration by a requester of registration, The user ID is delivered to the client as it is. Therefore, when user registration is performed by impersonation, there is a possibility that data is illegally used.

  An object of the present invention is to improve the security of medical information data shared in a medical cooperation system.

In order to solve the above-mentioned problem, the invention described in claim 1
A data management server comprising storage means for storing medical information shared by a cooperating doctor who requests medical cooperation with the cooperating doctor in association with a user ID and user registration information of the cooperating doctor, and the cooperating doctor Is connected to the link source terminal used by the communication device so that data can be transmitted and received via a communication network, and the data management server is configured to transfer the medical information data to the medical information data based on the user ID and user registration information stored in the storage unit. A medical cooperation system that performs access authentication,
The data management server transmits a confirmation request for the user registration information of the collaboration partner doctor to the collaboration source terminal before giving a user ID to the collaboration partner doctor, and the collaboration source terminal transmits the request of the collaboration partner doctor. When an approval notification of user registration information is received, a user ID is assigned to the collaborator and stored in the storage unit together with the user registration information.

The invention according to claim 2 is the invention according to claim 1,
The data management server receives a registration request e-mail in which a URL to a user registration screen for accessing the medical information data is described when the e-mail address of the cooperating doctor is received from the cooperating terminal. When the user registration information is input from the user registration screen corresponding to the URL, the input user registration information is the user registration information of the cooperation partner doctor. Is sent to the cooperation source terminal.

The invention according to claim 3 is the invention according to claim 2,
The e-mail for the registration request does not include the information on the cooperation partner doctor.

The invention according to claim 4 is the invention according to any one of claims 1 to 3,
The user registration information of the cooperation partner doctor includes a secret password predetermined between the cooperation source doctor and the cooperation destination doctor.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to improve the security of the medical treatment information data shared in a medical cooperation system.

It is a figure showing the whole community medical cooperation system composition in an embodiment of the invention. It is a block diagram which shows the functional structure of the center server of FIG. It is a block diagram which shows the functional structure of the terminal device of FIG. It is a figure which shows the flow of the user registration process which registers into a center server the user ID and user registration information of a cooperation destination doctor who can access the medical treatment information data transmitted to the center server of FIG. 1 from a cooperation former doctor. It is a figure which shows an example of the cooperation destination registration request screen for a cooperation former doctor to request | require cooperation destination doctor registration to a center server. It is a figure which shows an example of the registration request mail transmitted to the terminal device of a cooperation doctor. It is a figure which shows an example of the user registration screen for a cooperation doctor to perform user registration. It is a figure which shows an example of the confirmation request mail transmitted to the terminal device of a cooperation former doctor. It is a figure which shows an example of the registration confirmation screen for a cooperation former doctor to confirm user registration information. It is a figure which shows an example of the cooperation notification mail transmitted to the terminal device of a cooperation destination doctor.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. However, the scope of the invention is not limited to the illustrated examples.

[Configuration of regional medical cooperation system 100]
In FIG. 1, the system configuration | structure of the regional medical cooperation system 100 in this Embodiment is shown.
As shown in FIG. 1, a regional medical cooperation system 100 includes a center server 1 installed in a local data center, a terminal device 2A installed in a medical facility A, a PACS (Picture Archiving and Communication System) 3A, a medical facility. The terminal device 2B and the PACS 3B installed in B are configured. The number of medical facilities that can be connected to the regional medical cooperation system 100 is not limited to the illustrated example. Further, the number of terminal devices in each medical facility is not particularly limited.

The terminal device 2A and the PACS 3A of the medical facility A are connected to each other via a facility network 5A such as a LAN (Local Area Network) so that data can be transmitted and received between them. Of the devices connected to the in-facility network 5A, the terminal device 2A is connected to the center server 1 via the Internet N by a router 4A so that data can be transmitted and received.
Similarly, the terminal device 2B and the PACS 3B in the medical facility B are connected to each other via a facility network 5B such as a LAN so that data can be transmitted and received between them. Of the devices connected to the in-facility network 5B, the terminal device 2B is connected to the center server 1 via the Internet N by the router 4B so that data can be transmitted and received.

  Hereinafter, each apparatus which comprises the regional medical cooperation system 100 is demonstrated.

[Center server 1]
The center server 1 is a data management server that is installed in a data center and provides a medical cooperation service (cooperation service) between medical facilities. The cooperation service includes, for example, an interpretation request, a conference, an introduction, and the like from a doctor at one medical facility to a doctor at another medical facility. The requesting doctor who requested the medical cooperation is called the cooperation original doctor, and the requesting doctor who requested the medical cooperation is called the cooperation doctor.

FIG. 2 shows a functional configuration example of the center server 1.
As shown in FIG. 2, the center server 1 includes a control unit 11, a RAM 12, a storage unit 13, an operation unit 14, a display unit 15, a communication unit 16, a timing unit 17, and the like. Connected by.

The control unit 11 is configured by a CPU (Central Processing Unit) or the like, reads various programs including a system program stored in the storage unit 13, expands the program in the RAM 12, and executes various processes according to the expanded program. . For example, according to the program stored in the storage unit 13, the control unit 11 executes processing on the center server side in various processing including user registration processing described later.

  The RAM 12 temporarily stores a work area for temporarily storing various programs, input or output data, parameters, and the like that can be executed by the control unit 11 read from the storage unit 13 in various processes controlled by the control unit 11. Form.

The storage unit 13 includes an HDD (Hard Disk Drive), a semiconductor nonvolatile memory, or the like. The storage unit 13 stores various programs as described above. For example, in addition to the system program, the storage unit 13 performs a function as a Web server that provides various Web screens to the Web browser by communicating with the Web browser installed in the terminal devices 2A and 2B using the HTTP protocol. Web server program, a processing program for executing processing on the center server side in user registration processing described later, and the like are stored.

  The storage unit 13 stores medical information data transmitted from the user management table 131, the linkage information table 132, the medical information data table 133, the temporary registration table 134, the terminal devices 2A and 2B, and the like. Medical information data refers to information about a patient acquired in the course of medical treatment, and includes, for example, medical image data, specimen examination data, electronic medical record data, interpretation reports, pathological diagnosis reports, and the like.

The user management table 131 is a table for storing user registration information relating to a user who can request medical cooperation from another doctor as a cooperation source doctor using the cooperation service provided by the center server 1. The user management table 131 includes, for example, “user ID”, “password”, “facility name”, “clinic department”, “doctor name”, “address”, “phone number”, “mail address”, “folder path”. ”And the like, and user information data including information on these items is stored. The “mail address” is a mail address set in a terminal device used by the user for cooperation.
Here, the storage unit 13 of the center server 1 is provided with a folder for each user for storing medical information data transmitted via the terminal device so that the user can share it with the collaborator. The “folder path” included in the user information is information indicating the path to the user's folder.

The cooperation information table 132 is a table for storing data of a user ID (referred to as a cooperation destination user ID) and user registration information of a cooperation destination doctor that the user requested to cooperate in association with the user ID. The cooperation information table 132 includes, for example, “user ID (cooperation source)”, “cooperation destination user ID”, “cooperation destination password”, “secret password”, “name”, “address”, “phone number”, “ Items such as “email address” are provided.
The “cooperation destination user ID” is identification information for identifying the cooperation destination doctor who can access the medical information data transmitted from the doctor of the “user ID (cooperation source)”. When the same doctor becomes a cooperation destination for a plurality of different cooperation source doctors, a different cooperation destination user ID is assigned to each doctor. In the present embodiment, the cooperation destination user ID has a code system of “user ID of cooperation source doctor + sequence number”.
The “cooperation destination password” is a password registered by the cooperation destination doctor. The “secret password” is a secret password that is set in advance between the user and the partner doctor without using a communication network and cannot be known except by the parties concerned. “Facility name”, “Name”, “Address”, “Telephone number”, and “Email address” are the facility name of the medical facility to which the collaborating doctor belongs, the name, address, telephone number, and collaborating destination of the collaborating doctor, respectively. This is an e-mail address set in the terminal device used by the doctor for cooperation.

The medical information data table 133 is a table for storing information related to the medical information data transmitted from the cooperation source doctor in association with the medical information data. Specifically, the medical treatment information data table 133 includes “request ID”, “cooperation source information” (“user ID”, “facility name”, “doctor name”), “cooperation destination information” (“cooperation destination user ID”). ”,“ Cooperation destination password ”,“ facility name ”,“ doctor name ”),“ transmission date / time ”,“ patient name ”,“ file path ”, and the like.
“Request ID” is an identification ID issued each time a cooperation request is transmitted from a terminal device such as the terminal devices 2A and 2B.
“Cooperating source information” is information of the cooperating doctor who has transmitted the medical information data.
“Cooperation destination information” is information of a cooperation destination doctor who is permitted to view the medical treatment information data.
“Transmission date and time” is information indicating the date and time when the medical treatment information data is transmitted from the cooperating doctor.
The “file path” is information indicating a storage location of the medical information data file.

  The temporary registration table 134 is transmitted from the collaborating doctor in the user registration process described later, the user ID of the collaborating doctor and the information on the collaborating doctor, the URL of the user registration screen 252 (see FIG. 7), It is a table for temporarily registering the registered user registration information, the URL of the registration confirmation screen 253, and the like.

  The operation unit 14 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse, and includes a key pressing signal pressed by the keyboard and an operation signal by the mouse. Is output to the control unit 11 as an input signal.

  The display unit 15 includes a monitor such as a CRT (Cathode Ray Tube) or an LCD (Liquid Crystal Display), for example, and displays various screens according to instructions of display signals input from the control unit 11.

  The communication unit 16 includes a LAN (Local Area Network) adapter, a router, a TA (Terminal Adapter), and the like, and transmits and receives data to and from external devices such as the terminal devices 2A and 2B connected via the Internet N. .

  The timer unit 17 is configured by an RTC (Real Time Clock) or the like, and measures the current time and the current date and outputs them to the control unit 11.

[Configuration of Terminal Devices 2A and 2B]
The terminal devices 2A and 2B are computers equipped with Web browsers.
The terminal device 2A is a computer for cooperation for the doctor a of the medical facility A to perform medical cooperation with other doctors. That is, the doctor a of the medical facility A acquires the medical information data that the doctor a wants to share with the partner doctor from the PACS 3A and transmits it to the center server 1 or is stored in the center server 1 and accessible by the doctor a It is a computer for browsing.
Similarly, the terminal device 2B is a computer for cooperation for the doctor b of the medical facility B to perform medical cooperation with other doctors. That is, the doctor b of the medical facility B acquires medical information data to be shared with the partner doctor from the PACS 3B and transmits it to the center server 1 or is stored in the center server 1 and accessible by the doctor b. It is a computer for browsing.

  As shown in FIG. 3, the terminal devices 2A and 2B include a control unit 21, a RAM 22, a storage unit 23, an operation unit 24, a display unit 25, a communication unit 26, a clock unit 27, a printing unit 28, and the like. Each part is connected by a bus 29 or the like.

Functions of the control unit 21, RAM 22, storage unit 23, operation unit 24, display unit 25, communication unit 26, and timing unit 27 are the control unit 11, RAM 12, storage unit 13, operation unit 14 and display described in FIG. Since it is substantially the same as the part 15, the communication part 16, and the time measuring part 17, only a different part is demonstrated below.

  The control unit 21 is configured by a CPU or the like, expands various programs including a system program, a web browser, and e-mail software stored in the storage unit 23 to the RAM 22 and executes various processes according to the expanded program. .

The storage unit 23 includes an HDD (Hard Disk Drive), a semiconductor nonvolatile memory, or the like. As described above, the storage unit 23 stores various programs such as a system program executed by the control unit 21, a Web browser, and e-mail software, and various data.

  The printing unit 28 prints and outputs an image on a sheet based on the print data output from the control unit 21.

[Configuration of PACS3A, 3B]
PACS 3A and 3B are in-facility servers that store medical image data, specimen test data, and interpretation information data such as interpretation reports generated in a medical facility in association with patient information.

[Operation of regional medical cooperation system 100]
Next, referring to FIG. 4, in the regional medical cooperation system 100, the user ID and user registration information of the cooperation partner doctor who can access the medical treatment information data transmitted from the cooperation source doctor to the center server 1 are registered in the center server 1. The flow of user registration processing will be described.

  In the following description, a case where the doctor a of the medical facility A is a user of the cooperation service of the regional medical cooperation system 100 and the doctor b of the medical facility B is to be registered as a cooperation destination doctor will be described as an example. The operation of the terminal device 2A is executed in cooperation with the program stored in the control unit 21 and the storage unit 23 according to the operation of the operation unit 24 of the doctor a. The operation in the center server 1 is executed in cooperation with the control unit 11 and the program stored in the storage unit 13. The operation of the terminal device 2B is executed in cooperation with the program stored in the control unit 21 and the storage unit 23 according to the operation of the operation unit 24 of the doctor b.

  In the terminal device 2A of the doctor a who is the cooperation source, when the URL of the cooperation destination registration request screen 251 which is the Web screen for the cooperation destination registration request in the center server 1 is specified by the operation unit 24, the specified URL is displayed. , The cooperation destination registration request screen 251 is acquired from the center server 1 and displayed on the display unit 25. When the information on the doctor b, who is the partner doctor, is input from the cooperation destination registration request screen 251 by the operation unit 24, the registration request for the information on the doctor b that has been input is transmitted to the center server 1 by the communication unit 26 (Step S1). S1).

FIG. 5 shows an example of a cooperation destination registration request screen 251 displayed on the cooperation source terminal device. As shown in FIG. 5, in the cooperation destination registration request screen 251, a cooperation destination information input field 251 a for inputting information of a cooperation destination doctor (name, address, facility name, telephone number, e-mail address, secret password, etc.). And a registration request button 251b for requesting registration as a cooperation destination of the doctor input in the cooperation destination information input field 251a. When the cooperation destination information is input to the cooperation destination information input field 251a by the operation unit 24 and the registration request button 251b is pressed, the communication unit 26 transmits the information input to the cooperation destination information input field 251a to the center server 1. A user registration request is made. The secret password is a password that is determined in advance by a method that does not involve a network such as a telephone call or face-to-face contact with the doctor b who is the cooperation partner, and is a password that only the doctor a and the doctor b can know.
Here, the cooperation destination registration request screen 251 is a Web screen accessible only by the user of the cooperation service, and the center server 1 transmits a login screen to the terminal device 2A in advance before sending the cooperation destination registration request screen 251. It is assumed that the user ID of the doctor a is acquired and stored in the RAM 12 by performing user authentication.

  In the center server 1, when the communication unit 16 receives the doctor b information (including the email address of the doctor b) and the user registration request for the doctor b transmitted from the terminal device 2 </ b> A, the doctor a cooperation destination user registration is received. A user registration screen 252, which is a web screen for use, is generated and stored in the storage unit 13, and a registration request e-mail (registration request mail) in which a URL for accessing the user registration screen 252 is written is created Then, it is transmitted by the communication unit 16 to the email address of the doctor b (step S2). The doctor b information and the URL of the user registration screen 252 transmitted from the terminal device 2A are stored in the temporary registration table 134 in association with the user ID of the doctor a stored in the RAM 12.

  FIG. 6 shows an example of a registration request mail transmitted to the cooperation destination in step S2. As shown in FIG. 6, the registration request email includes information on the doctor a who is the cooperation source doctor and a URL for accessing the user registration screen 252.

  In the terminal device 2B of the doctor b, the registration request mail from the center server 1 is received by the communication unit 26, and the URL described in the registration request mail is designated by the operation unit 24, thereby accessing the URL. When the user registration screen 252 is acquired from the center server 1, the acquired user registration screen 252 is displayed on the display unit 25. When the user registration information (name, address, facility name, telephone number, e-mail address, secret password, password) of the doctor b is input from the user registration screen 252, the input user registration information of the doctor b is transmitted to the communication unit 26. Is transmitted to the center server 1 (step S3).

  FIG. 7 shows an example of a user registration screen 252 displayed on the terminal device 2B that is the cooperation destination. As shown in FIG. 7, on the user registration screen 252, user registration information for the collaborator to input his / her user registration information (name, address, facility name, telephone number, e-mail address, secret password, password). A registration request button 252b for requesting user registration with the contents input in the input field 252a and the user registration information input field 252a is provided. The password is a password used when the doctor b receives medical information data from the doctor a, and is a password that only the doctor b can know. When the user registration information is input to the cooperation destination information input field 252a by the operation unit 24 and the registration request button 252b is pressed, the user registration information registered in the center server 1 is transmitted by the communication unit 26.

  In the center server 1, when user registration information input from the user registration screen 252 is received by the communication unit 16, a registration confirmation screen 253 that is a Web screen for confirming user registration information is created and the storage unit 13. And a confirmation request electronic mail (confirmation request mail) in which a URL for accessing the registration confirmation screen 253 is described. Then, the communication unit 16 transmits the created confirmation request mail to the mail address of the doctor a stored in the user management table 131 (step S4). Note that the user registration information of the doctor b and the URL of the registration confirmation screen 253 transmitted from the terminal device 2B are temporarily associated with the user ID of the doctor a already registered and the information of the doctor b registered by the doctor a. It is stored in the registration table 134.

  FIG. 8 shows an example of the confirmation request mail transmitted to the cooperation destination in step S4. As shown in FIG. 8, the confirmation request email includes a confirmation request message of user registration information registered by the doctor b and the URL of the registration confirmation screen 253.

  In the terminal device 2A of the doctor a, when the confirmation request mail is received by the communication unit 26, the URL described in the confirmation request mail is specified by the operation unit 24, and the URL is accessed, the registration is performed in the display unit 25. A confirmation screen 253 is displayed. In the terminal device 2A, when the user a is confirmed by the doctor a and the registration approval button 253b or the registration denial button 253c on the registration confirmation screen 253 is pressed by the operation unit 24, a registration approval notification or A registration rejection notice is transmitted to the center server 1 by the communication unit 26 (step S5).

FIG. 9 shows an example of a registration confirmation screen 253 displayed on the terminal device 2A of the doctor a who is the cooperation source. As shown in FIG. 9, the registration confirmation screen 253 includes a registration content display field 253a for displaying the content registered by the collaborating doctor b and registration for notifying the center server 1 that the registration is approved. An approval button 253b and a registration denial button 253c for notifying the center server 1 of denial of registration are provided. When the registration approval button 253 b is pressed by the operation unit 24, a notification indicating registration approval is transmitted to the center server 1 by the communication unit 26. When the registration denial button 253c is pressed by the operation unit 24, a notification indicating registration denial is transmitted to the center server 1 by the communication unit 26.
The doctor a can check whether the registered name, address, facility name, telephone number, e-mail address, and secret password are correct by referring to the registered content display field 253a. For example, when a doctor a inputs an incorrect e-mail address from the cooperation destination registration request screen 251 or when an e-mail content is leaked on the Internet, a third party other than the doctor b accesses the URL of the user registration screen 252. When the user registration is performed, the doctor a can recognize the fact by referring to the registration content display field 253a. Therefore, by denying the registration, a third party other than the doctor b illegally treats the medical information data. Access can be prevented.

In the center server 1, when the communication unit 16 receives a notification from the terminal device 2A, it is determined whether the received notification is an approval notification or a denial notification (step S6). If it is determined that the received notification is an approval notification (step S6; Y), the cooperation destination user ID is given to the doctor b, and the user ID of the doctor a who is the cooperation source is stored in the temporary registration table 134. The cooperation destination user ID assigned to the doctor b and the user registration information of the doctor b are stored in the cooperation information table 132 (step S7). Data in the temporary registration table 134 is deleted.
When the user ID and the user registration information of the doctor b are stored in the cooperation information table 132, the doctor a transmits medical information data that allows the doctor b to browse to the center server 1 via the terminal device 2A. It becomes possible to make a storage request to the center server 1. In the center server 1, when the medical information data whose cooperation destination is the doctor b is received from the terminal device 2 </ b> A, the received medical information data is stored in the storage unit 13, and as the cooperation source information of the medical information data The information of the doctor b is registered in the medical care information data table 133 as the cooperation destination information.

  In the center server 1, when the user registration of the doctor b in the cooperation information table 132 is completed, a cooperation notification mail in which a cooperation destination user ID given to the doctor b, a URL for logging in to the cooperation service, and the like is described is created. Then, it is transmitted to the email address of the doctor b by the communication unit 16 (step S8).

  FIG. 10 shows an example of the cooperation notification mail transmitted to the cooperation destination in step S8. As shown in FIG. 10, the cooperation notification mail includes a cooperation destination user ID assigned to the doctor b, a URL for logging in to a browsing menu of medical information data among cooperation services, and the like.

  In the terminal device 2B, when the cooperation notification mail is received and the URL described in the cooperation notification mail is accessed by the operation unit 24, a login screen for the cooperation service is displayed on the display unit 25. When the cooperation destination user ID and password are input from the login screen by the operation unit 24, the input cooperation destination ID and password are transmitted to the center server 1 by the communication unit 26 (step S9).

  In the center server 1, access authentication is performed based on the cooperation destination user ID and password received from the terminal device 2B (step S10). That is, the received cooperation destination user ID and password are collated with the cooperation destination user ID and password of the record stored in the cooperation information table 132, and when there is a matching record, the received information is received in the medical treatment information data table 133. Access to medical information data associated with the cooperation destination user ID is permitted. If no matching record exists, access is not allowed.

  On the other hand, if it is determined that the received notification is a denial notification (step S6; N), the data temporarily registered in the temporary registration table 134 is discarded (step S11).

  As described above, according to the regional medical cooperation system 100, the center server 1 sends a confirmation request for the user registration information of the cooperation partner doctor before giving the user ID to the cooperation doctor. When the user registration information approval notification of the cooperation partner doctor is received from the terminal device of the cooperation source doctor, the user ID is given to the cooperation destination doctor and stored together with the user registration information registered from the cooperation destination doctor. Store in the unit 13.

  Therefore, even if a third party other than the partner doctor performs the user registration while pretending to be the partner doctor, it is possible to prevent the user ID from being given based on the user registration information. It is possible to prevent unauthorized access to medical information data by third parties and improve the security of medical information data.

  Specifically, the center server 1 receives a registration request in which a URL to the user registration screen 252 for accessing the medical information data is described when the mail address of the cooperation partner doctor is received from the terminal device of the cooperation source. When the user registration information is input from the user registration screen 252 corresponding to the URL, the user registration information is input to the email address of the cooperation partner doctor. A confirmation request as to whether or not the user registration information of the collaborator is sent to the terminal device of the collaborator. Therefore, the cooperation former doctor can easily confirm the user registration information of the cooperation destination doctor.

  In addition, since the registration request email does not include information about the partner doctor, even if a registration request email is received by a third party other than the partner, It becomes possible to make it impossible to specify and register the doctor's information.

  In addition, since the user registration information to be registered by the partner doctor includes a secret password predetermined between the partner doctor and the partner doctor, a third party other than the partner doctor temporarily Even if registration is performed, the fact is easily recognized by the collaborator and the user registration can be invalidated.

  In addition, the description content in the said embodiment is a suitable example of this invention, and is not limited to this.

  For example, in the above embodiment, the password is used as the means for identifying the person, but biological information such as a fingerprint and an iris may be used.

  In the above description, an example in which an HDD, a semiconductor nonvolatile memory, or the like is used as a computer-readable medium for the program according to the present invention is disclosed, but the present invention is not limited to this example. As another computer-readable medium, a portable recording medium such as a CD-ROM can be applied. Further, a carrier wave is also applied as a medium for providing program data according to the present invention via a communication line.

  In addition, the detailed configuration and detailed operation of each device constituting the regional medical cooperation system 100 can be changed as appropriate without departing from the spirit of the invention.

100 regional medical cooperation system 1 center server 11 control unit 12 RAM
13 Storage Unit 131 User Management Table 132 Cooperation Information Table 133 Medical Information Data Table 134 Temporary Registration Table 14 Operation Unit 15 Display Unit 16 Communication Unit 17 Timekeeping Unit 18 Bus 2A, 2B Terminal Device 21 Control Unit 22 RAM
23 storage unit 24 operation unit 25 display unit 251 cooperation destination registration request screen 252 user registration screen 253 registration confirmation screen 26 communication unit 27 timing unit 28 printing unit 29 bus 3A, 3B PACS
4A, 4B Router 5A, 5B Facility network N Internet

Claims (4)

A data management server comprising storage means for storing medical information shared by a cooperating doctor who requests medical cooperation with the cooperating doctor in association with a user ID and user registration information of the cooperating doctor, and the cooperating doctor Is connected to the link source terminal used by the communication device so that data can be transmitted and received via a communication network, and the data management server is configured to transfer the medical information data to the medical information data based on the user ID and user registration information stored in the storage unit. A medical cooperation system that performs access authentication,
The data management server transmits a confirmation request for the user registration information of the collaboration partner doctor to the collaboration source terminal before giving a user ID to the collaboration partner doctor, and the collaboration source terminal transmits the request of the collaboration partner doctor. The medical cooperation system which gives a user ID to the cooperation doctor and stores it in the storage unit together with the user registration information when an approval notification of the user registration information is received.   The data management server receives a registration request e-mail in which a URL to a user registration screen for accessing the medical information data is described when the e-mail address of the cooperating doctor is received from the cooperating terminal. When the user registration information is input from the user registration screen corresponding to the URL, the input user registration information is the user registration information of the cooperation partner doctor. The medical cooperation system of Claim 1 which transmits the confirmation request | requirement of whether it is to the said cooperation origin terminal.   The medical cooperation system according to claim 2, wherein the registration request electronic mail does not include information of the cooperation partner doctor. The medical cooperation system according to any one of claims 1 to 3, wherein the user registration information of the cooperation partner doctor includes a secret password predetermined between the cooperation source doctor and the cooperation partner doctor.

Images