Medical data transmitting and receiving system, medical data transmitting side system, medical data receiving side system, and medical data transmitting and receiving method

Abstract

To provide a medical data transmission / reception system, a medical data transmission-side system, a medical data reception-side system and a medical data transmission / reception method for reducing the labor of a patient, and for using a communication route corresponding to the type of medical data.SOLUTION: In a medical data transmission / reception system 10, for example, first medical data including at least one of electronic medical chart data, referral letter data and medical examination result data are transmitted from a transmission side system 20 to a reception side system 60 through a first communication network 70 and a management server 30. The second medical data such as medical image data is transmitted from the transmitting-side system to the receiving-side system via the second communication network 72 and the external repository 50. The first medical data includes a second medical data acquisition token for acquiring second medical data from an external repository.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a medical data transmission and reception system, a medical data transmission system, a medical data reception system, and a medical data transmission and reception method, and more particularly to a medical data transmission and reception system, a medical data transmission system, a medical data reception system, and a medical data transmission and reception method used for transmitting and receiving first medical data including at least one of electronic medical chart data, referral letter data, and medical examination result data, which are mainly composed of text information, and second medical data (e.g., medical image data) larger in size than the first medical data. [Background technology]

[0002] BACKGROUND ART When a patient is referred from one medical institution to another, a technique has been developed for transmitting the patient's medical data (for example, medical image data) to the referred medical institution (Patent Document 1).

[0003] Patent Document 1 aims to enable easy import of medical image data, etc. (

[0006] , Abstract). To achieve this aim, in Example 1 of Patent Document 1 (Abstract,

[0013] to

[0069] ), an image input device (211) transmits data acquired from a card as patient registration card data to a data processing device (213), and receives a response indicating a valid or invalid patient registration card from the data processing device (213). If the response indicating a valid patient registration card is received, the image input device (211) determines whether medical data exists in the medium (16), and if it determines that medical data exists in the medium (16), transmits the medical data acquired from the medium (16) to the data processing device (213). In Example 1 of Patent Document 1, the medium (16) recording the medical data is inserted by a patient (17), in other words, is carried by the patient (17) (

[0040] ,

[0071] , Figure 2).

[0004] In Example 2 (

[0070] to

[0076] ) of Patent Document 1, medical data is transmitted and received using a virtual private network (VPN). That is, the LANs (15, 25) of the source medical institution (10) and the destination medical institution (20) are connected to a server device (41) of an external network (40) via VPN routers (42, 43) (

[0072] ).

[0005] The image output device (11) of the medical institution (10) then uploads the medical data of the patient (17) to the server device (41) (export process). The patient (17) receives a slip containing an acquisition code (token) for acquiring his / her own medical data at the medical examination department counter or the like of the medical institution (10), and carries the slip to the medical institution (20) instead of the media (16). At the medical institution (20), the patient (17) inserts his / her medical institution (20) patient card into the medical card slot of the image input device (211) in accordance with instructions from the reception desk, and starts importing the medical data (

[0073] ). During the import, the data processing device (213) downloads the medical data from the server device (41) using the token as a key. The data processing device (213) then performs a match determination for the patient information, adapts the patient information, and transmits the data to the PACS (22) (import process) (

[0076] ). [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Publication No. 2017-021535 Summary of the Invention [Problem to be solved by the invention]

[0007] As described above, in Example 2 of Patent Document 1, medical data is transmitted from a source medical institution (10) to a destination medical institution (20) using a VPN and an external server device (41) (

[0070] to

[0076] , FIG. 2). In Example 2, the patient (17) carries an acquisition code (token) for acquiring the patient's (17) medical data to the destination medical institution (20) (

[0072] ). Then, the data processing device (213) of the import system (21) of the destination medical institution (20) downloads the medical data from the external server device (41) using the token as a key and via the VPN (

[0076] ). However, if the patient (17) carries a slip on which the token is recorded, there is a risk that the patient (17) may forget to carry the slip or lose it.

[0008] Furthermore, in Patent Document 1, all medical data provided to the referral destination is recorded on a medium (16) and carried or transmitted via a VPN. However, there may be cases where it is more convenient to transmit the medical data (first medical data) that is relatively small in size and includes electronic medical record data, etc., mainly consisting of text data, and the medical data (second medical data) that is relatively large in size, such as medical image data, separately.

[0009] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a medical data transmission and reception system, a medical data transmission system, a medical data receiving system, and a data transmission and reception method that can reduce the burden on patients and enable the use of communication paths according to the type of medical data. [Means for solving the problem]

[0010] A medical data transmission and reception system according to one aspect of the present invention comprises: a transmitting system in a medical institution that transmits the first medical data and the second medical data; a receiving system at a medical institution that receives the first medical data and the second medical data; and Furthermore, the medical data transmission and reception system includes: a management server that stores the first medical data received from the transmitting system via a first communication network and transmits the first medical data to the receiving system via the first communication network; an external repository that temporarily stores the second medical data received from the sending system via a second communication network and transfers the second medical data to the receiving system via the second communication network; and Furthermore, the first medical data includes a second medical data acquisition token for acquiring the second medical data from the external repository. It is characterized by:

[0011] According to the present invention, the first medical data is transmitted from the transmitting system to the receiving system via the first communication network and the management server, and the second medical data is transmitted from the transmitting system to the receiving system via the second communication network and the external repository. This makes it possible to transmit and receive medical data via a communication path appropriate for the type, size, etc. of the medical data.

[0012] Furthermore, the first medical data transmitted via the first communication network and the management server includes a second medical data acquisition token for acquiring the second medical data from an external repository in the second communication network. This ensures security when the first communication network has a higher level of security than the second communication network, eliminating the need for the patient to carry the second medical data acquisition token. Additionally, this eliminates the risk of the patient forgetting to carry the second medical data acquisition token or losing it, enabling the data to be delivered more reliably to the receiving system.

[0013] The first medical data may include at least one of electronic medical record data, referral letter data, and medical examination result data. The second medical data may include data larger in size than the first medical data. As a result, relatively small first medical data, including at least one of electronic medical record data, referral letter data, and medical examination result data, is transmitted from the transmitting system to the receiving system via the first communication network and the management server. Furthermore, relatively large second medical data (e.g., medical image data captured for patient diagnosis) is transmitted from the transmitting system to the receiving system via the second communication network and the external repository. For example, if the second communication network is a closed network or the Internet with a faster communication speed or larger communication capacity than the first communication network, it becomes possible to transmit and receive medical data via a communication path appropriate for the size (type, etc.) of the medical data. Furthermore, even if the first communication network has a relatively slow communication speed or a relatively small communication capacity and is therefore not suitable for transmitting the second medical data, or if the management server has a relatively low processing performance and is not suitable for transmitting the second medical data, it becomes possible to handle the second medical data. Furthermore, when the second communication network is the Internet, it is possible to build the second communication network at relatively low cost.

[0014] In addition, when at least the referral letter data is included in the first medical data, the second medical data is linked to the referral letter data, which makes it easier for the receiving system to manage the second medical data.

[0015] The receiving system a first medical data receiving terminal connected to the first communication network to receive the first medical data from the management server; a second medical data receiving terminal connected to the second communication network to receive the second medical data from the external repository; a receiving-side token transmitting means for transmitting the second medical data acquisition token included in the first medical data received by the first medical data receiving terminal from the management server to the second medical data receiving terminal; may include:

[0016] This makes it possible to transmit the second medical data acquisition token from the first medical data receiving terminal to the second medical data receiving terminal even if the first medical data and the second medical data are received at separate receiving terminals (first medical data receiving terminal and second medical data receiving terminal).

[0017] The first medical data receiving terminal may be disconnected from the second communication network. The second medical data receiving terminal may be disconnected from the first communication network. This makes it possible to input a second medical data acquisition token to the second medical data receiving terminal via the receiving token transmission means, even when the first medical data receiving terminal is disconnected from the second communication network. Therefore, it is possible to receive the second medical data via the second communication network while reducing the risk of external intrusion into the first medical data receiving terminal (and the first communication network).

[0018] The receiving system may further include a coded image display unit that displays the second medical data acquisition token included in the first medical data received by the first medical data receiving terminal as a coded image. The receiving token transmission means may include an optical sensor that reads the coded image. The second medical data receiving terminal may receive the second medical data from the external repository via the second communications network based on information about the second medical data acquisition token indicated by the coded image read by the optical sensor. This makes it relatively easy to transmit the second medical data acquisition token from the first medical data receiving terminal to the second medical data receiving terminal.

[0019] Alternatively or additionally, the receiving system may include a token transfer unit that guides the user through an operation to transfer the second medical data acquisition token included in the first medical data received by the first medical data receiving terminal from the first medical data receiving terminal to the second medical data receiving terminal, or that automatically transfers the second medical data acquisition token from the first medical data receiving terminal to the second medical data receiving terminal. This improves the convenience of the receiving user when receiving the first medical data via the first communications network and the second medical data via the second communications network.

[0020] The receiving system may further include a second medical data import terminal that acquires the second medical data acquisition token from the first medical data receiving terminal and supplies it to the second medical data receiving terminal, and acquires the second medical data from the second medical data receiving terminal and imports it into the receiving database.

[0021] As a result, the exchange of the second medical data with the second medical data receiving terminal and the import of the second medical data are performed by the second medical data import terminal, not the first medical data receiving terminal. Therefore, the work for receiving and importing the first medical data can be separated from the work for receiving and importing the second medical data. This allows different users to perform the work on the first medical data receiving terminal and the second medical data import terminal, respectively. Alternatively, it is easy to automate either the first medical data receiving terminal or the second medical data import terminal.

[0022] The sending system includes: a first medical data transmission terminal connected to the first communication network and transmitting the first medical data to the management server; a second medical data transmission terminal connected to the second communication network and transmitting the second medical data to the external repository; may include:

[0023] This allows the first medical data and the second medical data to be transmitted from separate transmitting terminals (first medical data transmitting terminal and second medical data transmitting terminal).

[0024] The first medical data transmission terminal may be disconnected from the second communication network. The second medical data transmission terminal may be disconnected from the first communication network. This allows the second medical data to be transmitted via the second communication network while reducing the risk of external intrusion into the first medical data transmission terminal (and the first communication network).

[0025] The transmitting system may further include a token adding unit that guides a user through an operation to add the second medical data acquisition token to the first medical data or automatically adds the second medical data acquisition token to the first medical data, thereby improving convenience for a transmitting user when transmitting the first medical data via the first communication network and the second medical data via the second communication network.

[0026] The transmitting system may further include a second medical data export terminal that exports the second medical data to the second medical data transmission terminal. The second medical data export terminal may generate the second medical data acquisition token, provide the second medical data acquisition token to the first medical data transmission terminal, and provide the second medical data and the second medical data acquisition token to the second medical data transmission terminal.

[0027] As a result, the second medical data export terminal, rather than the first medical data transmission terminal, exchanges (exports) the second medical data and the second medical data acquisition token with the second medical data transmission terminal. Therefore, the tasks for transmitting the first medical data and the tasks for transmitting the second medical data can be separated. This allows different users to perform tasks on the first medical data transmission terminal and the second medical data export terminal. Alternatively, automation of either the first medical data transmission terminal or the second medical data export terminal is facilitated. Furthermore, by having the second medical data export terminal generate the second medical data acquisition token, the first medical data transmission terminal can be specialized in processing the first medical data, except for adding the second medical data acquisition token to the first medical data. Therefore, for example, if a process already exists on the first medical data transmission terminal that exchanges with the management server, the existing process can be used as is.

[0028] A medical data transmitting system according to another aspect of the present invention is a transmitting medical institution that transmits first medical data and second medical data to a medical data receiving system at a receiving medical institution, The medical data transmitting system includes: a first medical data transmission unit that transmits the first medical data to a management server via a first communication network; a second medical data transmission unit that transmits the second medical data to an external repository via a second communication network; a token generating unit that generates a second medical data acquisition token for acquiring the second medical data from the external repository; a token adding unit that guides an operation of adding the second medical data acquisition token to the first medical data or automatically adds the second medical data acquisition token to the first medical data; Equipped with It is characterized by:

