JP5471683B2 - Medical cooperation system - Google Patents

Description

  The present invention relates to a medical cooperation system.

  In recent years, with the development of medical technology, a network framework called medical cooperation in which a plurality of medical facilities such as hospitals and clinics having specific functions cooperate to treat patients is becoming widespread. Between medical institutions that are linked, patient introductions, examination requests, treatment policy consultations, interpretation requests, etc. are performed.

  When performing medical cooperation, there is a system that performs charge management when a fee is paid between the cooperation source and the cooperation destination. For example, when a request for interpretation of a medical image is made, the medical facility of the interpretation request source sends an interpretation request document attached with an electronic coupon delegating the right to use the interpretation service to the coordinator, and the coordinator sends it to the interpretation ASP. In the interpretation service system in which the interpretation ASP sends the interpretation result to the medical facility and the interpretation ASP sends the interpretation result to the coordinator based on the interpretation request document, the coordinator charges for the interpretation service system There is one that performs management collectively (see Patent Document 1).

JP 2002-109054 A

However, in Patent Document 1, accounting management is performed for an interpretation request using an electronic coupon, and charging is requested to the cooperation source that receives the service.
Further, in a medical cooperation system provided with a server interposed between the cooperation source and the cooperation destination, the cooperation source transmits and saves data that can be referred to by the cooperation destination to the server, and is stored in the server. Billing is often made to the cooperation source according to the data capacity. Therefore, for example, even if the cooperation destination benefits from the service rather than the cooperation source such as patient introduction, the cooperation source is charged unilaterally and it takes a financial burden, which is not reasonable There is a problem.

  In view of the above problems, an object of the present invention is to provide a medical management system capable of charge management according to the type of cooperation.

  The invention according to claim 1 is a medical cooperation system in which a management server and a terminal device provided in each of a plurality of medical facilities are connected so as to be able to transmit and receive data via a communication network. The management server manages the link information including link source information regarding the link source user who operates the terminal device, link destination information regarding the link destination user operating the terminal device of the link destination medical facility, and link type information indicating the link type. A first storage unit that stores charging rate information in which a charging rate for a cooperation source user and a cooperation destination user is set for each type of cooperation; When the cooperation information is received, based on the cooperation type information included in the cooperation information and the accounting rate information stored in the first storage unit, the cooperation source user and It and a server control unit for generating billing information for the user of the cooperation destination, a medical cooperative system characterized.

  The invention according to claim 2 is the medical cooperation system according to claim 1, wherein the cooperation information includes medical data related to a patient, and the server control unit is included in the cooperation information. Based on the cooperation type information and the charging rate information stored in the first storage unit, the charging rate of the cooperation source user and the cooperation destination user for the medical data included in the cooperation information is set, and the medical data Charging information for the cooperation source user and the cooperation destination user is generated based on the capacity and the charge rate of the cooperation source user and the cooperation destination user for the medical data.

  According to a third aspect of the present invention, in the medical cooperation system according to the first or second aspect, the charge percentage information includes a user who has ownership of medical data included in the cooperation information for each type of cooperation. The management server includes a second storage unit having an area for storing medical data included in the cooperation information in units of users having the ownership, and the server control unit includes: Based on the right information and the cooperation type information included in the cooperation information, a user having ownership of the medical data included in the cooperation information is set, and the medical care is set in the area in the second storage unit for the set user. Storing the data.

  According to a fourth aspect of the present invention, in the medical cooperation system according to any one of the first to third aspects, the server control unit includes a terminal device that is operated by the cooperation source user, and the cooperation. It transmits to the terminal device which a previous user operates, It is characterized by the above-mentioned.

  ADVANTAGE OF THE INVENTION According to this invention, the medical management system which can perform the charge management according to the kind of cooperation can be provided.

It is a block diagram of a medical cooperation system. It is a figure which shows the function structural example of a center server. It is a figure which shows the example of a user management table. (A) is a figure which shows the example of a cooperation destination table, (b) is a figure which shows the example of a cooperation log | history table. (A) is a figure which shows the example of a charge ratio table, (b) is a figure which shows the example of a file management table. It is a figure which shows the function structural example of a terminal device. It is a figure which shows the operation | movement flow of a cooperation charge process. (A) is a figure which shows the example of the message of the result mail transmitted to a cooperation origin user address, (b) is a figure which shows the example of the message of the result mail transmitted to a cooperation destination user address.

