JP2013114289A - Data management server and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce time and labor in registration procedures for starting medical cooperation between users belonging to the same medical facility.SOLUTION: For registering a new user, a center server 1 searches a user management table 131 for users belonging to the same medical facility as the new user, and stores user registration information of the extracted users as cooperation destination information in a cooperation destination information table 132 in association with a user ID of the new user.

Description

  The present invention relates to a data management server and a program.

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

  Medical doctor data such as medical image data, specimen examination data, electronic medical record data, and interpretation reports are shared among doctors who cooperate with each other, and interpretation requests, introductions, conferences, and the like are performed. As a system for realizing such medical cooperation on the network, the doctor requesting the cooperation uploads the request contents and medical information data to the center server, and the doctor who is requested to cooperate accesses the center server. Thus, a system that enables acquisition of request contents and medical information data has been proposed.

In such a medical cooperation system, cooperation is started after obtaining approval from both doctors. For example, Patent Document 1 describes that the following procedures (1) to (5) are performed when starting cooperation.
(1) The doctor a requesting cooperation accesses the server and inputs the name, facility name, mail address, etc. of the doctor b who is the cooperation destination.
(2) Notifying doctor b by e-mail that the system server will start cooperation, and requesting registration as a cooperation destination.
(3) When the doctor b permits cooperation, his / her information is registered in the server.
(4) The server requests the doctor a to confirm the registration information of the doctor b by e-mail.
(5) The doctor a confirms the registration information of the doctor b, and notifies the server of cooperation approval or denial.
(6) When approval is obtained from the doctor a, cooperation from the doctor a to the doctor b is started.
When a request for cooperation is made from the doctor b to the doctor a, the procedure is performed separately for the doctors a and b in (1) to (5) above.

JP 2011-181025 A

  The medical cooperation system described in Patent Document 1 is based on the premise of cooperation between doctors at other facilities, so that cooperation with a desired partner can be started with certainty and so as not to cooperate with a wrong partner. In addition, it is a mechanism for performing the cooperation procedure while stepping one step at a time. Therefore, it is necessary to follow the same procedure when there is a need for cooperation between doctors in the same medical facility.

  For example, a doctor A1 of a hospital A concurrently serves as another hospital B, and works at the hospital B depending on the day of the week. When an image or the like that the doctor A1 wants to see on the day of the week when A1 is absent in the hospital A is generated, the doctor A2 of the hospital A will be linked to the doctor A1, but the doctor A2 can be linked to the doctor A1. In order to achieve this, first, it is necessary to follow the cooperation procedures (1) to (5) described above.

In addition, there is a case where the doctor A1 himself / herself wants to examine an image of interest in the hospital A while working at the hospital B. In this case, if oneself is registered as a cooperation destination, the image can be acquired by accessing the server. However, in order to do so, it is necessary to follow the cooperation procedures (1) to (5) with the self as the cooperation destination.
Note that a doctor belongs to a medical facility, and when one doctor also serves as a plurality of medical facilities, a user ID, a password, and the like are assigned to access the server for each medical facility.

  Users (doctors) in the same medical facility know each other's e-mail addresses, and e-mail exchanges should be natural. Medical information data is also shared within the same medical facility. However, when it was time to introduce the system and start cooperation, it was cumbersome because it was necessary for the doctors to perform complicated procedures such as (1) to (5) above.

  The subject of this invention is reducing the effort of the registration procedure for a cooperation start, when performing medical cooperation between the users in the same medical facility.

In order to solve the above-mentioned problem, the invention described in claim 1
User registration means for registering user registration information including user identification information and facility identification information of the medical facility to which the user belongs, storage means for storing medical care information data transmitted from the registered user, and registered user Based on a cooperation destination registration request from the user, cooperation destination registration means for storing the cooperation destination information about the cooperation destination user designated as the cooperation destination by the user in the storage means in association with the identification information of the user, Data for providing access right to the medical information data transmitted from the user stored in the storage unit based on cooperation destination information stored in association with the user identification information in the storage unit A management server,
When a new user is registered by the user registration unit, the storage unit is searched for a user belonging to the same medical facility as the new user, and the user registration information of the extracted user is used as cooperation destination information for the new user. An automatic cooperation destination registration unit is provided that is stored in the storage unit in association with the identification information.

The invention according to claim 2 is the invention according to claim 1,
The automatic cooperation destination registration means further stores the user registration information of the new user as cooperation destination information in association with the extracted user identification information in the storage means.

The invention according to claim 3 is the invention according to claim 1,
A setting unit for each user to set whether to permit registration by the automatic cooperation destination registration unit;
The automatic cooperation destination registration means permits registration by the automatic cooperation destination registration means belonging to the same medical facility as the new user when the new user permits registration of the cooperation destination by the automatic cooperation destination registration means. The user registration information of the user who is doing this is stored in the storage means in association with the identification information of the new user as cooperation destination information.

The invention according to claim 4 is the invention according to claim 3,
The automatic cooperation destination registration means is further configured to extract the user registration information of the new user as cooperation destination information when the new user permits registration of a cooperation destination by the automatic cooperation destination registration means. Among them, the information is stored in the storage unit in association with the identification information of the user permitted to register by the automatic cooperation destination registration unit.

The invention according to claim 5 is the invention according to claim 3 or 4,
The automatic cooperation destination registration means is a user who permits registration by the automatic cooperation destination registration means among users belonging to the same medical facility as the user based on a request from the user, and the user registration information is User registration information of users not stored in the storage means is extracted in association with the requested user identification information as cooperation destination information, and within the same medical facility as the requested user based on the extracted user registration information A list of unlinked users is generated and displayed on the terminal device of the user, and when the user permits registration by the automatic cooperation destination registration means, the list of unlinked users is created by the user terminal device. The user registration information of the user selected from the above is used as the cooperation destination information in the identification information of the requested user. Is stored in the storage means with response.

