Electronic medical record management system, electronic medical record management method, and transfer device

Abstract

To improve the usability of electronic medical record terminals. [Solution] An electronic medical record management system is provided, comprising a medical record creation support device, a transfer server, a transfer device, and an electronic medical record terminal, wherein the medical record creation support device acquires medical record information, transmits the acquired medical record information to the transfer server via a network, the transfer server transmits the medical record information from the medical record creation support device to the transfer device via a network, and the transfer device transfers the medical record information from the transfer server to the electronic medical record terminal without going through a network.

Description

Technical Field

[0001] The present invention relates to an electronic medical record management system, an electronic medical record management method, and a transfer device.

Background Art

[0002] Web services for assisting in the creation of electronic medical records are known (for example, Non-Patent Document 1). On the other hand, electronic medical record terminals in medical institutions are often not connected to the network for security reasons.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] To improve the usability of the electronic medical record terminal or to provide a new invention different from Non-Patent Document 1.

Means for Solving the Problems

[0005] The following configuration is provided as an example.

[0006] [1] An electronic medical record management system comprising a medical record creation assistance device, a transfer server, a transfer device, and an electronic medical record terminal, wherein the medical record creation assistance device acquires medical record information and transmits the acquired medical record information to the transfer server via a network, the transfer server transmits the medical record information from the medical record creation assistance device to the transfer device via a network, and the transfer device transfers the medical record information from the transfer server to the electronic medical record terminal without passing through a network.

[0007] [2] The electronic medical record management system according to [1], wherein the transfer device transfers medical record information from the transfer server to the electronic medical record terminal via a USB connection.

[0008] [3] The electronic medical record management system according to [1] or [2], wherein after the transfer device transfers the medical record information from the transfer server to the electronic medical record terminal, the medical record information is not stored in the transfer device.

[0009] [4] If a transfer device ID is set for the transfer device, A correspondence database showing the correspondence between the user ID for using the aforementioned medical record creation support device and the transfer device ID is stored in the storage unit. The medical record creation support device transmits the medical record information to the transfer server, linked to the user ID. The electronic medical record management system according to any one of [1] to [3], wherein the transfer server refers to the correspondence database and transmits the medical record information to the transfer device, which has a transfer device ID set that is associated with a user ID linked to the medical record information from the medical record creation support device.

[0010] [5] The medical record creation support device sends a transfer request to the transfer server in response to a predetermined operation from the user. The electronic medical record management system according to any one of [1] to [4], wherein the transfer server transmits medical record information from the medical record creation support device to the transfer device in response to the receipt of the transfer request.

[0011] [6] The aforementioned transfer server, When the transfer request is received while the transfer device is connected to the transfer server via the network, the medical record information is transmitted to the transfer device. The electronic medical record management system according to [5], which, when it receives the transfer request while the transfer device is not connected to the transfer server via the network, transmits error information to the medical record creation support device.

[0012] [7] The electronic medical record management system according to any one of [1] to [6], wherein the electronic medical record terminal writes the received medical record information to the clipboard of the electronic medical record terminal.

[0013] [8] An electronic medical record management system according to any one of [1] to [7], wherein, even when the transfer device is connected to the electronic medical record terminal, data cannot be written to the transfer device by operations on the electronic medical record terminal, and data written to the transfer device cannot be read by operations on the electronic medical record terminal.

[0014] [9] The electronic medical record terminal is not connected to a network, and is an electronic medical record management system as described in any one of [1] to [8].

[0015]

[10] The electronic medical record management system according to any one of [1] to [9], wherein the communication between the transfer server and the transfer device is encrypted communication established after authentication.

[0016]

[11] The aforementioned medical record information includes non-text data, The medical record creation support device converts non-text data in the medical record information into text data and transmits it to the transfer server. The electronic medical record terminal converts the text data into the non-text data, according to any one of [1] to

[10] .

[0017]

[12] The transfer device acquires patient information from the electronic medical record terminal without going through the network and transmits it to the transfer server via the network. The transfer server transmits the patient information received from the transfer device to the medical record creation assistance device via a network. The electronic medical record management system according to any one of [1] to

[11] .

[0018]

[13] The medical record creation assistance device, the transfer server, the transfer device, and the electronic medical record terminal are provided. The transfer device acquires patient information from the electronic medical record terminal without going through a network and transmits it to the transfer server via a network. The transfer server transmits the patient information received from the transfer device to the medical record creation assistance device via a network. The electronic medical record management system.

[0019]

[14] The transfer device, in response to a first operation on the electronic medical record terminal, acquires patient information from the electronic medical record terminal without going through a network, and transmits it to the transfer server via a network. The electronic medical record management system according to

[12] or

[13] .

[0020]

[15] The transfer server, in response to a second operation on the medical record creation assistance device, transmits the patient information from the transfer device to the medical record creation assistance device via a network. The electronic medical record management system according to any one of

[12] to

[14] .

[0021]

[16] The transfer server, writes the patient information received from the transfer device into the storage unit, when further patient information is received from the transfer device, overwrites the stored patient information with the further received patient information. The electronic medical record management system according to any one of

[12] to

[15] .

[0022]

[17] The transfer server, The patient information received from the transfer device is written to the storage unit. The electronic medical record management system described in any of

[12] to

[15] , wherein patient information is not deleted from the storage unit as a result of being transmitted to the medical record creation support device via the network.

[0023]

[18] The aforementioned transfer server, The patient information received from the transfer device is written to the storage unit. This patient information will not be deleted from the storage unit upon transmission to the medical record creation support device via the network. An electronic medical record management system according to any one of