[Configuration of medical cooperation system]
In FIG. 1, the block diagram of the medical cooperation system 100 in this Embodiment is shown.
As shown in FIG. 1, the medical cooperation system 100 includes a center server 1 and an in-facility system installed in each medical facility (in-facility systems 6A and 6B in FIG. 1) via a communication network N. They are connected to each other so as to be able to send and receive data.
Note that the numbers and types of the in-facility systems 6A and 6B constituting the regional medical cooperation system 100 and the devices of the in-facility system are not particularly limited.

  The communication network N may be a LAN (Local Area Network) or a WAN (Wide Area Network), and may be a telephone line network, an ISDN (Integrated Services Digital Network) line network, a broadband communication line network, a dedicated line, or a mobile communication network. A configuration including a communication satellite line, a CATV (Community Antenna Television) line, an optical communication line, a wireless communication line, etc., and an Internet service provider for connecting them may be used.

The in-facility system 6A is configured such that a terminal device 2A, a PACS (Picture Archiving and Communication System) 3A, a modality 4A, and the like are connected to each other via an in-facility network 5A such as a LAN (Local Area Network) so that data can be transmitted and received between them. Yes. 2 A of terminal devices are provided with communication parts, such as a router, and are connected with the center server 1 via the communication network N by the said communication part so that data transmission / reception is possible.
The in-facility system 6B is configured by connecting terminal devices 2B, PACS 3B, modality 4B, and the like to each other via an in-facility network 5B such as a LAN so that data can be transmitted and received. The terminal device 2B includes a communication unit such as a router, and is connected to the center server 1 through the communication network N so that data can be transmitted and received.

The terminal devices 2A and 2B are computers equipped with Web browsers.
The terminal device 2 </ b> A is a computer used by a doctor at the medical facility A to perform medical cooperation with a doctor at another medical facility. A doctor at the medical facility A accesses the center server 1 via the communication network N, transmits medical data to the center server 1, and browses medical data that the doctor stored in the center server 1 is permitted to view. And a computer for performing downloads and the like.
Similarly, the terminal device 2B is a computer that is used by a doctor at the medical facility B to cooperate with doctors at another medical facility. A doctor at the medical facility B accesses the center server 1 via the communication network N, transmits medical data to the center server 1, and browses medical data that the user stored in the center server 1 is permitted to view. And a computer for performing downloads and the like.

  The PACS 3A and 3B are computers including a control unit, a RAM, a storage unit, an operation unit, a display unit, a communication unit, and the like. Medical image data and specimen test data generated mainly by modalities 4A and 4B in a medical facility The in-facility server stores medical data such as an interpretation report in association with patient information in a storage unit.

  The modalities 4A and 4B are images of a human body and generate digital data of the captured image (medical image). For example, CR (Computed Radiography), FPD (Flat Panel Detector), CT (Computed Tomography), MRI (MRI) Magnetic Resonance Imaging), cassette-dedicated readers, film digitizers, etc. are applicable.