[0029] A medical data receiving system according to yet another aspect of the present invention is a medical institution on the receiving side that receives first medical data and second medical data from a medical data transmitting system on the transmitting side, The medical data receiving system includes: a first medical data receiving unit that receives the first medical data from a management server via a first communication network; a second medical data receiving unit that receives the second medical data from an external repository via a second communication network; a token transfer unit that guides an operation to transfer a second medical data acquisition token, which includes information for acquiring the second medical data from the external repository and is included in the first medical data received by the first medical data receiving unit, to the second medical data receiving unit or that automatically transfers the second medical data acquisition token to the second medical data receiving unit; Equipped with It is characterized by:

[0030] A medical data transmission and reception method according to yet another aspect of the present invention is a method for transmitting first medical data and second medical data from a transmitting system in a transmitting medical institution to a receiving system in a receiving medical institution, the method comprising: Furthermore, the medical data transmission and reception method includes: a first medical data upload step of transmitting the first medical data from the transmitting system to a management server via a first communication network, and causing the management server to temporarily store the first medical data; a first medical data download step of transmitting the first medical data from the management server to the receiving system via the first communication network; a second medical data upload step of transmitting the second medical data from the transmitting system to an external repository via a second communication network, and causing the external repository to temporarily store the second medical data; a second medical data download step of transmitting the second medical data from the external repository to the receiving system via the second communication network; and Furthermore, the medical data transmission and reception method includes: a token generation step in which the transmitting system generates a second medical data acquisition token for acquiring the second medical data from the external repository; a token addition step of adding the second medical data acquisition token to the first medical data to be transmitted to the management server by an operation of a transmitting side user or automatically by the transmitting side system; The present invention is characterized by having the following. [Effects of the Invention]

[0031] According to the present invention, it is possible to reduce the burden on patients and to use a communication path appropriate for the type of medical data. [Brief explanation of the drawings]

[0032] [Figure 1] 1 is a schematic configuration diagram of a medical data transmission / reception system according to a first embodiment of the present invention. [Figure 2] FIG. 2 is a schematic configuration diagram of a sender's private network connecting terminal (sender's first terminal) according to the first embodiment. [Figure 3] FIG. 2 is a schematic diagram illustrating the configuration of a sender's Internet connection terminal (sender's second terminal) according to the first embodiment. [Figure 4] FIG. 2 is a schematic configuration diagram of a receiving-side private network terminal (first receiving terminal) according to the first embodiment. [Figure 5] FIG. 2 is a schematic configuration diagram of a receiving-side Internet connection terminal (receiving-side second terminal) according to the first embodiment. [Figure 6] FIG. 2 is a diagram showing an outline of the flow when shared data (first medical data and second medical data) is transmitted and received in the first embodiment. [Figure 7] FIG. 4 is a diagram showing a flow of transmission of shared data (first medical data and second medical data) in the first embodiment. [Figure 8]It is a diagram showing the flow at the time of receiving shared data (first medical data and second medical data) in the first embodiment. [Figure 9] It is a schematic configuration diagram of a medical data transmission / reception system according to a second embodiment of the present invention. [Figure 10] It is a diagram showing the flow at the time of transmitting shared data (first medical data and second medical data) in the second embodiment. [Figure 11] It is a diagram showing the flow at the time of receiving shared data (first medical data and second medical data) in the second embodiment.

Mode for Carrying Out the Invention

[0033] A. First Embodiment <A-1. Configuration of the First Embodiment> [A-1-1. Overall Configuration] FIG. 1 is a schematic configuration diagram of a medical data transmission / reception system 10 according to a first embodiment of the present invention. The medical data transmission / reception system 10 (hereinafter also referred to as the "transmission / reception system 10") includes a plurality of transmission-side systems 20, a data sharing server 30 (hereinafter also referred to as the "sharing server 30"), an authentication server 40, an external repository 50, and a plurality of reception-side systems 60. Note that in FIG. 1, only one transmission-side system 20 and one reception-side system 60 are shown. Also, here, for ease of understanding, the transmission-side system 20 and the reception-side system 60 are separated, but it is also possible that the transmission-side system 20 has the functions of the reception-side system 60 and the reception-side system 60 has the functions of the transmission-side system 20.

[0034] The transmitting system 20 and the shared server 30 can communicate with each other via a first communication network 70. Furthermore, the shared server 30 and the receiving system 60 can communicate with each other via the first communication network 70. Therefore, the first medical data D1 transmitted from the transmitting system 20 can be transmitted to the receiving system 60 via the shared server 30. The first communication network 70 is a closed network using a dedicated line, a virtual private network (VPN), or the like. Furthermore, the transmitting system 20, the authentication server 40, the external repository 50, and the receiving system 60 can communicate with each other via a second communication network 72, which is the Internet.

[0035] In the transmitting / receiving system 10, first medical data D1 including electronic medical record data Dm is transmitted from the transmitting system 20 to the receiving system 60 via the first communication network 70 and the shared server 30. The electronic medical record data Dm is electronic data of medical records relating to individual patients and is mainly composed of text data. The electronic medical record data Dm may include, for example, at least one of the name of an illness or injury, allergy information, infectious disease information, drug contraindication information, test information, and prescription information. In addition to or instead of the electronic medical record data Dm, the first medical data D1 may include one or both of referral letter data (medical information report data) and health examination result data.

[0036] Furthermore, in the transmitting / receiving system 10, second medical data D2 including medical image data Di is transmitted from the transmitting system 20 to the receiving system 60 via the second communication network 72 and the external repository 50. The second medical data D2 includes data larger in size than the first medical data D1. A second medical data acquisition token T2 (hereinafter also referred to as "token T2") including information for the receiving system 60 to acquire the second medical data D2 from the external repository 50 is included in the first medical data D1 and transmitted from the transmitting system 20 to the receiving system 60.

[0037] The authentication server 40 performs authentication (grant of access authority) when the sending system 20 and the receiving system 60 access the external repository 50 .

[0038] [A-1-2. Transmitting system 20] (A-1-2-1. Overview of the transmitting system 20) The transmitting system 20 is used by a medical institution that transmits the first medical data D1 and the second medical data D2. As described above, the transmitting system 20 transmits the first medical data D1 (electronic medical record data Dm, etc.) to the receiving system 60, which is the data transmission destination, via the first communication network 70 and the shared server 30. In addition, the transmitting system 20 transmits the second medical data D2 (medical image data Di, etc.) to the receiving system 60, which is the data transmission destination, via the second communication network 72 and the external repository 50.

[0039] 1, the sending system 20 includes a PACS 200, an electronic medical record system 210, an SS-MIX standardized storage 220, a sending private network connection terminal 230, a sending Internet connection terminal 240, and a router 250. Hereinafter, the sending private network connection terminal 230 will also be referred to as the sending first terminal 230, and the sending Internet connection terminal 240 will also be referred to as the sending second terminal 240.

[0040] The PACS 200, the electronic medical record system 210, the SS-MIX standardized storage 220, and the first transmitting terminal 230 can communicate with each other via a transmitting hospital network 260, but are separated from the second communication network 72. The first transmitting terminal 230 is connected to the first communication network 70 via a router (not shown). Therefore, the PACS 200, the electronic medical record system 210, and the SS-MIX standardized storage 220 are connected to the first communication network 70 via the first transmitting terminal 230. The second transmitting terminal 240 and the router 250 are connected to the second communication network 72, but are separated from the first communication network 70 and the transmitting hospital network 260.

[0041] PACS 200 is a medical image management system. PACS is an abbreviation for "Picture Archiving and Communication System." Electronic medical record system 210 is a system that manages electronic medical records. SS-MIX standardized storage 220 is storage standardized by the Ministry of Health, Labor and Welfare's Electronic Medical Information Exchange Promotion Project (SS-MIX: Standardized Structured Medical Information eXchange).

[0042] The first transmitting terminal 230 transmits electronic medical record data Dm and the like, which are medical data stored in the electronic medical record system 210, to the receiving system 60 as first medical data D1. The second transmitting terminal 240 transmits medical image data Di and the like, which are medical data stored in the PACS 200, to the receiving system 60 as second medical data D2. The router 250 is a device for connecting the second transmitting terminal 240 and the like to the second communication network 72 (Internet). The router 250 in this embodiment is not a VPN (Virtual Private Network) type, but may be a VPN type.

[0043] (A-1-2-2. Sending-side private network connection terminal 230) 2 is a schematic configuration diagram of the transmitting-side private network connection terminal 230 (transmitting-side first terminal 230) according to the first embodiment. As described above, the transmitting-side first terminal 230 can display medical data stored in the PACS 200, the electronic medical record system 210, and the SS-MIX standardized storage 220. The transmitting-side first terminal 230 also transmits electronic medical record data Dm and the like (first medical data D1) as medical data stored in the electronic medical record system 210 to the receiving-side system 60 via a router (not shown), the first communication network 70, and the data sharing server 30. The transmitting-side first terminal 230 can be, for example, an information terminal such as a general personal computer (desktop type, notebook type, etc.), a smartphone, or a tablet terminal.

[0044] As shown in FIG. 2, the transmitting-side first terminal 230 has a communication device 2300, an input / output device 2310, a control device 2320, and a storage device 2330. The communication device 2300 is capable of communicating with the shared server 30 and the like via the first communication network 70 (FIG. 1). The input / output device 2310 accepts input from a user of the transmitting-side first terminal 230 (a person in charge (such as a doctor, a system person, an assistant, or an office worker) at the transmitting medical institution) and outputs to the user. The input / output device 2310 includes a keyboard 2311 and a mouse 2312 as user input devices, a display device 2313 as a user output device, and a recording medium drive 2314. If the transmitting-side first terminal 230 is, for example, a tablet terminal, the display device 2313 as a touch panel can also serve as an input device instead of the keyboard 2311 and the mouse 2312 (the same applies to other terminals (such as the transmitting-side second terminal 240)).

[0045] The control device 2320 controls the entire transmitting side first terminal 230. In the first embodiment, the control device 2320 performs processing related to the transmission of the first medical data D1. The storage device 2330 stores software executed by the control device 2320 and various data.

[0046] 2, the control device 2320 has a medical data processing unit 2321, a shared data generation unit 2322, a second medical data etc. output unit 2323, and a first medical data upload unit 2324. Each of the above units of the control device 2320 is positioned as a functional unit of the control device 2320, and is realized mainly by software.

[0047] In response to user input via a keyboard 2311 and a mouse 2312, the medical data processing unit 2321 reads medical data from the PACS 200, the electronic medical record system 210, and the SS-MIX standardized storage 220, displays the data on a display device 2313, and registers new medical data therein.

[0048] The shared data generation unit 2322 generates shared data Dsh as medical data to be provided to the destination medical institution (receiving system 60) in response to user input via the keyboard 2311 and mouse 2312. The shared data Dsh includes first medical data D1 including electronic medical record data Dm and second medical data D2 including medical image data Di. As described above, the first medical data D1 may include one or both of referral letter data (medical information report data) and medical examination result data in addition to or instead of the electronic medical record data Dm.

[0049] The shared data generation unit 2322 has a token generation unit 2325 that generates a second medical data acquisition token T2. ​​The token T2 is used when the receiving system 60 downloads the second medical data D2 that the transmitting system 20 has uploaded to the external repository 50. The token T2 includes, for example, a second medical data ID that is an identification code for the second medical data D2, and a password (common key) used to encrypt the second medical data D2. In the first embodiment, the token T2 is added to the first medical data D1. In the first embodiment, the token T2 included in the first medical data D1 is a two-dimensional code.

[0050] The second medical data output unit 2323 outputs the second medical data D2 and token T2 generated by the shared data generation unit 2322 to the outside. Specifically, the second medical data output unit 2323 outputs (copies) the second medical data D2 and token T2 to the transmitting portable recording medium 270 (FIG. 1) inserted into the recording medium drive 2314. The transmitting portable recording medium 270 may be, for example, a flash memory.

[0051] The first medical data upload unit 2324 uploads the first medical data D1 generated by the shared data generation unit 2322 to the data sharing server 30 via the first communication network .