[12] to

[15] , wherein when further patient information is received from the transfer device, the received patient information is overwritten and stored over the stored patient information.

[0024]

[19] The transfer server comprises a storage unit having multiple memory areas, each associated with one or more electronic medical record terminals and one or more user IDs for using the medical record creation support device. Each memory area stores patient information from the associated electronic medical record terminal. The electronic medical record management system according to any one of

[12] to

[18] , wherein the transfer server receives an acquisition request including a user ID from the medical record creation support device and transmits patient information written to the memory area associated with the user ID to the medical record creation support device.

[0025]

[20] A transfer device comprising a medical record information transfer unit that receives medical record information from a medical record creation support device via a network from a transfer server and transfers it to an electronic medical record terminal without going through the network, A transfer device that, even when connected to the electronic medical record terminal, cannot write data to the transfer device through operations on the electronic medical record terminal, nor can read data written to the transfer device through operations on the electronic medical record terminal.

[0026] [twenty one] The medical record creation support device acquires medical record information and transmits the acquired medical record information to a transfer server via the network. The transfer server transmits the medical record information from the medical record creation support device to the transfer device via the network. An electronic medical record management method wherein the transfer device transfers medical record information from the transfer server to an electronic medical record terminal without going through a network.

[0027] [twenty one] The transfer device acquires patient information from the electronic medical record terminal without going through the network and transmits it to the transfer server via the network. An electronic medical record management method comprising the transfer server transmitting patient information received from the transfer device to a medical record creation support device via a network.

[0028] [twenty two] A method for creating a dictionary that shows the relationship between a word requiring correction and the corrected word, The first step involves an AI-powered text-to-speech device reading out the target word, The process includes a second step in which an artificial intelligence-based transcription device transcribes spoken words into text, A method in which the transcribed word is registered in the dictionary as the word requiring correction, and the target word is registered in the dictionary as the corrected word.

[0029] [twenty three] The method according to

[22] , wherein the first step is a reading device using artificial intelligence to read out the target word.

[0030] [twenty four] The method according to

[22] or

[23] , wherein the second step involves a transcription device using artificial intelligence transcribing the spoken words.

[0031] [twenty five] The process includes a third step of determining whether the transcribed word matches the target word, The method described in any of

[22] to

[24] , wherein the transcribed words that do not match are registered in the dictionary as the corrected words.

[0032]

[26] A method for transcribing conversations between doctors and patients, using a dictionary that shows the relationship between words requiring correction and the corrected words, The first step is to convert the conversation between doctor and patient into text, A method comprising: a second step of correcting any word composed of the converted characters to a corrected word if that word matches a word registered in the dictionary that requires correction.

[0033]

[27] A learning method in artificial intelligence used to transcribe conversations between doctors and patients, This learning method uses human-transcribed recordings of conversations between doctors and patients as the ground truth data for training.

[0034]

[28] A learning method in artificial intelligence used to summarize conversations between doctors and patients, A learning method that involves learning for specific doctors or specific patients. [Brief explanation of the drawing]

[0035] [Figure 1] A block diagram showing the schematic configuration of the electronic medical record management system according to the first embodiment. [Figure 2] A schematic diagram illustrating the structure of the correspondence database. [Figure 3A] A schematic diagram showing the medical record information stored in the memory unit 21. [Figure 3B] A schematic diagram showing the medical record information stored in the memory unit 21. [Figure 4] A sequence diagram illustrating an example of the processing operation of an electronic medical record management system. [Figure 5A]A schematic diagram showing an example of a screen displayed on the display by the medical record creation support device 1. [Figure 5B] A schematic diagram showing an example of a screen displayed on the display by the medical record creation support device 1. [Figure 5C] A schematic diagram showing an example of a screen displayed on the display by the medical record creation support device 1. [Figure 6] A block diagram showing the general configuration of the medical record information acquisition unit 11. [Figure 7] A diagram explaining a dictionary. [Figure 8A] A block diagram illustrating the general characteristics of the dictionary creation system. [Figure 8B] A flowchart illustrating an example of the dictionary creation process. [Figure 9] A block diagram showing the schematic configuration of the electronic medical record management system according to the second embodiment. [Figure 10] A diagram illustrating the memory area in the storage unit 21. [Figure 11] A sequence diagram illustrating an example of the processing operation of an electronic medical record management system. [Modes for carrying out the invention]

[0036] Hereinafter, embodiments of the present invention will be specifically described with reference to the drawings.

[0037] (First Embodiment) Figure 1 is a block diagram illustrating the schematic configuration of an electronic medical record management system according to the first embodiment. The electronic medical record management system comprises one or more medical record creation support devices 1, a transfer server 2, one or more transfer devices 3, and one or more electronic medical record terminals 4.

[0038] The medical record creation support device 1 is connected to the transfer server 2 via a network (e.g., the internet; the same applies hereinafter). The transfer device 3 may also be connected to the transfer server 2 via a network. On the other hand, it is preferable that the electronic medical record terminal 4 is not connected to a network; for example, it may be connected to the transfer device 3 via USB without using a network.

[0039] [Medical record creation support device 1] To use the medical record creation support device 1, user registration is required in advance, and each user (doctor) is assigned a unique user ID. The user ID can be, for example, any letters, numbers, or a combination thereof.

[0040] The medical record creation support device 1 is used by a physician when examining a patient and assists in the creation of a medical record. More specifically, the medical record creation support device 1 acquires information used in the medical record (hereinafter referred to as "medical record information") (in this specification, "acquisition" includes both generating the information itself and obtaining it from an external source), links it with a user ID, and transmits it to the transfer server 2 via the network. In this embodiment, the medical record creation support device 1 also controls the transfer of medical record information to the electronic medical record terminal 4.