[Center server 1]
The center server 1 is a management server that is installed in a data center and provides a medical cooperation service between medical facilities.

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 storage unit 12, a RAM 13, a facility DB 14, a file DB 15, a linkage DB 16, a charge management DB 17, a communication unit 18, and the like. 19 is connected.

  The control unit 11 is configured by a CPU (Central Processing Unit) or the like, and comprehensively controls the processing operation of each unit of the center server 1. The control unit 11 reads out various programs including the system program stored in the storage unit 12, develops it in a work area formed in the RAM 13, and executes various processes in cooperation with the developed program.

  The control unit 11 performs processing on the center server side in various processes including a cooperative billing process to be described later according to an AP (Application Server) server program 121, a mail server program 122, and a file server program 123 stored in the storage unit 12. It functions as a server control unit that executes.

  In the cooperative billing process, when the cooperation information is received from the terminal device according to the AP server program 121, the mail server program 122, and the file server program 123 executed by the control unit 11, the cooperation type information (cooperation menu) included in the cooperation information. Based on the accounting rate table 171 stored in the accounting management DB, the cooperation source user (hereinafter also referred to as the cooperation source user) and the cooperation destination user (hereinafter referred to as the cooperation destination user) for the medical data included in the cooperation information. And the charging information for the cooperation source user and the cooperation destination user is generated based on the volume of the medical data and the charging rate of the cooperation source user and the cooperation destination user for the medical data. The generated billing information is transmitted to the terminal device operated by the cooperation source user and the terminal device operated by the cooperation destination user.

  Further, in the cooperative billing process, a user having ownership of the medical data included in the cooperative information is set based on the cooperation type information and the charging rate table included in the received cooperative information, and the set user belongs The medical data is stored in an area in the file DB of the medical facility.

  The storage unit 12 includes an HDD (Hard Disk Drive), a semiconductor nonvolatile memory, or the like. As described above, the storage unit 12 stores various programs executed by the control unit 11 and also stores parameters and data necessary for executing the various programs. For example, the storage unit 12 stores an AP server program 121, a mail server program 122, a file server program, various application programs operating on the AP server, a system program, and the like.

