JP2000331101A - System and method for managing information related to medical care - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a medical care linkage to effectively and efficiently utilize a computer network. SOLUTION: A medical care linkage server 11 which unitarily manages information related to medical care is installed at a prescribed or desired location on a computer network 9 and communicably connected to clients 13, 13a, 13b,... at each medical institution. On the network 9, fire walls 13a and 15b and a public key server 17 for medical care linkage are provided. The transmission and reception of information between the clients 13, 13a, 13b,... and the server 11 are performed based on MERIT-IX and MML. Upon sending information, the clients 13, 13a, 13b,... and server 11 convert the information to be sent into the MML form and send the converted information by adding electronic signatures produced by using prescribed secret keys and enciphering the information by using cryptographic keys. Upon receiving the MML information, the clients 13, 13a, 13b,... and server 11 decode the information by using the cryptographic keys, receive the public keys for the secret keys from the public key server 17 together with public key certificates, and verify the electronic signatures by using the public keys.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

TECHNICAL FIELD The present invention relates to a system for managing and sharing information on a computer network.
In particular, it relates to a technology for efficiently managing and sharing various medical-related information.

[0002]

2. Description of the Related Art With the recent reform of the medical system, the functional differentiation of various medical institutions has become clear, and it has become difficult to complete treatment in one hospital. If the patient has any reason (needs specialized treatment, needs consultation from another department, cannot diagnose without a specific medical device, etc.), the patient is referred to the attending physician and uses the referral medical institution Will be. In this case, the patient receives a referral letter, medical information managed by the referral medical institution (hereinafter referred to as referral information) from the doctor in charge, and goes to the referral medical institution with that. The above introduction information is typically recorded and passed on paper, but may be recorded on a floppy disk or an IC card and passed. Alternatively, the doctor in charge may send the above-mentioned referral information by e-mail to the referral destination medical institution. The physician of the referral destination medical institution grasps the disease name, health condition, and the like of the patient who is referred and visited based on the above-mentioned referral information and performs a medical examination.

[0003]

As described above, since it is difficult to complete treatment at one medical institution,
Cooperation between various medical institutions (for example, between hospitals and hospitals and clinics), that is, medical coordination, becomes essential. The Ministry of Health and Welfare recommends this approach for medical cooperation, and one of the expectations of the Ministry of Health and Welfare is that it enables smooth introduction of patients between hospitals and clinics.

[0004] However, the above-mentioned introduction information is shared only by mutual medical institutions that cooperate with the introduction information, and the management of the above-mentioned introduction information and other medical-related information is performed separately by various medical institutions. However, other medical institutions cannot refer to the desired referral information.

[0005] For example, when a patient is examined in the order of Hospital A → Hospital B → Hospital C, the above introduction information is also transmitted in the order of Hospital A → Hospital B → Hospital C. In this case, A
Between hospital and hospital B and between hospital B and hospital C,
Since the introduction is performed directly, the introduction information is shared between each other, but the introduction information is not shared between the hospital A and the hospital C because the introduction is not performed directly. Therefore, it is very difficult for Hospital A to refer to the referral information at Hospital C, or for Hospital C to refer to the referral information at Hospital A.

As described above, at present, sufficient medical cooperation is not performed.

As a method for making this possible, medical-related information (including the above-mentioned introduction information) managed by various medical institutions is input to a computer, and the medical-related information is shared through a computer network. It is possible that. However, no effective solution has been considered for the specifications such as the communication speed and the network protocol, the effective operation method, and the robust security.

Accordingly, an object of the present invention is to effectively and efficiently use a computer network in medical cooperation.

[0009]

A system according to the present invention comprises, on a computer network, a plurality of client machines and one or more server machines for managing various medical-related information. The server machine transmits and receives various medical-related information based on MERIT-IX and MML.

[0010] The client machine is installed in various medical institutions (clinics, health centers, municipal hospitals, national hospitals, etc.), and the server machine is installed or specified in a relatively large medical institution such as a municipal hospital or national hospital. Or at a medical center. MERIT-IX (MedicalRecord Image Text-Info
rmation eXchange) is a standard for medical information exchange,
MML (Medical Mark-up Language) is one of the data description languages (data exchange format), and both are defined by each medical institution.