[0052] (A-1-2-3. Sending side Internet connection terminal 240) 3 is a schematic diagram of the sending-side internet connection terminal 240 (sending-side second terminal 240) according to the first embodiment. As described above, the sending-side second terminal 240 acquires the second medical data D2 and the token T2 from the sending-side first terminal 230 via the sending-side portable recording medium 270. The sending-side second terminal 240 then uploads the second medical data D2 to the external repository 50 via the second communication network 72. At that time, part of the information in the token T2 (such as a data identifier) ​​is used. The sending-side second terminal 240 may be, for example, an information terminal such as a general personal computer (desktop, notebook, etc.), a smartphone, or a tablet terminal.

[0053] As shown in FIG. 3, the transmitting second terminal 240 has a communication device 2400, an input / output device 2410, a control device 2420, and a storage device 2430. The communication device 2400 is capable of communicating with the authentication server 40, the external repository 50, etc. via the router 250 and the second communication network 72 (FIG. 1). The input / output device 2410 accepts input from a user of the transmitting second terminal 240 (a person in charge (doctor, system person, assistant, office worker, etc.) of the transmitting medical institution) and outputs to the user. The input / output device 2410 includes a keyboard 2411 and a mouse 2412 as user input devices, a display device 2413 as user output devices, and a recording medium drive 2414.

[0054] The control device 2420 controls the entire transmitting side second terminal 240. In the first embodiment, the control device 2420 performs processing related to the transmission of the second medical data D2. The storage device 2430 stores software executed by the control device 2420 and various data.

[0055] 3, the control device 2420 has a second medical data input unit 2421 and a second medical data upload unit 2422. The above-mentioned units of the control device 2420 are positioned as functional units of the control device 2420, and are mainly realized by software.

[0056] The second medical data input unit 2421 imports the second medical data D2 and token T2 recorded on the transmitting-side portable recording medium 270 inserted in the recording medium drive 2414 into the storage device 2430. The second medical data upload unit 2422 uploads the imported second medical data D2 to the external repository 50. At that time, the second medical data upload unit 2422 uses the information of the imported token T2. ​​Specifically, the second medical data D2 to be uploaded is encrypted with a password (common key) included in the token T2. ​​The second medical data ID included in the token T2 is also transmitted to the external repository 50. The second medical data D2 may be encrypted in advance by the transmitting-side first terminal 230.

[0057] [A-1-3. Data Sharing Server 30] The data shared server 30 receives and temporarily stores first medical data D1 (electronic medical record data Dm, token T2, etc.) from the transmitting system 20 via a first communication network 70, which is a closed network. The shared server 30 also transmits the first medical data D1 to the receiving system 60 via the first communication network 70 (details will be described later with reference to FIG. 6, etc.). The shared server 30 has a communication device, an input / output device, a control device, and a storage device, all of which are not shown. Although the shared server 30 is described here as a single physical server, the shared server 30 may be configured from multiple physical servers or virtual servers for each function or role of the shared server 30.

[0058] [A-1-4. Authentication Server 40] The authentication server 40 performs authentication (grant of access authority) when the sending system 20 and the receiving system 60 access the external repository 50. The authentication server 40 has a communication device, an input / output device, a control device, and a storage device, which are not shown. Although the authentication server 40 is described here as a single physical server, the authentication server 40 may be configured from multiple physical servers or virtual servers for each function or role of the authentication server 40.

[0059] [A-1-5. External repository 50] The external repository 50 receives the second medical data D2 (medical image data Di, etc.) from the sending system 20 via the second communication network 72 and temporarily stores the data. The external repository 50 then transfers the second medical data D2 to the receiving system 60 via the second communication network 72. The external repository 50 can be configured as, for example, cloud storage. The external repository 50 includes a communication device, an input / output device, a control device, and a storage device, all of which are not shown. Although the external repository 50 is described here as being configured as a single physical unit, the external repository 50 may also be configured from multiple physical servers or virtual servers for each function or role of the external repository 50.

[0060] [A-1-6. Receiving system 60] (A-1-6-1. Overview of Receiving System 60) The receiving system 60 is used in a medical institution that receives the first medical data D1 and the second medical data D2. As described above, the receiving system 60 receives the first medical data D1 (electronic medical record data Dm, token T2, etc.) from the transmitting system 20 via the first communication network 70 and the shared server 30. The receiving system 60 also receives the second medical data D2 (medical image data Di, etc.) from the transmitting system 20 via the second communication network 72 and the external repository 50.

[0061] 1, the receiving system 60 includes a receiving private network connection terminal 600, a card reader 610, a router 620, a receiving internet connection terminal 630, an optical sensor 640, a RIS terminal 650, a PACS 660, an electronic medical record system 670, and an SS-MIX standardized storage 680. Hereinafter, the receiving private network connection terminal 600 will also be referred to as the first receiving terminal 600, and the receiving internet connection terminal 630 will also be referred to as the second receiving terminal 630.

[0062] The receiving-side first terminal 600, the RIS terminal 650, the PACS 660, the electronic medical record system 670, and the SS-MIX standardized storage 680 can communicate with each other via a receiving-side hospital network 690, but are separated from the second communication network 72. The receiving-side first terminal 600 is also connected to the first communication network 70 via a router (not shown). Therefore, the RIS terminal 650, the PACS 660, the electronic medical record system 670, and the SS-MIX standardized storage 680 are connected to the first communication network 70 via the receiving-side first terminal 600. The receiving-side second terminal 630 and the router 620 are connected to the second communication network 72, but are separated from the first communication network 70 and the receiving-side hospital network 690.

[0063] The receiving first terminal 600 is connected to the first communication network 70 to receive first medical data D1 (electronic medical record data Dm, token T2, etc.) from the shared server 30 and imports it into the electronic medical record system 670, etc. The receiving first terminal 600 also imports second medical data D2 received from the transmitting system 20 via the second communication network 72 and the receiving second terminal 630 into the PACS 660, etc. The card reader 610 reads data (patient identification data) from a personal identification card (e.g., My Number card) of a patient (a person referred from the hospital of the transmitting system 20 to the hospital of the receiving system 60).

[0064] The router 620 is a device for connecting the receiving second terminal 630 and the like to the second communication network 72 (Internet). The router 620 in this embodiment is not a VPN type, but it may be a VPN type. The receiving second terminal 630 imports the second medical data D2 (medical image data Di, etc.) from the transmitting system 20 to the PACS 660, etc. The optical sensor 640 reads the two-dimensionally coded token T2.

[0065] The RIS terminal 650 is a terminal for a Radiology Information System. The PACS 660 is a medical image management system. The electronic medical record system 670 is a system for managing electronic medical records. The SS-MIX standardized storage 680 is storage standardized by SS-MIX.

[0066] (A-1-6-2. Receiving-side private network connection terminal 600) 4 is a schematic configuration diagram of a receiving-side private network terminal 600 (receiving-side first terminal 600) according to the first embodiment. As described above, the receiving-side first terminal 600 can display medical data stored in the RIS terminal 650, PACS 660, electronic medical record system 670, and SS-MIX standardized storage 680. The receiving-side first terminal 600 is also connected to a first communication network 70 to receive first medical data D1 (electronic medical record data Dm, token T2, etc.) from the shared server 30 and import it into the electronic medical record system 670, etc. The receiving-side first terminal 600 can be, for example, an information terminal such as a general personal computer (desktop type, notebook type, etc.), a smartphone, or a tablet terminal.

[0067] As shown in FIG. 4, the receiving-side first terminal 600 has a communication device 6000, an input / output device 6010, a control device 6020, and a storage device 6030. The communication device 6000 is capable of communicating with the shared server 30 and the like via the first communication network 70 (FIG. 1). The input / output device 6010 accepts input from a user of the receiving-side first terminal 600 (a person in charge (such as a doctor, system person, assistant, or office worker) at the destination medical institution) and outputs to the user. The input / output device 6010 includes a keyboard 6011 and a mouse 6012 as user input devices, a display device 6013 as user output devices, and a recording medium drive 6014.

[0068] The control device 6020 controls the entire receiving side first terminal 600. In the first embodiment, the control device 6020 performs processing related to receiving the first medical data D1 and importing the second medical data D2. The storage device 6030 stores software executed by the control device 6020 and various data.

[0069] 4, the control device 6020 has a card reader control unit 6021, a first medical data download unit 6022, a token output unit 6023, and a second medical data input unit 6024. Each of the above units of the control device 6020 is positioned as a functional unit of the control device 6020, and is mainly realized by software.

[0070] The card reader control unit 6021 controls the operation of the card reader 610 to acquire patient identification data from the patient's personal identification card (patient card). The first medical data download unit 6022 downloads first medical data D1 (electronic medical record data Dm, token T2, etc.) from the shared server 30 using the patient identification data read from the card reader 610 and the identification data of the receiving medical institution (receiving system 60), and imports the first medical data D1 into the electronic medical record system 670, etc.

[0071] The token output unit 6023 displays the token T2 (two-dimensionally coded) included in the downloaded first medical data D1 on the display device 6013. This enables the optical sensor 640 on the receiving second terminal 630 to read the token T2. ​​The second medical data input unit 6024 reads the second medical data D2 (medical image data Di, etc.) from the receiving portable recording medium 692 (FIG. 1) on which the second medical data D2 is recorded on the receiving second terminal 630, and imports the second medical data D2 into the PACS 660, etc.

[0072] (A-1-6-3. Card reader 610) The card reader 610 reads data (patient identification data) from a personal identification card (for example, My Number card) of a patient (a person referred from the hospital of the transmitting system 20 to the hospital of the receiving system 60).

[0073] (A-1-6-4. Receiving side Internet connection terminal 630) 5 is a schematic diagram of the receiving internet connection terminal 630 (second receiving terminal 630) according to the first embodiment. The second receiving terminal 630 is connected to the second communication network 72 and receives the second medical data D2 from the external repository 50. As described above, the second receiving terminal 630 acquires the token T2 from the first receiving terminal 600 via the optical sensor 640. The second receiving terminal 630 then downloads the second medical data D2 from the external repository 50 via the second communication network 72, using the information in the token T2. ​​The second receiving terminal 630 may be, for example, an information terminal such as a general personal computer (desktop, notebook, etc.), a smartphone, or a tablet terminal.

[0074] As shown in Fig. 5, the receiving-side second terminal 630 has a communication device 6300, an input / output device 6310, a control device 6320, and a storage device 6330. The communication device 6300 is capable of communicating with the external repository 50 and the like via the router 620 and the second communication network 72 (Fig. 1). The input / output device 6310 accepts input from a user of the receiving-side second terminal 630 (a person in charge (doctor, system person, assistant, office worker, etc.) of the destination medical institution) and outputs to the user. The input / output device 6310 includes a keyboard 6311 and a mouse 6312 as user input devices, a display device 6313 as user output devices, and a recording medium drive 6314.

[0075] The control device 6320 controls the entire receiving side second terminal 630. In the first embodiment, the control device 6320 performs processing related to the reception of the second medical data D2. The storage device 6330 stores software executed by the control device 6320 and various data.

[0076] 5, the control device 6320 has a token input unit 6321, a second medical data download unit 6322, and a second medical data output unit 6323. The above units of the control device 6320 are positioned as functional units of the control device 6320 and are mainly realized by software. The token input unit 6321 reads the second medical data acquisition token D2 (two-dimensionally coded) displayed on the first receiving terminal 600 via the optical sensor 640 and inputs it to the second receiving terminal 630.

[0077] The second medical data download unit 6322 downloads the second medical data D2 from the external repository 50. At that time, the second medical data download unit 6323 uses the information of the imported token T2. ​​Specifically, the second medical data D2 to be downloaded is identified by the data ID included in the token T2. ​​The downloaded second medical data D2 is decrypted using the password (common key) included in the token T2. ​​The second medical data output unit 6323 outputs the second medical data D2 downloaded by the second medical data download unit 6322 to an external device. Specifically, the second medical data output unit 6323 outputs (copies) the second medical data D2 to a receiving-side portable recording medium 692 inserted in the recording medium drive 6314. The receiving-side portable recording medium 692 can be, for example, a flash memory.