The invention according to claim 6 is the invention according to claim 5,
The automatic cooperation destination registration means further stores the user registration information of the requested user in the storage means in association with the selected user identification information as cooperation destination information.

The program of the invention described in claim 7 is:
User registration means for registering user registration information including user identification information and facility identification information of the medical facility to which the user belongs, storage means for storing medical care information data transmitted from the registered user, and registered user Based on the cooperation destination registration request from the user, cooperation destination registration means for associating the cooperation destination information about the cooperation destination user designated as the cooperation destination by the user with the identification information of the user and storing it in the storage means, Data for providing access right to the medical information data transmitted from the user stored in the storage unit based on cooperation destination information stored in association with the user identification information in the storage unit The computer used for the management server
When a new user is registered by the user registration unit, the storage unit is searched for a user belonging to the same medical facility as the new user, and the user registration information of the extracted user is used as cooperation destination information for the new user. It is made to function as an automatic cooperation destination registration unit that is stored in the storage unit in association with the identification information.

  ADVANTAGE OF THE INVENTION According to this invention, when performing medical cooperation between users in the same medical facility, it becomes possible to reduce the effort of the registration procedure for starting cooperation.

It is a figure showing the whole 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 flowchart which shows the cooperation destination registration process performed in a medical cooperation system. It is a flowchart which shows the automatic cooperation process at the time of user registration performed in a medical cooperation system. It is a flowchart which shows the in-facility cooperation setting process performed in a medical cooperation system. It is a flowchart which shows the in-facility cooperation setting process performed in a medical cooperation system. It is a figure which shows an example of an in-facility cooperation setting screen. It is a figure which shows an example of an acquisition screen. It is a figure which shows an example of a cooperation destination selection screen. It is a figure which shows an example of the transmission / reception log | history screen.

  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 Medical Cooperation System 100]
In FIG. 1, the system configuration | structure of the medical cooperation system 100 in this Embodiment is shown.
As shown in FIG. 1, a medical cooperation system 100 is installed in a center server 1 installed in a data center, a terminal device 2A installed in a medical facility A, a PACS (Picture Archiving and Communication System) 3A, and a medical facility B. The terminal device 2B and the PACS 3B are configured. In addition, the number of medical facilities which can be connected to the medical cooperation system 100 should just be plural, and is not limited to the example of illustration. 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 as to be able to transmit and receive data.
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 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 various support services to medical facilities and doctors who are users. Examples of the support service include a data backup service in a medical facility, a content distribution service, a medical cooperation service (cooperation service), and the like. The cooperation service includes, for example, mediation on a network of medical cooperation such as an interpretation request from one doctor to another doctor, a conference, and an introduction.

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 time measuring 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 a process on the center server side of a cooperation destination registration process, a user registration automatic cooperation process, and an in-facility cooperation setting process described later. Thereby, functions as a cooperation destination registration unit, a user registration unit, a cooperation destination automatic registration unit, and a setting unit are realized.

  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 functions as a Web server that provides various Web screens to the Web browser by communicating with a Web browser installed in the terminal device such as the terminal devices 2A and 2B using the HTTP protocol. Server program for executing the program, and a program for executing the processing on the center server side of the cooperation destination registration process, the automatic cooperation process at the time of user registration, and the in-facility cooperation setting process described later in cooperation with the Web server program Has been.

  The storage unit 13 stores a facility management table 130, a user management table 131, a cooperation destination information table 132, a transmission / reception history table 133, a temporary registration table 134, and medical information information transmitted from the user. 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 facility management table 130 is a table for storing facility registration information of medical facilities contracted to receive support services from the center server 1. In the facility management table 130, for example, items such as “facility ID (facility identification information)”, “facility name”, “location”, “representative telephone number”, and the like are provided. Stores registration information data.

The user management table 131 is a table for storing user registration information of users who can use the support service provided by the center server 1. The user management table 131 includes, for example, “user ID (user identification information)”, “password”, “facility ID”, “clinical department”, “doctor name”, “address”, “phone number”, “mail address”. ”,“ Folder path ”,“ Automatic linkage flag ”,“ Registration number ”, and the like, and user registration information data including information on these items is stored. “Automatic cooperation flag” indicates whether or not to permit the user in the same medical facility (abbreviated as the same facility) to be automatically registered as a cooperation destination user (referred to as a cooperation destination user) (referred to as automatic cooperation). It is a flag indicating that. Here, “OFF” indicates that automatic cooperation is not permitted, and “ON” indicates that automatic cooperation is permitted. The “registration number” is an identification number uniquely assigned to the user.
Further, 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 cooperation destination user. “Folder path” included in the user information is information indicating a path to the folder of the user.
Note that the user ID and password of the user management table 131 are used as the cooperation destination user ID, the cooperation destination password, the transmission source user ID, and the transmission destination user ID described below.

  The cooperation destination information table 132 is associated with the user ID, and the user ID (referred to as the cooperation destination user ID) and the cooperation destination information (the user registration information are predetermined) of the cooperation destination user designated as the cooperation destination by the user. This is a table for storing data having items. In the cooperation destination information table 132, for example, “user ID (cooperation source)”, “cooperation destination user ID”, “cooperation destination password”, “name”, “address”, “phone number”, “mail address”, etc. Items are provided.