[0041] As a specific example of configuration, the medical record creation support device 1 includes a medical record information acquisition unit 11, a medical record information transmission unit 12, and a transfer request unit 13. Some or all of these may be realized by a processor executing a predetermined program, or they may be implemented in hardware. The medical record creation support device 1 may consist of one or more devices.

[0042] The medical record information acquisition unit 11 records conversations between doctors and patients, transcribes the conversation content, and summarizes it to create medical record information. The medical record information transmission unit 12 links the created medical record information to a user ID and sends it to the transfer server 2 via the network at any time. The transfer request unit 13 sends a transfer request to the transfer server 2 in response to a transfer instruction from the user, instructing it to transfer the medical record information to the electronic medical record terminal 4 via the transfer device 3. This transfer request includes the user ID.

[0043] The medical record creation support device 1 may be a standalone device that does not require a network connection. In this case, the medical record information acquisition unit 11, the medical record information transmission unit 12, and the transfer request unit 13 are provided in the standalone device.

[0044] Alternatively, the medical record creation support device 1 may utilize a web service. In this case, the medical record creation support device 1 may consist of a user terminal (such as a PC or smartphone) and a medical record information generation server. The medical record information acquisition unit 11, the medical record information transmission unit 12, and the transfer request unit 13 may be provided on the user terminal, on the medical record information generation server, or both may cooperate to function as these units.

[0045] As a specific example of processing, the user terminal records a conversation between a doctor and a patient and sends the recorded data to the medical record information generation server. The medical record information generation server applies pre-trained artificial intelligence to the conversation contained in the recorded data and performs processing such as transcription and summarization to generate medical record information. The medical record information generation server then sends the generated medical record information to the user terminal. The transmission of medical record information to the transfer server 2 may be performed by the medical record information generation server or by the user terminal.

[0046] In a medical record information generation server, it is desirable for the AI ​​that performs transcription to undergo further learning and updates at appropriate intervals. For example, it is conceivable to periodically have a human transcribe the recorded data and use this as correct data for learning (fine-tuning). This will improve the accuracy of the transcription of doctor-patient conversations. In particular, for specific patients who visit frequently, the accuracy will improve even further because their conversations will be included in a large amount of the recorded data used for learning.

[0047] It is desirable that the artificial intelligence used to generate summaries on the medical record information generation server undergoes further learning and updates at appropriate intervals. For example, it is conceivable to periodically have a human (e.g., a doctor) create summaries from the transcribed information and use these as ground truth data for learning (fine-tuning). This would improve the accuracy of summary creation.

[0048] The above learning may be performed for multiple doctors or patients together, or for each doctor or patient individually.

[0049] Furthermore, so-called generative AI (especially large-scale language models (LLMs)) may be used to create summaries using artificial intelligence. By learning (fine-tuning) and refining the generative AI account based on previously created summaries and concepts likely to appear in summaries (e.g., information on diagnosis, treatment, and medication), summaries can be created with high accuracy.

[0050] Note that transcription may be performed based on a pre-created dictionary. An example of a dictionary creation method will be described later.

[0051] [Transfer Server 2] Transfer server 2 controls the transfer of medical record information from medical record creation support device 1 to electronic medical record terminal 4. Transfer server 2 is configured using, for example, AWS (Amazon Web Services). Transfer server 2 may consist of one or more devices.

[0052] As a specific example of configuration, the transfer server 2 has a storage unit 21. The transfer server 2 also has a communication control unit 22, a medical record information receiving unit 23, a control unit 24, and a medical record information transmission unit 25. Some or all of these may be realized by a processor executing a predetermined program, or they may be implemented in hardware.

[0053] The storage unit 21 stores a correspondence database that shows the correspondence between user IDs and transfer device IDs that are uniquely set for each of the transfer devices 3.

[0054] Figure 2 schematically illustrates the structure of the correspondence database. As shown in the figure, user IDs are associated with transfer device IDs. One transfer device ID may be associated with one user ID, or two or more transfer device IDs may be associated with one user ID, or one transfer device ID may be associated with two or more user IDs. Such a correspondence database is set up, for example, by the system administrator and updated as needed.

[0055] In Figure 2, for example, medical record information generated by user ID "U01" should be sent to transfer device 3, which is configured with transfer device ID "ID01". Hereafter, the user with user ID "U01" may be referred to as "User U01". Also, transfer device 3, which is configured with transfer device ID "ID01", may be referred to as "Transfer device TD01".

[0056] Returning to Figure 1, the communication control unit 22 establishes communication with the transfer device 3. The medical record information receiving unit 23 receives medical record information linked to the user ID from the medical record creation support device 1 via the network and writes it to the storage unit 21. As a result, as shown in Figure 3A, each of the multiple medical record information entries is stored in association with the user ID. In Figure 3A, for example, medical record information MR01 generated by user U01 is stored.

[0057] Returning to Figure 1, the control unit 24 controls which medical record information from the medical record creation support device 1 is sent to which transfer device 3. Specifically, the control unit 24 identifies the medical record information (Figure 3A) stored in association with the user ID included in the transfer request as the transfer target. Then, the control unit 24 refers to the correspondence database (Figure 2A) and identifies the transfer device 3 with the transfer device ID associated with the user ID included in the transfer request as the transfer destination.

