JP6971610B2 - Server, data update method, and electronic medical record system - Google Patents

Description

The present invention relates to a server, a data update method, and an electronic medical record system.

The electronic medical record system is a system that replaces a conventional paper medical record with an electronic medical record and manages it. Patent Document 1 discloses an electronic medical record system in which a server for managing an electronic medical record and a terminal for inputting and displaying the electronic medical record are connected via a network.

In addition, having a doctor or the like manually input all medical records is a heavy burden and is prone to input errors. Therefore, in Patent Document 2, the name of the disease, the name of the drug, etc. is prepared in advance as master data, and the doctor or the like is made to select the master data, thereby reducing the input burden of the electronic medical record and reducing the input error. doing.

Japanese Unexamined Patent Publication No. 2013-37586 Japanese Unexamined Patent Publication No. 2005-316868

Since doctors and the like need to input medical records within a limited time, low latency is required for operating electronic medical records on terminals. However, it is difficult to achieve low latency in the terminal by the conventional technique in which the terminal acquires the master data managed in the database of the server each time. In addition, the master data is the kind of data that is updated from time to time, and it is necessary to reliably convey the update to the terminal.

An object of the present invention is to provide a server device, a data update method, and an electronic medical record system that enable data update on the server side to be reliably transmitted to a terminal and low latency in the terminal.

The server according to one aspect of the present invention is a server that transmits data conforming to the request information received from the terminal to the terminal, and is a database and a cache in which at least a part of the data acquired from the database is stored. A memory unit and a control unit that acquires data matching the request information from the cache memory unit and generates response information corresponding to the request information are provided, and the request information is transmitted from the terminal. The control unit subtracts a predetermined time from the first confirmation time included in the request information transmitted from the terminal, including the first confirmation time which is the time when the server received the previous request information. calculating a subtraction after confirmation time, new data than the update time of data the subtraction after confirmation time is obtained from the cache memory unit, including Me in the response information, the predetermined time is updated in the database It is a longer time than the time until the data is reflected in the cache memory unit .

According to the present invention, it is possible to reliably transmit data updates on the server side to the terminal and enable low latency in the terminal.

It is a block diagram which shows the structural example of the electronic medical record system which concerns on this embodiment. It is a sequence chart which shows the process when "ALL" is set in the data query mode of a request message. It is a sequence chart which shows the process when "Time" is set in the data query mode of a request message. It is a sequence chart which shows the process when the ID of the master data is set in the request message. It is a sequence chart which shows the process of changing the data of a database. It is a figure which shows the hardware configuration of the computer which concerns on this invention.

Hereinafter, embodiments will be described with reference to the drawings. In the following embodiments, the components (including element steps and the like) are not necessarily essential except when explicitly stated and when it is clearly considered to be essential in principle.

FIG. 1 is a block diagram showing a configuration example of the electronic medical record system 1.

The electronic medical record system 1 includes a server 10 and at least one terminal 20. The server 10 and the terminal 20 are connected by a predetermined communication network, and bidirectional communication is possible.

The server 10 is a device for managing various data related to electronic medical records. The terminal 20 is a device for medical personnel such as doctors, nurses, pharmacists, and clerks to use electronic medical records. The terminal 20 is, for example, a PC, a tablet terminal, a smartphone, or the like.

<Configuration of server 10>
Next, the configuration of the server 10 will be described. The server 10 has a server control unit 100, a server-side cache unit 102, a DB (DataBase) control unit 104, and a DB 106 as functions.

The DB 106 holds a master related to electronic medical records, medical records, and the like. The DB 106 is built in a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), for example.

The latest master data related to the electronic medical record is cached in the server-side cache unit 102. The server-side cache unit 102 is built in a storage device such as a DRAM (Dynamic Random Access Memory), for example. The access speed of the storage device in which the server-side cache unit 102 is constructed is preferably higher than the access speed of the storage device in which the DB 106 is constructed.

The master regarding the electronic medical record contains information about items that can be selected when inputting to the electronic medical record. The master related to the electronic medical record includes, for example, a user master, a medical record article template master, an order master, a disease name master, an inspection request master, and an inspection result master.