The transmission / reception history table 133 is a table for storing history information of transmission / reception of cooperation requests and responses between the user and the cooperation destination.
The transmission / reception history table 133 includes, for example, “request ID”, “transmission source information” (“transmission source facility ID”, “transmission source facility name”, “transmission source user ID”, “transmission source user name”), “ "Destination Information"("Destination Facility ID", "Destination Facility Name", "Destination User ID", "Destination User Name"), "Send Date", "Patient Name", "Classification", "Title" ”,“ Comment ”,“ request / reply category ”,“ file path ”, and the like.
“Request ID” is identification information issued each time a cooperation request is transmitted from the user. The cooperation request is a request for medical cooperation (interpretation request, introduction, conference, etc.) to a cooperation destination user selected from cooperation destination users registered in advance as cooperation destinations.
A series of data sent and received between the requesting user and the cooperation destination after the cooperation request (for example, medical information data sent together with the cooperation request from the requesting user, sent as a reply from the cooperation destination to the requesting user) The medical information data) is managed with the same request ID.
“Transmission source information” is information of a transmission source. For example, when medical information data is transmitted from the requesting user of the cooperation request to the cooperation destination, it is the information of the requesting user, and the medical information data (edited medical information data or When new medical information data or the like is transmitted, the information is information on the cooperation destination.
“Transmission destination information” is information about the transmission destination of the medical information data designated by the transmission source. That is, the transmission destination is a user who is permitted to access the medical information data transmitted from the transmission source (to which the access right is given). For example, the transmission destination information is information on the cooperation destination when the user requesting the cooperation request transmits the medical information data to the cooperation destination, and the medical information data is transmitted from the cooperation destination to the requesting user as a reply. Is information of the requesting user.
“Category” is information indicating the classification of request contents. In the present embodiment, the classification includes conference (public), interpretation request, lung cancer screening, examination request, introduction, and the like.
“Title” is a title given by the transmission source of the medical information data. “Comment” is a comment to the transmission destination input by the transmission source. The “request / reply category” is information indicating a category of whether the request is a cooperation request or a reply. The “file path” is information indicating the storage location of the medical information data file.

  The temporary registration table 134 includes a user ID of a user who has requested cooperation registration, information on a cooperation destination user, a URL of a cooperation destination registration screen, cooperation destination registration information transmitted from the cooperation destination user, and registration in a cooperation registration process described later. It is a table for temporarily registering the URL and the like of the approval screen.

  The storage unit 13 stores display data for displaying various screens transmitted to the client such as the terminal device 2A and the terminal device 2B in the support service.

  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 provided in the medical facility A. The medical device A doctor obtains medical information data that the doctor in the medical facility A wants to share with the cooperation destination from the PACS 3A and transmits it to the center server 1, or the center server 1 and the PACS 3A. Is a computer for browsing medical information data that can be accessed by the doctor.
Similarly, the terminal device 2B is a computer provided in the medical facility B. The doctor of the medical facility B acquires medical information data that the medical facility B wants to share with the cooperation destination from the PACS 3B and transmits it to the center server 1, 1 or a computer for browsing medical information data stored in the PACS 3B and accessible by the doctor.

  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 programs. .

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 electronic 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]
The PACSs 3A and 3B are in-facility servers that store medical information data generated in the medical facility, such as medical image data, specimen test data, and interpretation reports, in association with patient information.

[Operation of Medical Cooperation System 100]
In the medical cooperation system 100, when a user wants to make a cooperation request such as interpretation request, introduction, conference, etc. to another user, the other user needs to be registered in advance as a cooperation destination user. This is because, among the registered cooperation destination users, only the user designated for each cooperation request can access the user's folder, and exchange of medical information data can be performed.
In the medical cooperation system 100 according to the present embodiment, the mutual approval between the cooperation source user and the cooperation destination user who intends to register the cooperation destination is basically acquired by the cooperation destination registration process shown in FIG. The cooperation destination registration is performed as described above. For the cooperation with the users in the same facility, the user registration automatic cooperation processing shown in FIG. 5 and the in-facility cooperation setting processing shown in FIGS. It is possible to automatically register the link destination.

(Cooperation destination registration process)
First, the flow of the cooperation destination registration process will be described with reference to FIG.
In the description of FIG. 4, a user who intends to perform cooperation registration (cooperation source user) is described as a user of the medical facility A, and a user of the cooperation destination is a user of the medical facility B. However, the present invention is not limited to this. For example, the cooperation source user and the cooperation destination user may belong to the same facility. Further, the terminal device used by the cooperation source user is described as the terminal device 2A, and the terminal device used by the cooperation destination user is described as the terminal device 2B. However, since the communication with the center server 1 is performed via the Web screen, the Web browser The terminal device is not particularly limited as long as the terminal device is installed.

  The operation of the terminal device 2A shown in FIG. 4 is executed by the cooperation of the control unit 21 and the program stored in the storage unit 23 according to the operation of the operation unit 24 by the cooperation source user. The operation in the center server 1 is executed in cooperation with the control unit 11 and a program stored in the storage unit 13. The operation of the terminal device 2B is executed by the cooperation of the control unit 21 and the program stored in the storage unit 23 according to the operation of the operation unit 24 by the cooperation destination user.