The AP server program 121 executes a function as an AP server (also referred to as a Web application 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. Is to do.
The mail server program 122 is connected to the communication network N, and is for executing a function as a mail server for managing delivery of electronic mail of the terminal devices 2A and 2B connected to the communication network N.
The file server program 123 is for executing a function as a file server for saving and reading medical data in the file DB.

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

  The facility DB 14 includes a nonvolatile large-capacity memory such as a hard disk, and stores a user management table 141 and information unique to each medical facility. The user management table 141 stores user management information related to users (cooperation source users and cooperation destination users) who can use the cooperation service function provided by the center server 1.

FIG. 3 shows an example of the user management table 141.
As shown in FIG. 3, the user management table 141 includes, for example, “user ID”, “login password”, “facility ID”, “facility name”, “clinical department”, “user name” for identifying the user. (Doctor name) "," address "," phone number "," e-mail address ", etc. are provided, and information on each user (user management information) is stored for these items. Has been.

  The file DB 15 is composed of a non-volatile large-capacity memory such as a hard disk, etc., and stores medical facility A area 151, medical facility B area 152, etc. for each medical facility to which a user having medical data ownership belongs. And functions as a second storage unit. Each medical facility area such as the medical facility A area 151 and the medical facility B area 152 has an area for storing a patient information table and medical data related to the patient.

Patient information such as “patient ID”, “patient name”, “sex”, “birth date”, “address”, “phone number”, etc., is included in the patient information table for each patient. Stored.
Medical data is information acquired in the course of medical care for each patient. Examples of the medical data include medical image data, specimen examination data, electronic medical record data, interpretation reports, pathological diagnosis reports, and the like. Each data is added with a UID (Unique ID) for identifying each data, a file name, a file storage location (file path), a file size, an update date and time, and the like.

  The cooperation DB 16 is composed of a non-volatile large-capacity memory such as a hard disk, and stores information related to cooperation services such as a cooperation destination table 161 and a cooperation history table 162.

  The cooperation destination table 161 is a table for storing information (cooperation destination information) of users who are cooperation destination candidates registered by the cooperation source user. The user who becomes a cooperation destination candidate is a user (for example, a doctor) who operates a terminal device provided in a medical facility that is a request destination for medical cooperation.

FIG. 4A shows an example of the cooperation destination table 161.
As shown in FIG. 4A, in the cooperation destination table 161, for example, a “user ID” for identifying a user as a cooperation source, and a user registered as a cooperation destination user by the cooperation source user indicated by the user ID “Cooperation destination facility ID”, “cooperation destination facility name”, “cooperation destination user ID”, “cooperation destination user name”, “cooperation destination address”, “cooperation destination telephone number”, Items such as “cooperation destination email address” are provided, and data of cooperation destination information including information of these items is stored.
In this embodiment, the “cooperation destination user ID” is the user ID of the cooperation destination user.

  In the cooperation history table 162, each record is generated each time a cooperation request is made. The cooperation history table 162 stores cooperation information transmitted and received between the terminal device operated by the cooperation source user and the terminal device operated by the cooperation destination user. It is a table for managing a transition state.

FIG. 4B shows an example of the cooperation history table 162.
As shown in FIG. 4B, the cooperation history table 162 includes, for example, “cooperation ID”, “cooperation date / time”, “cooperation source information” (cooperation source user “facility ID”, “facility name”, “ User ID "," user name ", etc.)," cooperation destination information "(cooperation destination user" facility ID "," facility name "," user ID "," user name "etc.), cooperating patient information (cooperation source) User patient information ("patient ID", "patient name", "birth date", "gender", etc.)), "link menu", "link status", "title", "comment", attached as link information Items such as a file name of the medical data that has been processed and a storage location (file path) in the file DB 15 in which the medical data is stored are provided.

  The “cooperation ID” is identification information issued by the control unit 11 for the received cooperation information every time the center server 1 receives the cooperation information. A series of data transmitted / received between the cooperation source and the cooperation destination after receiving the cooperation information (for example, data transmitted as a reply from the cooperation destination terminal device to the cooperation source terminal device) is the same cooperation ID. Is granted and managed.

“Cooperation source information” is information relating to a cooperation source user who operates the terminal device that is the source of the cooperation information. For example, when the terminal device 2A operated by the user X in the medical facility A transmits the link information to the terminal device 2B operated by the user Y in the medical facility B, the user X in the medical facility A becomes the link source user. , The cooperation source information regarding the user X.
“Cooperation destination information” is information relating to the cooperation destination user specified by the cooperation source user who operates the terminal device that is the transmission destination of the cooperation information. For example, when the terminal device 2A operated by the user X in the medical facility A transmits cooperation information to the terminal device 2B operated by the user Y in the medical facility B, the user Y in the medical facility B becomes the cooperation destination user. This is the cooperation destination information regarding the user Y.

  The “cooperation menu” is cooperation type information indicating the type (classification) of cooperation selected by the cooperation source user. In this embodiment, the cooperation menu has a plurality of types of cooperation set in advance. For example, patient introduction cooperation (patient introduction), examination request cooperation (examination request), interpretation request cooperation (interpretation request) ), Consultation request cooperation (consultation).

The “cooperation state” indicates a transition state of medical cooperation between the cooperation destination user and the cooperation source user in the cooperation information indicated by each record.
“Title” is a title assigned by the cooperation source user.
“Comment” is a comment to the cooperation destination user input by the cooperation source user.
“File path” is information indicating a storage location (address) in the file DB in which medical data is stored.

  The billing management DB 17 is composed of a non-volatile large-capacity memory such as a hard disk, and stores a billing rate table 171 and a file management table 172.

FIG. 5A shows an example of the accounting rate table 171.
As shown in FIG. 5A, the charge rate table 171 stores, for each link menu, the “charge rate” between the link source user and the link destination user and the medical data included in the link information in the file DB. "Ownership" as right information indicating whether the authority to delete or edit is a medical facility to which the cooperation source user belongs or a medical facility to which the cooperation destination user belongs.

  In this embodiment, it is assumed that charging is performed for the target for which “ownership” is set, and the medical facility to which the user having the ownership of the medical data belongs as the target for which “ownership” is set. However, the present invention is not limited to this. For example, when charging is performed in units of medical facilities and clinical departments, the target for which ownership is set may be the medical facility and clinical department to which the user belongs, and when charging is performed in units of users, An object for which ownership is set may be an individual user.

  For example, in FIG. 5A, when the cooperation menu is patient introduction, the charge rate for the patient introduction is 0% for the cooperation source user who introduces the patient, and the cooperation in which the patient is introduced. The charging rate for the previous user is set to 100%. In addition, the ownership of the medical data included in the cooperation information of the patient introduction is set in the medical facility to which the cooperation destination user belongs.

FIG. 5B shows an example of the file management table 172.
The file management table 172 manages a fee charged for each medical data stored in the file DB 15. As shown in FIG. 5B, the file management table 172 includes “storage address”, “file name”, “capacity”, “ownership”, “ownership holding destination information”, “ownership holding destination”. Items such as “information” are provided. Each record is generated when medical data is stored in the file DB.

  The “storage address” indicates a storage area (address) for medical data stored in the file DB 15. “File name” indicates the file name of the medical data. The “capacity” is a capacity of medical data, and is a capacity of an area used for storing the medical data in the file DB 15.

  “Ownership” indicates a user (in this embodiment, a medical facility to which the user belongs) having the ownership of the medical data when the medical data is stored in the file DB.

“Ownership holding destination information” is information of a user having “ownership”, here, information of a medical facility to which the user belongs (“facility ID”, “facility name”, etc.).
“Ownership retention destination information” does not have “ownership”, but when medical data is stored, information of a user whose charging rate is set by the charging rate table 171, here the user belongs Information on medical facilities (“facility ID”, “facility name”, etc.).

  For example, when the user X of the medical facility A introduces the patient to the user Y of the medical facility B, the “ownership” becomes the medical facility B to which the user Y belongs based on the charge rate table 171, The facility ID of the “destination information” is the facility ID of the medical facility B and the charging rate is 100%, the facility ID of the “ownership holding destination information” is the facility ID of the medical facility A, and the charging rate is 0%.

  The communication unit 18 includes various interfaces such as a network interface card, a modem, and a USB, and transmits and receives information to and from terminal devices of each in-facility system on the communication network N.

[Terminal devices 2A, 2B]
FIG. 6 shows a functional configuration example of the terminal devices 2A and 2B.
As shown in FIG. 6, the terminal devices 2A and 2B include a control unit 21, a storage unit 22, a RAM 23, an operation unit 24, a display unit 25, a first communication unit 26, a second communication unit 27, and the like. Each part is connected by a bus 28 or the like.

  The control unit 21 is configured by a CPU or the like, and comprehensively controls processing operations of the respective units of the terminal devices 2A and 2B. The control unit 21 expands various programs including the system program stored in the storage unit 22, the web browser 221, and the script provided from the center server 1 in a work area formed in the RAM 23. Various processes are executed in cooperation with the program. For example, the control unit 21 functions as a terminal control unit that executes processes on the terminal device side in various processes including a cooperative billing process described later according to the developed program.

  In the cooperative billing process, in accordance with the Web browser 221 executed by the control unit 21, the cooperation information including the cooperation source information regarding the cooperation source user who operates the terminal device itself, the cooperation destination information regarding the cooperation destination user, the cooperation menu, and the like is displayed on the center server 1. Sent to.

  The storage unit 22 includes an HDD (Hard Disk Drive), a semiconductor nonvolatile memory, or the like. As described above, the storage unit 22 stores a system program executed by the control unit 21, various programs including the web browser 221, and various data.

  The RAM 23 has a work area for temporarily storing various programs, input or output data, parameters, and the like that can be executed by the control unit 21 read from the storage unit 22 in various processes that are executed and controlled by the control unit 21. Form.

  The operation unit 24 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 21 as an input signal.

  The display unit 25 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 21.

  The first communication unit 26 includes various interfaces such as a network interface card (NIC), a modem (MODEM: DE Modulator), and a USB (Universal Serial Bus), and is a center server on the communication network N. 1 to / from each other.

  The second communication unit 27 transmits / receives data to / from external devices connected to the in-facility networks 5A, 5B, for example, PACS 3A, 3B, modalities 4A, 4B.

Next, the operation of the present embodiment will be described.
[Login process]
First, login processing from the terminal devices 2A and 2B to the cooperation service of the center server 1 will be described.
The operation in the center server 1 is executed by the cooperation of the control unit 11, the AP server program 121, the mail server program 122, and the file server program 123. The operations in the terminal devices 2A and 2B are executed by the cooperation of the control unit 21 and the Web browser 221. In the following, the access operation from the terminal device 2A to the cooperation service of the center server 1 will be described as a representative, but the same applies to the terminal device 2B.

  In the terminal device 2 </ b> A, when a URL for accessing the cooperation service of the center server 1 is input from the Web browser 221 by the operation unit 24, the input URL is transmitted to the center server 1 by the first communication unit 26. .

  In the center server 1, when the URL for accessing the cooperation service is received from the terminal device 2A by the communication unit 18, display data for displaying the login screen is transmitted to the terminal device 2A.

  Note that HTML, style sheets, image data, and predetermined processing are executed in the terminal device 2A for display data of various Web screens including a login screen transmitted to the terminal device 2A by the Web server function of the center server 1. Scripts to make it included.

  In the terminal device 2 </ b> A, when the display data of the login screen is received by the first communication unit 26, a login screen (not shown) is displayed on the display unit 25. The login screen is a screen on which input fields for a user ID and a login password are displayed. When the user ID and the login password are input from the login screen, the input user ID and login password are transmitted to the center server 1 by the first communication unit 26.

  In the center server 1, when a user ID and a login password are received by the communication unit 18, user authentication is executed. Specifically, a record in which the user ID matches the received user ID is searched from the user management table 141, and if the searched record matches the received login password, it is determined that the user authentication is OK. The

  If the record whose user ID matches the received user ID is not searched or the login password of the searched record does not match the received login password, it is determined that the user authentication is NG.

  If it is determined that the user authentication is OK, the cooperation service is provided according to the operation in the Web browser 221 of the terminal device 2A. When the user authentication is NG, the terminal device 2A is notified via the communication unit 18 that the user authentication is NG.

  After the user authentication is OK, a cooperation initial screen (not shown) is displayed on the display unit 25 of the terminal device 2A. When the “new link button” provided on the link initial screen is pressed by the operation unit 24, execution of the link billing process is started.

[Linked billing process]
FIG. 7 shows an operation flow of the cooperative billing process.
In the following, an example in which a user who operates the terminal device 2A makes a request for cooperation to a user who operates the terminal device 2B will be described.

  First, a display request for a cooperation information acquisition screen (not shown) for acquiring cooperation information to be transmitted to a terminal device operated by a cooperation destination user is transmitted to the center server 1 by the first communication unit 26. In the center server 1, when a display request for the cooperation information acquisition screen is received, display data for the cooperation information acquisition screen is read from the storage unit 12 and transmitted to the terminal device 2 </ b> A by the communication unit 18. In the terminal device 2 </ b> A, when the first communication unit 26 receives the display data for the link information acquisition screen, the link information acquisition screen is displayed on the display unit 25 based on the received display data.

  In the terminal device 2A, on the cooperation information acquisition screen, input of cooperation destination information from the operation unit 24 (step S1), designation of a cooperation menu (step S2), and selection of medical data as content attached to the cooperation information (step S3) Then, the setting of the publication period of the selected content, the input of patient information, the input of the title and the comment about the content of the requested cooperation are performed, and the cooperation information is acquired. And the acquired cooperation information is transmitted to the center server 1 by the 1st communication part 26 (step S4).

The link information transmitted to the center server 1 in step S4 includes link source information, link destination information, medical data, and link content information.
The cooperation source information is a user ID and a login password input when the terminal device 2A logs in. The cooperation destination information, medical data, and cooperation content information are acquired on the cooperation information acquisition screen.

  In the AP server activated in the center server 1, when the cooperation information is received from the terminal device 2A by the communication unit 18, a cooperation ID for identifying the received cooperation information is generated, and is included as content in the cooperation information. The storage location of the stored medical data is determined (step S5).

  In step S5, the ownership corresponding to the cooperation menu is acquired based on the cooperation menu included in the received cooperation information and the charge ratio table 171 in the charge management DB 17. And the area | region provided in file DB15 for the user which this ownership shows is determined as a preservation | save destination of medical data.

  In the AP server, the determined storage location and the medical data included as content are notified to the file server (step S6), and a record is generated in the cooperation history table 162 based on the cooperation ID and the cooperation information. Is done.

  In the file server, when the notification in step S6 is received from the AP server, the notified medical data is stored in the determined storage destination based on the notification (step S7).

  Further, in the AP server, the charge ratio between the cooperation source user and the cooperation destination user is determined based on the cooperation menu included in the received cooperation information and the charge ratio table 171 in the charge management DB 17 (step S8). .

In the AP server, after step S8, a record of each medical data included in the content is generated in the file management table 172.
The record includes the address in the file DB 15 where the medical data is stored, the file name, the capacity, etc. of the medical data, the user having the “ownership” acquired in step S5, and the link source information included in the link information, It is generated based on the cooperation destination information.

When a record of medical data included in the cooperation information received in the file management table is generated, billing information is generated in the AP server (step S9).
In step S9, based on the file management table, each medical data of the medical facility to which the cooperation source user indicated by the cooperation source information included in the received cooperation information belongs and the medical facility to which the cooperation destination user indicated by the cooperation destination information belongs. The used capacity and unused capacity in the file DB 15 corresponding to the charging rate are calculated, and the charging fee corresponding to the used capacity is calculated. And used capacity and unused capacity calculated for each medical facility, charging fee, linkage ID for identifying linkage information used to calculate these, linkage menu, charging rate, possession of medical data included in linkage information Billing information including rights and the like is generated.

  In the AP server, when the billing information is generated, the communication unit 18 sends the billing fee to the medical facility to which the cooperation source user belongs and the billing fee to the medical facility to which the cooperation destination user belongs to the billing management company. The information shown is transmitted (step S10). The billing management company is a company that charges and collects charges to a user who receives a cooperation service of the medical cooperation system 100 (in this embodiment, a medical facility to which the user belongs).

In the AP server, the e-mail addresses of the cooperation source user and the cooperation destination user are acquired.
For example, for obtaining the email address of the cooperation source user, the user management table 141 is referred to, and a record that matches the user ID of the cooperation source user indicated by the cooperation source information included in the received cooperation information is searched and searched. E-mail address included in each record is acquired.
For obtaining the email address of the cooperation destination user, the cooperation destination table 161 is referred to, and a record that matches the user ID of the cooperation source user indicated by the cooperation source information included in the received cooperation information is searched. Then, among the retrieved records, the e-mail address included in the record that matches the user ID of the cooperation destination user indicated by the cooperation destination information included in the cooperation information is acquired.

  Then, in the AP server, a request for sending a result mail addressed to the email address of the cooperation source user and a request for sending a result mail addressed to the email address of the cooperation destination user are made to the mail server (step). S11).

  In the mail server, when a result mail transmission request is received by the AP server, an e-mail (result mail) is transmitted to the designated e-mail address (step S12). The result mail transmitted to the terminal device operated by the cooperation source user in step S12 includes a message indicating charging information for the cooperation source user. The result mail transmitted to the terminal device operated by the cooperation destination user includes a message indicating charging information for the cooperation destination user.

  In the terminal device operated by the cooperation source user, the result mail transmitted from the mail server of the center server 1 is received by the first communication unit 26 (step S13). In the terminal device operated by the cooperation destination user, the first communication unit 26, the result mail transmitted from the mail server of the center server 1 is received (step S14).