[0011] As a preferred example, when the server machine receives the patient's referral information including the referral information from the client machine, the server machine sends the patient's referral information to the client machine or server machine installed at the referral destination of the referral information. Send referral information. In this example, the client machine
Let the operator input the above introduction information in advance and enter it into MML
The information can be converted into the format and transmitted to the server machine, or the user can log in to the server machine, input the above-mentioned introduction information in real time, convert the information into the MML format, and transmit the information.

When the server machine receives the reply information in the mutual introduction of the patient, the server machine transmits the reply information to the client machine or the server machine installed at the referral source.

The server machine receives the identification information of the medical institution from the client machine when requested to provide the patient's introduction information or return information from the client machine. Then, the medical institution is identified from the identification information, and if the identified medical institution is a medical institution where the patient has never been consulted, the requested information is not transmitted.

[0014] In a preferred embodiment, the client machine and the server machine include an MML conversion unit for converting the information to be transmitted into an MML file converted into an MML format, an electronic signature creation unit for creating an electronic signature with a predetermined secret key, MML
Electronic signature attaching means for attaching the electronic signature to a file, encryption means for encrypting the MML file with a predetermined encryption key, and encrypted MM with the electronic signature
File sending means for sending the L file. File receiving means for receiving the encrypted MML file with the electronic signature; decryption means for decrypting the MML file with the predetermined encryption key; Electronic signature verification means for verifying the electronic signature with the public key paired with the predetermined secret key is provided.

In a preferred embodiment, the computer network includes an access control device for controlling external access to a client machine or a server machine, and a public key management device for managing a public key.
The public key management device also manages the public key certificate to which the electronic signature of the public key holder is attached, and distributes the public key together with the public key certificate when distributing the public key.

In a preferred embodiment, the server machine also has an authentication means for receiving predetermined authentication data from the client machine and performing an authentication check on the data.

[0017]

FIG. 1 shows the overall configuration of a medical cooperation system according to an embodiment of the present invention.

Various medical institutions, for example, clinics 1, health centers 3, municipal hospitals 5, or national hospitals 7, are communicably connected to each other via a computer network 9 (typically, the Internet, hereinafter, a network). I have. Each of these various medical institutions is provided with one or more clients (typically personal computers or workstations, not shown) for inputting and outputting desired medical-related information. Relatively large medical institutions, for example, municipal hospitals 5 and national hospitals 7, have information on themselves or other medical institutions (number of doctors,
A medical cooperation server (not shown) for managing the list of medical devices, the presence or absence of hospitalization equipment, etc.) and the above-mentioned introduction information of each patient is also installed. Hereinafter, the respective configurations will be described by taking the clinic 1 as a relatively small medical institution and the municipal hospital 5 as a relatively large medical institution.

FIG. 2 shows the configuration of the clinic 1 and the municipal hospital 5.

In the clinic 1, for example, one client 13 is installed. The municipal hospital 5 includes a plurality of clients 13a, 13b,..., The medical cooperation server 11 communicably connected to the clients 13a, 13b,. A medical-related information DB) 10 is provided. In this system, transmission and reception of the various types of information are performed based on the above-described MERIT-IX and MML.

The client 13 is connected to the network 9
, Is communicably connected to the medical cooperation server 11, converts predetermined or desired introduction information or the like input by an operator (for example, a doctor) into an MML format, and transmits the converted information to the medical cooperation server 11. Further, the client 13 requests the desired introduction information or the like from the medical cooperation server 11 and receives the requested information from the medical cooperation server 11 in the MML format.

The medical cooperation server 11 is a client 1
3 or the clients 13a, 13b,..., And receives the various types of information in the MML format and stores them in the medical-related information DB 10, and
a, 13b,... to the medical-related information D
B10 is searched for and obtained, and it is
Or, it transmits to the clients 13a, 13b,.

The above-mentioned MERIT-IX and MML are:
As already mentioned, since the rules are established among the majority of medical institutions, by transmitting and receiving information based on these rules, it is possible to smoothly introduce patients to each other and to ensure that virtually all medical institutions Medical related information can be shared. In this system, various kinds of security are constructed so that such a thing can be performed with security.

FIG. 3 is a block diagram showing the configuration shown in FIG. 2 in more detail.

Between the client 13 and the network 9 and between the network 9 and the medical cooperation server 11, firewalls 15a and 15b for controlling unauthorized access from outside are interposed. A public key server for medical cooperation (hereinafter, public key server) 17 that manages a public key and distributes the public key together with a signed public key certificate is provided.