First, in the terminal device 2A, the operation unit 24 inputs user authentication information such as the facility ID, user ID, and password of the medical facility A from the portal site for providing the support service in the center server 1, and instructs to log in to the cooperation service. Then, the input user authentication information and the login request to the cooperation service are transmitted to the center server 1 by the communication unit 26 (step S1).
In the center server 1, when the communication unit 16 receives the authentication information and the login request to the cooperation service, the login authentication is performed (step S2). That is, in the user management table 131, user registration information having a facility ID, a user ID, and a password that match the input authentication information (here, a facility ID, a user ID, and a password) is searched. If user registration information having a facility ID, user ID, and password that matches the input authentication information does not exist in the user management table 131, a login error is notified to the terminal device 2A. If user registration information having a facility ID, user ID, and password that matches the input authentication information exists in the user management table 131, the authentication information of the login user and the IP address of the terminal device 2A as the transmission source are temporarily stored in the RAM 12. At the same time, the initial screen of the cooperation service is read from the storage unit 13 and transmitted to the terminal device 2A by the communication unit 16 (step S3). The initial screen of the linked service is a screen for selecting a menu. For example, menus such as cooperation registration, in-facility cooperation setting, display of cooperation transmission / reception history, and cooperation request can be selected.

  In the terminal device 2 </ b> A, when the initial screen of the cooperation service is received by the communication unit 26, the received initial screen is displayed on the display unit 25. When cooperation destination registration is selected from the menu on the initial screen displayed by the operation unit 24, a cooperation destination registration request is transmitted to the center server 1 by the communication unit 26 (step S4).

  In the center server 1, when the communication destination 16 receives the cooperation destination registration request from the terminal device 2A, the cooperation destination designation screen is read from the storage unit 13 and transmitted to the terminal device 2A by the communication unit 16 ( Step S5). The cooperation destination designation screen includes an input field for inputting information of the cooperation destination user such as the name and mail address of the cooperation destination user, and a registration request button for instructing to send a registration request to the center server 1. Etc. are provided on the screen.

  In the terminal device 2 </ b> A, when the cooperation destination designation screen is received from the center server 1 by the communication unit 26, the received cooperation destination designation screen is displayed on the display unit 25. When information of a cooperation destination user is input from the cooperation destination designation screen by the operation unit 24 and the registration request button is pressed, a registration request for the input information of the cooperation destination user is transmitted to the center server 1 by the communication unit 26. (Step S6).

In the center server 1, when the communication unit 16 receives the cooperation destination registration request and the information of the cooperation destination user transmitted from the terminal device 2A, a cooperation destination registration screen that is a Web screen for login user cooperation destination registration is displayed. A registration request e-mail (registration request e-mail) in which a URL for accessing the cooperation destination registration screen is described is created and stored in the storage unit 13. It is transmitted to the mail address (step S7). Here, it is assumed that an e-mail addressed to the e-mail address of the cooperation destination user can be browsed from the terminal device 2B.
The cooperation destination user information and the cooperation destination registration screen URL transmitted from the terminal device 2 </ b> A are stored in the temporary registration table 134 in association with the user ID of the login user stored in the RAM 12.

  In the terminal device 2B of the cooperation destination user, 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 cooperation destination registration screen is acquired from the center server 1, the acquired cooperation destination registration screen is displayed on the display unit 25. On the cooperation destination registration screen, the cooperation source user name, a message that the cooperation destination information must be entered when approving the cooperation with this user, and the cooperation destination user (the user ID, password, An input field for inputting a registration number, name, address, facility name, etc.) and a registration approval button for instructing to transmit the input information to the center server 1 are provided. When cooperation destination information (user ID, password, registration number, name, address, facility name, etc.) is input from the cooperation destination registration screen and the registration approval button is pressed, the input cooperation destination information is transmitted by the communication unit 26. It is transmitted to the center server 1 (step S8).

  In the center server 1, when the communication destination 16 receives the cooperation destination information input from the cooperation destination registration screen, a registration approval screen, which is a web screen for approval of the cooperation destination information by the cooperation source, is created and stored. An approval request electronic mail (approval request mail) in which the URL for accessing the registration approval screen is described is created. Then, the created approval request mail is transmitted to the mail address of the login user stored in the user management table 131 by the communication unit 16 (step S9). Note that the cooperation destination information of the cooperation destination user and the URL of the registration approval screen transmitted from the terminal device 2B are associated with the user ID of the login user already registered and the information of the cooperation destination user registered by the login user. It is stored in the temporary registration table 134.

  In the terminal device 2A, when the approval request mail is received by the communication unit 26, the URL described in the approval request mail is specified by the operation unit 24, and the URL is accessed, the registration approval screen is displayed on the display unit 25. Is displayed. On the registration approval screen, cooperation destination information (name, address, facility name, registration number, etc. of the cooperation destination user) transmitted from the cooperation destination user is displayed. In the terminal device 2A, when the cooperation destination registration content is confirmed by the login user who is the cooperation source user, and the registration approval button or the registration rejection button on the registration confirmation screen is pressed by the operation unit 24, registration is performed according to the pressed button. An approval notification or a registration rejection notification is transmitted to the center server 1 by the communication unit 26 (step S10).

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 S11). If it is determined that the received notification is an approval notification (step S11; YES), the link destination user's ID stored in the user management table 131 is associated with the user ID of the login user who is the link source user. Information on predetermined items of user registration information corresponding to the user ID is stored in the cooperation destination information table 132 (step S12). Data in the temporary registration table 134 is deleted. Then, a registration completion notification is transmitted to the terminal device 2A by the communication unit 16 (step S13), and the cooperation destination registration process ends.
On the other hand, if it is determined that the received notification is a denial notification (step S11; NO), the data temporarily registered in the temporary registration table 134 is discarded (step S14), and the cooperation destination registration process ends.

  When the user registration information of the cooperation destination user is stored as the cooperation destination information of the logged-in user in the cooperation destination information table 132, the information is linked to the list 261a of the cooperation destination selection screen 261 (see FIG. 9) of the previous cooperation source user. Since the previous user is displayed, the cooperation source user can make a cooperation request to the cooperation destination user. A specific method of requesting cooperation will be described later.

In the conventional medical facility system, the cooperation destination user is registered by the cooperation registration process shown in FIG. 4 regardless of whether or not the medical facility to which the cooperation destination user belongs is the same as the cooperation source user. However, if the doctors in the same facility originally share the medical information data in the facility, and the doctors in the facility want to cooperate using this system, the above-described cooperation registration process is bothered. Is cumbersome and it takes time to start cooperation.
Therefore, in the medical cooperation system 100 according to the present embodiment, automatic cooperation processing at the time of user registration and in-facility cooperation setting processing described below can be executed, and cooperation destination information is linked with users in the same facility. It is possible to request cooperation without complicated procedures such as inputting in the original, approving the cooperation at the cooperation destination and entering the cooperation destination information, or approving the cooperation destination information registered by the cooperation destination at the cooperation source. To.