[0058] The medical record information transmission unit 25 transmits the medical record information identified by the control unit 24 to the transfer device 3 identified by the control unit 24 via the network. It is desirable for the medical record information transmission unit 25 to delete the transmitted medical record information from the storage unit 21.

[0059] [Transfer device 3] The transfer device 3 receives medical record information from the transfer server 2 via the network and transfers it to the electronic medical record terminal 4 without going through the network. As a specific example of configuration, the transfer device 3 has a communication control unit 31, a medical record information transfer unit 32, and a USB terminal 33. The transfer device 3 may take the form of, for example, a USB memory stick.

[0060] The communication control unit 31 establishes communication with the transfer server 2. Specifically, when the transfer device 3 is inserted into the USB port 42 of the electronic medical record terminal 4 on which a predetermined transfer management program (described later) is installed, the transfer device 3 becomes able to communicate with the transfer server 2, for example, via a network connection through Wi-Fi.

[0061] The communication control unit 31 should ideally establish communication after performing authentication to confirm the communication partner, so that medical record information from the transfer server 2 is not transmitted to an unintended device. Furthermore, it is desirable to use encrypted communication such as TLS to prevent medical record information from the transfer device 3 from being intercepted by a third party. The transfer device 3 stores its own transfer device ID and notifies the transfer server 2 of its transfer device ID when communicating.

[0062] The medical record information transfer unit 32 transfers medical record information to the electronic medical record terminal 4. Specifically, when medical record information is transmitted from the transfer server 2, the medical record information transfer unit 32 receives it and immediately transfers it to the electronic medical record terminal 4 via USB connection. It is desirable that the medical record information is not stored in the transfer device 3 after the transfer.

[0063] Furthermore, the communication protocol for the USB connection is arbitrary and may include, for example, USB HID. Also, the connection between the transfer device 3 and the electronic medical record terminal 4 is not limited to a USB connection; it may also be a wired communication other than USB, short-range wireless communication, etc. In any case, it is desirable to connect the transfer device 3 and the electronic medical record terminal 4 in a way that prevents access from other devices.

[0064] Furthermore, unlike a USB memory stick, it is desirable that, even when the transfer device 3 is connected to (inserted into) the electronic medical record terminal 4, data cannot be written to the transfer device 3 by operations on the electronic medical record terminal 4 (including the input interface connected thereto; the same applies hereinafter), and that data written to the transfer device 3 cannot be read by operations on the electronic medical record terminal 4. In other words, it is desirable that the functions of the transfer device 3 be limited to the transfer of medical record information, authentication, and encrypted communication.

[0065] [Electronic medical record terminal 4] The electronic medical record terminal 4 is any personal computer used by a physician to manage each patient's medical record. The electronic medical record terminal 4 does not need to be connected to a network.

[0066] The electronic medical record terminal 4 has a transfer management unit 41. The transfer management unit 41 is realized by installing a transfer management program on the electronic medical record terminal 4. The transfer management unit 41 receives medical record information via USB connection from a transfer device 3 connected to a USB port 42, without using a network. The transfer management unit 41 then writes the received medical record information to the clipboard of the electronic medical record terminal 4. The doctor can write out the written medical record information by performing a predetermined operation (for example, simultaneously pressing the control key and the "V" key on the keyboard).

[0067] Furthermore, the transfer of medical record information from the transfer device 3 to the electronic medical record terminal 4 is not limited to the medical record information transfer unit 32 actively transmitting the medical record information; the electronic medical record terminal 4 may also read the medical record information from the transfer device 3. For example, the transfer device 3 may be designed as a virtual storage device, and the transfer management unit 41 of the electronic medical record terminal 4 may monitor the transfer device 3, detect that medical record information has been sent from the transfer server 2 to the transfer device 3, and then read the medical record information from the transfer device 3.

[0068] [Processing Sequence] Figure 4 is a sequence diagram showing an example of the processing operation of the electronic medical record management system. Note that Figure 4 is merely an example, and some processes may be omitted, other processes may be added, or the order of processes may be changed as appropriate. Also, it is assumed that the USB terminal 33 of the transfer device 3 is inserted into the USB port 42 of the electronic medical record terminal 4, and that the transfer device 3 is in a state where it can communicate with the transfer server 2.

[0069] First, the physician enters their user ID (hereinafter referred to as "U01") into the medical record creation support device 1, making it available for use. Then, in response to the physician's operation, the medical record information acquisition unit 11 of the medical record creation support device 1 acquires medical record information, and the medical record information transmission unit 12 transmits the medical record information to the transfer server 2 (step S1). A specific example is described below.

[0070] Figure 5A schematically shows an example of a screen displayed on the display by the medical record creation support device 1. As shown in the figure, this screen includes a "Start New Consultation" button, a transcription results field, a summary field, etc. The doctor presses the "Start New Consultation" button and then engages in conversation (diagnosis) with the patient. As a result, the medical record information acquisition unit 11 records the conversation between the two, transcribes the conversation and displays it in the transcription results field, and also creates a summary and displays it in the summary field (see Figure 5B).

[0071] The physician completes the summary by correcting the transcription results and revising the summary as needed. The medical record information transmission unit 12 sends the completed summary as medical record information to the transfer server 2. Specifically, the medical record information transmission unit 12 sends the medical record information (here referred to as medical record information MR01) to the transfer server 2, linked to the user ID "U01". The timing of sending the medical record information is arbitrary; for example, it may be when the physician instructs the medical record creation support device 1 that the summary is complete.