The user master includes items that can be selected when inputting information about the examinee into the electronic medical record. For example, the user master includes items such as name, date of birth, gender, and blood type.

The medical record article template master includes items that can be selected when inputting information regarding medical records into an electronic medical record, such as vital information and an image of a schema.

The order master includes items that can be selected when inputting information on the prescription into the electronic medical record, for example, items such as a drug name and a sample name.

The disease name master includes items that can be selected when inputting information about the disease name into the electronic medical record, for example, items such as the disease name.

The inspection request master includes items that can be selected when inputting information about the inspection request into the electronic medical record, such as an inspection name and an inspection target.

The inspection result master includes items that can be selected when inputting information about the inspection result into the electronic medical record, such as an inspection name and an inspection classification.

The server control unit 100 controls the data in the DB 106 and the server-side cache unit 102. For example, when the master data in the DB 106 is updated, the server control unit 100 reflects the updated master data in the server-side cache unit 102. That is, the server control unit 100 ensures that the latest master data is held in the server-side cache unit 102.

Further, the server control unit 100 returns necessary data to the terminal 20 in response to a request from the terminal 20. For example, when the server control unit 100 receives the request message from the terminal 20, it acquires the master data matching the search query included in the request message from the server-side cache unit 102 and returns it to the terminal 20 as a response message. The server-side cache unit 102 has higher response performance than the DB 106, and the data stored in the server-side cache unit 102 may be in the form of a response message. Therefore, the server control unit 100 can return the response message to the terminal 20 in a shorter time than acquiring the master data from the DB 106.

<Configuration of terminal 20>
Next, the configuration of the terminal 20 will be described. The terminal 20 includes a module unit 202, an application unit 200, a cache control unit 204, and a terminal-side cache unit 206 as functions.

The module unit 202 is a program module including the common logic of the electronic medical record on the terminal 20 side. The module unit 202 is also called a library, a plug-in, or the like.

The application unit 200 is an application program for using an electronic medical record from the terminal 20 side. The application unit 200 is created by using the module unit 202. By separating the common logic of the electronic medical record as the module unit 202 in this way, it is possible to implement only the parts that differ depending on the type of the terminal 20 (for example, a PC or a tablet terminal 20) in the application unit 200. .. This makes it possible to implement an optimal electronic medical record application according to the type of the terminal 20 relatively easily.

The cache control unit 204 controls the terminal-side cache unit 206 in cooperation with the server control unit 100. For example, the cache control unit 204 acquires the latest master data from the server control unit 100 and stores it in the terminal side cache unit 206 to keep the master data of the terminal side cache unit 206 up to date. The exchange between the cache control unit 204 and the server control unit 100 may be performed using the WEB API published by the server 10.

<Structure of request message and response message>
Next, the configuration of the request message and the response message will be described.

The request message is a message for the cache control unit 204 to request data from the server control unit 100. The request message includes a data query mode and a confirmation time. The response message is a message for the server control unit 100 to return a response to the request message to the cache control unit 204. The response message includes the server query time and the data.

In the data query mode, a mode indicating what kind of data is requested can be set as follows.
-"ALL" that requests all data.
-"Time" that requests data updated after the confirmation time.

The server query time is the time when the server control unit 100 receives the request message from the cache control unit 204. The server query time is included in the response message, transmitted to the terminal 20, and stored in the terminal-side cache unit 206. The cache control unit 204 acquires the server query time from the terminal side cache unit 206, and sets the acquired server query time in the message request as the confirmation time.

FIG. 2 is a sequence chart showing processing when "ALL" is set in the data query mode of the request message.

The cache control unit 204 acquires the server query time from the terminal side cache unit 206 (ST100, ST102).

Next, the cache control unit 204 sets "ALL" in the data query mode and "Null" in the confirmation time to generate a request message and sends it to the server control unit 100 (ST104). If "NULL" is set for the confirmation time, all master data will be the query target.

The server control unit 100 receives the request message of ST104. Then, the server control unit 100 generates a server query time from the time when the request message is received (ST106).

Next, since the data query mode is "ALL", the server control unit 100 acquires all master data from the server-side cache unit 102 (ST108, ST110).