(Automatic linkage process during user registration)
First, the flow of automatic cooperation processing at the time of user registration will be described with reference to FIG.
In the description of FIG. 5, a case where a doctor who has not yet performed user registration for the support service of the center server 1 in the medical facility A will be described as a new user registration, but the same applies to the medical facility B. The terminal device for performing user registration is not particularly limited as long as it has a Web browser, but here it will be described as being the terminal device 2A.
The operation of the terminal device 2 </ b> A is executed by the cooperation of the control unit 21 and the program stored in the storage unit 23 according to the operation of the operation unit 24. The operation in the center server 1 is executed in cooperation with the control unit 11 and a program stored in the storage unit 13.

  First, in the terminal apparatus 2A, when the facility ID of the medical facility A is input from the portal site for providing the support service in the center server 1 by the operation unit 24 and a new user registration is instructed, the input is performed by the communication unit 26. The facility ID and the user registration screen display request are transmitted to the center server 1 (step S21). In the center server 1, when the facility ID and the user registration screen display request are received by the communication unit 16, the facility ID and the IP address of the terminal device 2 </ b> A of the transmission source are temporarily stored in the RAM 12 and from the storage unit 13. The user registration screen is read and transmitted to the terminal device 2A by the communication unit 16 (step S22).

  In the terminal device 2 </ b> A, when the user registration screen is received by the communication unit 26, the user registration screen is displayed on the display unit 25. The user registration screen includes, for example, an input field for inputting information of user registration information items (other than “user ID”, “folder path”, “automatic linkage flag”, and “registration number”) in the user management table 131. This is a screen provided with a registration button or the like for instructing registration with the input contents. When user registration information is input from the displayed user registration screen by the operation unit 24 and registration is instructed, the user registration information is transmitted to the center server 1 by the communication unit 26 (step S23).

  In the center server 1, when user registration information is received from the terminal device 2 </ b> A by the communication unit 16, a user ID and registration number are issued, and the issued user ID and registration are stored in the user management table 131 of the storage unit 13. The number and the received user registration information are stored. Also, a registered user-specific folder is created in the storage unit 13, and the folder path is added to the user registration information (step S24). When the user registration is completed, in the center server 1, the automatic cooperation setting screen is read from the storage unit 13 and transmitted to the terminal device 2A by the communication unit 16 (step S25). The automatic cooperation setting screen is, for example, a message such as “Do you want to automatically start cooperation with users in the facility?” And a “permit” button for notifying the center server 1 of permission, permission This is a screen on which a “no permission” button for notifying the center server 1 of the fact that it is not to be displayed is displayed.

  In the terminal device 2 </ b> A, when the automatic cooperation setting screen is received by the communication unit 26, the automatic cooperation setting screen is displayed on the display unit 25. When whether or not automatic cooperation is permitted is input from the automatic cooperation setting screen by the operation unit 24, an input result indicating whether or not to permit the center server 1 is transmitted by the communication unit 26 (step S26).

  In the center server 1, when an input result indicating whether or not automatic cooperation is permitted is received from the terminal device 2A by the communication unit 16, it is determined whether or not automatic cooperation is permitted (step S27). If it is determined that automatic cooperation is not permitted (step S27; NO), the process proceeds to step S34.

  On the other hand, when it is determined in step S27 that automatic cooperation is permitted (step S27; YES), user registration information (including newly registered users themselves) having the facility ID transmitted from the terminal device 2A in step S21. Is retrieved from the user management table 131. The retrieved user registration information is stored in an array from user [0] to user [N-1]. Then, the number of user registration information items searched for in variable N, that is, the number of users in the facility, is stored, and 0 is stored in variable i (step S28).

  Next, in the center server 1, it is determined whether or not N> 0, and if it is determined that N> 0 is not satisfied (step S29; NO), the process proceeds to step S34. If it is determined that N> 0 (step S29; YES), it is determined whether N> i is satisfied (step S32). If it is determined that N> i (step S30; YES), it is determined whether or not the automatic cooperation flag in the user registration information of the user [i] is ON (step S31). If it is determined that the automatic cooperation flag of the user [i] is not ON (step S31; NO), the process proceeds to step S33.

  On the other hand, if it is determined that the automatic cooperation flag of the user [i] is ON (step S31; YES), bidirectional cooperation is performed between the newly registered user (new user) and the user [i]. The relationship is registered (step S32). Specifically, in the cooperation destination information table 132, information on predetermined items such as a user ID and a password among the user registration information of the user [i] is newly associated with the user ID issued to the new user. Written as user cooperation destination information. Further, in association with the user ID of the user [i], information on predetermined items such as a user ID and a password among the user registration information of the new user is written as the cooperation destination information of the user [i]. When the process of step S32 ends, the process proceeds to step S33.

In step S33, the variable i is incremented by 1 (step S33), and the process returns to step S30. If it is determined in step S30 that N> i is not satisfied (step S30; NO), the process proceeds to step S34.

  In step S34, a user registration completion notification screen for notifying the user of the completion of user registration, the issued user ID, password, and registration number is generated, and the generated user registration completion notification screen is displayed as the communication unit 16. Is transmitted to the terminal device 2A (step S34). In the terminal device 2A, when the user registration completion notification screen is received, the user registration completion notification screen is displayed on the display unit 25 (step S35). Then, the automatic linkage process at the time of user registration ends.

  As described above, when the user newly registering user permits automatic cooperation with other users in the same facility by the automatic cooperation processing at the time of user registration, the center server 1 is set as the cooperation destination user of the new user. , Automatically register other users in the same facility that allow automatic linkage. In addition, this new user is automatically registered as a cooperation destination user of another user who permits automatic cooperation in the same facility. Therefore, in the case where it is desired to link between a newly registered user and another user in the same facility that permits automatic linkage, it is performed with a user at another medical facility. It is possible to immediately start cooperation without performing the cooperation destination registration process shown in FIG.