[0072] Returning to Figure 4, the medical record information receiving unit 23 of the transfer server 2 receives medical record information from the medical record creation support device 1 and stores it in the storage unit 21 (step S11). In this example, as shown in Figure 3A, medical record information MR01 is stored in the storage unit 21 in association with user ID "U01". Figure 3A also illustrates a state in which medical record information MR02 and MR03, created by physicians with other user IDs "U02" and "U03", respectively, are also written to the storage unit 21.

[0073] Meanwhile, in the medical record creation support device 1, after the medical record information is transmitted (step S1), a transfer button appears on the screen (see Figure 5C). The doctor then presses the transfer button to send the medical record information to the electronic medical record terminal 4. In response to this operation, the transfer request unit 13 sends a transfer request including user ID "U01" to the transfer server 2 (step S2).

[0074] When the transfer server 2 receives a transfer request, its control unit 24 identifies which medical record information should be transferred to which transfer device 3 (step S12). In this example, the control unit 24 refers to the storage unit 21 (Figure 3A) and identifies medical record information MR01, which is associated with the user ID "U01" in the transfer request, as the medical record information to be transferred. The control unit 24 also refers to the correspondence database (Figure 2) in the storage unit 21 and identifies transfer device TD01, which is associated with the user ID "U01" in the transfer request, as the transfer device 3 to which the transfer should be made.

[0075] The communication control unit 22 then establishes communication with the transfer device 3 (step S13). It is desirable that this communication be encrypted (e.g., TLS communication). It is also desirable that appropriate authentication (e.g., X.509 authentication) be performed between the communication control unit 22 of the transfer server 2 and the communication control unit 31 of the transfer device 3 prior to establishing communication. The timing of establishing communication is arbitrary and may be done, for example, when the transfer device 3 is inserted into the electronic medical record terminal 4.

[0076] Next, the medical record information transmission unit 25 transmits the identified medical record information to the identified transfer device 3 (step S14). In this example, the medical record information MR01 is transmitted to the transfer device TD01. After that, it is desirable for the control unit 24 to delete the medical record information MR01 from the storage unit 21 (step S15, see Figure 3B). This reduces the risk of unintentional leakage of medical record information.

[0077] When the transfer device 3 receives medical record information from the transfer server 2, the medical record information transfer unit 32 transfers the received medical record information to the connected electronic medical record terminal 4 (step S21). The transfer of medical record information from the transfer server 2 to the transfer device 3 is performed via the network. On the other hand, the transfer of medical record information from the transfer device 3 to the electronic medical record terminal 4 is performed via a USB connection without going through the network. If the medical record information received by the transfer device 3 from the transfer server 2 is temporarily stored in its own storage unit (not shown), it is desirable for the medical record information transfer unit 32 to delete the medical record information from the storage unit immediately after transferring it to the electronic medical record terminal 4 (step S22). This reduces the risk of unintentional leakage of medical record information.

[0078] When the electronic medical record terminal 4 receives medical record information from the transfer device 3, its transfer management unit 41 writes the medical record information to the electronic medical record terminal 4's clipboard (step S31). In this way, the medical record information created by the medical record creation support device 1 becomes usable even on the electronic medical record terminal 4 which is not connected to the network.

[0079] The above explanation assumed that the transfer device T01, which is the transfer destination, is connected to the electronic medical record terminal 4 and that the transfer request (step S2) is made when it is able to communicate with the transfer server 2. If the transfer request (step S2) is made when the transfer device T01 is not connected to the electronic medical record terminal 4, the transfer server 2 cannot send the medical record information to the transfer device T01 (step S14). Therefore, the control unit 24 of the transfer server 2 may return error information to the medical record creation support device 1. The error information may be displayed on the display by the medical record creation support device 1. This error information indicates that the transfer device T01, which should be the transfer destination, is not connected to the electronic medical record terminal 4, or that the medical record information cannot be transferred.

[0080] Furthermore, as shown in Figure 2, a single user ID "U02" may be associated with multiple transfer devices TD02 and TD03.

[0081] If, at the time of the transfer request (step S2 in Figure 4), both transfer devices TD02 and TD03 are inserted into the electronic medical record terminal 4, the medical record information transfer unit 32 of the transfer server 2 transmits the medical record information to both transfer devices TD02 and TD03.

[0082] If, at the time a transfer request is made, some transfer devices TD02 are inserted into the electronic medical record terminal 4, but other transfer devices TD03 are not inserted into the electronic medical record terminal 4, the medical record information transfer unit 32 of the transfer server 2 sends the medical record information to the transfer device TD02 inserted into the electronic medical record terminal 4. In this case, the control unit 24 of the transfer server 2 may return error information to the medical record creation support device 1. This error information indicates that the transfer device TD03 that should be the transfer destination is not connected to the electronic medical record terminal 4, or that the medical record information cannot be transferred to the transfer device TD03. Alternatively, if the information can be transferred to at least some of the transfer devices TD02, it is not necessary to send error information.

[0083] If neither of the transfer devices TD02 and TD03 are inserted into the electronic medical record terminal 4 at the time the transfer request is made, the control unit 24 of the transfer server 2 may return error information to the medical record creation support device 1. This error information indicates that neither of the transfer devices T02 and T03, which should be the transfer destinations, are connected to the electronic medical record terminal 4, or that the medical record information cannot be transferred.

[0084] As described above, medical record information becomes available on the electronic medical record terminal 4, improving the usability of the electronic medical record terminal 4.

[0085] Furthermore, medical record information is not limited to text information such as summaries of conversations between doctors and patients, but may also include non-text data such as image data and audio data. If medical record information includes non-text data, a decoding function may be added to the medical record information transmission unit 12 of the medical record creation support device 1, and an encoding function may be added to the transfer management unit 41 of the electronic medical record terminal 4. The decoding function converts non-text data into text data such as binary data through a predetermined decoding process. The encoding function restores text data to non-text data through an encoding process that is the reverse of the decoding process.