[0078] (A-1-6-5. Optical sensor 640) The optical sensor 640 reads the two-dimensionally coded token T2. ​​The optical sensor 640 of the first embodiment functions as a receiving-side token transmission means that transmits the second medical data acquisition token T2 included in the first medical data D1 received by the first receiving terminal 600 from the shared server 30 to the second receiving terminal 630.

[0079] [A-1-7. First communication network 70] The first communication network 70 is a closed network using a dedicated line, a virtual private network (VPN), or the like. In the first communication network 70 of FIG. 1, it is assumed that each transmission-side system 20 is connected to the shared server 30 by a dedicated line and each reception-side system 60 is connected to the shared server 30 by a dedicated line (a so-called star type) network configuration. However, the network configuration of the first communication network 70 may be other types (for example, a tree type). The first communication network 70 has a slower communication speed or a smaller communication capacity than the second communication network 72.

[0080] [A-1-8. The second communication network 72] The second communication network 72 is the Internet and enables communication between the transmission-side system 20, the authentication server 40, the external repository 50, and the reception-side system 60. The second communication network 72 may be a closed network with a faster communication speed or a larger communication capacity than the first communication network 70.

[0081] <A-2. Operations and processes in the first embodiment> [A-2-1. Overview] Next, the user operations in the first embodiment and the processing of each part of the transmission and reception system 10 will be described. As described above, in the first embodiment, the shared data Dsh is transmitted from the transmission-side system 20 to the reception-side system 60. Among the shared data Dsh, the first medical data D1 (such as electronic medical record data Dm) is transmitted via the first communication network 70, which is a closed network, and the shared server 30. Also, among the shared data Dsh, the second medical data D2 (such as medical image data Di) is transmitted via the second communication network 72, which is the Internet, and the external repository 50. A token T2 for the reception-side system 60 to download the second medical data D2 from the external repository 50 is included in the first medical data D1 and is transmitted via the first communication network 70 and the shared server 30.

[0082] [A-2-2. General flow during medical data transmission and reception] Fig. 6 is a diagram showing an outline of the flow of transmitting and receiving shared data Dsh (first medical data D1 and second medical data D2) in the first embodiment. Of the steps in Fig. 6, steps S101 to S105 are performed when a patient visits a medical institution that referred the patient (a medical institution that has the transmitting system 20), and steps S201 to S207 are performed when the patient visits a medical institution that referred the patient (a medical institution that has the receiving system 60). Further details of the operations and processing in Fig. 6 will be described later with reference to Figs. 7 and 8.

[0083] In step S101 of FIG. 6, the transmitting system 20 generates shared data Dsh (first medical data D1 and second medical data D2) based on the operation of a user (a person in charge (such as a doctor, system person, assistant, or office worker) at the transmitting medical institution). In step S102, the transmitting system 20 uploads the second medical data D2 (such as medical image data Di) to the external repository 50 based on the operation of the user. In step S103, the external repository 50 temporarily stores the second medical data D2 uploaded from the transmitting system 20.

[0084] In step S104, the transmitting system 20 uploads the first medical data D1 (electronic medical record data Dm, token T2, etc.) based on a user operation to the shared server 30. In step S105, the shared server 30 temporarily stores the first medical data D1 uploaded from the transmitting system 20.

[0085] When a patient goes to a medical institution to which the patient is referred (a medical institution where the receiving system 60 is located), in step S201, the receiving system 60 reads the patient information from the patient card via the card reader 610 based on the operation of a user (a person in charge at the destination medical institution (such as a doctor, system person, assistant, or office worker)). In step S202, the receiving system 60 requests the shared server 30 to download first medical data D1 corresponding to the read patient information. In step S203, the shared server 30 downloads the first medical data D1 corresponding to the patient information to the receiving system 60. In step S204, the receiving system 60 saves the downloaded first medical data D1.

[0086] In step S205, the receiving system 60 requests the external repository 50 to download the second medical data D2. At that time, the receiving system 60 uses the token T2 included in the first medical data D1. In step S206, the external repository 50 downloads the second medical data D2 requested by the receiving system 60 to the receiving system 60. In step S207, the receiving system 60 saves the downloaded second medical data D2.

[0087] [A-2-3. Flow of sending shared data] 7 is a diagram showing a flow of transmission of shared data Dsh (first medical data D1 and second medical data D2) in the first embodiment. Each step in FIG. 7 shows details of steps S101 to S105 in FIG.

[0088] In step S301 of FIG. 7, the private network connection terminal 230 (first transmitting terminal 230) of the transmitting system 20 accepts a request to generate shared data Dsh (first medical data D1 and second medical data D2) based on the operation of a user (a person in charge (doctor, system person, assistant, office worker, etc.) of the transmitting medical institution). For example, when the "Create shared data" button (not shown) is selected while the patient's medical record data is displayed or selected on the display device 2313 of the first transmitting terminal 230, the first transmitting terminal 230 (shared data generation unit 2322) displays a shared data input screen (not shown).

[0089] In step S302, the transmitting first terminal 230 (shared data generator 2322) generates shared data Dsh (first medical data D1 and second medical data D2) based on the user's input on the shared data input screen. On the shared data input screen, the first medical data D1 (electronic medical record data Dm, etc.) and second medical data D2 (medical image data Di, etc.) are displayed and input or selected.

[0090] The shared data input screen includes, for example, a patient name input field, an examination input field, a medical data input field, a transmission destination input field, and a confirm button (none of which are shown). The patient name input field is an input field for the name of a patient to whom shared data is to be sent to a destination medical institution. The examination input field is an input field for the examination details that specify the medical data to be sent. The medical data input field is a field for inputting one or more pieces of medical data to be sent (e.g., data on a medical information report, an image file showing test results, prescription data) and a token T2 that are included in the shared data. Note that medical data with a relatively small data size entered in the medical data input field is attached as is and included in the first medical data D1. On the other hand, medical data with a relatively large data size entered in the medical data input field is not included in the first medical data D1 and is transmitted as included in the second medical data D2. The transmission destination input field is a field for inputting a transmission destination of the shared data Dsh selected from multiple receiving systems 60.

[0091] When inputting data into the patient name input field, test input field, and medical data input field, the transmitting system 20 (the first transmitting terminal 230) may assist the user's input by appropriately acquiring data from the PACS 200, the electronic medical record system 210, or the SS-MIX standardized storage 220 and using an easy-to-use user interface. Examples of such a user interface include keyword search and thumbnail display of image data. Similarly, when inputting data into the destination input field, the transmitting system 20 (the first transmitting terminal 230) may assist the user's input by, for example, acquiring data of the destination medical institution (the receiving system 60) from the shared server 30 and using an easy-to-use user interface.

[0092] The decision button is a button for deciding the input content on the shared data input screen. When the decision button is pressed, the process proceeds to step S303. Note that part of step S302 (e.g., selection of the transmission destination, selection of medical data (file) to be transmitted) can be performed in the same way as in Patent Document 1.

[0093] In step S303, the transmitting first terminal 230 (token generating unit 2325) generates a second medical data acquisition token T2. ​​The token T2 includes, for example, a second medical data ID, which is an identification code of the second medical data D2, and a password (common key) used to encrypt the second medical data D2.

[0094] In step S304, the transmitting-side first terminal 230 (second medical data output unit 2323) copies the second medical data D2 and the token T2 to the transmitting-side portable recording medium 270 inserted in the recording medium drive 2314. For example, when a shared data determination button (not shown) is pressed on the shared data input screen, the transmitting-side first terminal 230 displays a message such as "Please insert the transmitting-side portable recording medium into the recording medium drive and press the 'copy button'." Then, when the copy button (not shown) is pressed with the transmitting-side portable recording medium 270 inserted in the recording medium drive 2314, the transmitting-side first terminal 230 copies the second medical data D2 and the token T2 selected on the shared data input screen to the transmitting-side portable recording medium 270.

[0095] In step S305, the transmitting first terminal 230 (second medical data etc. output unit 2323) displays a message (second medical data etc. transfer request message) requesting that the data (second medical data D2 and token T2) copied to the transmitting portable recording medium 270 be transferred to the transmitting internet connection terminal 240 (transmitting second terminal 240). Also displayed is a message requesting that the transmitting portable recording medium 270 be removed from the recording medium drive 2314 of the transmitting first terminal 230 and inserted into the recording medium drive 2414 of the transmitting second terminal 240, and that the second medical data upload application software be started on the transmitting second terminal 240.

[0096] In step S306, the user, upon seeing these messages, removes the transmitting-side portable recording medium 270 from the recording medium drive 2314 of the first transmitting-side terminal 230 and then inserts it into the recording medium drive 2414 of the second transmitting-side terminal 240. The user also starts up the second medical data upload application software on the second transmitting-side terminal 240. Note that step S306 is a user operation that does not include processing by the transmitting-side system 20, and therefore the arrow corresponding to step S306 in FIG. 7 is indicated by a dashed line.

[0097] In step S307, the transmitting second terminal 240 (second medical data etc. input unit 2421) acquires the second medical data D2 and the token T2 from the transmitting portable recording medium 270 inserted in the recording medium drive 2414. For example, when the second medical data upload application software is started on the transmitting second terminal 240, a second medical data import button (not shown) is displayed on the operation screen. When the user selects the second medical data import button, the transmitting second terminal 240 (second medical data etc. input unit 2421) acquires the second medical data D2 and the token T2 from the transmitting portable recording medium 270 inserted in the recording medium drive 2414, and displays the acquired second medical data D2 (medical image data).

[0098] In step S308, the transmitting second terminal 240 (second medical data upload unit 2422) uploads the second medical data D2 to the external repository 50 using the token T2. ​​For example, a second medical data upload button (not shown) is displayed together with the acquired second medical data D2 (medical image data Di). When the user selects the second medical data upload button, the transmitting second terminal 240 (second medical data upload unit 2422) uploads the second medical data D2 to the external repository 50 using the token T2. ​​That is, the transmitting second terminal 240 encrypts the second medical data D2 to be uploaded with the password (common key) included in the token T2. ​​The transmitting second terminal 240 also transmits the second medical data ID included in the token T2 to the external repository 50.

[0099] In step S309, the external repository 50 temporarily stores the second medical data D2 received from the second transmitting terminal 240. When the upload to the external repository 50 is complete, in step S310, the second transmitting terminal 240 (second medical data upload unit 2422) displays a message notifying the user that the upload of the second medical data D2 is complete. In addition, the second transmitting terminal 240 also displays a message requesting the user to perform subsequent operations (such as converting the token T2 into a two-dimensional code and uploading the first medical data D1). Upon seeing this message, the user moves from the second transmitting terminal 240 to the first transmitting terminal 230 and performs the operations related to step S311.

[0100] Before the second transmitting terminal 240 uploads the second medical data D2 to the external repository 50 in step S308, the second transmitting terminal 240 may request access authority to the external repository 50 from the authentication server 40. The request may include authentication information for the transmitting system 20 or the second transmitting terminal 240. This authentication information may include, for example, an account number and account password for the transmitting system 20 or the second transmitting terminal 240. In response, the authentication server 40 grants access authority to the second transmitting terminal 240. More specifically, the authentication server 40 uses the authentication information included in the request from the second transmitting terminal 240 to confirm (authenticate) whether the second transmitting terminal 240 is permitted to access the external repository 50. If the authentication is successful, the authentication server 40 then transmits a token (access token) indicating access authority to the second transmitting terminal 240. The access token may be, for example, one defined in OAuth 2.0. A similar authentication process may also be performed when the second receiving terminal 630 requests the external repository 50 to download the second medical data D2 (S407 in FIG. 8).

[0101] In step S311, the transmitting first terminal 230 (first medical data upload unit 2324) converts the token T2 as text data into a two-dimensional code based on a user operation. For example, when a two-dimensional code button (not shown) displayed on the display device 2313 is selected by the user, the token T2 is converted into a two-dimensional code. The encoded token T2 is then displayed in the medical data input field of the shared data input screen. The addition of the token T2 to the first medical data D1 may be performed automatically by the transmitting first terminal 230 instead of manually by the user.