(Institutional collaboration setting process)
Next, the flow of in-facility cooperation setting processing will be described with reference to FIGS. 6A to 6B.
In the description of FIGS. 6A to 6B, a case where a user in the medical facility A performs setting of in-facility cooperation using the terminal device 2 </ b> A will be described as an example. However, the terminal device used for in-facility cooperation setting is a web browser. If it has, it will not specifically limit.
The operation of the terminal device 2 </ b> A illustrated in FIGS. 6A to 6B is executed by the cooperation of the control unit 21 and the program stored in the storage unit 23 according to the operation of the operation unit 24. The operation in the center server 1 is executed in cooperation with the control unit 11 and a program stored in the storage unit 13.

First, in the terminal device 2A, the operation unit 24 inputs user authentication information such as the facility ID, user ID, and password of the medical facility A from the portal site for providing the support service in the center server 1, and instructs to log in to the cooperation service. Then, the input user authentication information and a login request to the cooperation service are transmitted to the center server 1 by the communication unit 26 (step S41).
In the center server 1, when the communication unit 16 receives the authentication information and the login request to the cooperation service, the login authentication is performed (step S42). That is, in the user management table 131, user registration information having a facility ID, a user ID, and a password that match the input authentication information (here, a facility ID, a user ID, and a password) is searched. If user registration information having authentication information that matches the input authentication information does not exist in the user management table 131, a login error is notified to the terminal device 2A. When user registration information having authentication information that matches the input authentication information exists in the user management table 131, the authentication information of the logged-in user and the IP address of the terminal device 2A are temporarily stored in the RAM 12, and the storage unit 13 The initial screen of the cooperation service is read out from, and transmitted to the terminal device 2A by the communication unit 16 (step S43). The initial screen of the linked service is a screen for selecting a menu. For example, menus such as cooperation registration, in-facility cooperation setting, display of cooperation transmission / reception history, and cooperation request can be selected.

  In the terminal device 2 </ b> A, when the communication unit 26 receives the initial screen of the cooperative service from the center server 1, the received initial screen of the cooperative service is displayed on the display unit 25. When the setting of in-facility cooperation is instructed from the displayed initial screen by the operation unit 24, a display request for the in-facility cooperation setting screen is transmitted to the center server 1 by the communication unit 26 (step S44).

In the center server 1, when the communication unit 16 receives a display request for the in-facility cooperation setting screen from the terminal device 2A, a list of in-facility users that are not linked to the logged-in user is generated by the processing in steps S45 to S51. The
First, in step S41, user registration information (including the login user's own) having the facility ID transmitted from the terminal device 2A is retrieved from the user management table 131, and the retrieved user registration information is retrieved from the user [0] to the user. It is stored in the array [N-1]. Then, the number of user registration information items retrieved, that is, the number of users in the facility, is stored in the variable N, and 0 is stored in the variable i (step S45).

  Next, in the center server 1, it is determined whether or not N> 0, and if it is determined that N> 0 is not satisfied (step S46; NO), the process proceeds to step S52. If it is determined that N> 0 (step S46; YES), it is determined whether N> i is satisfied (step S47). If it is determined that N> i (step S47; YES), it is determined whether or not the automatic cooperation flag of the user [i] is ON (step S48). If it is determined that the automatic cooperation flag of the user [i] is not ON (step S48; NO), the process proceeds to step S51.

  On the other hand, if it is determined that the automatic cooperation flag of the user [i] is ON (step S48; YES), whether or not the user [i] is the cooperation destination of the login user in the cooperation destination information table 132, that is, the user It is determined whether or not the user registration information [i] is registered as cooperation destination information for the login user (step S49). If it is determined that the user registration information of the user [i] is registered as the cooperation destination information of the login user (step S49; YES), the process proceeds to step S51. If it is determined that the user registration information of the user [i] is not registered as the link destination information of the login user (step S49; NO), the user name of the user [i] is added to the list (step S50), The process proceeds to step S51.

  In step S51, the variable i is incremented (step S51), and the process returns to step S47. If it is determined in step S47 that N> i is not satisfied (step S47; NO), the process proceeds to step S52.

  In step S52, an in-facility cooperation setting screen in which a list of in-facility users who are not linked with the logged-in user is generated, and the in-facility cooperation setting screen is transmitted to the terminal device 2A by the communication unit 16 (step S52). S52). In the terminal device 2A, when the in-facility cooperation setting screen is received from the center server 1 by the communication unit 26, the in-facility cooperation setting screen 251 is displayed on the display unit 25 (step S53).

  FIG. 7 shows an example of the in-facility cooperation setting screen 251. As shown in FIG. 7, the in-facility cooperation setting screen 251 is used to set whether to permit automatic cooperation for automatically registering users in the same facility (users in the same facility) as cooperation destinations. An automatic cooperation permission check box 251a, a list of in-facility users that are not linked with the login user (referred to as an unlinked in-facility user list) 251b, an OK button 251c, and a cancel button 251d are displayed. When the automatic cooperation permission check box 251a is checked on by the operation unit 24, a user who wants to be a cooperation destination is selected from the user list 251b in the uncooperative facility and the OK button is pressed, a two-way cooperation relationship is created with the selected user. (Registered as a cooperation destination in the mutual cooperation information table 132).

  If the automatic cooperation permission check box 251a is checked, the two-way cooperation relationship is automatically established with the new user when a new user registration is subsequently performed in the same facility by the process of FIG. You can register. That is, the user registration information of the logged-in user is written as the cooperation destination information of the new user in the cooperation destination information table 132 by the automatic cooperation processing at the time of user registration that is subsequently executed, and the user registration information of the new user as the cooperation destination information of the login user. Is written. In addition, when an in-facility in-facility user subsequently displays the in-facility cooperation setting screen 251, the login user information is displayed in the list of the in-facility cooperation setting screen 251. On the other hand, when the automatic cooperation permission check box 251a is turned off, automatic cooperation is not performed when a new user is registered thereafter. Further, it is not displayed in the list on the in-facility cooperation setting screen 251.

  When input is performed by the operation unit 24 on the in-facility cooperation setting screen 251 and the OK button 251c or the cancel button 251d is pressed, the input result is transmitted to the center server 1 by the communication unit 26 (step S54).

  In the center server 1, when an input result is received by the communication unit 16, it is determined whether or not cancellation is instructed (step S55). If it is determined that cancellation has been instructed (step S55; YES), this process ends. On the other hand, if it is determined that cancellation is not instructed (step S55; NO), it is determined whether or not the automatic cooperation permission check box 251a is in a check-on state (step S56). If it is determined that the automatic cooperation permission check box 251a is in the check-on state (step S56; YES), the “automatic cooperation flag” of the user registration information of the login user in the user management table 131 is set to ON (step S57). ). In addition, a bidirectional linkage relationship is registered between the login user and the user selected from the unlinked facility user list 251b (step S58). Specifically, in the cooperation destination information table 132, information on predetermined items such as a user ID and a password among the user registration information of the selected user in association with the user ID of the login user is used as the cooperation destination information. Written. Further, in association with the user ID of the selected user, information of predetermined items such as a user ID and a password among the user registration information of the login user is written as cooperation destination information.

  On the other hand, if it is determined that the automatic cooperation permission check box 521a is in the check-off state (step S56; NO), the “automatic cooperation flag” of the user registration information of the login user in the user management table 131 is set to OFF, ( Step S59), this process ends.

  As described above, according to the in-facility cooperation setting process, even if the setting is such that automatic cooperation is not permitted at the time of user registration, it is changed to a setting that allows automatic cooperation later, and the user who permits automatic cooperation. The selected user can be automatically registered as a link destination. Therefore, if you want to start cooperation with users in the same facility that allows automatic cooperation, you can immediately cooperate without performing the cooperation registration process (a process that requires mutual approval) shown in FIG. Can be started.

