Medical data acquisition device, medical data acquisition system, and medical data acquisition program

Abstract

To provide a medical data acquisition apparatus, a medical data acquisition system, a method and a program that can acquire medical data even when communication cannot be performed with a server.SOLUTION: In a medical data acquisition system 100, a client 3 that is a medical data acquisition apparatus which can communicate with a server 2 through a network 1, comprises: a first control section that controls a first application which acquires first medical data stored in the server; a storage section that stores first medical data at a first time point as second medical data; and a second control section that controls a second application which acquires second medical data stored in the storage section. The first control section acquires difference data from the server by means of the first application when there is a difference between first medical data at a second time point after the first time point and the first medical data at the first time point. The storage section updates the second medical data on the basis of the difference data.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a medical data acquisition device, a medical data acquisition system, and a medical data acquisition program.

Background Art

[0002] Cloud-based electronic medical records are becoming widespread. Also, an electronic medical record system is disclosed that can search for medical record data related to the medical record data from a medical record database based on patient information and date information in the medical record data retrieved from the medical record database (see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in a cloud-based electronic medical record, since the client and the server communicate via a network, when the communication state is poor, a network failure occurs, or a problem occurs in the server, etc., the client cannot communicate with the server and cannot access the data stored in the server. In this case, the patient reception work and examination work will be delayed.

[0005] Also, when the client stores the data stored in the server in the client in preparation for a situation where communication with the server is impossible, if the amount of data to be stored increases, the load on the client and the server becomes excessive. Further, if all the data stored in the server is stored in the client, there is a possibility that the memory capacity of the client's storage device is insufficient.

Means for Solving the Problems

[0006] The medical data acquisition device of the present invention is a medical data acquisition device capable of communicating with a server via a network, and includes a first control unit that controls a first application for acquiring first medical data stored in the server, a storage unit that stores the first medical data at a first time point as the second medical data, and a second control unit that controls a second application for acquiring the second medical data stored in the storage unit. The first control unit acquires the difference as difference data from the server by the first application when there is a difference between the first medical data at a second time point after the first time point and the first medical data at the first time point, and the storage unit can update the second medical data based on the difference data.

Effects of the Invention

[0007] According to the present invention, it is possible to provide a medical data acquisition device capable of acquiring medical data even when communication with a server is not possible. Further, by updating medical data by acquiring difference data, the load on the medical data acquisition device and the server can be reduced.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Mode for Carrying Out the Invention

[0009] The medical data acquisition system according to the embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of a system configuration of the medical data acquisition system of the present embodiment.

[0010] As shown in FIG. 1, the medical data acquisition system 100 includes a server 2 and a client (medical data acquisition device) 3 that are communicably connected via a network 1 such as the Internet. In the present embodiment, the medical data acquisition system 100 is assumed to be a cloud-based electronic medical record system, and a system for inputting and outputting attribute information, reception information, and medical record information of outpatients who visit a medical institution between the server 2 and the client (medical data acquisition device) 3 is assumed. Note that the present invention is not limited to outpatients and includes patients other than outpatients (such as inpatients).

[0011] Server 2 includes a storage unit 4, a control unit 5, and a transceiver unit 7. The storage unit 4, the control unit 5, and the transceiver unit 7 are electrically connected by a bus (not shown) and can communicate with each other. The storage unit 4 stores first medical data 8 and time data 9. The first medical data 8 includes difference data 10. The storage unit 4 is a storage device such as a main memory or a storage. The control unit 6 includes a difference data generation unit 6. The control unit 5 is a processor such as a CPU, an MPU, or a GPU, controls hardware resources, and executes various applications.

[0012] The client (medical data acquisition device) 3 includes a control unit 11, a storage unit 12, an input information storage unit 13, an input / output unit 15, a display unit 17, and a transceiver unit 18. The control unit 11, the storage unit 12, the input information storage unit 13, the input / output unit 15, the display unit 17, and the transceiver unit 18 are electrically connected by a bus (not shown) and can communicate with each other. The control unit 11 includes a first control unit 11-1, a second control unit 11-2, a difference data acquisition unit 14, and a medical data selection unit 16. The storage unit 12 stores a first application 24, a second application 25, second medical data 19, time data 20, and difference data 21. The input information storage unit 13 includes a first information storage unit 22 and a second information storage unit 23.

[0013] The control unit 11 is a processor such as a CPU, an MPU, or a GPU, controls hardware resources, and executes the first application (cloud application) 24, the second application (local application) 25, and various applications. The first control unit 11-1 controls the first application 24. The second control unit 11-2 controls the second application 25. The storage unit 12 and the input information storage unit 13 are storage devices such as a main memory or a storage.

[0014] FIG. 2 is a diagram showing an example of the data configuration of the first medical data according to the present embodiment. As shown in FIG. 2, the first medical data 8 includes attribute information 30 of outpatients at the patient medical institution, reception information 31 related to the reception work of outpatients, medical record information 32 of outpatients, medical images 33 of outpatients (images such as simple X-ray images, CT, MRI, ultrasonic tomographic images, and angiograms), and differential data 10.

[0015] The attribute information 30 includes name information 34 of the outpatient, ID information 35, insurance information 36, age information 37, gender information 38, date of birth information 39, and other attribute information 40. The reception information 31 includes reservation date and time information 41, hospital visit date and time information 42, number of hospital visits information 43, time division information 44, department information 45, doctor information 46, consultation status information 47, and other reception information 48. The medical record information 32 includes chief complaint information 49, findings information 50, disease name information 51, examination information 52, treatment information 53, prescription information 54, instruction information 56, and other medical record information 55.

[0016] FIG. 3 is a diagram showing an example of the data configuration of the second medical data according to the present embodiment. As shown in FIG. 3, the second medical data 19 includes attribute information 60 of outpatients at the patient medical institution, reception information 61 related to the reception work of outpatients, and medical record information 62 of outpatients, but does not include medical images of outpatients (images such as simple X-ray images, CT, MRI, ultrasonic tomographic images, and angiograms).

[0017] The attribute information 60 includes name information 64 of the outpatient, ID information 65, insurance information 66, age information 67, gender information 68, and date of birth information 69. The attribute information 60 may include other attribute information. The reception information 61 includes reservation date and time information 71, hospital visit date and time information 72, number of hospital visits information 73, time division information 74, department information 75, doctor information 76, and consultation status information 77. The reception information 61 may include other reception information. The medical record information 62 includes chief complaint information 79, findings information 80, disease name information 81, examination information 82, treatment information 83, prescription information 84, and instruction information 78. The medical record information 62 may include other medical record information.

[0018] Thus, the second medical data 19 is a part of the medical data selected from the first medical data 8 by the medical data selection unit 16, and is at least one of the attribute information of outpatients in a medical institution, the reception information related to the reception work of outpatients, and the medical record information of outpatients. To store a part of the first medical data 8 in the client (medical data acquisition device) 3, it is possible to avoid the possibility that the memory capacity of the memory device of the client is insufficient.

[0019] Next, the process in which the client (medical data acquisition device) 3 acquires the first medical data 8 stored in the server 2 and stores it as the second medical data 19 will be described. Also, the process in which the client (medical data acquisition device) 3 acquires the differential data 10 from the server 2 and updates the second medical data 19 based on the differential data 10 will be described.

[0020] FIG. 4 is a flowchart showing an example of the process of storing the first medical data 8 as the second medical data 19. FIG. 5 is a flowchart showing an example of the process of updating the second medical data 19 based on the acquired differential data 10. FIG. 6 is a sequence diagram showing an example of the operations of the server 2 and the client (medical data acquisition device) 3 in these processes.

[0021] In step S1, the control unit 11 (the first control unit 11-1) activates (for example, logs in) the first application (cloud application) 24. By inputting by the reception staff or the doctor using an input device (not shown), based on the activation command input by the input / output unit 15, the control unit 11 (the first control unit 11-1) executes the activation command of the first application 24 (CL1). Here, the first application 24 is an application for the reception staff or doctor in a medical institution to input, output, or view information related to the first medical data 8 as the first information on an electronic medical record system. These information are input and output by the input / output unit 15, displayed on a display device (not shown) such as a monitor by the display unit 17, and stored in the first information storage unit 22.

[0022] In step S2, the transceiver unit 18 connects to the transceiver unit 7 so as to be communicable with the server 2 via the network 1. For example, when an icon or the like for connecting to the server 2 is clicked on the operation screen of the first application 24, the input / output unit 15 inputs a connection command, and the transceiver unit 18 executes the connection command.

[0023] In step S3, the first control unit 11-1 acquires the first medical data 8 stored in the storage unit 8 of the server 2 via the transceiver units 7 and 18 by the first application 24. Note that the medical data acquired by the first application 24 is a part of the medical data selected from the first medical data 8 by the medical data selection unit 16. Also, when the client (medical data acquisition device) 3 has already acquired and stored the past first medical data 8, the medical data acquired by the first application 24 may be the differential data 10 that is the difference from the past first medical data 8.

[0024] When an icon or the like for acquiring the first medical data 8 is clicked on the operation screen of the first application 24, the first application 24 executes an acquisition command for the first medical data 8 and transmits transmission request information to the server 2. The server 2 that has received the transmission request information transmits the requested first medical data 8 to the client (medical data acquisition device) 3 (SV1). The first control unit 11-1 acquires the first medical data 8 by the first application 24 (CL2).

[0025] In step S4, the first control unit 11-1 determines whether to store the acquired first medical data 8 as the second medical data 19 by the first application 24. If it is determined to store, in step S5, the first control unit 11-1 executes a storage command to store the acquired first medical data 8 as the second medical data 19 by the first application 24, and stores the second medical data 19 in the storage unit 12 (CL3). For example, when an icon or the like for storing the second medical data 19 is clicked on the operation screen of the first application 24, the storage unit 12 stores the second medical data 19.

[0026] The first medical data 8 is associated with time data 9, and the access time, transmission time, and update time of the first medical data 8 are recorded. The access time, acquisition time of the first medical data 8 by the first application 24, and the transmission time of the first medical data 8 by the server 2 are recorded as the time data 9. Also, the second medical data 19 is associated with time data 20, and the access time, acquisition time of the first medical data 8 by the first application 24, and the storage time and update time of the second medical data 19 are recorded. For example, the acquisition time of the first medical data 8 in step S3 is recorded in the time data 9 and 20, and the storage time of the second medical data 19 in step S5 is recorded in the time data 20. Note that the acquisition time of the first medical data 8 in step S3 is taken as the first point in time. Also, the storage time of the second medical data 19 in step S5 may be taken as the first point in time. Also, the startup time (for example, login time) or end time (for example, logout time, etc.) of the first application 24 may be taken as the first point in time. Also, a preset predetermined time (for example, 0:00 am) may be taken as the first point in time. The first point in time is recorded in the time data 9 and / or the time data 20.

[0027] By a reception staff or a doctor at a medical institution inputting first information regarding first medical data 8, the input / output unit 15 causes the first application 24 to input the first information, and the transmission / reception unit 18 causes the first application 24 to transmit the first information to the server 2 via the network 1 (CL4). For example, as the first information regarding the first medical data 8, the first application 24 inputs attribute information of an outpatient at a medical institution, reception information regarding the reception work of the outpatient, medical record information of the outpatient, and a medical image of the outpatient. Further, the first control unit 11-1 has functions of causing the first application 24 to input attribute information of a new patient (a new case) newly visiting a medical institution, retrieving and acquiring the attribute information of an outpatient from the first medical data 8, retrieving and acquiring the past medical record information of the outpatient from the first medical data 8, and selecting and acquiring a set of pre-registered medical record information from the first medical data 8.

[0028] The first information transmitted to the server 2 is received by the transmission / reception unit 7. The first medical data 8 is updated based on the received first information (SV2). This update time is recorded in the time data 9.

[0029] The control unit 11 (the first control unit 11-1) terminates the first application 24 (for example, logs out). By a reception staff or a doctor using an input device (not shown) to input, based on the termination command input by the input / output unit 15, the control unit 11 (the first control unit 11-1) executes the termination command of the first application 24 (CL5).

[0030] Server 2 detects the first medical data 8 at the second time point (SV3). The second time point is after the first time point. Also, the second time point may be a time after the first time point when the medical data 8 is updated based on the first information, or may be the start time (for example, login time) or end time (for example, logout time, etc.) of the first application 24. Further, a preset predetermined time (for example, 0:00 am on the day after the first time point) may be set as the second time point. The second time point is recorded in the time data 9 and / or the time data 20.

[0031] If there is a difference between the first medical data 8 at the second time point and the first medical data 8 at the first time point, the server 2 generates the difference as difference data 10 by the difference data generation unit 6 (SV4). The generated difference data 10 is stored in the storage unit 4 in association with the generation time. The generation time is recorded in the time data 9. The difference data 10 is generated by the server 2 at a predetermined time after the second time point. For example, the difference data 10 is generated during a time period when the load on the server 2 is low (such as at night).

[0032] Next, in step S6, after the second time point, the control unit 11 (the first control unit 11-1) starts the first application 24 (CL6). In step S7, the transmission / reception unit 18 connects to the transmission / reception unit 7 so as to be able to communicate with the server 2 via the network 1. In step S8, the control unit 11 (the first control unit 11-1) ends the first application 24 (CL7).

[0033] On the operation screen of the first application 24, when an icon or the like for acquiring the difference data 10 is clicked, the first application 24 executes an acquisition command for the difference data 10 by the difference data acquisition unit 14 and transmits transmission request information to the server 2. The server 2 that has received the transmission request information transmits the requested difference data 10 to the client (medical data acquisition device) 3 (SV5). The first application 24 acquires the difference data 10 (CL8). For example, when the first application 24 ends (for example, logs out) after the second time point from the first time point, the first control unit 11-1 acquires the difference data 10.

[0034] Thus, in step S9, if there is a difference between the first medical data 8 at the second time point after the first time point and the first medical data 8 at the first time point, the first control unit 11-1 acquires the difference from the server 2 as the difference data 10 by the first application 24. Then, the acquired difference data 10 is stored in the difference data 21. For example, if the first application 24 has input the chief complaint information 49, findings information 50, examination information 52, treatment information 53, prescription information 54, and instruction information 56 of an outpatient and added them to the first medical data 8 from the first time point to the second time point, the added chief complaint information, findings information, examination information, and treatment information become the difference data. The first medical data 8 deleted from the first time point to the second time point also becomes the difference data. Note that the difference data 10 may be generated and / or acquired for each of the attribute information 30, reception information 31, and medical record information 32.

[0035] In step S10, the first control unit 11-1 determines whether to store the difference data 10 acquired by the first application 24 as the second medical data 19. For example, when an icon for updating the second medical data 19 is clicked on the operation screen of the first application 24, the storage unit 12 updates the second medical data 19 based on the difference data 10. Note that the control unit 11 (the second control unit 11-2) may start the second application 25, and the second application 25 may determine whether to store the acquired difference data 10 as the second medical data 19. Also, the storage unit 12 may update the second medical data 19 based on a part of the difference data 10 selected from the acquired difference data 10. In this case, a part of the difference data 10 is selected by the first application 24 or the second application 25.

[0036] If it is determined to store, in step S11, the storage unit 12 executes an update command and updates the second medical data 19 based on the difference data 10 (CL9). In this way, by acquiring the difference data 10 having a smaller data amount than the first medical data 8 and updating the second medical data 19 based on the difference data 10, the second medical data 19 can be stored in the client (medical data acquisition device) 3 without overloading the server 2 or the client (medical data acquisition device) 3.

[0037] Next, when the communication state is poor, a network failure occurs, a problem occurs in the server, etc., and the first medical data 8 cannot be acquired from the server 2 via the network 1, the process in which the second application acquires the second medical data 19 and inputs information of an outpatient will be described.

[0038] FIG. 7 is a flowchart showing an example of a process in which, immediately after starting the first application 24, the first medical data 8 cannot be obtained from the server 2, the second application obtains the second medical data 19, and information of an outpatient is input. FIG. 8 is a sequence diagram showing an example of operations of the server 2 and the client (medical data acquisition device) 3 in this process.

[0039] As described above, the second medical data 19 is stored in the storage unit 12 (CL10). If there is differential data 10, the second medical data 19 is updated based on the differential data.

[0040] In step S12, the control unit 11 (the first control unit 11-1) starts (for example, logs in to) the first application 24. By inputting using an input device (not shown) by a reception staff or a doctor, based on the start command input by the input / output unit 15, the control unit 11 (the first control unit 11-1) executes the start command of the first application 24 (CL11).

[0041] In step S16, communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible, and the client (medical data acquisition device) 3 cannot obtain the first medical data 8 from the server 2.

[0042] In step S17, the control unit 11 (the second control unit 11-2) activates (for example, logs in) the second application (local application) 25. Here, the second application 25 is an application that acquires the second medical data 19 stored in the storage unit 12. Further, the second application 25 is an application for a reception staff or a doctor of a medical institution to input, view, or browse information regarding the second medical data 19 as second information on the client (medical data acquisition device) 3. These information are input and output by the input / output unit 15, displayed on a display device (not shown) such as a monitor by the display unit 17, and stored in the second information storage unit 23. Further, the second information stored in the second information storage unit 23 is associated with the time data 20, and the access time, acquisition time, storage time, and update time of the second information by the second application 25 are recorded.

[0043] When a reception staff or a doctor inputs using an input device (not shown), based on the activation command input by the input / output unit 15, the control unit 11 (the second control unit 11-2) executes the activation command of the second application 25 (CL15). For example, on the operation screen of the first application 24, when an icon or the like for activating the second application 25 is clicked, the input / output unit 15 inputs a connection command, and the control unit 11 (the second control unit 11-2) executes the activation command. In this way, the second control unit 11-2 activates the second application 25 when the first medical data 8 cannot be acquired from the server 2 via the network 1.

[0044] In step S18, the control unit 11 (the second control unit 11-2) selects whether to acquire the second medical data 19 stored in the storage unit 12. If the acquisition of the second medical data 19 is selected, the second application 25 acquires the second medical data 19 stored in the storage unit 12 by the second control unit 11-2 (CL17). When an icon or the like for acquiring the second medical data 19 is clicked on the operation screen of the second application 25, the second application 25 executes an acquisition command for the second medical data 19, and the second application 25 acquires the second medical data 19 (CL17).

[0045] In step S25, by the reception staff or doctor of the medical institution inputting and outputting second information regarding the second medical data 25, the input / output unit 15 inputs and outputs the second information by the second application 25 (CL18). For example, the second application 25 inputs, as second information regarding the second medical data 19, the attribute information of outpatients of the medical institution, the reception information regarding the reception work of outpatients, the medical record information of outpatients, and the medical images of outpatients. In addition, the second control unit 11-2 has functions for the second application 25 to input the attribute information of a new patient (newcomer) newly visiting the medical institution (new patient information input function), search for and acquire the attribute information of outpatients from the second medical data 19 (search function), search for and acquire the past medical record information of outpatients from the second medical data 19 (past medical record information acquisition function), and select and acquire a set of pre-registered medical record information from the second medical data 19 (set acquisition function). The input second information is stored in the second information storage unit 23 (CL19). This storage time is recorded in the time data 20.

[0046] In this way, even when communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible and the client (medical data acquisition device) 3 cannot obtain the first medical data 8 from the server 2, the second application 25 can obtain the second medical data 19 equivalent to the first medical data 8, and an electronic medical record system that can smoothly proceed with the reception work and examination work for outpatients can be provided. Next, steps S18, S19, S25 and operations CL17, CL18, CL19 will be described with specific examples.

[0047] FIG. 9 is a diagram showing an example (display of attribute information and reception information) of the second application activated in the reception work. Using the second application, information regarding the second medical data 19 (attribute information 60 and reception information 61) can be input, output, and browsed as the second information by the reception staff or doctors in the medical institution on the client (medical data acquisition device) 3.

[0048] As shown in FIG. 9, the reception screen 25-1 of the second application 25 is opened. On the reception screen 25-1 of the second application 25, the attribute information and reception information of outpatients are displayed. The displayed information (second information) is stored in the second information storage unit 23.

[0049] In FIG. 9, on the tab 85 of the reception list, as the attribute information of outpatients, the ID information 88 and the name information 89 are displayed, and as the reception information of outpatients, the arrival order information 86, the arrival date and time information (reception time information) 87, the department information 90, the doctor information 91, the new patient information 92, the consultation status information 93, and the past arrival date and time information 94 are displayed. Here, the department information 90 is information regarding the department where the outpatient undergoes consultation, the doctor information 91 is the name of the doctor in charge of the outpatient's examination, the new patient information 92 is information indicating whether the outpatient is a new patient, and the consultation status information 93 is information indicating which of the situations of "waiting for consultation", "under examination", "under consultation", "waiting for accounting", or "accounting completed" the outpatient is in.

[0050] In the "Examine Patients" tab 95, the second application 25 has a function of searching and sorting the attribute information and reception information of outpatients displayed in the reception list based on the attribute information and medical visit information of outpatients.

[0051] When the "Patient Search" icon 96 is specified (e.g., clicked) (S18), a search screen for inputting name information and ID information as search keys is opened. By the second control unit 11-2, the second application 25 searches the second medical data 19 stored in the storage unit 12 based on the input attribute information of outpatients, etc., and obtains the corresponding attribute information 60 (name information 64, ID information 65, insurance information 66, age information 67, gender information 68, and date of birth information 69 of outpatients) (S19, CL17), and displays all or part of it on the reception screen 25-1. This is the function of the second application 25 to search and obtain the attribute information of outpatients from the second medical data 19. When the second application 25 selects an outpatient from the search results, it transitions from the search screen to the hospital visit setting screen 25-3.

[0052] When the "Add New Patient's Hospital Visit" icon 97 is specified (e.g., clicked) (S18), a new patient input screen 25-2 for inputting the attribute information and reception information of a new patient (newcomer) who newly visits the medical institution as the second information is opened. FIG. 10 is a diagram showing an example (input of attribute information of a new patient) of the second application activated in the reception operation. As shown in FIG. 10, the new patient input screen (attribute information input screen) 25-2 of the second application 25 is opened. In the new patient input screen 25-2 of the second application 25, a temporary patient number as ID information, name information of the new patient, gender information, and date of birth information are input (S25, CL18). The temporary patient number is automatically assigned.

[0053] When the icon 101 of "Register and Set Appointment" is specified (e.g., clicked) (S18), the attribute information (second information) of the new patient obtained and / or input on the new patient input screen 25-2 is stored in the second information storage unit 23 (step S25, operation CL19), and the screen transitions from the new patient input screen 25-2 to the appointment setting screen 25-3. Also, by the second control unit 11-2, the second application 25 displays all or part of the attribute information (second information) of the new patient input on the new patient input screen 25-2 on the reception screen 25-1.

[0054] FIG. 11 is a diagram showing an example (input of reception information) of the second application activated in the reception operation. FIG. 12 is a diagram showing an example (input of reception information) of a new insurance information column on the reception information input screen.

[0055] As shown in FIG. 11, the appointment setting screen (reception information input screen) 25-3 of the second application 25 opens. In the attribute information column 102, the attribute information of the outpatient selected from the search results of the second application 25 or the attribute information of the new patient input on the new patient input screen 25-2 is displayed. Also, the existing insurance tab 103 and the new insurance tab 113 are displayed. When the existing insurance tab 103 is specified (e.g., clicked), the insurance information 66 acquired by the second application 25 is displayed in the insurance information column 104. As shown in FIG. 12, when the new insurance tab 113 is specified (e.g., clicked) (S18), insurance information is input into the insurance classification column 114 (S25, CL18).

[0056] Also, when transitioning to the appointment setting screen (reception information input screen) 25-3 (S18), the second control unit 11-2 obtains, by the second application 25, the reception information 61 (reservation date and time information 71, appointment date and time information 72, number of visits information 73, time slot information 74, department information 75, doctor information 76, and consultation status information 77) from the second medical data 19 stored in the storage unit 12 based on the input attribute information of the outpatient, etc. (S19, CL17), and displays all or part of it on the appointment setting screen 25-3.

[0057] When changing the received information obtained or newly inputting received information, visit frequency information is input into the visit frequency column 106, time classification information is input into the time classification column 107, department information is input into the department column 108, doctor information is input into the doctor column 109, reception comment information is input into the reception comment column 110, and consultation status information is input into the consultation status column 111 (S25, CL18).

[0058] When the "Visit Registration" icon 112 is specified (e.g., clicked) (S18), the received information (second information) obtained and / or input on the visit setting screen 25-3 is stored in the second information storage unit 23 (step S25, operation CL19). Also, by the second control unit 11-2, the second application 25 displays all or part of the received information 61 obtained on the visit setting screen 25-3 and the input received information (second information) on the reception screen 25-1. In this way, the second application 25 has a function of inputting the attribute information of a new patient (newcomer) who newly visits a medical institution.

[0059] As shown in FIG. 9, the attribute information and received information obtained by the second application 25 from the second medical data 19 and the second information storage unit 23 are displayed on the reception screen 25-1.

[0060] Thereby, even when the client (medical data acquisition device) 3 cannot obtain the first medical data 8 from the server 2, it is possible to input and manage the attribute information of a new patient, etc., and it is possible to provide an electronic medical record system that can smoothly proceed with the reception work of outpatient patients (including new patients).

[0061] When a part of the attribute information and received information of the outpatient patient displayed on the reception screen 25-1 is specified (e.g., clicked with the cursor 99), the information screen 105 of the outpatient patient opens. The items of "Local Medical Record Input", "Prescription Printing", "Instruction Sheet Printing", "Visit Setting", and "Visit Deletion" are displayed on the information screen 105.

[0062] When "Local Chart Input" is specified (e.g., clicked) (S18), the second control unit 11-2 causes the second application 25 to obtain corresponding chart information 62 (chief complaint information 79, findings information 80, disease name information 81, examination information 82, treatment information 83, prescription information 84, and instruction information 78) from the second medical data 19 stored in the storage unit 12 based on the attribute information of outpatients, etc. (S19, CL17), and displays all or part of it on the local chart screen.

[0063] When "Prescription Printing" is specified (e.g., clicked) (S18), the obtained prescription information 84 is printed (S25, CL18). When "Instruction Sheet Printing" is specified (e.g., clicked) (S18), the obtained instruction information 78 is printed (S25, CL18). When "Hospital Visit Setting" is specified (e.g., clicked), the hospital visit setting screen (reception information input screen) 25-3 shown in FIGS. 11 and 12 is opened. When "Hospital Visit Deletion" is specified (e.g., clicked) (S18), the attribute information and reception information of the outpatient are deleted from the reception screen 25-1 (S25, CL18).

[0064] FIG. 13 is a diagram showing an example (input of chart information) of the second application activated in the medical treatment business. When "Local Chart Input" in FIG. 9 is specified (e.g., clicked) (S18), the medical treatment screen 25-4 shown in FIG. 13 is opened, and the second application 25, by the second control unit 11-2, obtains chart information 62 (chief complaint information 79, findings information 80, disease name information 81, examination information 82, treatment information 83, prescription information 84, and instruction information 78) from the second medical data 19 stored in the storage unit 12 based on the input attribute information of outpatients, etc. (S19, CL17), and displays all or part of it on the medical treatment screen (local chart screen) 25-4. However, in the case of a new patient, the chart information 62 is not obtained.

[0065] In this way, using the second application, a doctor in a medical institution can input, output, and view information regarding the second medical data 19 (chart information 62) as the second information on the client (medical data acquisition device) 3.

[0066] In the attribute information column 102, the attribute information of outpatients obtained from the second medical data 19 by the search function of the second application 25 or the attribute information of new patients input by the new patient information input function of the second application 25 is displayed. Also, in the reception information column 115, all or part of the reception information 61 obtained on the hospital visit setting screen 25-3 or the input reception information (second information) is displayed.

[0067] In the chief complaint and findings column 116, the medical record information 62 (chief complaint information 79, findings information 80, and disease name information 81) of the outpatients displayed in the attribute information column 102 is obtained from the second medical data 19 by the second application 25, and the obtained medical record information 62 is displayed. In the case of a new patient, the chief complaint and findings column 116 is blank.

[0068] In the medical treatment column 117, the medical record information 62 (examination information 82, treatment information 83, prescription information 84, and instruction information 78) of the outpatients displayed in the attribute information column 102 is obtained from the second medical data 19 by the second application 25, and the obtained medical record information 62 is displayed. In the case of a new patient, the medical treatment column 117 is blank.

[0069] When changing the obtained medical record information 62 or newly inputting medical record information, using the second application, a doctor at a medical institution inputs information regarding the second medical data 19 (medical record information 62) as the second information into the chief complaint and findings column 116 or the medical treatment column 117 (S25, CL18). These information are input and output by the input / output unit 15 (for example, a keyboard, etc.) and are displayed on a display device (not shown) such as a monitor by the display unit 17.

[0070] When the icon 123 of the "Treatment Set" is specified (e.g., clicked) (S18), a combination of treatment items (treatment set) created in advance is retrieved from the treatment information 83 (S19, CL17), and a treatment set is selected from a treatment set screen (not shown). The selected treatment set is input into the medical treatment act column 117 (S25, CL18). When the icon 124 of the "Prescription Input" is specified (e.g., clicked) (S18), the preset prescription items are retrieved from the prescription information 84 (S19, CL17), and prescription items are input from a prescription screen (not shown) (S25, CL18). The selected prescription items are reflected in the medical treatment act column 117. Thus, the second application 25 has a function (set acquisition function) of selecting and acquiring a set of pre-registered medical record information from the second medical data 19. In addition, as the set of medical record information, there are also combinations of inspection items (inspection sets) created in advance, etc.

[0071] When the icon 118 of "All Deletion" is specified (e.g., clicked) (S18), all the items in the medical treatment act column 117 are deleted (S25, CL18). When the icon 119 of "Row Deletion" is specified (e.g., clicked) (S18), the specified item in the medical treatment act column 117 is deleted (S25, CL18). When the icon 120 of "Insert Above" is specified (e.g., clicked) (S18), a new item can be input above the specified item in the medical treatment act column 117 (S25, CL18). When the icon 121 of "Insert Below" is specified (e.g., clicked) (S18), a new item can be input below the specified item in the medical treatment act column 117 (S25, CL18).

[0072] When the icon 122 of "Local Save" is specified (e.g., clicked) (S18), the medical record information (second information) acquired and / or input on the medical treatment screen 25-4 is stored in the second information storage unit 23 (step S25, operation CL19). In addition, the second information stored in the second information storage unit 23 is associated with the time data 20, and the access time, acquisition time, storage time, and update time of the second information by the second application 25 are recorded.

[0073] Thus, even when communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible and the client (medical data acquisition device) 3 cannot obtain the first medical data 8 from the server 2, the second application 25 can input the second information and store it in the input information storage unit 13 (second information storage unit 23), and an electronic medical record system that can smoothly proceed with the reception and examination operations for outpatients can be provided.

[0074] Next, a process of reflecting the second information input by the second control unit 11-2 in the first application 24 will be described. FIG. 14 is a flowchart showing an example of a process in which the first control unit 11-1 cannot obtain the first medical data 8 from the server 2 immediately after starting the first application 24, the second control unit 11-2 starts the second application 25, obtains the second medical data 19, inputs the second information, and then the first control unit 11-1 or the second control unit 11-2 reflects the second information in the first application 24. FIG. 15 is a sequence diagram showing an example of the operations of the server 2 and the client (medical data acquisition device) 3 in this process. Since steps S12 to S25 in FIG. 14 are the same as those in FIG. 7, the description thereof is omitted. Also, since operations CL11 to CL19 in FIG. 15 are the same as those in FIG. 8, the description thereof is omitted.

[0075] In step S26, the control unit 11 (the first control unit 11-1 or the second control unit 11-2) determines whether to reflect the second information stored in the second information storage unit 23 by the second application 25 on the screen of the first application 24. If it is determined to reflect, in step S27, the first control unit 11-1 acquires the second information from the second information storage unit 23, reflects (displays) the second information at the corresponding location on the screen of the first application 24 (CL20), and stores the second information as the first information in the first information storage unit 22 (CL21). For example, when an icon (not shown) of "reflect second information" displayed on the screen of the first application 24 or the second application 25 is specified (e.g., clicked) (step S26), the first control unit 11-1 acquires the second information stored in the second information storage unit 23 and reflects it on the first application 24 as the first information (CL20).

[0076] FIG. 16 is a diagram showing that the second information is reflected at the corresponding location on the screen of the first application 24. As shown in FIG. 16, the medical record information displayed on the medical treatment screen (local medical record input screen) 25-4 of the second application 25 and stored in the second information storage unit 23 is reflected as the first information on the medical treatment screen (cloud medical record input screen) 24-4 of the first application 24. In FIG. 16, the medical record information in the chief complaint and findings column 116 of the medical treatment screen 25-4 of the second application 25 is reflected as the medical record information in the chief complaint and findings column 216 of the medical treatment screen 24-4 of the first application 24. Also, the medical record information in the medical treatment act column 117 of the medical treatment screen 25-4 of the second application 25 is reflected as the medical record information in the medical treatment act column 217 of the medical treatment screen 24-4 of the first application 24.

[0077] Next, in step S28, the transmission / reception unit 18 connects to the transmission / reception unit 7 so as to be able to communicate with the server 2 via the network 1. When communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible and the client (medical data acquisition device) 3 cannot acquire the first medical data 8 from the server 2, in step S17, the control unit 11 (second control unit 11-2) starts (for example, logs in) the second application (local application) 25 or maintains the start (for example, login) of the second application 25 that is already started.

[0078] When communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible and the client (medical data acquisition device) 3 can acquire the first medical data 8 from the server 2, in step S29, the first control unit 11-1 transmits the first information stored in the first information storage unit 22 to the server 2 by the first application 25. The first control unit 11-1 executes a transmission command, and the first application 25 transmits the first information from the first information storage unit 22 to the server 2 via the network 1. The transmitted first information is received by the transmission / reception unit 7, and the control unit 5 executes an update command and updates the first medical data 8 based on the first information (SV6).

[0079] In this way, the second information input by the second application 25 is reflected as the first information in the first application 24, and when communication between the server 2 and the client (medical data acquisition device) 3 is restored, the first medical data 8 can be updated by the first application 24, and an electronic medical record system that can smoothly proceed with the reception work and examination work for outpatients can be provided. force As described above, the embodiments according to the present invention have been described, but the present invention is not limited thereto, and modifications and variations are possible within the scope described in the claims.

[0080]

[0081] ​In the above, the second information input by the second application 25 was reflected as the first information in the first application 24. However, the first information input by the first application 24 may be reflected as the second information in the second application 25. force In the above, the second information input by the second application 25 was reflected as the first information in the first application 24. However, the first information input by the first application 24 may be reflected as the second information in the second application 25. force In the above, the second information input by the second application 25 was reflected as the first information in the first application 24. However, the first information input by the first application 24 may be reflected as the second information in the second application 25.

[0082] A process of reflecting the first information input by the first control unit 11-1 in the second application 25 will be described. FIG. 17 is a flowchart showing an example of a process in which the first control unit 11-1 starts the first application 24, and when the first medical data 8 cannot be obtained from the server 2 during or after inputting the first information, the second control unit 11-2 obtains the first information when the second application 25 is started and reflects the first information in the second application 25. FIG. 18 is a sequence diagram showing an example of the operations of the server 2 and the client (medical data acquisition device) 3 in this process.

[0083] The first control unit 11-1 inputs first information regarding the first medical data 8, and when the first medical data 8 cannot be obtained from the server 2 via the network 1, reflects the first information in the second application 25.

[0084] In step S12, the control unit 11 (the first control unit 11-1) starts the first application 24 (for example, logs in). By inputting using an input device (not shown) by the reception staff or the doctor, based on the start command input by the input / output unit 15, the control unit 11 (the first control unit 11-1) executes the start command of the first application 24 (CL11).

[0085] In step S13, the transceiver unit 18 is connected to the transceiver unit 7 so as to be able to communicate with the server 2 via the network 1. In step S14, the first control unit 11-1 acquires the first medical data 8 stored in the storage unit 8 of the server 2 via the transceiver units 7 and 18 by the first application 24. When an icon or the like for acquiring the first medical data 8 is clicked on the operation screen of the first application 24, the first application 24 executes an acquisition command for the first medical data 8 and transmits transmission request information to the server 2. The server 2 that has received the transmission request information transmits the requested first medical data 8 to the client (medical data acquisition device) 3 (SV7). The first control unit 11-1 acquires the first medical data 8 by the first application 24 (CL12).

[0086] For example, when the "patient search" icon of the first application 24 is specified (e.g., clicked), a search screen for inputting name information and ID information as search keys is opened, and the first application 24 searches the first medical data 8 stored in the storage unit 4 based on the input outpatient attribute information and the like by the first control unit 11-1, and obtains the corresponding attribute information 30 (outpatient name information 34, ID information 35, insurance information 36, age information 37, gender information 38, date of birth information 39, and other attribute information 40), and displays all or part of it on the display unit 17. This is a function in which the first application 24 searches and acquires outpatient attribute information from the first medical data 8.

[0087] In addition, the first control unit 11-1 acquires the reception information 31 (reservation date and time information 41, hospital visit date and time information 42, number of hospital visits information 43, time slot information 44, department information 45, doctor information 46, consultation status information 47, and other reception information 48) from the first medical data 8 stored in the storage unit 4 based on the input outpatient attribute information and the like by the first application 24, and displays all or part of it on the display unit 17.

[0088] Further, the first control unit 11-1, based on the attribute information of outpatients, etc. by the first application 24, acquires the corresponding medical record information 32 (chief complaint information 49, findings information 50, disease name information 51, examination information 52, treatment information 53, prescription information 54, instruction information 56, and other medical record information 55) and medical images 33 from the first medical data 8 stored in the storage unit 4, and displays all or part of them on the display unit 17.

[0089] Also, the first control unit 11-1 has a function of selecting and acquiring a set of pre-registered medical record information from the first medical data 8 by the first application 24.

[0090] In step S15, when a reception staff or a doctor of a medical institution inputs first information regarding the first medical data 8, the first application 24 inputs the first information by the input / output unit 15, and the first application 24 transmits the first information to the server 2 via the network 1 by the transmission / reception unit 18 (CL13). For example, as the first information regarding the first medical data 8, the first application 24 inputs the attribute information of outpatients of a medical institution, reception information regarding the reception work of outpatients, medical record information of outpatients, and medical images of outpatients. Also, the first control unit 11-1 has a function of inputting the attribute information of a new patient (newcomer) newly visiting a medical institution by the first application 24.

[0091] The first information transmitted to the server 2 is received by the transmission / reception unit 7. The first medical data 8 is updated based on the received first information (SV8). This update time is recorded in the time data 9.

[0092] The first information is input / output by the input / output unit 15, displayed on a display device (not shown) such as a monitor by the display unit 17, and stored in the first information storage unit 22 (CL14). Also, the first information stored in the first information storage unit 22 is associated with the time data 20, and the access time, acquisition time, storage time, and update time of the first information by the first application 24 are recorded.

[0093] Next, in step S16, communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible, and the client (medical data acquisition device) 3 cannot acquire the first medical data 8 from the server 2. In step S17, the control unit 11 (the second control unit 11-2) starts (for example, logs in) the second application (local application) 25 (CL15).

[0094] Next, in step S20, the control unit 11 (the first control unit 11-1 or the second control unit 11-2) determines whether to reflect the first information stored in the first information storage unit 22 on the screen of the second application 25 by the first application 24. If it is determined to reflect, in step S21, the second control unit 11-2 acquires the first information from the first information storage unit 22 and reflects (displays) the first information at the corresponding location on the screen of the second application 25 (CL16), and stores the first information as the second information in the second information storage unit 23 (CL22). For example, when an icon (not shown) of "reflect first information" displayed on the screen of the first application 24 or the second application 25 is specified (for example, clicked) (step S20), the second control unit 11-2 acquires the first information stored in the first information storage unit 22 and reflects it on the second application 25 as the second information (CL22).

[0095] FIG. 19 is a diagram showing that the first information is reflected in the corresponding part of the screen of the second application 25. As shown in FIG. 19, the reception information displayed on the reception screen 24-1 of the first application 24 and stored in the first information storage unit 22 is reflected as the first information on the reception screen 25-1 of the second application 25. In FIG. 19, the reception information of the arrival order information 286, arrival date and time information (reception time information) 287, medical department information 290, doctor information 291, new patient information 292, consultation status information 293, and past arrival date and time information 294 on the reception screen 24-1 of the first application 24 is reflected as the reception information of the arrival order information 86, arrival date and time information (reception time information) 87, medical department information 90, doctor information 91, new patient information 92, consultation status information 93, and past arrival date and time information 94 on the consultation screen 25-1 of the second application 25.

[0096] Steps S18, S19, and S25 in FIG. 17 are the same as those in FIG. 14, so the description is omitted. Also, the operations from operation CL17 to operation CL19 in FIG. 18 are the same as those in FIG. 15, so the description is omitted.

[0097] In this way, even when communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible and the client (medical data acquisition device) 3 cannot acquire the first medical data 8 from the server 2, the first information input by the first application 24 can be reflected as the second information in the second application 25, and the second application 25 can add and / or delete the second information and store it in the input information storage unit 13 (the second information storage unit 23), and an electronic medical record system that can smoothly proceed with the reception work and examination work of outpatients can be provided. force rected second information, and the second application 25 can add and / or delete the second information and store it in the input information storage unit 13 (the second information storage unit 23). p An electronic medical record system that can smoothly proceed with the reception work and examination work of outpatients can be provided.

[0098] Further, in the above-described embodiment, regardless of whether or not the second application 25 is started, the first control unit 11-1 obtains the difference from the server 2 as the difference data 10 by the first application 24 and updates the second medical data 19. However, the second control unit 11-2 may determine whether or not to update the second medical data 19 by the second application 25.

[0099] FIG. 20 is a flowchart showing an example of a process in which the second control unit 11-2 determines whether or not to update the second medical data 19 by the second application 25. FIG. 21 is a sequence diagram showing an example of the operations of the server 2 and the client (medical data acquisition device) 3 in these processes. Since the operations from operation SV1 to operation SV4 and the operations from operation CL1 to operation CL4 in FIG. 21 are the same as those in FIG. 6, the description thereof is omitted. Further, since the processes corresponding to the operations from operation SV1 to operation SV4 and the operations from operation CL1 to operation CL4 in FIG. 21 are the same as those in FIGS. 3 and 4, the drawings are omitted.

[0100] As shown in FIG. 20, in step S99, without the first application 24 transmitting the transmission request information of the difference data 10 to the server 2, the difference data acquisition unit 14 acquires the difference data 10 (CL88).

[0101] Steps S12, S16, and S17 in FIG. 20 are the same as those in FIG. 7, so the description thereof is omitted. Operations SV11 and SV15 in FIG. 21 are the same as those in FIG. 8, so the description thereof is omitted.

[0102] In step S30, the second control unit 11-2 detects that the first application 24 has acquired the difference data 10 (CL24). When the acquisition of the difference data 10 is detected, in step S31, the second control unit 11-2 selects whether or not to update the second medical data 19 based on the difference data 10. When the update of the second medical data 19 is selected, in step S32, the storage unit 12 updates the second medical data 19 based on the difference data 10 (CL25).

[0103] For example, on the operation screen of the second application 25, when the acquisition of the differential data 10 is detected, an icon or the like for updating the second medical data 19 blinks. When an icon or the like for updating the second medical data 19 is clicked, the update of the second medical data 19 is selected, and the storage unit 12 updates the second medical data 19 based on the differential data 10. Note that the storage unit 12 may update the second medical data 19 based on a part of the differential data 10 selected from the acquired differential data 10. In this case, a part of the differential data 10 is selected by the first application 24 or the second application 25.

[0104] Further, a medical data acquisition system 100 including the server 2 as described above and a client (medical data acquisition device) 3 capable of communicating with the server 2 via the network 1 is also included in the present invention. In the medical data acquisition system 100, the client (medical data acquisition device) 3 includes a first control unit 11-1 that controls a first application 25 for acquiring the first medical data 8 stored in the server 2, a storage unit 12 that stores the first medical data 8 at the first time point as the second medical data 19, and a second control unit 11-2 that controls a second application 25 for acquiring the second medical data 19 stored in the storage unit 12. The first control unit 11-1 acquires, from the server 2, a difference as the differential data 10 when there is a difference between the first medical data 8 at the second time point after the first time point and the first medical data 8 at the first time point. The storage unit 12 can update the second medical data 19 based on the differential data 10. A medical data acquisition system characterized by this is also included in the present invention.

[0105] Further, the medical data acquisition system 100 may include a plurality of clients (medical data acquisition devices) 3. FIG. 22 is a block diagram showing an example of the system configuration of a medical data acquisition system including a plurality of clients (medical data acquisition devices) 3-1 and 3-2.

[0106] In this case, the storage units 12 of each of the plurality of clients (medical data acquisition devices) 3-1 and 3-2 share or synchronize and store the second medical data 19. Also, each of the plurality of clients (medical data acquisition devices) 3-1 and 3-2 inputs information (second information) regarding the second medical data 19, and shares or synchronizes the information (second information) with other clients (medical data acquisition devices) 3 and stores it in the second information storage unit 23.

[0107] In this way, even when communication between the server 2 and the client (medical data acquisition device) 3 becomes impossible and the client (medical data acquisition device) 3 cannot acquire the first medical data 8 from the server 2, the second medical data 19, the first information, and the second information can be shared among the plurality of clients (medical data acquisition devices) 3, and an electronic medical record system can be provided that can smoothly proceed with the reception work and examination work for outpatients.

[0108] Also, a medical data acquisition method for communicating with the server 2 via the network 1 as described above is also included in the present invention. This medical data acquisition method includes a step of acquiring the first medical data 8 stored in the server 2, a step of storing the first medical data 8 at the first time point as the second medical data 19, a step of acquiring the second medical data 19 stored in the storage unit 12, and a step of acquiring, from the server 2, as difference data 10, a difference if there is a difference between the first medical data 8 at the second time point after the first time point and the first medical data 8 at the first time point, and a step of updating the second medical data 19 based on the difference data 10.

[0109] Also included in the present invention is a medical data acquisition program executed on a computer capable of communicating with a server 2 via the network 1 as described above. This medical data acquisition program causes the computer to execute instructions to acquire the first medical data 8 stored in the server 2, store the first medical data 8 at the first point in time as the second medical data 19, acquire the second medical data 19 stored in the storage unit 12, and, if there is a difference between the first medical data 8 at the second point in time after the first point in time and the first medical data 8 at the first point in time, acquire the difference from the server 2 as the difference data 10, and update the second medical data 19 based on the difference data 10.

Industrial Applicability

[0110] The present invention is useful as a medical data acquisition system capable of acquiring medical data even when communication with a server is not possible.

Explanation of Signs

[0111] 1…Network 2…Server 3…Client (Medical Data Acquisition Device) 6…Difference Data Generation Unit 8…First Medical Data 10…Difference Data 14…Difference Data Acquisition Unit 19…Second Medical Data 24…Second Application 25…First Application 30, 60…Attribute Information 31, 61…Reception Information 32, 62…Medical Record Information 100…Medical Data Acquisition System

Claims

1. A medical data acquisition device used in an electronic medical record system for inputting and outputting medical record information as medical data, capable of communicating with a server via a network, a first control unit that acquires first medical data stored in the server via the network and controls a first application that displays first information regarding the medical data on a display device; a storage unit that stores the first medical data at a first point in time as second medical data; a second control unit that acquires the second medical data stored in the storage unit by reading it out and controls a second application that displays second information regarding the medical data on the display device; an input information storage unit that stores the first information and the second information; comprising: when there is a difference between the first medical data at a second point in time after the first point in time and the first medical data at the first point in time, the first control unit acquires the difference as difference data from the server by the first application; the storage unit is capable of updating the second medical data based on the difference data; when the first control unit is unable to acquire the first medical data from the server immediately after starting the first application, the second control unit starts the second application, inputs the second information into the screen of the second application, at least one of the first control unit and the second control unit stores the second information in the input information storage unit by the second application, the first control unit inputs the second information stored in the input information storage unit to a corresponding location on the screen of the first application, and stores the second information as the first information in the input information storage unit. A medical data acquisition device characterized by this.

2. A medical data acquisition device used in an electronic medical record system for inputting and outputting medical record information as medical data, capable of communicating with a server via a network, a first control unit that acquires first medical data stored in the server via the network and controls a first application that displays first information regarding the medical data on a display device; a storage unit that stores the first medical data at a first point in time as second medical data; A second control unit that acquires, by reading out second medical data stored in the storage unit, and controls a second application that displays second information regarding the medical data on the display device; An input information storage unit that stores the first information and the second information; Comprising: When there is a difference between the first medical data at a second time point after the first time point and the first medical data at the first time point, the first control unit acquires the difference from the server as difference data by the first application; The storage unit can update the second medical data based on the difference data; When the first control unit cannot acquire the first medical data from the server immediately after starting the first application; A medical data acquisition device, characterized in that the second control unit starts the second application, inputs the first information at a corresponding position on the screen of the second application, and stores the first information as the second information in the input information storage unit.

3. The second control unit starts the second application when it cannot acquire the first medical data from the server via the network, and shares or synchronizes and stores the second medical data with another medical data acquisition device via the network. The medical data acquisition device according to claim 1 or claim 2.

4. The second medical data is a part of the medical data selected from the first medical data, and is at least one of attribute information of outpatients in a medical institution, reception information regarding the reception work of the outpatients, and medical record information of the outpatients. The medical data acquisition device according to any one of claims 1 to 3.

5. The difference data is generated by the server at a predetermined time after the second time point. The medical data acquisition device according to any one of claims 1 to 4.

6. The first control unit acquires the difference data when the first application ends after the second time point. The medical data acquisition device according to any one of claims 1 to 5.

7. The second control unit is characterized in that, as second information regarding the second medical data, it inputs at least one of attribute information of outpatients of a medical institution, reception information regarding the reception work of the outpatients, and medical record information of the outpatients. The medical data acquisition device according to any one of claims 1 to 6.

8. The second control unit is capable of executing at least one of a function of inputting the attribute information of a new patient newly visiting the medical institution, a function of retrieving and obtaining the attribute information of the outpatient from the second medical data, a function of retrieving and obtaining the past medical record information of the outpatient from the second medical data, and a function of selecting and obtaining a set of the pre-registered medical record information from the second medical data. The medical data acquisition device according to claim 7.

9. The first control unit is characterized in that it transmits the first information to the server via the network. The medical data acquisition device according to any one of claims 1 to 8.

10. A medical data acquisition system comprising a server used in an electronic medical record system for inputting and outputting medical record information as medical data, and a client capable of communicating with the server via a network, wherein the client a first control unit that acquires the first medical data stored in the server via the network and controls a first application that displays first information regarding the medical data on a display device; a storage unit that stores the first medical data at a first point in time as second medical data; a second control unit that acquires the second medical data stored in the storage unit by reading it out and controls a second application that displays second information regarding the medical data on the display device; an input information storage unit that stores the first information and the second information; and is provided with when there is a difference between the first medical data at a second point in time after the first point in time and the first medical data at the first point in time, the first control unit acquires the difference from the server as difference data, the storage unit is capable of updating the second medical data based on the difference data, when the first control unit is unable to acquire the first medical data from the server immediately after starting the first application, The second control unit starts the second application, inputs the second information to a corresponding location on the screen of the second application, the first control unit stores the second information in the input information storage unit by the second application, the first control unit inputs the second information stored in the input information storage unit to a corresponding location on the screen of the first application, and stores the second information as the first information in the input information storage unit. A medical data acquisition system characterized by this.

11. A medical data acquisition system including a server used in an electronic medical record system for inputting and outputting medical record information as medical data, and a client capable of communicating with the server via a network, the client is a first control unit that acquires the first medical data stored in the server via the network and controls a first application that displays first information regarding the medical data on a display device; a storage unit that stores the first medical data at a first point in time as second medical data; a second control unit that acquires the second medical data stored in the storage unit by reading it out, and controls a second application that displays second information regarding the medical data on the display device; an input information storage unit that stores the first information and the second information; and is provided with when there is a difference between the first medical data at a second point in time after the first point in time and the first medical data at the first point in time, the first control unit acquires the difference from the server as difference data, the storage unit can update the second medical data based on the difference data, when the first control unit cannot acquire the first medical data from the server immediately after starting the first application, the second control unit starts the second application, inputs the first information to a corresponding location on the screen of the second application, and stores the first information as the second information in the input information storage unit. A medical data acquisition system characterized by this.

12. The medical data acquisition system includes a plurality of clients, The medical data acquisition system according to claim 10 or claim 11, wherein each of the storage units of the plurality of clients stores the second medical data by sharing or synchronizing it.

13. The medical data acquisition system includes a plurality of the clients, The medical data acquisition system according to any one of claims 10 to 12, wherein each of the plurality of clients inputs information regarding the second medical data and stores the information by sharing or synchronizing it with other clients.

14. A medical data acquisition method in which a computer used in an electronic medical record system including a processor and a storage unit and inputting and outputting medical record information as medical data communicates with a server via a network, wherein the processor acquires, by a first application, first medical data stored in the server via the network and displays first information regarding the medical data on a display device; stores the first medical data at the first time point as second medical data; acquires, by a second application, the second medical data stored in the storage unit by reading it out and displays second information regarding the medical data on the display device; stores the first information and the second information in an input information storage unit; when there is a difference between the first medical data at a second time point after the first time point and the first medical data at the first time point, acquiring the difference from the server as difference data; updating the second medical data based on the difference data; when the first medical data cannot be acquired from the server immediately after the first application is started, starting the second application and displaying the second information on the screen of the second application; storing the second information in the input information storage unit by the second application; inputting the second information stored in the input information storage unit to a corresponding location on the screen of the first application and storing the second information as the first information in the input information storage unit; A medical data acquisition method characterized by comprising the above steps.

15. A medical data acquisition method in which a computer including a processor and a storage unit and used in an electronic medical record system for inputting and outputting medical record information as medical data communicates with a server via a network, wherein the processor acquires, via the network, first medical data stored in the server by a first application, and displays first information regarding the medical data on a display device; stores the first medical data at a first point in time as second medical data; acquires, by reading out the second medical data stored in the storage unit by a second application, and displays second information regarding the medical data on the display device; stores the first information and the second information in an input information storage unit; when there is a difference between the first medical data at a second point in time after the first point in time and the first medical data at the first point in time, acquires the difference from the server as difference data; updates the second medical data based on the difference data; when, immediately after starting the first application, it becomes impossible to acquire the first medical data from the server, starts the second application, inputs the first information at a corresponding location on the screen of the second application, and stores the first information in the input information storage unit as the second information; A medical data acquisition method characterized by comprising the above steps.

16. A medical data acquisition program executed by a computer capable of communicating with a server used in an electronic medical record system including a processor and a storage unit and inputting and outputting medical record information as medical data, wherein the computer is instructed to acquire, via a network, first medical data stored in the server by a first application, and display first information regarding the medical data on a display device; to store the first medical data at a first point in time as second medical data; to acquire, by reading out the second medical data stored in the storage unit by a second application, and display second information regarding the medical data on the display device; to store the first information and the second information in an input information storage unit; If there is a difference between the first medical data at a second time point after the first time point and the first medical data at the first time point, an instruction to obtain the difference as difference data from the server, An instruction to update the second medical data based on the difference data, If, immediately after starting the first application, it becomes impossible to obtain the first medical data from the server, An instruction to start the second application and display the second information on the screen of the second application, An instruction to store the second information in the input information storage unit by the second application, An instruction to input the second information stored in the input information storage unit at a corresponding location on the screen of the first application, and store the second information as the first information in the input information storage unit, A medical data acquisition program characterized by causing the above to be executed. [

17. ] A medical data acquisition program executed by a computer capable of communicating with a server used in an electronic medical record system that includes a processor and a storage unit and inputs and outputs medical record information as medical data, To the computer, An instruction to obtain the first medical data stored in the server via a network by a first application and display first information regarding the medical data on a display device, An instruction to store the first medical data at the first time point as second medical data, An instruction to obtain, by reading the second medical data stored in the storage unit by a second application, and display second information regarding the medical data on the display device, An instruction to store the first information and the second information in an input information storage unit, If there is a difference between the first medical data at a second time point after the first time point and the first medical data at the first time point, an instruction to obtain the difference as difference data from the server, An instruction to update the second medical data based on the difference data, If, immediately after starting the first application, it becomes impossible to obtain the first medical data from the server, An instruction to start the second application, input the first information at a corresponding location on the screen of the second application, and store the first information as the second information in the input information storage unit, A medical data acquisition program characterized by causing

Images