[0102] In step S312, triggered by a user operation (e.g., selection of the first medical data upload button), the transmitting first terminal 230 uploads the first medical data D1 including the two-dimensionally coded token T2 (coded image) to the shared server 30. In step S313, the shared server 30 temporarily stores the first medical data D1 received from the transmitting first terminal 230.

[0103] As described above, it is the first transmitting terminal 230, not the second transmitting terminal 240, that generates the token T2. ​​Therefore, steps S311 to S313 can be performed, for example, immediately after step S303. However, considering that the first medical data D1 (including token T2) is uploaded after confirming that the upload of the second medical data D2 has been completed, it is preferable to perform steps S311 to S313 after the upload of the second medical data D2 has been completed. Furthermore, token T2 can also be generated by the second transmitting terminal 240, not the first transmitting terminal 230. In this case, it becomes necessary to transmit token T2 from the second transmitting terminal 240 to the first transmitting terminal 230 using the transmitting portable recording medium 270 or the like.

[0104] [A-2-4. Flow when receiving shared data] 8 is a diagram showing a flow of receiving shared data Dsh (first medical data D1 and second medical data D2) in the first embodiment. Each step in FIG. 8 shows details of steps S201 to S207 in FIG.

[0105] In step S401 of Figure 8, the private network connection terminal 600 (first receiving terminal 600) of the receiving system 60 reads the patient identification data from the patient card based on the operation of the user (a person in charge at the destination medical institution (doctor, system person, assistant, office worker, etc.)) and using the card reader 610.

[0106] For example, when a new patient referred from a referring medical institution visits a referring medical institution for the first examination, the user starts the referred patient data registration software on the receiving first terminal 600. The software (or the card reader control unit 6021) displays, for example, a "referred patient data registration button" (not shown) on the screen of the display device 6013. When the user selects the referred patient data registration button, the software displays a message requesting the patient identification card to be read using the card reader 610, and waits for or monitors for input of patient identification data from the card reader 610. When the user reads the patient identification card using the card reader 610, the software accepts the input of patient identification data from the patient identification card.

[0107] In step S402, the receiving first terminal 600 (first medical data download unit 6022) requests the shared server 30 to download the first medical data D1 corresponding to the patient identification data. In this request, the receiving first terminal 600 transmits, for example, the identification number of the receiving medical institution (or the receiving system 60 or the receiving first terminal 600), the patient identification data, etc. to the shared server 30. In step S403, the shared server 30 downloads the first medical data D1 in response to the request to the receiving first terminal 600.

[0108] In step S404, the receiving first terminal 600 (first medical data download unit 6022) saves the downloaded first medical data D1 (electronic medical chart data Dm, etc.) in the electronic medical chart system 670, etc. via the receiving hospital network 690. When the download and saving of the first medical data D1 (S404) is complete, the receiving first terminal 600 (first medical data download unit 6022) displays a message indicating that the download is complete and an OK button (not shown). When the user presses the OK button, the process proceeds to step S405.

[0109] The specific process for downloading and saving the first medical data D1 can be performed, for example, as follows. That is, when the download of the first medical data D1 is completed, the receiving first terminal 600 displays a screen (downloaded first medical data display screen) (not shown) showing the contents of the downloaded first medical data D1. After the user confirms the contents of the downloaded first medical data display screen, the user presses a first medical data import button (not shown) on the screen. When this button is pressed, the receiving first terminal 600 saves or registers the downloaded first medical data D1 (electronic medical record data Dm, etc.) in the electronic medical record system 670, etc.

[0110] Furthermore, in the first embodiment, the RIS terminal 650 manages the patient data at the highest level so that the destination medical institution can associate and manage each patient data. Therefore, in order to associate the patient data managed by the RIS terminal 650 with the first medical data D1 received from the transmitting system 20, an import command must be issued by the RIS terminal 650 when importing the first medical data D1.

[0111] If this is the patient's first visit to the destination medical institution, the patient's basic data (patient ID number, etc.) is entered and recorded in the RIS terminal 650. Then, the RIS terminal 650 issues an import command to the first receiving terminal 600. The user of the first receiving terminal 600 confirms that the patient specified in the import command is the same as the patient in the first medical data D1 that has been downloaded by the first receiving terminal 600, and then imports the data into the PACS 660, electronic medical record system 670, SS-MIX standardized storage 680, etc.

[0112] When a patient is returning to the destination medical institution, just as in the case of an initial visit, the user of the receiving first terminal 600 confirms that the patient identified in the import command is the same as the patient in the first medical data D1 that has already been downloaded by the receiving first terminal 600, and then imports the data into the PACS 660, electronic medical record system 670, SS-MIX standardized storage 680, etc.

[0113] Note that part of the import process can be performed in the same way as in Patent Document 1.

[0114] In step S405, the receiving first terminal 600 (token output unit 6023) displays the token T2 (two-dimensionally coded) included in the downloaded first medical data D1 on the display device 6013. At this time, the receiving first terminal 600 also displays on the display device 6013 a message (read request message) stating, "Start the software for downloading the medical image data Di (second medical data D2) on the receiving second terminal 630, insert the receiving portable recording medium 692 into the recording medium drive 6314, and press the 'medical image data download button', and then read the two-dimensional token T2 with the optical sensor 640 and download and copy the second medical data D2 to the receiving portable recording medium 692." Furthermore, the read request message may include a message indicating that when copying of the second medical data D2 to the receiving portable recording medium 692 is complete, the receiving portable recording medium 692 should be inserted into the recording medium drive 6014 of the receiving first terminal 600.

[0115] In step S406, the receiving second terminal 630 (token input unit 6321) reads the token T2 (two-dimensionally coded) displayed on the display device 6013 of the receiving first terminal 600 based on the user's operation and via the optical sensor 640.

[0116] For example, upon seeing the read request message displayed on the display device 6013 of the first receiving terminal 600, the user starts software for downloading the medical image data Di (second medical data D2) on the second receiving terminal 630. In other words, the second receiving terminal 630 starts the software based on the user's operation. The screen after startup includes a medical image data download button (not shown).

[0117] Next, when the user selects the medical image data download button on the second receiving terminal 630, the software (second medical data download unit 6322) displays a message requesting that the token T2 displayed on the first receiving terminal 600 be read using the optical sensor 640, and waits for or monitors for input of the token T2 from the optical sensor 640. When the user reads the token T2 using the optical sensor 640, the process proceeds to step S407. Note that if the receiving portable recording medium 692 is not inserted in the recording medium drive 6313 at this point, the first receiving terminal 600 may display a message requesting that the receiving portable recording medium 692 be inserted.

[0118] In step S407, the second receiving terminal 630 (second medical data download unit 6322) requests the external repository 50 to download the second medical data D2 based on the read token T2. ​​In the request, the second receiving terminal 630 transmits, for example, the second medical data ID.

[0119] It is assumed here that the URL (Uniform Resource Locator) of the external repository 50 is registered in advance in the second receiving terminal 630, but the URL of the external repository 50 may be included in the token T2, and the second receiving terminal 630 may access the external repository 50 based on this. Furthermore, when the second sending terminal 240 uploads the second medical data D2 to the external repository 50, the external repository 50 may be notified of the identification ID of the receiving system 60, and when the second receiving terminal 630 accesses the external repository 50, the external repository 50 may determine whether the identification ID of the receiving system 60 matches.

[0120] In step S408, the external repository 50 downloads the second medical data D2 in response to the request to the receiving second terminal 630. In step S409, the receiving second terminal 630 (second medical data output unit 6323) copies the downloaded second medical data D2 to the receiving portable recording medium 692. In addition, in order to associate the second medical data D2 with the first medical data D1 (electronic medical record data Dm, etc.), the receiving second terminal 630 records the content of the token T2 (two-dimensional coded data or text data) read in step S406 together with the copy of the second medical data D2 to the receiving portable recording medium 692.

[0121] When the download of the second medical data D2 and the copying to the receiving-side portable recording medium 692 (S409) are completed, the receiving-side second terminal 630 (second medical data output unit 6323) requests the user to transfer the downloaded second medical data D2 to the receiving-side first terminal 600. For example, the receiving-side second terminal 630 displays a message indicating that the download of the second medical data D2 is completed and a request to remove the receiving-side portable recording medium 692 from the recording medium drive 6314 and insert it into the recording medium drive 6014 of the receiving-side first terminal 600, as well as an OK button (not shown).

[0122] When the user who has seen the message presses the OK button and removes the receiving-side portable recording medium 692 from the recording medium drive 6314 and inserts (moves) it into the recording medium drive 6014 (step S411). Note that since step S411 is a user operation that does not include the processing of the receiving-side system 60, the arrow corresponding to step S411 in FIG. 8 is shown by a dashed line.

[0123] When the receiving-side portable recording medium 692 is inserted into the recording medium drive 6014 of the receiving-side first terminal 600, in step S412, the receiving-side first terminal 600 (second medical data input unit 6024) causes the second medical data D2 (especially medical image data Di) recorded on the receiving-side portable recording medium 692 to be saved (imported) to the PACS 660 or the like via the receiving-side in-hospital network 690.

[0124] In addition, the specific processing when inputting the second medical data D2 from the receiving-side portable recording medium 692 to the receiving-side first terminal 600 can be performed as follows, for example. That is, when detecting the insertion of the receiving-side portable recording medium 692 into the recording medium drive 6014, the receiving-side first terminal 600 reads the content of the token T2 recorded on the receiving-side portable recording medium 692. Then, it is determined whether the content of the token T2 read from the receiving-side portable recording medium 692 corresponds to the first medical data D1 (or electronic medical record data Dm, etc.) saved in step S404. If, by this determination, the content of the token T2 read from the receiving-side portable recording medium 692 corresponds to the first medical data D1 (or electronic medical record data Dm) saved in step S404, the receiving-side first terminal 600 saves (imports) the second medical data D2 in association with the first medical data D1 (or electronic medical record data Dm, etc.) to the PACS 660 or the like.

[0125] <A-3. Effects of the First Embodiment> According to the first embodiment, first medical data D1 including electronic medical record data Dm and the like is transmitted from the transmitting system 20 to the receiving system 60 via the first communication network 70 (closed network) and the shared server 30 (management server) (S104, S105, S202, S203 in FIG. 6 , S312, S313 in FIG. 7 , S402, S403 in FIG. 8 ). Furthermore, second medical data D2 (e.g., medical image data Di captured for diagnosing a patient) is transmitted from the transmitting system 20 to the receiving system 60 via the second communication network 72 (Internet) and the external repository 50 (S102, S103, S205, S206 in FIG. 6 , S308, S309 in FIG. 7 , S407, S408 in FIG. 8 ). This allows medical data to be transmitted and received via a communication path appropriate for the type, size, etc. of the medical data. Furthermore, even if the communication speed of the first communication network 70 is relatively slow or the communication capacity is relatively small and therefore not suitable for communicating the second medical data D2, or if the processing performance of the shared server 30 is relatively low and therefore not suitable for communicating the second medical data D2, it is possible to handle the second medical data D2.

[0126] Furthermore, the first medical data D1 transmitted via the first communication network 70 (closed network) and the shared server 30 includes a second medical data acquisition token T2 for acquiring the second medical data D2 from an external repository 50 in the second communication network 72 (Internet). This ensures security when the first communication network 70 has a higher level of security than the second communication network 72, eliminating the need for the patient to carry the token T2. ​​In addition, the risk of the patient forgetting to carry the token T2 or losing the token T2 is eliminated, enabling the data to be delivered more reliably to the receiving system 60.

[0127] In addition, if at least referral letter data is included in the first medical data D1, the second medical data D2 will be linked to the referral letter data, which makes it easier for the receiving system 60 to manage the second medical data D2.

[0128] In the first embodiment, the receiving system 60 a receiving-side private network connection terminal 600 (receiving-side first terminal 600, first medical data receiving terminal) connected to the first communication network 70 and receiving the first medical data D1 from the data sharing server 30 (management server); a receiving internet connection terminal 630 (receiving second terminal 630, second medical data receiving terminal) connected to the second communication network 72 and receiving second medical data D2 from the external repository 50; an optical sensor 640 (receiving-side token transmitting means) that transmits to a second receiving terminal 630 a second medical data acquisition token T2 included in the first medical data D1 received by the first receiving terminal 600 from the shared server 30; Includes (Figure 1).