The client 13 has a data input / output unit 18
, A file generation unit 19, an MML encoding / decoding unit 21, an electronic signature generation / verification unit 23 (hereinafter, a signature unit 23), an encryption / decryption unit 25, and a file transmission / reception unit 27.
And This configuration is suitable for clients installed in other various medical institutions (that is, clients 13a, 13a).
b,...).

The medical cooperation server 11 includes an authentication unit 29, an authentication data storage unit 30, a file transmission / reception unit 31, an encryption / decryption unit 33, an electronic signature generation / verification unit 35 (hereinafter, signature unit 35), An MML encoding / decoding unit 37;
A file generation unit 39 and a database input / output unit (DB input / output unit) 41 are provided.

In the following, the function of each component described above will be described together with the operation performed in this system.

Data input / output unit 18 of client 13
Is a medical cooperation server 1 of a hospital where an operator (eg, a doctor) inputs a desired URL and the operator wants to access.
1 and then a predetermined authentication data (for example,
A password or the ID of a hospital or a doctor is input and transmitted to the medical cooperation server 11 (step S1). Upon receiving the authentication data, the authentication unit 29 of the medical cooperation server 11 refers to the authentication data storage unit 30 storing various authentication data (S2), and determines whether the received authentication data is correct. If it is correct, an authentication OK (login OK) is returned to the client 13 (S3).

After logging in, for example, when the client 13 transmits information to the medical cooperation server 11, first, the data input / output unit 18 of the client 13 allows the doctor (operator) to input desired information such as patient introduction information. Then, it is passed to the file generation unit 18 (S4). The file generation unit 18 converts the information from the data input / output unit 18 into a predetermined file format, that is, the MML format, and passes the information in the MML format (hereinafter, MML file) to the MML encoding / decoding unit 21 (S5). . The MML encoding / decoding unit 21 encodes the passed MML file and passes it to the signature unit 23 (S6). The signature unit 23 generates an electronic signature using, for example, the operator's private key, attaches the digital signature to the MML file, and passes the digital signature to the encryption / decryption unit 25.
(S7). The encryption / decryption unit 25 encrypts the passed MML file using a predetermined encryption key (for example, shared by the client 13 and the medical cooperation server 11), and passes it to the file transmission / reception unit 27 (S8). . The file transmitting / receiving unit 27 transmits the encrypted MML file to the medical cooperation server 11 (S9). Medical cooperation server 11
Receives the MML file and passes it to the encryption / decryption unit 33 (S10). The encryption / decryption unit 33 receives the MM passed using the predetermined encryption key.
The L file is decrypted and passed to the signature unit 35 (S1
1). The signature unit 35 receives the public key paired with the private key from the public key server 17 together with the public key certificate (S12), and uses the public key to send the electronic mail attached to the MML file. The signature is verified, and if it is verified that the signature is valid, the MML file is passed to the MML encoding / decoding unit 37 (S13). The MML encoding / decoding unit 37 decodes the MML file and passes it to the DB input / output unit 41 (S14). The DB input / output unit 41 converts the passed MML file into a medical-related information DB.
10 (S15).

When the client 13 obtains desired information from the medical cooperation server 11 after the above-mentioned login, first, the data input / output unit 18 of the client 13 makes the medical cooperation server 1 transmit the information requested by the operator.
1 (step S16). Upon receiving the request, the DB input / output unit 41 of the medical cooperation server 11 acquires the requested information from the medical-related information DB 10 (S17), and passes the acquired information to the file generation unit 39 (S18). The file generation unit 39 converts the passed information into an MML file in the MML format and passes it to the MML encoding / decoding unit 37 (S19). The MML encoding / decoding unit 37 encodes the passed MML file and passes it to the signature unit 35 (S20). The signature unit 35 generates an electronic signature using a predetermined private key (for example, the creator of the information), attaches the electronic signature to the MML file, and passes it to the encryption / decryption unit 33.
(S21). The encryption / decryption unit 33 encrypts the passed MML file using the predetermined encryption key, and passes the encrypted MML file to the file transmission / reception unit 31 (S22). File transmitting / receiving unit 3
1 transmits the passed MML file to the client 13 (S23). The file transmission / reception unit 27 of the client 13 receives the information requested by the operator, that is, the MML file, and passes it to the encryption / decryption unit 25 (S24). The encryption / decryption unit 25 decrypts the passed MML file using the predetermined encryption key, and passes the decrypted MML file to the signature unit 23 (S25). The signature unit 23 receives the public key paired with the private key from the public key server 17 together with the public key certificate (S26), verifies the electronic signature using the public key, and verifies the electronic signature. If the signature is verified as a valid signature, the MML file is transferred to the MML encoding / decoding unit 21 (S27). The MML encoding / decoding unit 21 decodes the passed MML file and passes it to the data input / output unit 18 (S28). The data input / output unit 18 displays the passed MML file to the operator.

In this embodiment, the secret key and the public key correspond to each other, and they correspond to various medical institutions,
Each department (internal medicine, surgery, etc.) in various medical institutions or each doctor has it. The secret key may be managed by each of the client 13 and the disease cooperation server 1, or may be managed by using an information recording medium such as a floppy disk, an IC card, or a magnetic card. Client 1
3 and the medical cooperation server 1 may be shared via the network 9 or a floppy disk or an I / O
This may be performed using various information recording media such as a C card. The authentication data sent by the client 13 may be encrypted using, for example, a Java applet. The authentication of the authentication data is performed by the network 9
The authentication server installed above may perform the authentication.

According to the system described above, four types of security are established. That is, the first is the installation of the firewalls 15a and 15b and the authentication check at the time of login. As a result, it is possible to control unauthorized access from the outside and prevent illegal intrusion. Second,
Information encryption. Thus, it is possible to prevent eavesdropping of information by a third party or leakage of information, and it is possible to enhance the confidentiality of the introduction information and the like. If the encryption key is shared as described above, the processing speed of the encryption or decryption can be increased. Third, generation and verification of a digital signature. As a result, it is possible to prove that the creation of the introduction information and the like is legitimate, that is, to prevent impersonation of a third party, and
It is also possible to prevent information from being falsified. 4th
Is to manage the public key and distribute the public key together with the certificate. Thereby, the validity and certainty of the proof of the creator of the introduction information or the like can be increased.

As described above, in this system, since robust security is constructed, the above-mentioned introduction information and the like which are highly confidential can be safely introduced to the mutual introduction of patients on a computer network, and the above-mentioned introduction information and the like can be shared. Or you can. Hereinafter, the mutual introduction of patients and the sharing of the above-mentioned introduction information and the like performed by this system will be described.

FIG. 4 shows an example of the configuration of the medical-related information DB 10 in the embodiment.

The medical-related information DB 10 includes, for example, a user information storage unit 55, a patient basic information storage unit 57, a consultation information storage unit 59, an introduction management information storage unit 61, an introduction information storage unit 63, An information storage unit 65 is provided.
The user information storage unit 55 stores, for example, information (user ID, password, hospital name, doctor name, etc.) regarding each doctor who is a user. In the patient basic information storage unit 57,
Basic information on the patient (medical cooperation ID, patient name, gender, date of birth, address, etc.) is stored. The consultation information storage unit 59 stores consultation information (medical cooperation ID, hospital ID, patient number, and the like) indicating which patient has undergone consultation at which hospital. In the referral management information storage unit 61, information on which hospital was referred to which hospital (introduction date,
(Medical cooperation ID, referral hospital ID, referral hospital ID, etc.)
Is stored. The introduction information storage unit 63 stores the above introduction information.
(Medical cooperation ID, introduction date, prescription information, examination information, etc.) are stored. The return information storage unit 65 stores return information (medical cooperation ID, consultation date, referral hospital ID, referral hospital ID, etc.) for notifying the referrer of the results of the consultation performed at the referral destination.
Prescription information, examination information, etc.) are stored. The medical cooperation ID is for uniquely identifying a patient commonly used in various medical institutions. On the other hand, the patient number is a number for identifying a patient unique to various medical institutions.

In a system provided with such a medical-related information DB 10, mutual introduction of patients is performed by the operation shown in FIG.

FIG. 5 shows the operation in mutual introduction of patients. In the figure, the clinic 1 is referred to as a referral hospital, and the municipal hospital 5 is referred to as a referral hospital.

The clinic 1, that is, the client 13,
An operator (for example, a doctor) inputs the introduction information in a predetermined format as shown in FIG.
29). According to FIG. 6, the client 13 has the hospital ID
And patient number, referral medical institution, referral department, referral doctor, referral medical institution, referral doctor name, location and phone number (of referrer), and patient name as information of the patient to be referred, The operator inputs gender, occupation, date of birth, age, purpose of introduction, reason for introduction, considerations for the patient, and the like. Then, the client 13 converts the input introduction information into the MML format and creates an MML file (S3).
0), start a WWW browser and input a desired URL (for example, the address of a login page for transmitting introduction information described below) (S31-a), and access the medical cooperation server 11 of the municipal hospital 5 via the network 9. (S31-b).
The medical cooperation server 11 performs login authentication and transmits an introduction information transmission login page for permitting transmission of the introduction information (S32). The client 13 allows the operator to input predetermined authentication data on the login page, encrypts the authentication data, for example, and transmits the encrypted data to the medical cooperation server 11 (S33). If the received authentication data is valid (Y in S34), the medical cooperation server 11 transmits a file upload page for uploading the introduction information to the client 13 (S35). The client 13 receives the file upload page and, for example, “send” described on the page.
When the button is clicked by the operator, the MML file is uploaded to the medical cooperation server 11 (S3).
7). The medical cooperation server 11 analyzes the received MML file and extracts each item in the file, that is, the hospital ID and the patient number shown in FIG. 6, the referral medical institution and the like (S38), and retrieves the retrieved hospital ID and the patient. The consultation information storage unit 59 in the medical-related information DB 10 is searched using the number as a key, and it is confirmed whether or not a consultation for the patient has been made in the past from the hospital (S39). When the consultation is confirmed (Y in S39), the medical cooperation ID is acquired (S40), and the predetermined information described above is stored in each of the introduction management information storage unit 61 and the introduction information storage unit 63 using the medical cooperation ID as a key. Is stored (S43). If you cannot confirm the above consultation
(N in S39), by searching the patient basic information storage unit 57 using the patient name, gender, and date of birth in the retrieved items as keys, to confirm whether the basic information of the patient has been registered. (S41). If the above registration is confirmed (S4
If the registration is not confirmed (N in S41), the basic information of the patient in the extracted items is stored in the patient basic information storage unit 57.
Is newly registered (S42), and the predetermined information is stored in each of the introduction management information storage unit 61 and the introduction information storage unit 63 (S43).

The client 13 is connected to the medical cooperation server 11
You can also access and enter your referral information in real time. In that case, first, the client 13 accesses the medical cooperation server 11 and receives authentication OK. Next, the client 13 allows the operator to input the hospital ID and the patient number or the medical cooperation ID, and transmits it to the medical cooperation server 11. The medical cooperation server 11 specifies the patient by searching the medical-related information DB 10 using the hospital ID and patient number of the consultation or the medical cooperation ID as a key, and displays an introduction information input page in a format as shown in FIG. 6, for example. Send to client 13. Client 13
Enter predetermined information in the introduction information input page and
The data is converted into the ML format and transmitted to the medical cooperation server 11. The medical cooperation server 11 stores the predetermined information in each of the introduction management information storage unit 61 and the introduction information storage unit 63 using the medical cooperation ID as a key.

Note that the client 13 can
(For example, when a request is received from the municipal hospital 5), the patient basic information is input in a predetermined format as shown in FIG.
According to FIG. 7, the client 13 allows the operator to input, for example, a chart number, a patient number, a date of birth, a kana name, a kanji name, a side effect history, allergies, a carrier, or a blood type as patient basic information. . Client 1
3. The medical cooperation server 1 prepares the patient information in advance and
1 or log in to the medical cooperation server 11 and input to the medical cooperation server 11 in real time.

The physician of the municipal hospital 5 who has been referred to the above-mentioned patient, when examining the patient, has the client 1
3a, 13b,... Using a predetermined key (medical cooperation I
D, referrer hospital ID, patient number, etc.), and causes the medical cooperation server 11 to search for desired introduction information using the predetermined key, and receives the introduction information from the medical cooperation server 11.

When the doctor of the municipal hospital 5 has received the referral information and has finished examining the patient, he / she replies as follows.

FIG. 8 is a flowchart showing the flow of the reply.

The clients 13a, 13b,...
A doctor of the municipal hospital 5 starts a WWW browser to enter a desired URL, for example, a U of a return creation login page for logging in to the medical cooperation server 11 and creating a return.
The user inputs or specifies the RL (step S44-a), and accesses the medical cooperation server 11 (S44-b). The medical cooperation server 11 transmits the above-mentioned reply creation login page to the clients 13a, 13b,... (S45). The client 13a, 13b,... Inputs predetermined authentication data and transmits it to the medical cooperation server 11 (S46).
The medical cooperation server 11 checks the validity of the authentication data (S47), and if it is valid (Y in S47), transmits a return creation page to the clients 13a, 13b, ... (S48). Clients 13a, 13b, ...
Predetermined or desired reply information (medical cooperation ID, consultation date, referral hospital ID, referral hospital ID, prescription information, examination information, etc.) is input and transmitted to the medical cooperation server 11 (S50). . The medical cooperation server 11 converts the received return information into the medical-related information D using the medical cooperation ID as a key.
Stored in the reply information storage unit 65 in B10,
A reply mail for notifying the return information ant is transmitted from the referral source hospital to (clinic 1) (S51). When the client 13 of the clinic 1 confirms the return mail (S52), the client 13 activates the WWW browser and enters a predetermined URL.
For example, the user inputs or specifies the URL of the login page for acquiring the return information (S53-a), and accesses the medical cooperation server 11 via the network 9 (S5).
3-b). The medical cooperation server 11 transmits a login page for obtaining reply information to the client 13 (S54). The client 13 inputs predetermined authentication data into the received page and transmits it to the medical cooperation server 11 (S
55). If the authentication data is valid (Y in S56), the medical cooperation server 11 transmits a return information acquisition page to the client 13 (S57). The client 13 inputs the referral destination hospital ID on the received page and transmits it to the medical cooperation server 11 (S59). Medical cooperation server 1
1 searches the return information storage unit 65 using the referral destination hospital ID as a key, acquires all the relevant return information, creates a list of them, and transmits the list to the client 13. The client 13 displays the list,
The desired reply information is selected from the list, and the desired reply information is confirmed (S61). In this flow, if the patient is to be hospitalized, the return information may include a hospitalization report, a hospital name of the hospital, transfer department information, hospitalization progress information, and the like.
When the patient is discharged from the hospital,
A discharge report, a medical examination / test result, a policy after discharge, or the like may be included.