In addition, when performing a cooperation request with respect to a cooperation destination user, it can carry out as follows.
First, after logging in to the cooperation service, when a cooperation request is selected from the menu of the initial screen of the cooperation service, the capture screen 252 is transmitted from the center server 1 to the terminal device that has logged in. FIG. 8 shows an example of the capture screen 252. When the data import button 252a is pressed from this import screen 252, a file selection screen 260 is displayed. This file selection screen 260 is a screen for selecting medical information data shared with the cooperation destination, and is stored in the local disk of the operating terminal device and the connected PACS (here, PACS 3A). Can be selected. When a file is selected from the file selection screen 260 and a transition to the next process is instructed, the cooperation destination information associated with the user ID of the login user is retrieved from the cooperation destination information table 132 in the center server 1, and the list 261a is retrieved. The cooperation destination selection screen 261 on which is displayed is transmitted. FIG. 9 shows an example of the cooperation destination selection screen 261. While selecting the cooperation destination user who becomes the cooperation request destination from the list 261a of the cooperation destination selection screen 261, the request content (cooperation menu) is selected with the button 261e, the necessary items such as a title and a comment are input, and the transmission button 261h is pressed. Then, cooperation request information such as cooperation destination information of a cooperation request destination, a file of medical information data, and request contents is transmitted to the center server 1. In the center server 1, when the cooperation request information is received, a request ID is issued, and transmission source information, transmission destination information, request contents, and the like are written in the transmission / reception history table 133 in association with the request ID. Specifically, the login user information is written in the transmission source information, and the cooperation request destination information (cooperation destination information selected by the login user) is written in the transmission destination information. In addition, medical information data is stored in the login user folder.

  As will be described later, the cooperation destination user registered in the transmission destination information by the above-described cooperation request processing can access the medical information data transmitted from the login user by the cooperation request. That is, the center server 1 grants an access right to the medical information data transmitted as the cooperation request based on the cooperation destination information stored in association with the user ID of the login user in the cooperation destination information table 132. ing.

  On the other hand, after the cooperation destination user logs in to the cooperation service, when the transmission / reception history display of cooperation is selected from the menu on the initial screen, the user ID of the login user (cooperation destination user) is transmitted from the transmission / reception history table 133 in the center server 1. The history information that is the ID is searched, and the transmission / reception history screen 262 on which the list 262a is displayed is transmitted to the terminal device that has logged in. FIG. 10 shows an example of the transmission / reception history screen 262. In other words, the list 262a is a list of cooperation requests addressed to the login user, and is a list of cooperation requests to which the login user has been granted access rights. When the desired history information is selected from the list 262a and the button for viewing contents is pressed, the contents of cooperation request and medical information data corresponding to the selected history information are read from the storage unit 13 in the center server 1, The medical information display screen on which the contents of the medical information are displayed is created and transmitted to the terminal device of the login user. In the terminal device, a medical information display screen is displayed. Thereby, the cooperation destination user can browse the medical treatment information data transmitted from the cooperation source user.