FIG. 8 shows an example of a message included in the result mail.
FIG. 8A shows an example of a result mail message sent to the cooperation source user, and FIG. 8B shows an example of a result mail message sent to the cooperation destination user.

As shown in FIG. 8A, the message M1 addressed to the cooperation source user includes a cooperation ID message M11, a menu message M12, a charging rate message M13, an unused capacity message M14, an ownership message M15, and the like. .
The cooperation ID message M11 indicates a cooperation ID for identifying the cooperation information. The menu message M12 indicates a cooperation menu included in the cooperation information. The charging rate message M13 indicates the charging rate of the cooperation source user and the cooperation destination user. The unused capacity message M14 indicates the capacity (unused capacity) that can be used by the medical facility to which the cooperation source user belongs. The ownership message M15 indicates the ownership of the medical data included in the cooperation information.

As shown in FIG. 8B, the message M2 addressed to the cooperation destination user includes a cooperation ID message M21, a menu message M22, a charging rate message M23, an unused capacity message M24, an ownership message M25, and the like. .
The cooperation ID message M21 indicates a cooperation ID for identifying the cooperation information. The menu message M22 indicates a cooperation menu included in the cooperation information. The charging rate message M23 indicates the charging rate of the cooperation source user and the cooperation destination user. The unused capacity message M24 indicates the capacity (unused capacity) that can be used by the medical facility to which the cooperation destination user belongs. The ownership message M25 indicates the ownership of the medical data included in the cooperation information.