[0129] This makes it possible to transmit the second medical data acquisition token T2 from the first receiving terminal 600 to the second receiving terminal 630, even if the first medical data D1 and the second medical data D2 are received at different receiving terminals (the first receiving terminal 600 and the second receiving terminal 630).

[0130] In the first embodiment, the first receiving terminal 600 (first medical data receiving terminal) is disconnected from the second communication network 72, and the second receiving terminal 630 (second medical data receiving terminal) is disconnected from the first communication network 70 (FIG. 1). This makes it possible to input the second medical data acquisition token T2 to the second receiving terminal 630 via the optical sensor 640 (receiving token transmission means) even when the first receiving terminal 600 is disconnected from the second communication network 72. Therefore, the second medical data D2 can be received via the second communication network 72 while reducing the risk of external intrusion into the first receiving terminal 600 (and the first communication network 70).

[0131] In the first embodiment, the receiving system 60 includes a display device 2313 (coded image display unit) that displays, as a coded image, the second medical data acquisition token T2 included in the first medical data D1 received by the first receiving terminal 600 (first medical data receiving terminal) (FIGS. 2 and S405 in FIG. 8). The receiving system 60 includes an optical sensor 640 that reads the coded image as a receiving token transmission means (FIG. 1). The second receiving terminal 630 (second medical data receiving terminal) receives the second medical data D2 from the external repository 50 via the second communication network 72 based on the information of the second medical data acquisition token T2 indicated by the coded image read by the optical sensor 640 (S406 to S409 in FIG. 8). This allows the token T2 to be transmitted relatively easily from the first receiving terminal 600 to the second receiving terminal 630.

[0132] In the first embodiment, the transmitting system 20 (medical data transmitting system) further includes a shared data generator 2322 (token adder) that guides the user through an operation to add a second medical data acquisition token T2 to the first medical data D1 or automatically adds the token T2 to the first medical data D1 (FIG. 2). This improves the convenience of the transmitting user when transmitting the first medical data D1 (including electronic medical record data Dm, etc.) via the first communication network 70 (closed network) and when transmitting the second medical data D2 (data larger in size than the first medical data D1) via the second communication network 72 (Internet).

[0133] In the first embodiment, the transmitting system 20 includes a first transmitting terminal 230 (first medical data transmitting terminal) connected to a first communication network 70 and transmitting first medical data D1 to a shared server 30 (management server), and a second transmitting terminal 240 (second medical data transmitting terminal) connected to a second communication network 72 and transmitting second medical data D2 to an external repository 50 (FIG. 1). This allows the first medical data D1 and the second medical data D2 to be transmitted by separate transmitting terminals (the first transmitting terminal 230 and the second transmitting terminal 240).

[0134] In the first embodiment, the first transmitting terminal 230 (first medical data transmitting terminal) is separated from the second communication network 72, and the second transmitting terminal 240 (second medical data transmitting terminal) is separated from the first communication network 70 (FIG. 1). This allows the second medical data D2 to be transmitted via the second communication network 72 while reducing the risk of external intrusion into the first transmitting terminal 230 (and the first communication network 70).

[0135] In the first embodiment, the receiving system 60 (medical data receiving system) a receiving first terminal 600 (first medical data receiving unit) that receives first medical data D1 from a shared server 30 (management server) via a first communication network 70, which is a closed network; a receiving second terminal 630 (second medical data receiving unit) that receives second medical data D2 from the external repository 50 via a second communication network 72, which is the Internet; a token output unit 6023 (token transfer unit) that guides the user to transfer the second medical data acquisition token T2, which includes information for acquiring the second medical data D2 from the external repository 50 and is included in the first medical data D1 received by the first receiving terminal 600, from the first receiving terminal 600 to the second receiving terminal 630, or that automatically transfers the token T2 from the first receiving terminal 600 to the second receiving terminal 630; (Figures 1 and 4).

[0136] According to the first embodiment, information for acquiring second medical data D2 (data larger in size than the first medical data D1) from the external repository 50 is included, and a second medical data acquisition token T2 included in the first medical data D1 (such as electronic medical record data Dm) received by the receiving-side first terminal 600 is guided from the receiving-side first terminal 600 to the receiving-side second terminal 630 or automatically transferred from the receiving-side first terminal 600 to the receiving-side second terminal 630. Thereby, the first medical data D1 (including electronic medical record data Dm, etc.) is received via the first communication network 70 (closed network), and the convenience of the receiving-side user when receiving the second medical data D2 via the second communication network 72 (Internet) can be improved.

[0137] B. Second Embodiment <B-1. Configuration of the Second Embodiment> [B-1-1. Overall Configuration] FIG. 9 is a schematic configuration diagram of a medical data transmission / reception system 10A according to the second embodiment of the present invention. The medical data transmission / reception system 10A (hereinafter also referred to as the "transmission / reception system 10A") includes a plurality of transmission-side systems 20a, a data sharing server 30, an authentication server 40, an external repository 50, and a plurality of receiving-side systems 60a. Note that in FIG. 9, only one transmission-side system 20a and one receiving-side system 60a are shown. Also, here, for ease of understanding, the transmission-side system 20a and the receiving-side system 60a are separated, but it is also possible that the transmission-side system 20a has the functions of the receiving-side system 60a and the receiving-side system 60a has the functions of the transmission-side system 20a.

[0138] The second embodiment differs from the first embodiment, which has a sending system 20 and a receiving system 60, in that it has a sending system 20a and a receiving system 60a. More specifically, the functions of the sending private network connection terminal 230 (sending first terminal 230) of the sending system 20 of the first embodiment are performed by the sending private network connection terminal 230a and the sending export terminal 280 of the sending system 20a in the second embodiment. Furthermore, the functions of the receiving private network connection terminal 600 of the receiving system 60 of the first embodiment are performed by the receiving private network connection terminal 600a and the receiving import terminal 694 of the receiving system 60a in the second embodiment. Other components (e.g., the data sharing server 30, the authentication server 40, the external repository 50, the receiving second terminal 240, the receiving second terminal 630, and the first communication network 70 and the second communication network 72) are the same as those of the first embodiment.

[0139] [B-1-2. Transmitting system 20a] 9, the sending system 20a includes a PACS 200, an electronic medical record system 210, an SS-MIX standardized storage 220, a sending private network connection terminal 230a, a sending export terminal 280, a sending Internet connection terminal 240, and a router 250. Hereinafter, the sending private network connection terminal 230a will also be referred to as the sending first terminal 230a, and the sending export terminal 280 will also be referred to as the sending third terminal 280.

[0140] The PACS 200, the electronic medical record system 210, the SS-MIX standardized storage 220, the first transmitting terminal 230a, and the third transmitting terminal 280 can communicate with each other via the transmitting hospital network 260, but are separated from the second communication network 72. The first transmitting terminal 230a is connected to the first communication network 70 via a router (not shown). Therefore, the PACS 200, the electronic medical record system 210, the SS-MIX standardized storage 220, and the third transmitting terminal 280 are connected to the first communication network 70 via the first transmitting terminal 230a. The second transmitting terminal 240 and the router 250 are connected to the second communication network 72, but are separated from the first communication network 70 and the transmitting hospital network 260.

[0141] The hardware configurations of the first transmitting terminal 230a and the third transmitting terminal 280 are similar to that of the first transmitting terminal 230 (FIG. 2) of the first embodiment. The first transmitting terminal 230a of the second embodiment is responsible for generating and transmitting (uploading) the first medical data D1 among the units (functions) of the first transmitting terminal 230 of the first embodiment. In other words, the first transmitting terminal 230a has a part of the medical data processing unit 2321, a part of the shared data generating unit 2322 (excluding the token generating unit 2325), and a first medical data uploading unit 2324. The third transmitting terminal 280 is responsible for generating and transmitting the second medical data D2 among the units (functions) of the first transmitting terminal 230 of the first embodiment. In other words, the transmitting third terminal 280 includes, among the units (functions) of the transmitting first terminal 230 of the first embodiment, a part of the medical data processing unit 2321, the token generating unit 2325, and the second medical data etc. output unit 2323. Further details of the transmitting first terminal 230a and the transmitting third terminal 280 will be described later with reference to FIG.

[0142] [B-1-3. Receiving system 60a] 9, the receiving system 60a includes a receiving private network connection terminal 600a, a card reader 610, a receiving import terminal 694, a router 620, a receiving internet connection terminal 630, an optical sensor 640, a RIS terminal 650, a PACS 660, an electronic medical record system 670, and an SS-MIX standardized storage 680. Hereinafter, the receiving private network connection terminal 600a will also be referred to as the first receiving terminal 600a, the receiving internet connection terminal 630 will also be referred to as the second receiving terminal 630, and the receiving import terminal 694 will also be referred to as the third receiving terminal 694.

[0143] The receiving-side first terminal 600a, the receiving-side third terminal 694, the RIS terminal 650, the PACS 660, the electronic medical record system 670, and the SS-MIX standardized storage 680 can communicate with each other via a receiving-side hospital network 690, but are separated from the second communication network 72. The receiving-side first terminal 600 is connected to the first communication network 70 via a router (not shown). Therefore, the receiving-side third terminal 694, the RIS terminal 650, the PACS 660, the electronic medical record system 670, and the SS-MIX standardized storage 680 are connected to the first communication network 70 via the receiving-side first terminal 600a. The receiving-side second terminal 630 and the router 620 are connected to the second communication network 72, but are separated from the first communication network 70 and the receiving-side hospital network 690.

[0144] The hardware configurations of the receiving-side first terminal 600a and the receiving-side third terminal 694 are the same as those of the receiving-side first terminal 600 (FIG. 4) in the first embodiment. The receiving-side first terminal 600a in the second embodiment is responsible for receiving (downloading) and storing the first medical data D1 among the respective parts (functions) of the receiving-side first terminal 600 in the first embodiment. In other words, the receiving-side first terminal 600a has a part of the card reader control unit 6021, the first medical data download 6022, and the token output unit 6023 among the respective parts (functions) of the receiving-side first terminal 600 in the first embodiment. The receiving-side third terminal 694 in the second embodiment is responsible for receiving (downloading) and storing the second medical data D2 among the respective parts (functions) of the receiving-side first terminal 600 in the first embodiment. In other words, the receiving-side third terminal 694 includes a part of the token output unit 6023 and the second medical data input unit 6024 among the respective parts (functions) of the receiving-side first terminal 600 in the first embodiment. Further details of the receiving-side first terminal �00a and the receiving-side third terminal 694 will be described later with reference to FIG. 11.

[0145] <B-2. Operations and Processes in the Second Embodiment> [B-2-1. Overview] Next, the user operations and the processing of each part of the transmission / reception system 10A in the second embodiment will be described. The user operations and the processing of each part of the transmission / reception system 10A in the second embodiment are the same as those in the first embodiment and are shown by the flow in FIG. 6. That is, in the second embodiment, the shared data Dsh is transmitted from the transmission-side system 20a to the receiving-side system 60a. Among the shared data Dsh, the first medical data D1 (such as electronic medical record data Dm) is transmitted via the first communication network 70, which is a closed network, and the shared server 30. Also, among the shared data Dsh, the second medical data D2 (such as medical image data Di) is transmitted via the second communication network 72, which is the Internet, and the external repository 50. The second medical data acquisition token T2 for the receiving-side system 60a to download the second medical data D2 from the external repository 50 is included in the first medical data D1 and is transmitted via the first communication network 70 and the shared server 30.

[0146] [B-2-2. Flow of sending shared data] 10 is a diagram showing a flow of transmission of shared data Dsh (first medical data D1 and second medical data D2) in the second embodiment. Each step in FIG. 10 shows details of steps S101 to S105 in FIG.

[0147] 10, the private network connection terminal 230a (first transmitting terminal 230a) of the transmitting system 20a receives a request to generate shared data Dsh (first medical data D1) based on an operation by a user (a person in charge (doctor, system person, assistant, office worker, etc.) of the transmitting medical institution). Step S501 can be performed in the same manner as step S301 of FIG. 7, using, for example, the shared data input screen described above.