Next, the server control unit 100 generates a response message including the server query time generated in ST106 and all the master data acquired in ST110, and sends (replies) to the cache control unit 204 (ST112).

The cache control unit 204 receives the response message of ST112. Then, the cache control unit 204 stores the server query time and all the master data included in the received response message in the terminal side cache unit 206 (ST114, ST116). If the server query time and master data already exist in the terminal-side cache unit 206, the cache control unit 204 updates the server query time and all data in the terminal-side cache unit 206.

According to the process of FIG. 2, all the master data of the terminal-side cache unit 206 is up-to-date. This process is executed, for example, when the terminal 20 is started or when the application unit 200 is started.

FIG. 3 is a sequence chart showing processing when "Time" is set in the data query mode of the request message.

The cache control unit 204 acquires the server query time from the terminal side cache unit 206 (ST150, ST152).

Next, the cache control unit 204 generates a request message in which "Time" is set in the data query mode and the server query time acquired above is set as the confirmation time, and is transmitted to the server control unit 100 (ST154).

The server control unit 100 receives the request message of ST104. Then, the server control unit 100 generates a server query time from the time when the request message is received (ST156).

Next, since the data query mode is "Time", the server control unit 100 searches the server-side cache unit 102 for data that matches the query condition of "confirmation time-α <DB update time" (ST158, ST160). α is a predetermined time. Here, the reason why the predetermined time α is subtracted from the confirmation time is as follows.

If α is not subtracted and the server query generation time of ST156 is the time between the time when the data is updated in DB 106 and the time when the data is stored in the server-side cache unit 102, "latest update time> DB update time". , And the cache control unit 204 cannot acquire the update data. That is, by subtracting α, the occurrence of such a situation can be prevented. Therefore, the predetermined time α is longer than the longest time until the master data is updated in the DB 106 and stored in the server-side cache unit 102. The “confirmation time −α” may be referred to as the confirmation time after subtraction.

<When there is data that matches the query conditions>
First, a case where master data satisfying the query condition “confirmation time −α <DB update time” of ST158 exists in the server-side cache unit 102 will be described.

In this case, the master data of the terminal-side cache unit 206 is not the latest state. Therefore, the server control unit 100 generates a response message including the server query time generated in ST156, the flag value indicating that the update master data exists, and the update master data acquired in ST160, and the cache control unit 204. Send (reply) to (ST162).

The cache control unit 204 receives the response message of ST162. Then, the cache control unit 204 stores the server query time and the update master data included in the received response message in the terminal side cache unit 206 (ST164, ST166). That is, the server query time of the terminal-side cache unit 206 and the data stored in the terminal-side cache unit 206 that have been updated on the server 10 side are updated.

<When there is no data that matches the query conditions>
Next, a case where the master data satisfying the query condition “confirmation time −α <DB update time” of ST158 does not exist in the server-side cache unit 102 will be described.

In this case, the master data of the terminal-side cache unit 206 is in the latest state. Therefore, the server control unit 100 generates a response message including the server query time generated by ST156 and the flag value indicating that the update master data does not exist, and sends (replies) to the cache control unit 204 (ST162). ..

The cache control unit 204 receives the response message of ST162. Then, the cache control unit 204 stores the server query time included in the received response message in the terminal side cache unit 206 (ST164, ST166).

According to the process of FIG. 3, it is possible to prevent the possibility that the update of the master data in the DB 106 of the server 10 will not be reflected in the cache unit 206 on the terminal side due to the time lag until it is reflected in the cache unit 102 on the server side. can. That is, the data update on the server 10 side is surely transmitted to the terminal 20. The process of FIG. 3 may be executed at a predetermined cycle.

Further, according to the process of FIG. 3, the server 10 transmits only the updated master data to the terminal 20. As a result, the amount of communication between the server 10 and the terminal 20 is reduced, and the amount of update of the master data in the terminal 20 is also reduced, so that the operating speed of the entire electronic medical record system 1 is improved.

FIG. 4 is a sequence chart showing processing when an ID, which is an identifier of master data, is set in the request message.

The cache control unit 204 acquires the server query time from the terminal side cache unit 206 (ST200, ST202).