In the above-described system, mutual introduction of patients is performed in such a flow. The above various medical institutions can acquire and refer to desired introduction information managed by each of them as follows.

For example, when a doctor at the national hospital 7 wants to refer to the referral information managed at the municipal hospital 5, the doctor uses the client in the national hospital 7 to use the medical cooperation server 11 Login to your own hospital I
D and a medical cooperation ID or a desired introduction date. The medical cooperation server 11 searches the medical-related information DB 10 using the input key, extracts all managed introduction information, and transmits the extraction result to the client. The client displays a list of the extraction results and allows the doctor to select desired introduction information. The medical cooperation server 11 acquires the selected introduction information from the medical-related information DB 10 and causes the client to display the information.

In this embodiment, the various medical institutions share information on each patient, not limited to the above-mentioned introduction information, but also the above-mentioned basic patient information, past / current disease information, family history information, examination result information, prescription history. Time-series information or image information such as X-rays and echoes can also be shared. When acquiring information on each of these patients, the hospital ID
To prevent a hospital that has never been consulted by that patient from acquiring information related to that patient.

Although some preferred embodiments of the present invention have been described above, these are merely examples for describing the present invention, and are not intended to limit the scope of the present invention only to these examples. . The present invention can be implemented in other various forms. For example, the medical cooperation server 11 can be installed in a specific medical center, receive medical-related information including the above-mentioned introduction information from various medical institutions, and manage the medical-related information in various medical institutions in a unified manner. When the medical cooperation server 11 receives the introduction information,
The introduction information may be automatically distributed to the introduction destination, or the return information may be automatically distributed to the introduction source.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the overall configuration of a medical cooperation system according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a configuration of a clinic 1 and a municipal hospital 5.