[0148] In step S502, the transmitting-side first terminal 230a generates shared data Dsh (electronic medical record data Dm, etc.) based on the user's input on the shared data input screen. On the shared data input screen, first medical data D1 (electronic medical record data Dm, etc.) is displayed and input or selection is performed. When the decision button, which is a button for deciding the input content on the shared data input screen, is pressed, the transmitting-side first terminal 230a proceeds to step S514. In other words, the transmitting-side first terminal 230a is in a waiting state until the token T2 is input in step S513. Also, the user moves from the transmitting-side first terminal 230a to the transmitting-side third terminal 280.

[0149] In step S503, the export terminal 280 (transmitting-side third terminal 280) of the transmitting-side system 20a accepts a request to generate shared data Dsh (second medical data D2) based on a user operation. For example, the transmitting-side third terminal 280 starts up second medical data upload software in the transmitting-side third terminal 280 based on a user operation. When a "Create Second Medical Data" button (not shown) on the screen displayed after startup is selected, the transmitting-side third terminal 280 displays a second medical data input screen (not shown).

[0150] In step S504, the transmitting third terminal 280 generates second medical data D2 (medical image data Di, etc.) based on the user's input on the second medical data input screen. On the second medical data input screen, the second medical data D2 (medical image data Di, etc.) is displayed and input or selected.

[0151] The second medical data input screen includes, for example, a patient name input field, an examination input field, a medical data input field, a transmission destination input field, and a decision button (none of which are shown). The patient name input field is an input field for the name of the patient to whom shared data is to be sent to the destination medical institution. The examination input field is an input field for the examination details that specify the medical data to be sent. The medical data input field is a field for inputting one or more pieces of medical data to be sent (here, particularly the second medical data D2) included in the shared data Dsh. The contents of the medical data included in the first medical data D1 are not entered in the medical data input field. The transmission destination input field is a field for inputting the transmission destination of the second medical data D2 selected from the multiple receiving systems 60a.

[0152] When inputting data into the patient name input field, the test input field, and the medical data input field, the transmitting-side third terminal 280 may assist the user's input by appropriately acquiring data from the PACS 200, the electronic medical record system 210, or the SS-MIX standardized storage 220 and using an easy-to-use user interface. Examples of such a user interface include keyword search and thumbnail display of image data. Similarly, when inputting data into the destination input field, the transmitting-side third terminal 280 may assist the user's input by, for example, acquiring data of the destination medical institution (receiving-side system 60a) from the shared server 30 and using an easy-to-use user interface.

[0153] The decision button is a button for deciding the input contents on the second medical data input screen. When the decision button is pressed, the transmitting third terminal 280 proceeds to step S505. Note that part of step S504 (e.g., selection of the transmission destination, selection of medical data (file) to be transmitted) can be performed in the same way as in Patent Document 1.

[0154] Steps S505, S506, S507, S508, S509, S510, S511, and S512 are similar to steps S303, S304, S305, S306, S307, S308, S309, and S310 in FIG.

[0155] In step S513, the transmitting-side third terminal 280 converts the token T2 as text data into a two-dimensional code and transmits it to the transmitting-side first terminal 230a via the transmitting-side hospital network 260. The transmission may be, for example, in a hospital system (intra-system) using the transmitting-side hospital network 260, by attaching an image file of the token T2 to an e-mail.

[0156] In step S514, the first transmitting terminal 230a uploads the first medical data D1 including the two-dimensionally coded token T2 to the shared server 30. In step S515, the shared server 30 temporarily stores the first medical data D1 received from the first transmitting terminal 230.

[0157] Steps S513 and S514 are performed based on a user operation. Alternatively, they may be performed automatically by the transmitting third terminal 280 and the transmitting first terminal 230a. When steps S513 and S514 are performed based on a user operation, the transmitting third terminal 280 and the transmitting first terminal 230a each provide operation guidance to the user.

[0158] [B-2-3. Flow when receiving shared data] 11 is a diagram showing a flow of receiving shared data Dsh (first medical data D1 and second medical data D2) in the second embodiment. Each step in FIG. 11 shows details of steps S201 to S207 in FIG.

[0159] Steps S601, S602, S603, and S604 in Fig. 11 are the same as steps S401, S402, S403, and S404 in Fig. 8. When the download and storage of the first medical data D1 (S604) is complete, the receiving first terminal 600a displays a message indicating that the download is complete and an OK button (not shown). When the user presses the OK button, the process proceeds to step S605.

[0160] In step S605, the first receiving terminal 600a transfers the token T2 (two-dimensionally coded) included in the downloaded first medical data D1 to the third receiving terminal 694. This transfer may be performed, for example, in an in-hospital system (intra-system) using the receiving-hospital network 690, by sending an image of the token T2 from the first receiving terminal 600a to the third receiving terminal 694 as an attachment to an email. Alternatively, the first receiving terminal 600a may automatically detect the token T2 and automatically transfer it to the third receiving terminal 694. After step S605, the user moves from the first receiving terminal 600a to the third receiving terminal 694.

[0161] In step S606, the receiving third terminal 694 displays the token T2 received from the receiving first terminal 600a. This display can be achieved, for example, by the user double-clicking on an image of the token T2 attached to an e-mail. Alternatively, the receiving third terminal 694 may detect that the token T2 has been automatically transmitted from the receiving first terminal 600a and automatically display the token T2. ​​In either case, the user can first perform work and processing with the import terminal-side import processing software running on the receiving third terminal 694. Furthermore, after the import processing software is started and the user selects an import button (not shown), the software can provide user operation guidance (such as the double-click described above) or automatically display the token T2.

[0162] Also, in accordance with the display of token T2, the receiving-side third terminal 694 causes the display device to display, in addition, a message (reading request message) stating that "in the receiving-side second terminal 630, software for downloading medical image data (second medical data D2) is launched, the receiving-side portable recording medium 692 is inserted into the drive for the recording medium, after pressing the 'Medical Image Data Download Button', the two-dimensionalized token T2 is read by the optical sensor 640, and the second medical data D2 should be downloaded and copied to the receiving-side portable recording medium 692". Further, the reading request message may include a description stating that when the copying of the second medical data D2 to the receiving-side portable recording medium 692 is completed, the receiving-side portable recording medium 692 should be inserted into the drive for the recording medium of the receiving-side third terminal 694.

[0163] Steps S607, S608, S609, S610, S611, S612, S613 in FIG. 11 are the same as steps S406, S407, S408, S409, S410, S411, S412 in FIG. 8. However, the destination of the second medical data D2 is the receiving-side third terminal 694 instead of the receiving-side first terminal 600a.

[0164] <B-3. Effects of the Second Embodiment> According to the second embodiment as described above, in addition to or instead of the effects of the first embodiment, the following effects can be achieved.

[0165] In the second embodiment, the receiving-side system 60a further includes a receiving-side third terminal 694 (second medical data import terminal) that acquires the second medical data acquisition token T2 from the receiving-side first terminal 600a and supplies it to the receiving-side second terminal 630 (second medical data receiving terminal), and acquires the second medical data D2 from the receiving-side second terminal 630 and imports it into the PACS 660 (receiving-side database) connected to the receiving-side in-hospital network 690 (FIG. 9).

[0166] As a result, the exchange of the second medical data D2 with the second receiving terminal 630 and the import of the second medical data D2 are performed by the third receiving terminal 694, not the first receiving terminal 600a. Therefore, the work for receiving and importing the first medical data D1 can be separated from the work for receiving and importing the second medical data D2. This allows different users to perform the work on the first receiving terminal 600a and the third receiving terminal 694. Alternatively, it is easy to automate either the first receiving terminal 600a or the third receiving terminal 694.

[0167] In the second embodiment, the transmitting system 20a further includes a third transmitting terminal 280 (second medical data export terminal) that exports the second medical data D2 to the second transmitting terminal 240 (second medical data transmitting terminal) (FIG. 9). The third transmitting terminal 280 supplies the second medical data acquisition token T2 to the first transmitting terminal 230a (S513 in FIG. 10), and supplies the second medical data D2 and the token T2 to the second transmitting terminal 240 (S506 to S509 in FIG. 10).

[0168] As a result, the exchange (export) of the second medical data D2 and the second medical data acquisition token T2 with the second transmitting terminal 240 is performed by the third transmitting terminal 280, not the first transmitting terminal 230a. Therefore, the task of transmitting the first medical data D1 can be separated from the task of transmitting the second medical data D2. This allows different users to perform tasks on the first transmitting terminal 230a and the third transmitting terminal 280. Alternatively, automation of either the first transmitting terminal 230a or the third transmitting terminal 280 is facilitated. Furthermore, by having the third transmitting terminal 280 generate the second medical data acquisition token T2, the first transmitting terminal 230a can be specialized in processing the first medical data D1, except for adding the token T2 to the first medical data D1. Therefore, for example, if the first transmitting terminal 230a already has a process for exchanging data with the data sharing server 30, the existing process can be used as is.

[0169] C. Variations Note that the present invention is not limited to the above-described embodiments, and various configurations can be adopted based on the description in this specification. For example, the following configurations can be employed.

[0170] <C-1. Configuration> In the transmission / reception system 10 of the first embodiment, the first medical data D1 includes at least one of electronic medical record data Dm, referral data, and health examination result data, and the second medical data D2 includes data (e.g., medical image data Di taken for diagnosing a patient) that is larger in size than the first medical data D1. However, for example, focusing on the point of transmitting the first medical data D1 via the first communication network 70 and the shared server 30 and transmitting the second medical data D2 via the second communication network 72 and the external repository 50, or including the token T2 in the first medical data D1 and transmitting and receiving it via the first communication network 70 and the shared server 30, it is not limited to this. For example, the first medical data D1 may not include electronic medical record data Dm, referral data, and health examination result data. Also, the second medical data D2 may be data that is smaller in size than the first medical data D1. The same applies to the transmission / reception system 10A of the second embodiment.

[0171] The transmission-side system 20 of the first embodiment had two transmission terminals (the transmission-side first terminal 230 and the transmission-side second terminal 240) (FIG. 1). However, for example, focusing on the point of transmitting the first medical data D1 via the first communication network 70 and the shared server 30 and transmitting the second medical data D2 via the second communication network 72 and the external repository 50, it is not limited to this. For example, it is also possible for one transmission terminal to play the roles of the transmission-side first terminal 230 (the first medical data transmission unit) and the transmission-side second terminal 240 (the second medical data transmission unit).

[0172] The transmitting system 20 of the first embodiment had a PACS 200, an electronic medical record system 210, and an SS-MIX standardized storage 220 as transmitting databases for medical data (FIG. 1). However, the configuration of the transmitting database is not limited to this, for example, if attention is paid to the fact that the first medical data D1 is transmitted via the first communication network 70 and the shared server 30, and the second medical data D2 is transmitted via the second communication network 72 and the external repository 50. The same is true for the transmitting system 20a of the second embodiment.

[0173] The receiving system 60 of the first embodiment had a RIS terminal 650, a PACS 660, an electronic medical record system 670, and an SS-MIX standardized storage 680 as a receiving database for medical data (FIG. 1). However, the configuration of the receiving database is not limited to this, for example, if attention is paid to the fact that the first medical data D1 is transmitted via the first communication network 70 and the shared server 30, and the second medical data D2 is transmitted via the second communication network 72 and the external repository 50. The same is true for the receiving system 60a of the second embodiment.

[0174] In the transmitting system 20 of the first embodiment, the first transmitting terminal 230 is connected to the transmitting hospital network 260, and the second transmitting terminal 240 is disconnected from the transmitting hospital network 260 (FIG. 1). However, for example, if attention is paid to the fact that the first medical data D1 is transmitted via the first communication network 70 and the shared server 30, and the second medical data D2 is transmitted via the second communication network 72 and the external repository 50, the present invention is not limited to this, and the second transmitting terminal 240 may also be connected to the transmitting hospital network 260. In this case, the second medical data D2 and the token T2 may be transferred from the first transmitting terminal 230 to the second transmitting terminal 240 via the transmitting hospital network 260 instead of the transmitting portable recording medium 270. The same applies to the transmitting system 20a of the second embodiment.