As described above, according to the present embodiment, it is possible to generate charging information for the cooperation source user and the cooperation destination user at a charging rate corresponding to the type of cooperation indicated by the cooperation menu. For this reason, the cooperation source user is not unilaterally charged for the fee, and it is possible to prevent the cooperation source user from being subjected to all financial burdens.
Therefore, it is possible to provide a medical management system capable of managing billing according to the type of cooperation.

  Further, based on the “linkage menu” included in the link information and the “ownership” of the charge ratio table for the link menu, a user having medical data included in the link information can be set, and the file DB for the set user The medical data can be stored in the area. Therefore, the area in the file DB can be divided for each ownership, and the used capacity in the file DB can be easily calculated for each ownership.

  Further, since the result mail including the billing information is transmitted to the email address of the cooperation source user and to the email address of the cooperation destination user, the financial information related to the cooperation is provided to the cooperation source user and the cooperation destination user. Information can be easily grasped.

  In the above description, an example in which a nonvolatile memory is used as a computer-readable medium of the program according to the present invention is disclosed, but the present invention is not limited to this example. As other computer-readable media, a non-volatile memory such as a flash memory and a portable recording medium such as a CD-ROM can be applied. Further, a carrier wave (carrier wave) is also applied to the present invention as a medium for providing program data according to the present invention via a communication line.

  Further, the present invention is not limited to the contents of the above embodiment, and can be appropriately changed without departing from the gist of the present invention.