[0086] Furthermore, MQTT communication, for example, can be applied to communication between the medical record creation support device 1 and the transfer server 2, and between the transfer server 2 and the transfer device 3. If there are limitations on communication capacity, an upper limit on the number of characters or other parameters may be set for the medical record information. Alternatively, the medical record information may be divided into two or more parts for communication.

[0087] The following describes an example of the transcription process when generating medical record information. As shown in Figure 6, the medical record information acquisition unit 11 in the medical record creation assistance device 1 has a transcription unit 110 which has a transcription unit 111 and a character correction unit 112.

[0088] The transcription unit 111 converts the conversation between the doctor and the patient into text. Then, the text correction unit 112 uses the dictionary stored in the dictionary memory unit 112a to correct any words that appear to be incorrect among the words composed of the converted text. The corrected text is displayed in the transcription results column of Figure 5B.

[0089] Figure 7 is a schematic diagram illustrating an example of a dictionary. This dictionary shows the correspondence between words that need correction and the corrected words (what words should be used to correct the words that need correction). For example, if the transcription results in "physical condition policy," "physical condition monk," and "weight improvement," it means that these are errors and should be corrected to "shingles." By using such a dictionary, transcription can be performed with high accuracy, and the summary based on that transcription will also be accurate.

[0090] Next, we will describe an example of a dictionary creation method. Figure 8A is a block diagram showing the schematic configuration of a dictionary creation system. Figure 8B is a flowchart showing an example of the dictionary creation process.

[0091] First, the target word to be designated as a "word requiring correction" is set in the dictionary and input into the reading device 51 and the association device 53 (step S51). The target word can be any word, but for example, a doctor might select a word that is frequently misused.

[0092] Next, for example, a text-to-speech device 51 using artificial intelligence reads out the target word (step S52). It is desirable that the text-to-speech device 51 can read in multiple voices (male voice, female voice, etc.).

[0093] Next, for example, an artificial intelligence transcription device 52 transcribes the spoken words (step S53). If multiple readings occur in step S52, transcription is performed for each reading. The transcribed words are input into the association device 53.

[0094] The association device 53 then determines whether the transcribed word matches the target word (step S54). If they do not match (NO in step S54), the association device 53 identifies the transcribed word as the word requiring correction, associates it with the target word as the corrected word, and registers it in the dictionary storage unit 112a (step S55).

[0095] Note that some or all of the above steps (reading aloud, transcription, matching, and registration) may be performed by a human.

[0096] By creating a dictionary in this manner, if any of the words composed of characters converted by the transcription unit 111 in Figure 6 match a word that requires correction and is registered in the dictionary, the character correction unit 112 can correct that word to the corrected word.

[0097] (Second Embodiment) The first embodiment involved transferring medical record information from the medical record creation support device 1 to the electronic medical record terminal 4. The second embodiment, described below, adds the ability to transfer patient information from the electronic medical record terminal 4 to the medical record creation support device 1. In other words, it enables bidirectional transfer, both from the medical record creation support device 1 to the electronic medical record terminal 4 and from the electronic medical record terminal 4 to the medical record creation support device 1.

[0098] Here, patient information refers to any information about the patient recorded in the medical record of the electronic medical record terminal 4 (not limited to text information, but may also include image data, etc.), such as the patient's gender, age, medical history, and test results. By transferring patient information to the medical record creation support device 1, doctors can refer to the patient information when examining the patient using the medical record creation support device 1, and it becomes easier to create summaries that take the patient information into consideration.

[0099] Figure 9 is a block diagram illustrating the schematic configuration of the electronic medical record management system according to the second embodiment. Hereafter, commonalities with the first embodiment may be omitted or simplified in the explanation.

[0100] In this embodiment, each electronic medical record terminal 4 is uniquely assigned a medical record terminal ID. When a physician performs a predetermined operation on the electronic medical record terminal 4, the transfer management unit 41 of the electronic medical record terminal 4 transmits the patient information to be transferred, linked to the medical record terminal ID, to the transfer device 3 connected to the USB port 42 (without going through a network). It can also be said that the transfer device 3 acquires the patient information in response to the predetermined operation by the physician.

[0101] The transfer device 3 has a patient information transfer unit 32a. The patient information transfer unit 32a transfers patient information from the electronic medical record terminal 4 to the transfer server 2. Specifically, the patient information transfer unit 32a obtains patient information linked to the medical record terminal ID from the electronic medical record terminal 4 and transfers it to the transfer server 2 via the network. It is desirable that this transfer be triggered by a predetermined operation from the physician to the electronic medical record terminal 4 and performed without any further operation. It is also desirable that the patient information is not stored in the transfer device 3 after the transfer.

[0102] The transfer server 2 has a patient information receiving unit 23a and a patient information transmitting unit 25a. The patient information receiving unit 23a receives patient information linked to the medical record terminal ID from the transfer device 3 via the network and writes it to the memory area in the storage unit 21 associated with the received medical record terminal ID. The control unit 24 identifies the patient information stored in the memory area associated with the user ID as the transfer target based on the user ID included in the acquisition request (described later) from the medical record creation support device 1. Then, the patient information transmitting unit 25a transmits the identified patient information to the medical record creation support device 1 via the network. Details are as follows.