Next, the cache control unit 204 sets the ID of the master data to be requested as the ID of the server query time acquired above at the confirmation time, generates a request message, and transmits it to the server control unit 100 (ST204). ..

The server control unit 100 receives the request message of ST204. Then, the server control unit 100 generates a server query time from the time when the request message is received (ST206).

Next, the server control unit 100 searches the server-side cache unit 102 for master data that matches the ID set in the request message and that matches the "confirmation time-α <DB update time" (ST208). ). Then, the server control unit 100 acquires master data matching the search from the server-side cache unit 102 (ST210). Here, when a plurality of IDs are set, if even one of those IDs is updated, the server control unit 100 acquires the data of all the IDs.

Next, when the data matching the query conditions exists, the server control unit 100 includes the server query time generated in ST206, the flag value indicating that the update data exists, and the master data acquired in ST210. A response message is generated and transmitted (replied) to the cache control unit 204 (ST212). When the update data does not exist, the server control unit 100 generates a response message including the server query time generated by ST206 and the flag value indicating that the update data does not exist, as described above, and the cache control unit 204 generates a response message. Send to.

The cache control unit 204 receives the response message of ST212. Then, the cache control unit 204 stores the update master data included in the received response message in the terminal side cache unit 206 (ST214, ST216). That is, among the master data stored in the terminal-side cache unit 206, the master data updated on the server 10 side is updated.

In ST214, the cache control unit 204 does not update the server query time of the terminal side cache unit 206. This is because in the terminal-side cache unit 206, only the data corresponding to the ID is updated, so if the server query time is updated, there is a possibility that other data to be updated may not be updated. be.

According to the process of FIG. 4, only specific master data can be updated. For example, when a new drug arrives, only the prescription master can be updated. As a result, the amount of communication between the server 10 and the terminal 20 is reduced, and the amount of update of the master data in the terminal 20 is also reduced, so that the operating speed of the entire electronic medical record system 1 is improved.

FIG. 5 is a sequence chart showing a process of changing the data of the DB.

The cache control unit 204 generates a request message including update data on the terminal 20 side and transmits it to the server control unit 100 (ST300).

The server control unit 100 receives the request message of ST300 and extracts the update data. Then, the server control unit 100 transmits an update request for this update data to the DB control unit 104 (ST302).

The DB control unit 104 receives the update request of ST302 and extracts the update data. Then, the DB control unit 104 reflects (registers or updates) this update data in the DB 106 (ST304, ST306).

Next, the DB control unit 104 transmits (replies) a response to the update request (referred to as “update response”) to the server control unit 100 (ST308).

The server control unit 100 receives the update response of ST308. Then, the server control unit 100 reflects (registers or updates) the update data of ST 302 in the server-side cache unit 102 (ST310, ST312). As a result, the update data is reflected in both the DB 106 and the server-side cache unit 102.

Next, the server control unit 100 transmits a response message to the request message of ST300 to the cache control unit 204 (ST314).

The cache control unit 204 receives the response message of ST314. Then, the cache control unit 204 reflects (registers or updates) the update data of the ST300 in the terminal-side cache unit 206 (ST316, ST318). As a result, the updated data is also reflected in the cache unit 206 on the terminal side. In this case, the cache control unit 204 does not update the server query time of the terminal side cache unit 206.

According to the process of FIG. 5, since the update data by the terminal 20 is reflected in the DB 106 on the server 10 side and the cache unit 102 on the server side and then reflected in the cache unit 206 on the terminal side, it is between the server 10 and the terminal 20. It is possible to prevent inconsistencies in the updated data.

<Hardware configuration>
Although the embodiments according to the present invention have been described in detail with reference to the drawings, the functions of the server 10 and the terminal 20 described above can be realized by a computer program.

FIG. 6 is a diagram showing a hardware configuration of a computer that realizes the functions of each device by a program. The computer 1100 includes an input device 1101 such as a keyboard, a mouse, and a touch pad, an output device 1102 such as a display and a speaker, a CPU (Central Processing Unit) 1103, a ROM (Read Only Memory) 1104, and a RAM (Random Access Memory) 1105. A storage device 1106 such as a hard disk device or SSD (Solid State Drive), a reading device 1107 that reads information from a recording medium such as a DVD-ROM (Digital Versatile Disk Read Only Memory) or a USB (Universal Serial Bus) memory, and a network. A transmission / reception device 1108 for communication is provided, and each unit is connected by a bus 1109.