1 Center server 2A, 2B Terminal equipment 3A, 3B PACS
4A, 4B Modality 5A, 5B In-facility network 6A, 6B In-facility system 11 Control section 12 Storage section 13 RAM
14 facility DB
15 File DB
16 Cooperation DB
17 Charge management DB
18 Communication unit 19 Bus 21 Control unit 22 Storage unit 23 RAM
24 operation unit 25 display unit 26 first communication unit 27 second communication unit 28 bus 100 medical cooperation system 121 AP server program 122 mail server program 123 file server program 141 user management table 151 medical facility A area 152 medical facility B area 161 cooperation Destination table 162 Cooperation history table 171 Charge ratio table 172 File management table 221 Web browser M1, M2 message M11, M21 Cooperation ID message M12, M22 Menu message M13, M23 Charge ratio message M14, M24 Unused capacity message M15, M25 Ownership Message N Communication network

Claims (4)

In a medical cooperation system in which a management server and a terminal device provided in each of a plurality of medical facilities are connected via a communication network so that data can be transmitted and received,
The terminal device
Manages collaboration information including collaboration source information regarding the collaboration source user who operates the terminal device, collaboration destination information regarding the collaboration destination user who operates the terminal device of the collaboration destination medical facility, and collaboration type information indicating the type of collaboration. A terminal control unit for sending to the server,
The management server
A first storage unit that stores charging rate information in which a charging rate is set for a cooperation source user and a cooperation destination user for each type of linkage;
When the cooperation information is received, charging information for the cooperation source user and the cooperation destination user is obtained based on the cooperation type information included in the cooperation information and the charging rate information stored in the first storage unit. A server controller to generate;
Providing
Medical collaboration system characterized by The linkage information includes medical data related to the patient,
The server control unit
Based on the link type information included in the link information and the charge rate information stored in the first storage unit, the charge rate of the link source user and link destination user for the medical data included in the link information is set. And
Generating charging information for the cooperation source user and the cooperation destination user based on the capacity of the medical data and the charge rate of the cooperation source user and the cooperation destination user for the medical data;
The medical cooperation system according to claim 1. The billing rate information includes, for each type of cooperation, right information indicating a user having ownership of the medical data included in the cooperation information,
The management server
A second storage unit having an area for storing medical data included in the linkage information in units of users having the ownership;
The server control unit
Based on the link information included in the rights information and the link information, a user having ownership of the medical data included in the link information is set,
Storing the medical data in an area in the second storage unit for the set user;
The medical cooperation system according to claim 1 or 2. The server control unit
Transmitting the billing information to a terminal device operated by the cooperation source user and a terminal device operated by the cooperation destination user;
The medical cooperation system as described in any one of Claim 1 to 3 characterized by these.

Images