[0103] As shown in Figure 10, the storage unit 21 has multiple memory areas, each associated with one or more medical record terminal IDs and one or more user IDs. It can also be said that each memory area is associated with one or more electronic medical record terminals 4 and one or more users. The memory areas may be physical or virtual concepts. The association between such memory areas and the medical record terminal IDs and user IDs is set, for example, by the system administrator and updated as needed.

[0104] For example, the memory area M1 in Figure 10 is associated with one medical record terminal ID "KT01" and one user ID "U11". This means that patient information from the electronic medical record terminal 4 (hereinafter sometimes referred to as "electronic medical record terminal KT01"), whose medical record terminal ID is "KT01", is written to the memory area M1 and transferred to the medical record creation support device 1 used by user U11.

[0105] Furthermore, memory area M2 is associated with the electronic medical record terminals KT02 and KT03 and user U12. This means that patient information from electronic medical record terminals KT02 and KT03 is written to memory area M2 and transferred to the medical record creation support device 1 used by user U12. This is convenient, for example, when electronic medical record terminals KT02 and KT03 are installed in two separate examination rooms.

[0106] Furthermore, memory area M3 is associated with the electronic medical record terminal KT04 and users U13 and U14. This means that patient information from the electronic medical record terminal KT04 is written to memory area M3 and transferred to the medical record creation support device 1 used by users U13 and U14. This is convenient when two users, U13 and U14, share one electronic medical record terminal KT04.

[0107] Furthermore, memory area M4 is associated with electronic medical record terminals KT05 and KT06 and users U15 and U16. This means that patient information from electronic medical record terminals KT05 and KT06 is written to memory area M4 and transferred to the medical record creation support device 1 used by users U15 and U16.

[0108] Returning to Figure 9, the medical record creation support device 1 has an acquisition request unit 13a. In response to an acquisition instruction from the user, the acquisition request unit 13a sends an acquisition request to the transfer server 2 to send patient information stored in the transfer server 2 to the medical record creation support device 1. This acquisition request includes the user ID.

[0109] Figure 11 is a sequence diagram showing an example of the processing operation of the electronic medical record management system, illustrating the patient information transfer process from the electronic medical record terminal 4 to the medical record creation support device 1. It is assumed that the USB terminal 33 of the transfer device 3 is inserted into the USB port 42 of the electronic medical record terminal 4 (hereinafter referred to as the electronic medical record terminal KT01), and that the transfer device 3 is in a state where it can communicate with the transfer server 2. Furthermore, it is assumed that the physician has entered their user ID (hereinafter referred to as "U11") into the medical record creation support device 1 and is in a state where it can be used.

[0110] The physician selects patient information to be transferred to the medical record creation support device 1 on the electronic medical record terminal 4. The physician then performs a predetermined operation on the electronic medical record terminal 4 to transfer the patient information. In response, the transfer management unit 41 of the electronic medical record terminal 4 associates the medical record terminal ID "KT01" with the selected patient information and sends it to the transfer device 3 (step S111). For example, the selected patient information is written to the clipboard of the electronic medical record terminal 4 and sent from the clipboard to the transfer device 3.

[0111] When patient information is transmitted (i.e., when patient information is acquired), the transfer device 3 establishes communication with the transfer server 2 (step S121). The patient information transfer unit 32a then transmits the patient information to the transfer server 2 via the network (step S122). If the patient information received by the transfer device 3 from the electronic medical record terminal 4 is temporarily stored in its own memory unit (not shown), it is desirable for the patient information transfer unit 32a to delete the patient information from the memory unit immediately after transferring it to the transfer server 2 (step S123). This reduces the risk of unintentional leakage of patient information.

[0112] The patient information receiving unit 23a of the transfer server 2 receives patient information from the transfer device 3 and writes it to a memory area in the storage unit 21 associated with the medical record terminal ID linked to the patient information (step S131). In this example (see Figure 10), the patient information receiving unit 23a writes the patient information from the transfer device 3 to memory area M1 associated with the medical record terminal ID "KT01" linked to the patient information. If patient information is already written to the memory area to be written to, the newly received patient information is overwritten.

[0113] The physician then performs a predetermined operation on the medical record creation support device 1 to obtain patient information. For example, a patient information acquisition button is provided on the screen displayed on the medical record creation support device 1's display (for example, Figure 5A), and the physician presses this button. In response to this operation, the acquisition request unit 13a of the medical record creation support device 1 sends an acquisition request including user ID "U11" to the transfer server 2 (step S141).

[0114] When the transfer server 2 receives an acquisition request, its control unit 24 identifies which memory area contains the patient information that should be transferred to the medical record creation support device 1 (step S132). In this example (see Figure 10), the control unit 24 identifies the patient information written to memory area M1 associated with the user ID "U11" in the acquisition request as the medical record information to be transferred.

[0115] Then, the patient information transmission unit 25a transmits the identified patient information to the medical record creation support device 1, which is the source of the acquisition request (step S133). As a result, the medical record creation support device 1 receives the patient information (step S142). For example, the patient information may be written to the clipboard of the medical record creation support device 1 or displayed in a designated field on the screen displayed on the display of the medical record creation support device 1 (for example, Figure 5A). The medical record information acquisition unit 11 may also transcribe or summarize this patient information.

[0116] Furthermore, after the patient information transmission unit 25a transmits the patient information to the medical record creation support device 1 in step S133, the control unit 24 may or may not delete the patient information written to the memory area M1 of the storage unit 21. Deleting it reduces the risk of unintentional leakage of patient information. By not deleting the information triggered by transmission to the medical record creation support device 1, even if the medical record creation support device 1 accidentally edits or deletes the patient information, for example, the same patient information can be retrieved again from the transfer server 2.