Then, the reading device 1107 reads the program from the recording medium on which the program for realizing the function of each of the above devices is recorded, and stores the program in the storage device 1106. Alternatively, the transmission / reception device 1108 communicates with the server device connected to the network, and stores the program downloaded from the server device for realizing the function of each device in the storage device 1106.

Then, the CPU 1103 copies the program stored in the storage device 1106 to the RAM 1105, and sequentially reads and executes the instructions included in the program from the RAM 1105, thereby realizing the functions of the respective devices.

The embodiments described above are examples for the purpose of explaining the present invention, and the scope of the present invention is not limited to the embodiments. Those skilled in the art can practice the invention in various other embodiments without departing from the gist of the invention.

The server, data update method, and electronic medical record system according to the present invention are suitable for use in a system or a computer that handles electronic medical records.

1 Electronic medical record system 10 Server 20 Terminal 100 Server control unit 102 Server side cache unit 104 DB control unit 106 DB
200 Application part 202 Module part 204 Cache control part 206 Terminal side cache part

Claims (4)

A server that sends data that matches the request information received from the terminal to the terminal.
Database and
A cache memory unit in which at least a part of the data acquired from the database is stored, and
A control unit that acquires data conforming to the request information from the cache memory unit and generates response information corresponding to the request information is provided.
The request information includes a first confirmation time which is a time when the server received the previous request information transmitted from the terminal.
The control unit calculates the confirmation time after subtraction by subtracting a predetermined time from the first confirmation time included in the request information transmitted from the terminal, and the data update time is newer than the confirmation time after subtraction. the data acquired from the cache memory unit, including Me in the response information,
The predetermined time is longer than the time until the data updated in the database is reflected in the cache memory unit.
server. The control unit includes the time when the request information transmitted from the terminal is received in the response information as the second confirmation time.
The server according to claim 1. It is a data update method in a system equipped with a terminal and a server.
The terminal includes a first cache memory unit in which data acquired from the server and a first confirmation time, which is the time when the server receives the first request information of the data, are stored.
The server includes a database and a second cache memory unit in which at least a part of data acquired from the database is stored.
The terminal transmits the second request information including the first confirmation time to the server.
The server
The second request information is received from the terminal, and the second request information is received.
A predetermined time is subtracted from the first confirmation time included in the second request information to calculate the confirmation time after subtraction.
Data whose update time is newer than the confirmation time after subtraction is acquired from the second cache memory unit.
Response information including the acquired data and the second confirmation time, which is the time when the second request information is received, is generated and transmitted to the terminal.
The terminal is
Upon receiving the response information,
With the data included in the response information, the data in the first cache memory unit is updated.
In the second confirmation time included in the response information, and updates the first check time in the first cache memory unit,
The predetermined time is longer than the time until the data updated in the database is reflected in the second cache memory unit.
Data update method. An electronic medical record system with terminals and servers
The terminal is a first cache memory in which a master data related to an electronic medical record acquired from the server and a first confirmation time, which is a time when the server receives the first request information of the master data, are stored. Equipped with a part
The server includes a database and a second cache memory unit in which at least a part of master data acquired from the database is stored.
The terminal transmits the second request information including the first confirmation time to the server.
The server
The second request information is received from the terminal, and the second request information is received.
A predetermined time is subtracted from the first confirmation time included in the second request information to calculate the confirmation time after subtraction.
The master data whose data update time is newer than the confirmation time after subtraction is acquired from the second cache memory unit.
Response information including the acquired data and the second confirmation time, which is the time when the second request information is received, is generated and transmitted to the terminal.
The terminal is
Upon receiving the response information,
With the master data included in the response information, the master data in the first cache memory unit is updated.
In the second confirmation time included in the response information, and updates the first check time in the first cache memory unit,
The predetermined time is longer than the time until the data updated in the database is reflected in the second cache memory unit.
Electronic medical record system.

Images