[0175] In the receiving system 60 of the first embodiment, the first receiving terminal 600 is connected to the receiving hospital network 690, and the second receiving terminal 630 is disconnected from the receiving hospital network 690 (FIG. 1). However, for example, if attention is paid to the fact that the first medical data D1 is transmitted via the first communication network 70 and the shared server 30, and the second medical data D2 is transmitted via the second communication network 72 and the external repository 50, the present invention is not limited to this, and the second receiving terminal 630 may also be connected to the receiving hospital network 690. In this case, the transfer of the token T2 from the first receiving terminal 600 to the second receiving terminal 630 and the transfer of the second medical data D2 from the second receiving terminal 630 to the first receiving terminal 600 may be performed via the receiving hospital network 690, instead of the optical sensor 640 and the receiving portable recording medium 692. The same applies to the receiving system 60a of the second embodiment.

[0176] In the transmitting system 20a of the second embodiment, the third transmitting terminal 280 is connected to the first transmitting terminal 230a via the transmitting hospital network 260 (FIG. 9). However, this is not limiting, for example, if attention is paid to the fact that data is exchanged between the first transmitting terminal 230a and the third transmitting terminal 280. For example, the first transmitting terminal 230a and the third transmitting terminal 280 may not be connected via the transmitting hospital network 260, and may exchange data using, for example, a USB memory.

[0177] In the receiving system 60a of the second embodiment, the third receiving terminal 694 is connected to the first receiving terminal 600a via the receiving hospital network 690 (FIG. 9). However, this is not limiting, for example, if attention is focused on the fact that data is exchanged between the first receiving terminal 600a and the third receiving terminal 694. For example, the first receiving terminal 600a and the third receiving terminal 694 may not be connected via the receiving hospital network 690, and may exchange data using, for example, a USB memory.

[0178] In the transmission and reception system 10 of the first embodiment, the first communication network 70 is a closed network, and the second communication network 72 is the Internet or a closed network with a higher communication speed or larger communication capacity than the first communication network 70. However, for example, it is not limited to this, focusing on the point of transmitting the first medical data D1 via the first communication network 70 and the shared server 30 and transmitting the second medical data D2 via the second communication network 72 and the external repository 50, or the point of including the token T2 in the first medical data D1 and transmitting and receiving it via the first communication network 70 and the shared server 30. For example, the first communication network 70 may not be a closed network. Also, the second communication network 72 may have a lower communication speed or smaller communication capacity than the first communication network 70. The same applies to the transmission and reception system 10A of the second embodiment.

[0179] <C-2. Control> In the first embodiment, the shared data Dsh (the first medical data D1 and the second medical data D2) was transmitted in the order shown in FIGS. 6 to 8. However, for example, it is not limited to this, focusing on the point of transmitting the first medical data D1 via the first communication network 70 and the shared server 30 and transmitting the second medical data D2 via the second communication network 72 and the external repository 50. For example, steps S104 and S105 in FIG. 6 may be performed before steps S102 and S103. The same applies to the second embodiment (FIGS. 10 and 11).

[0180] In the first embodiment, the token T2 included in the first medical data D1 was two-dimensionally coded (S311 in FIG. 7). However, for example, it is not limited to this, focusing on the point of conveying the token T2 to the receiving-side system 60. For example, the token T2 included in the first medical data D1 may be text data. In that case, the token T2 may be transmitted as text data from the receiving-side first terminal 600 to the receiving-side second terminal 630. Alternatively, the token T2 received by the receiving-side first terminal 600 in text data form may be two-dimensionally coded by the receiving-side first terminal 600 and transmitted to the receiving-side second terminal 630.

[0181] In the first embodiment, the download of the first medical data D1 in the receiving system 60 is triggered by reading the patient card (S201 in FIG. 6, S401 in FIG. 8). However, for example, if attention is focused on the point of transmitting the token T2 to the receiving system 60, the download of the first medical data D1 in the receiving system 60 is not limited to this, and may be performed at other timings.

[0182] For example, the data sharing server 30 temporarily stores the first medical data D1 from the transmitting system 20 and notifies the receiving system 60 of the temporary storage. Upon receiving the notification, the receiving system 60 (first receiving terminal 600) requests the shared server 30 to download the first medical data D1, either automatically or in response to a user operation, and downloads the first medical data D1. Next, the receiving system 60 (second receiving terminal 630) requests the external repository 50 to download the second medical data D2, either automatically or in response to a user operation, and downloads and stores the second medical data D2. This makes it possible to make the shared data Dsh (first medical data D1 and second medical data D2) available before the patient arrives at the medical institution where the receiving system 60 is located. The same applies to the second embodiment. [Explanation of symbols]

[0183] 10, 10A...Medical data transmission and reception system 20, 20a...Transmitting system (medical data transmitting system) 30...Data sharing server (management server) 50…External repository 60, 60a... Receiving system (medical data receiving system) 70...first communication network 72...second communication network 230, 230a...Transmitter private network connection terminal (transmitter first terminal, first medical data transmission terminal, first medical data transmission unit) 240...Transmitter's Internet connection terminal (transmitter's second terminal, second medical data transmission terminal, second medical data transmission unit) 260...Sender's hospital network (sender's local network) 270...Transmitting side recording medium (transmitting side token transmission means) 280...Transmitting side export terminal (transmitting side third terminal, second medical data export terminal) 600, 600a... Receiving-side private network connection terminal (receiving-side first terminal, first medical data receiving terminal, first medical data receiving unit) 630... Receiving-side Internet connection terminal (receiving-side second terminal, second medical data receiving terminal, second medical data receiving unit) 640...Optical sensor (receiving side token transmission means) 660...PACS (receiving database) 690...Receiving hospital network (receiving local network) 694... Receiving side import terminal (receiving side third terminal, second medical data import terminal) 2313...Display device (encoded image display unit) 2322...Shared data generation unit (token addition unit) 2325...Token generation unit 6023...Token output unit (token transition unit) D1: First medical data D2: Second medical data Dm: Electronic medical record data T2: Second medical data acquisition token

Claims

1. a transmitting system in a medical institution that transmits the first medical data and the second medical data; a receiving system at a medical institution that receives the first medical data and the second medical data; A medical data transmission and reception system having: Furthermore, the medical data transmission and reception system includes: a management server that stores the first medical data received from the transmitting system via a first communication network and transmits the first medical data to the receiving system via the first communication network; an external repository that temporarily stores the second medical data received from the sending system via a second communication network and transfers the second medical data to the receiving system via the second communication network; and Furthermore, the first medical data includes a second medical data acquisition token for acquiring the second medical data from the external repository. A medical data transmission and reception system.

2. 2. The medical data transmission and reception system according to claim 1, the first medical data includes at least one of electronic medical record data, referral letter data, and medical examination result data; The second medical data includes data having a size larger than that of the first medical data. A medical data transmission and reception system.

3. 3. The medical data transmission and reception system according to claim 1, The receiving system a first medical data receiving terminal connected to the first communication network to receive the first medical data from the management server; a second medical data receiving terminal connected to the second communication network to receive the second medical data from the external repository; a receiving-side token transmitting means for transmitting the second medical data acquisition token included in the first medical data received by the first medical data receiving terminal from the management server to the second medical data receiving terminal; Contains A medical data transmission and reception system.

4. 4. The medical data transmission and reception system according to claim 3, the first medical data receiving terminal is separated from the second communication network; The second medical data receiving terminal is separated from the first communication network. A medical data transmission and reception system.

5. 4. The medical data transmission and reception system according to claim 3, the receiving system further includes a coded image display unit that displays the second medical data acquisition token included in the first medical data received by the first medical data receiving terminal as a coded image; the receiving token transmitting means includes an optical sensor for reading the coded image; The second medical data receiving terminal receives the second medical data from the external repository via the second communication network based on information of the second medical data acquisition token indicated by the coded image read by the optical sensor. A medical data transmission and reception system.

6. 4. The medical data transmission and reception system according to claim 3, The receiving system further includes a token transfer unit that guides an operation to transfer the second medical data acquisition token included in the first medical data received by the first medical data receiving terminal from the first medical data receiving terminal to the second medical data receiving terminal or that automatically transfers the second medical data acquisition token from the first medical data receiving terminal to the second medical data receiving terminal. A medical data transmission and reception system.

7. 4. The medical data transmission and reception system according to claim 3, The receiving system further includes a second medical data import terminal that acquires the second medical data acquisition token from the first medical data receiving terminal and supplies the second medical data acquisition token to the second medical data receiving terminal, and acquires the second medical data from the second medical data receiving terminal and imports the second medical data into the receiving database. A medical data transmission and reception system.

8. 3. The medical data transmission and reception system according to claim 1, The sending system includes: a first medical data transmission terminal connected to the first communication network and transmitting the first medical data to the management server; a second medical data transmission terminal connected to the second communication network and transmitting the second medical data to the external repository; Contains A medical data transmission and reception system.

9. 9. The medical data transmission and reception system according to claim 8, the first medical data transmission terminal is separated from the second communication network; The second medical data transmission terminal is separated from the first communication network. A medical data transmission and reception system.

10. 3. The medical data transmission and reception system according to claim 1, The transmitting system further includes a token adding unit that guides an operation for adding the second medical data acquisition token to the first medical data or automatically adds the second medical data acquisition token to the first medical data. A medical data transmission and reception system.

11. 9. The medical data transmission and reception system according to claim 8, the transmitting side system further includes a second medical data export terminal that exports the second medical data to the second medical data transmitting terminal; The second medical data export terminal generating the second medical data acquisition token; supplying the second medical data acquisition token to the first medical data transmission terminal; The second medical data and the second medical data acquisition token are supplied to the second medical data transmission terminal. A medical data transmission and reception system.

12. A medical data transmitting system at a transmitting medical institution that transmits first medical data and second medical data to a medical data receiving system at a receiving medical institution, The medical data transmitting system includes: a first medical data transmission unit that transmits the first medical data to a management server via a first communication network; a second medical data transmission unit that transmits the second medical data to an external repository via a second communication network; a token generating unit that generates a second medical data acquisition token for acquiring the second medical data from the external repository; a token adding unit that guides an operation of adding the second medical data acquisition token to the first medical data or automatically adds the second medical data acquisition token to the first medical data; Equipped with A medical data transmitting system characterized by:

13. A medical data receiving system at a receiving medical institution that receives first medical data and second medical data from a medical data transmitting system at a transmitting medical institution, The medical data receiving system includes: a first medical data receiving unit that receives the first medical data from a management server via a first communication network; a second medical data receiving unit that receives the second medical data from an external repository via a second communication network; a token transfer unit that guides an operation to transfer a second medical data acquisition token, which includes information for acquiring the second medical data from the external repository and is included in the first medical data received by the first medical data receiving unit, to the second medical data receiving unit or that automatically transfers the second medical data acquisition token to the second medical data receiving unit; Equipped with A medical data receiving system characterized by:

14. A medical data transmission and reception method for transmitting first medical data and second medical data from a transmission-side system in a transmission-side medical institution to a reception-side system in a reception-side medical institution, comprising: Furthermore, the medical data transmission and reception method includes: a first medical data upload step of transmitting the first medical data from the transmitting system to a management server via a first communication network, and causing the management server to temporarily store the first medical data; a first medical data download step of transmitting the first medical data from the management server to the receiving system via the first communication network; a second medical data upload step of transmitting the second medical data from the transmitting system to an external repository via a second communication network, and temporarily storing the second medical data in the external repository; a second medical data download step of transmitting the second medical data from the external repository to the receiving system via the second communication network; and Furthermore, the medical data transmission and reception method includes: a token generation step in which the transmitting system generates a second medical data acquisition token for acquiring the second medical data from the external repository; a token addition step of adding the second medical data acquisition token to the first medical data to be transmitted to the management server by an operation of a transmitting side user or automatically by the transmitting side system; have A medical data transmission and reception method comprising:

Images