[0117] As described above, in this embodiment, patient information can be acquired from the electronic medical record terminal 4 to the medical record creation support device 1.

[0118] Although this embodiment was designed to enable bidirectional transfer in combination with the first embodiment, it may also be sufficient to simply transfer patient information from the electronic medical record terminal 4 to the medical record creation support device 1.

[0119] Any part or all of the functional components described herein may be implemented by program. Programs referred to herein may be recorded non-temporarily on a computer-readable recording medium.

[0120] Such programs may be installed on a computer (so-called native apps). In that case, the program may be downloaded to the computer via a communication line such as the internet (including wireless communication), or it may be distributed already installed on the computer.

[0121] Alternatively, the program may run on a web browser (a so-called web application). In that case, the computer may receive the program, written in a markup language file (e.g., an HTML file), from a server and execute it through the web browser.

[0122] Based on the above description, those skilled in the art may be able to conceive of additional effects and various modifications of the present invention, but the embodiments of the present invention are not limited to the individual embodiments described above. For example, inventions that take only a part of each embodiment, or inventions that combine multiple embodiments, are naturally conceivable. Various additions, modifications, and partial deletions are possible as long as they do not depart from the conceptual idea and spirit of the present invention derived from the contents of the claims and their equivalents.

[0123] For example, what is described herein as a single device (or component, hereinafter the same) (including what is depicted as a single device in the drawings) may be implemented by multiple devices. Conversely, what is described herein as multiple devices (including what is depicted as multiple devices in the drawings) may be implemented by a single device. Alternatively, some or all of the means or functions that are included in one device may be included in another device. Furthermore, a "system" may consist of one device or two or more devices.

[0124] Furthermore, not all matters described herein are mandatory requirements. In particular, matters described herein but not included in the claims can be considered optional additional matters.

[0125] Furthermore, unless otherwise specified, the term “means” in this specification and the claims means hardware (or functions realized by hardware) and does not include human beings (or human mental activity).

[0126] It should also be noted that the applicant is only aware of the prior art inventions described in the "Prior Art Documents" section of this specification, and the present invention is not necessarily intended to solve the problems described in those prior art inventions. The problems that the present invention aims to solve should be determined by considering this specification as a whole. For example, if this specification describes that a certain effect is achieved by a particular configuration, it can also be said that the problem that is the inverse of that predetermined effect is solved. However, this does not necessarily mean that such a particular configuration is an essential requirement. [Explanation of Symbols]

[0127] 1. Medical record creation support device 11. Medical Record Information Acquisition Department 110 Transcription Section 111 Transcription Section 112 Character correction section 112a Dictionary memory section 12 Medical Record Information Transmission Department 13 Transfer Request Section 2 Transfer Server 21 Memory section 22 Communication Control Unit 23 Medical Record Information Receiving Unit 24 Control Unit 25 Medical Record Information Transmission Department 3 Transfer device 31 Communication Control Unit 32 Medical Record Information Transfer Department 33 USB ports 4. Electronic medical record terminal 41 Transfer Management Department 42 USB ports 51. Text-to-speech device 52 Transcription device 53 Association device

Claims

1. The system comprises a medical record creation support device, a transfer server, a transfer device, and an electronic medical record terminal. The medical record creation support device acquires medical record information and transmits the acquired medical record information to the transfer server via the network. The transfer server transmits the medical record information from the medical record creation support device to the transfer device via the network. The transfer device transfers medical record information from the transfer server to the electronic medical record terminal via USB HID without going through the network. The transfer device acquires patient information from the electronic medical record terminal without going through the network and transmits it to the transfer server via the network. The transfer server is an electronic medical record management system that transmits patient information received from the transfer device to the medical record creation support device via a network.

2. The transfer device responds to the first operation on the electronic medical record terminal, Patient information from the aforementioned electronic medical record terminal is acquired without going through the network, and, The electronic medical record management system according to claim 1, which transmits to the transfer server via a network.

3. The electronic medical record management system according to claim 1 or 2, wherein the transfer server transmits patient information from the transfer device to the medical record creation support device via a network in response to a second operation on the medical record creation support device.

4. The aforementioned transfer server, The patient information received from the transfer device is written to the storage unit. The electronic medical record management system according to claim 1 or 2, wherein when further patient information is received from the transfer device, the received patient information overwrites the stored patient information.

5. The aforementioned transfer server, The patient information received from the transfer device is written to the storage unit. The electronic medical record management system according to claim 1 or 2, wherein patient information is not deleted from the storage unit as a result of being transmitted to the medical record creation support device via the network.

6. The aforementioned transfer server, The patient information received from the transfer device is written to the storage unit. This patient information will not be deleted from the storage unit upon transmission to the medical record creation support device via the network. The electronic medical record management system according to claim 1 or 2, wherein when further patient information is received from the transfer device, the received patient information is overwritten and stored over the stored patient information.

7. The system comprises a medical record creation support device, a transfer server, a transfer device, and an electronic medical record terminal. The transfer server comprises a storage unit having multiple memory areas, each associated with one or more electronic medical record terminals and one or more user IDs for using the medical record creation support device. Each memory area stores patient information from the associated electronic medical record terminal. The transfer device acquires patient information from the electronic medical record terminal without going through the network and transmits it to the transfer server via the network. An electronic medical record management system comprising: a transfer server that receives an acquisition request including a user ID from the medical record creation support device, and a transfer server that transmits patient information received from the transfer device, which is written to a memory area associated with the user ID, to the medical record creation support device via the network.

Images