FIG. 3 is a block diagram showing the configuration of the medical cooperation system shown in FIG. 2 in more detail;

FIG. 4 is a block diagram showing an example of the configuration of a medical-related information DB 10;

FIG. 5 is a flowchart showing an operation when introducing a patient.

FIG. 6 is a diagram showing an example of a format for inputting introduction information.

FIG. 7 is a view showing an example of an input format of basic patient information.

FIG. 8 is a flowchart showing the flow of a reply.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Clinic 3 Health center 5 Municipal hospital 7 National hospital 9 Computer network 10 Medical related information database 11 Medical cooperation server 13, 13a, 13b ... Client 15a, 15b Firewall

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5J104 AA01 AA09 EA16 LA03 NA02 NA36 NA38 PA07 PA09 9A001 BB04 CC03 DD10 EE02 EE03 EE06 EZ04 JJ07 JJ09 KK60 LL03

Claims (11)

[Claims] 1. A computer network comprising: a plurality of client machines; and one or a plurality of server machines for managing various medical-related information, wherein the client machines and the server machines are connected to a MERIT-IX. And a medical-related information management system that transmits and receives the various medical-related information based on the MML. 2. When the server machine receives patient's referral information including referral letter information from the client machine, the server machine sends the referral information to a client machine or a server machine installed at the referral destination of the referral information. The medical-related information management system according to claim 1, wherein the information is transmitted. 3. The medical-related information system according to claim 2, wherein when the server machine receives the return information, the server machine transmits the return information to a client machine or a server machine installed at the referral source medical institution. . 4. The server machine, when requested to provide the patient's introduction information or the return information from the client machine, receives the identification information of the medical institution from the client machine, and from the identification information, 4. The medical-related information according to claim 2, wherein the medical institution is identified, and the requested information is not transmitted if the identified medical institution is a medical institution to which the patient has never been consulted. Management system. 5. The client machine and the server machine, wherein: MML conversion means for converting the information to be transmitted into an MML file converted into an MML format; electronic signature creation means for creating an electronic signature with a predetermined secret key; Electronic signature attaching means for attaching the electronic signature to a file; encrypting means for encrypting the MML file with a predetermined encryption key; file sending means for sending the encrypted MML file with the electronic signature File receiving means for receiving the encrypted MML file with the digital signature; decryption means for decrypting the encrypted MML file with the predetermined encryption key; and MML with the digital signature Electronic signature verification means for verifying the electronic signature of the file with the public key paired with the predetermined private key. Medical information management system of claim 1, wherein. 6. An access control device for controlling external access to the client machine or the server machine on the computer network, and a public key management device for managing the public key, The key management device also manages a public key certificate to which an electronic signature of the public key holder is attached, and distributes the public key together with the public key certificate when distributing the public key. 5. The medical-related information management system according to 5. 7. The medical-related information management system according to claim 6, wherein the server machine further includes an authentication unit that receives predetermined authentication data from the client machine and performs an authentication check on the data. 8. An information management device for managing various medical-related information, the information managing device being installed on a computer network, transmitting and receiving the various medical-related information based on MERIT-IX and MML, If you receive referral information,
An information management device for transmitting the introduction information to a predetermined device installed at the introduction destination. 9. An M format obtained by converting information to be transmitted into an MML format
MML conversion means for converting the MML file into an ML file; electronic signature creating means for creating an electronic signature with a predetermined secret key; electronic signature attaching means for attaching the electronic signature to the MML file; Encrypting means for encrypting; file transmitting means for transmitting the encrypted MML file with the digital signature; file receiving means for receiving the encrypted MML file with the digital signature; Decryption means for decrypting the encrypted MML file with the encryption key, and an electronic device for verifying the electronic signature of the MML file with the electronic signature with a public key paired with the predetermined secret key. The information management apparatus according to claim 8, further comprising a signature verification unit. 10. An MML conversion step of converting medical information to be transmitted into an MML file converted into an MML format, a first file transmission step of transmitting the MML file, a file reception step of receiving the MML file, And transmitting the MML file to the introduction destination of the introduction information when the received MML file is the converted file of the patient's introduction information including the introduction letter information.
And a computer-readable recording medium recording a program for causing a computer to execute the file sending step. 11. An electronic signature creating step of creating an electronic signature with a predetermined secret key, electronic signature attaching means for attaching the electronic signature to the MML file, and an encryption for encrypting the MML file with a predetermined encryption key. Decryption means for decrypting the encrypted MML file with the predetermined encryption key; and decryption of the MML file with the electronic signature with the public key paired with the predetermined secret key. The computer-readable recording medium according to claim 10, further comprising a program for causing a computer to execute an electronic signature verification unit that verifies a signature.