As described above, according to the center server 1, when a new user is registered, a user belonging to the same medical facility as the new user is searched from the user management table 131, and the user registration information of the extracted user is obtained as cooperation destination information. And stored in the cooperation destination information table 132 in association with the user ID of the new user.
Therefore, when performing medical cooperation between users in the same medical facility, it is possible to reduce the labor of registration procedures for starting cooperation.

  In addition, when registering a new user, the user registration information of the new user is stored in the cooperation destination information table 132 in association with user IDs of other users in the same medical facility as cooperation destination information. It is possible to further reduce the labor of registration procedures for starting cooperation.

In addition, only when a new user permits automatic cooperation, by registering a user who allows automatic cooperation that belongs to the same medical facility as the new user as a new user's cooperation destination, It is possible to prevent a user who does not cooperate with other users, a user who does not cooperate with other than a specific user, or the like from having an unintended partner.
Similarly, only when a new user permits automatic cooperation, the new user is registered as a cooperation destination of a user who is permitted automatic cooperation among users belonging to the same medical facility. It is possible to prevent a user who does not collaborate with other users, a user who does not collaborate with a user other than a specific user, or the like from collaborating with an unintended partner.

Further, the center server 1 generates a list of users who are permitted to automatically cooperate among users belonging to the same medical facility as the user and are not associated with the user based on a request from the user. When the user permits automatic cooperation, the user registration information of the user selected from the unlinked user list is registered in the cooperation destination information table 132 as the user cooperation destination information. To do. Therefore, it is possible to reduce the labor of the registration procedure for starting cooperation with uncooperated users in the same facility.
Further, by automatically registering the user registration information of the user who requested the cooperation in the cooperation destination information table 132 as the cooperation destination information of the selected non-cooperation user, the unregistered user in the same facility It is possible to further reduce the labor of the registration procedure for starting the cooperation.

  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 case where the terminal devices 2A and 2B provided in the medical facility and connected to the center server 1 by wire is used as a client has been described as an example. However, the client can browse the Web screen. Any terminal device may be used as long as it is wired to the center server 1 or wirelessly connected. For example, a mobile device equipped with a web browser may be used as the terminal device.

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 medical cooperation system 100 can be changed as appropriate without departing from the spirit of the invention.

100 medical cooperation system 1 center server 11 control unit 12 RAM
DESCRIPTION OF SYMBOLS 13 Memory | storage part 130 Facility management table 131 User management table 132 Cooperation destination information table 133 Transmission / reception log | history table 134 Temporary registration table 14 Operation part 15 Display part 16 Communication part 17 Time measuring part 18 Bus 2A, 2B Terminal device 21 Control part 22 RAM
23 storage unit 24 operation unit 25 display unit 251 in-facility cooperation setting screen 252 capture screen 261 cooperation destination selection screen 262 transmission / reception history 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 (7)

User registration means for registering user registration information including user identification information and facility identification information of the medical facility to which the user belongs, storage means for storing medical care information data transmitted from the registered user, and registered user Based on a cooperation destination registration request from the user, cooperation destination registration means for storing the cooperation destination information about the cooperation destination user designated as the cooperation destination by the user in the storage means in association with the identification information of the user, Data for providing access right to the medical information data transmitted from the user stored in the storage unit based on cooperation destination information stored in association with the user identification information in the storage unit A management server,
When a new user is registered by the user registration unit, the storage unit is searched for a user belonging to the same medical facility as the new user, and the user registration information of the extracted user is used as cooperation destination information for the new user. A data management server comprising automatic cooperation destination registration means for storing in the storage means in association with identification information.   2. The data management server according to claim 1, wherein the automatic cooperation destination registration unit further stores user registration information of the new user as cooperation destination information in association with the extracted user identification information in the storage unit. A setting unit for each user to set whether to permit registration by the automatic cooperation destination registration unit;
The automatic cooperation destination registration means permits registration by the automatic cooperation destination registration means belonging to the same medical facility as the new user when the new user permits registration of the cooperation destination by the automatic cooperation destination registration means. 2. The data management server according to claim 1, wherein user registration information of a user who is in charge is stored in the storage unit in association with identification information of the new user as cooperation destination information.   The automatic cooperation destination registration means is further configured to extract the user registration information of the new user as cooperation destination information when the new user permits registration of a cooperation destination by the automatic cooperation destination registration means. The data management server according to claim 3, wherein the storage unit stores the information in association with identification information of a user permitted to register by the automatic cooperation destination registration unit.   The automatic cooperation destination registration means is a user who permits registration by the automatic cooperation destination registration means among users belonging to the same medical facility as the user based on a request from the user, and the user registration information is User registration information of users not stored in the storage means is extracted in association with the requested user identification information as cooperation destination information, and within the same medical facility as the requested user based on the extracted user registration information A list of unlinked users is generated and displayed on the terminal device of the user, and when the user permits registration by the automatic cooperation destination registration means, the list of unlinked users is created by the user terminal device. The user registration information of the user selected from the above is used as the cooperation destination information in the identification information of the requested user. The data management server according to claim 3 or 4 put response is stored in the storage means.   6. The data management server according to claim 5, wherein the automatic cooperation destination registration means further stores the user registration information of the requested user in the storage means in association with the identification information of the selected user as cooperation destination information. . User registration means for registering user registration information including user identification information and facility identification information of the medical facility to which the user belongs, storage means for storing medical care information data transmitted from the registered user, and registered user Based on the cooperation destination registration request from the user, cooperation destination registration means for associating the cooperation destination information about the cooperation destination user designated as the cooperation destination by the user with the identification information of the user and storing it in the storage means, Data for providing access right to the medical information data transmitted from the user stored in the storage unit based on cooperation destination information stored in association with the user identification information in the storage unit The computer used for the management server
When a new user is registered by the user registration unit, the storage unit is searched for a user belonging to the same medical facility as the new user, and the user registration information of the extracted user is used as cooperation destination information for the new user. A program for functioning as an automatic cooperation destination registration unit that is stored in the storage unit in association with identification information.

Images