Server equipment, computer programs, and data management methods
The server device automates drug prescription application updates by determining necessary updates and providing location information, addressing user burden and computational load, thus improving convenience and security.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2026-04-08
AI Technical Summary
Existing drug prescription systems require users to manually check for application updates and locate update files, increasing user burden and computational load.
A server device communicates with a client device to determine if an application update is necessary based on version information, sending location information for the update file if needed, thereby automating the process and reducing user intervention.
This approach simplifies the update process, reduces user burden, and decreases computational load by automating version checking and update file location retrieval, enhancing user convenience and security.
Smart Images

Figure 2026060348000001_ABST
Abstract
Description
Technical Field
[0004] , , , , , , ,
[0005] , , , , ,
[0003] , , , , ,
[0001] The present disclosure relates to a server device capable of communicating with a client device on which a service related to a drug prescription is executed. The present disclosure also relates to a computer program executable by a processor mounted on the server device. The present disclosure also relates to a data management method executed by the server device and the client device.
Background Art
[0002] A dosing management system including a client device and a server device capable of data communication via a communication network is disclosed. Information related to a drug prescription for a patient is transmitted from the client terminal device to the server device. The server device stores the acquired information in a database.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] It is required to improve the convenience of users of a client device on which an application for providing a service related to a drug prescription is executed. <00A processor that determines whether an update to the application is necessary based on the version information, and if such an update is determined to be necessary, sends location information indicating the location of the update file to the client device. It is equipped with.
[0006] One possible embodiment provided by this disclosure is a computer program executable by a processor installed in a server device capable of communicating with a client device on which an application for providing drug prescription services is executed, By being executed, the server device will The client device receives version information that can identify the version of the aforementioned application. Based on the aforementioned version information, determine whether an update to the application is necessary. If it is determined that the update is necessary, location information indicating the location of the update file is sent to the client device.
[0007] One example of an embodiment that may be provided by this disclosure is an application management method performed by a client device on which an application for providing drug prescription services is executed and a server device located at a location separate from the client device, Version information that can identify the version of the aforementioned application is transmitted from the client device to the server device. The server device determines whether an update to the application is necessary based on the version information. When it is determined that the update is necessary, location information indicating the location of the update file is transmitted from the server device to the client device. The client device uses the location information to obtain the update file.
[0008] According to the configurations described in each of the above examples, the client device sends version information that identifies the application version, and the server device then checks whether the application needs to be updated and provides information indicating the location of the update file. Since the client device user does not need to check the application version or the location of the update file, the burden on the client device user can be reduced. In addition, since a series of processes are performed triggered by the transmission of version information inherently associated with the application, there is no need to associate certificate information, passwords, etc. with the application. This allows for simplification of the application and reduces the increase in the computational processing load on the client device. Therefore, the convenience of the user of the client device running the application that provides drug prescription services can be improved. [Brief explanation of the drawing]
[0009] [Figure 1] This illustrates the configuration of a data management system according to one embodiment. [Figure 2] Figure 1 illustrates the functional configuration of the client and server devices. [Figure 3] Figure 1 shows an example of the data management process performed by the data management system. [Figure 4] Figure 2 illustrates the update management information stored in the server device's storage. [Figure 5] Figure 1 shows another example of the data management method flow performed by the data management system. [Modes for carrying out the invention]
[0010] Examples of embodiments will be described in detail below with reference to the attached drawings. In each drawing referenced in the following description, the elements shown have been made recognizable as necessary. The scale is being changed.
[0011] As used in the present disclosure, the term "medical institution" means an institution where medical staff provide explanations about pharmaceuticals to patients. Examples of "medical institutions" include hospitals, clinics, dispensaries, pharmacies, drugstores, etc. Examples of "medical staff" include doctors, nurses, pharmacists, care managers, dietitians, etc.
[0012] FIG. 1 illustrates the configuration of a data management system 10 according to an exemplary embodiment. The data management system 10 includes a client device 11 and a server device 12.
[0013] In the client device 11, an application for providing services related to drug prescriptions to the user is executed. The "user" may include both medical staff and patients. Examples of "services related to drug prescriptions" include creation and management of electronic medical records, support for medication guidance, support for dispensing, follow-up of medication, remote medication guidance, provision of an electronic version of a medicine diary, support for the operation of medical institutions, inventory management of pharmaceuticals, etc.
[0014] There may be a plurality of client devices 11. The client device 11 may be a stationary device installed at a specific location, or a portable device that can be carried by the user.
[0015] The server device 12 is installed at a location remote from the client device 11. The client device 11 and the server device 12 are configured to perform two-way communication of data via a communication network 20.
[0016] As illustrated in FIG. 2, the client device 11 includes a communication interface 111. On the other hand, the server device 12 includes a communication interface 121. Each of the communication interface 111 and the communication interface 121 is a hardware interface configured to enable the above-described two-way data communication.
[0017] The client device 11 includes a user interface 112 and a processor 113. The user interface 112 is a hardware interface that mediates the exchange of information between the user and the processor 113 and receives a user's instruction to cause the client device 11 to execute a predetermined operation. The user interface 112 and the processor 113 may be mounted in a common housing or provided in a distributed manner in independent housings.
[0018] The predetermined operation executed by the client device 11 includes transmitting the version information VS to the server device 12. The version information VS is information that can identify the version of the above application executed in the client device 11.
[0019] The server device 12 includes a storage 122. The storage 122 is a storage device realized by a semiconductor memory, a hard disk device, a magnetic tape device, etc. In the storage 122, an update file UD for updating the above application to the latest version is stored. In addition, in the storage 122, the latest version information LV indicating the version number of the update file UD is stored.
[0020] Note that there may be a plurality of storages 122. The update file UD and the latest version information LV may be stored in different storage areas of the same storage or in a plurality of different storages.
[0021] The server device 12 includes a processor 123. The processor 123 is configured to be able to refer to the latest version information LV stored in the storage 122 as necessary.
[0022] While referring to FIG. 3, the flow of the data management method executed in the data management system 10 will be described in detail.
[0023] A user of client device 11 who wishes to check whether an application for providing drug prescription services needs to be updated enters a predetermined operation into the user interface 112. In response to this operation, the processor 113 reads the version information VS stored in storage (not shown) and transmits it to the server device 12 via the communication interface 111 (STEP 11).
[0024] The reading of version information VS and its transmission to the server device 12 may be performed automatically by the processor 113 at a timing specified in the application.
[0025] When the server device 12 receives version information VS via the communication interface 121, the processor 123 determines whether the application needs to be updated (STEP 21). Specifically, the latest version information LV stored in the storage 122 is compared with the version information VS received from the client device 11.
[0026] If the version indicated by the latest version information LV matches the version indicated by the version information VS, the processor 123 determines that an application update is not necessary (NO in STEP 21). In this case, the processor 123 sends notification information NT indicating that an application update is not necessary to the client device 11 via the communication interface 121.
[0027] When notification information NT is received by the communication interface 111 of the client device 11, the processor 113 causes the user interface 112 to provide information notifying that an application update is not required (STEP 12).
[0028] If the version indicated by the latest version information LV is newer than the version indicated by the version information VS, the processor 123 determines that an application update is necessary (YES in STEP 21). In this case, the processor 123 of the server device 12 generates location information LC indicating the location of the update file UD and sends it to the client device 11 via the communication interface 111 (STEP 22).
[0029] For example, the location of the update file UD can be identified by a URL corresponding to the storage area of storage 122 where the update file UD is stored. Alternatively, the location of the update file UD can be identified by a one-dimensional code, a two-dimensional code, or the like, containing information related to the storage area.
[0030] When the location information LC is received by the communication interface 111 of the client device 11, the processor 113 causes the user interface 112 to provide the location information LC along with information notifying that an update is necessary (STEP 13). Providing the location information LC may be used in lieu of notifying that an update is necessary.
[0031] The user of client device 11 accesses the location indicated by location information LC through the user interface 112 and performs an operation to request the download of the update file UD. In response to this operation, processor 113 sends a download request DL from communication interface 111 to server device 12 (STEP 14).
[0032] When a download request DL is received by the communication interface 121 of the server device 12, the processor 123 reads the update file UD from the storage 122 and sends it to the client device 11 via the communication interface 121 (STEP 23).
[0033] When the update file UD is received by the communication interface 111 of the client device 11, the user of the client device 11 performs an operation to update the application through the user interface 112 (STEP 15).
[0034] With the configuration described above, the client device 11 sends version information VS that identifies the application version, and the server device 12 then checks whether the application needs to be updated and provides information indicating the location of the update files. Since the user of the client device 11 does not need to check the application version or the location of the update files, the burden on the user of the client device 11 can be reduced. In addition, since a series of processes are performed triggered by the transmission of version information VS which is inherently associated with the application, there is no need to associate certificate information, passwords, etc. with the application. This allows for simplification of the application and reduces the increase in the computational processing load on the client device 11. Therefore, the convenience for the user of the client device 11 running the application that provides drug prescription services can be improved.
[0035] The location information LC transmitted from the server device 12 to the client device 11 may include signature information with an expiration date. This signature information is configured to be authenticated by the client device 11.
[0036] This configuration makes it possible to suppress the use of location information LC by unintended users, thereby enhancing the security of the data management system 10.
[0037] As illustrated in Figure 2, a predetermined operation performed by the client device 11 may include sending an identification information ID to the server device 12. The identification information ID is information that can identify at least one of the client device 11 and the user using the client device 11. Examples of identification information IDs include a client certificate assigned to the client device 11 or the user, and a terminal identifier assigned to the client device 11.
[0038] In this case, in order to allow bidirectional communication between the client device 11 and the server device 12, the identification information ID of the client device 11 is stored in the storage 122 in advance.
[0039] In addition, the update management information MG, illustrated in Figure 4, is stored in storage 122. The update management information MG associates an identification information ID that identifies the client device with the latest version information LV that identifies the latest version of the application that can be run on that client device. In this example, only a single application is shown, but multiple applications can be associated with a single client device in the update management information MG.
[0040] Figure 5 shows another example of the data management method flow executed in the data management system 10 configured as described above. Processing elements that are substantially the same as those explained with reference to Figure 3 are given the same reference numerals, and redundant explanations are omitted.
[0041] In this case, as illustrated in Figure 3, in response to a predetermined operation on the user interface 112 by the user of the client device 11, the processor 113 transmits identification information ID from the communication interface 111 to the server device 12 (STEP 16). The transmission of identification information ID may be performed prior to or simultaneously with the transmission of version information VS.
[0042] When the server device 12 receives the identification information ID via the communication interface 121, the processor 123 performs authentication processing for the client device 11 (STEP 24). Specifically, the processor 123 compares the identification information ID received via the communication interface 121 with the identification information ID of the client device 11 that is pre-stored in the update management information MG, and determines whether the two match.
[0043] If the identification information ID does not match (NO in STEP 24), the processor 123 sends notification information NT indicating that authentication failed to the client device 11 via the communication interface 121.
[0044] When notification information NT is received by the communication interface 111 of the client device 11, the processor 113 causes the user interface 112 to provide information notifying that authentication has failed (STEP 17).
[0045] If the identification information ID matches (YES in STEP 24), the processor 123 determines that authentication of the client device 11 has been successful and executes the process to determine whether the application needs to be updated (STEP 21).
[0046] With this configuration, unless authentication of the client device 11 is successful, the server device 12 will not send location information LC indicating the location of the update file UD. Therefore, it is possible to prevent application updates by client devices 11, for example, whose user agreement has been terminated. This enhances the security of the data management system 10.
[0047] As illustrated in Figure 4, the update management information MG may include identification information IDs for multiple client devices. In this case, the latest version of the application that can be updated may differ for each client device. The processor 123 of the server device 12 refers to the update management information MG based on the identification information IDs received via the communication interface 121 and identifies the client devices to be checked for update necessity. Subsequently, the processor 123 compares the latest version information LV associated with the identified client device with the version information VS received via the communication interface 121 to determine whether an update is necessary.
[0048] The update management information (MG) may include condition information (QL). The condition information (QL) is configured to define the update conditions for the target application. In the example in Figure 4, update condition a and update condition b are included in the condition information (QL). Update condition a is, for example, "Perform the update immediately when the latest version is released." Update condition b is, for example, "Wait for one month after the latest version is released before updating."
[0049] In this case, the processor 123 of the server device 12 refers to the update management information MG based on the identification information ID received via the communication interface 121, and identifies the latest version of the client device and application to be checked for update requirements. Subsequently, the processor 123 determines whether the application needs to be updated by referring to the condition information QL.
[0050] In the example in Figure 4, both client device A and client device B are associated with version 3.1 of the application. On the other hand, update condition a is set for client device A, and update condition b is set for client device B. If the application version is 3.0 for both client device A and client device B, and it is immediately after the release of version 3.1 of the application, client device A will be determined to require an update based on update condition a, and client device B will be determined not to require an update based on update condition b.
[0051] Policies regarding application updates may differ for each client device user. For example, one policy might be that the application version should always be the latest. Another example is a request to wait and see for a while before updating, even after the latest version of the application has been released. With the above configuration, a data management system 10 can be provided that can flexibly respond to the application update policies that may differ for each user.
[0052] As illustrated in Figure 2, a predetermined operation performed by the client device 11 may include sending change information CG to the server device 12. The change information CG is configured to allow changes to the application update conditions.
[0053] As an example, consider the case where client device 11 is "client device A" in the update management information MG. That is, client device 11 is assigned "update condition a". The user of client device 11 performs an operation on the user interface 112 to change "update condition a" to "update condition b". The processor 113 sends change information CG corresponding to this operation from the output interface 133 to the server device 12.
[0054] When the server device 12 receives change information CG via the communication interface 121, the processor 123 changes the condition information QL associated with "client device A" in the update management information MG stored in the storage 122 from "update condition a" to "update condition b". Thereafter, each time the client device 11 corresponding to "client device A" requests confirmation of whether an application needs to be updated, a determination of necessity is made based on the changed condition information QL.
[0055] With this configuration, a data management system 10 can be provided that can flexibly respond to changes in the application update policies of the user of the client device 11.
[0056] Each of the processors 113 of the client device 11 and the processor 123 of the server device 12, which have the various functions described above, can be realized by at least one general-purpose microprocessor that works in cooperation with at least one general-purpose memory. Examples of general-purpose microprocessors include CPUs, MPUs, and GPUs. Examples of general-purpose memory include ROMs and RAMs. In this case, the ROM may store a computer program that performs the above-described processing. ROM is an example of a non-temporary computer-readable medium in which a computer program is stored. The general-purpose microprocessor selects at least a portion of the program stored in the ROM and loads it onto the RAM, and then works in cooperation with the RAM to execute the above-described processing. The computer program may be pre-installed in the general-purpose memory, or it may be downloaded from an external server device via a communication network and then installed in the general-purpose memory. In this case, the external server device is an example of a non-temporary computer-readable medium in which a computer program is stored.
[0057] Each of processors 113 and 123 may be implemented by at least one dedicated integrated circuit capable of executing the above-described computer program. Examples of dedicated integrated circuits include microcontrollers, ASICs, FPGAs, etc. In this case, the above-described computer program is pre-installed in a memory element included in the dedicated integrated circuit. This memory element is an example of a computer-readable medium in which the computer program is stored. Each of processors 113 and 123 can also be implemented by a combination of a general-purpose microprocessor and a dedicated integrated circuit.
[0058] The configurations described herein are merely examples to facilitate understanding of this disclosure. Each configuration example may be modified or combined with other configuration examples as appropriate, as long as it does not deviate from the intent of this disclosure.
[0059] The configurations listed below also constitute part of this disclosure. Item 1: A server device capable of communicating with a client device on which an application for providing drug prescription services is executed, An interface that receives version information from the client device that can identify the version of the aforementioned application, A processor that determines whether an update to the application is necessary based on the version information, and if such an update is determined to be necessary, sends location information indicating the location of the update file to the client device. It is equipped with Server device. Item 2: The interface receives identification information from the client device that identifies the client device. The processor authenticates the client device based on the identification information, and if the authentication is successful, it determines whether the update is necessary. The server device described in item 1. Item 3: The aforementioned location information includes signature information that has an expiration date. The server device described in item 1 or 2. Item 4: The client device includes a plurality of client devices, The interface receives identification information that identifies itself from each of the multiple client devices. The processor determines whether the update is necessary by referring to condition information indicating the update conditions defined for each of the plurality of client devices. A server device as described in any one of items 1 through 3. Item 5: The interface receives instructions to change the update conditions from at least one of the plurality of client devices. The server device described in item 4. [Explanation of Symbols]
[0060] 11: Client device, 12: Server device, 121: Communication interface, 123: Processor, CD: Condition information, ID: Identification information, LC: Location information, UD: Update file, VS: Version information
Claims
1. A server device capable of communicating with a client device on which an application for providing drug prescription services is executed, An interface that receives version information from the client device that can identify the version of the aforementioned application, A processor that determines whether an update to the application is necessary based on the version information, and if such an update is determined to be necessary, sends location information indicating the location of the update file to the client device. It is equipped with Server device.
2. The interface receives identification information from the client device that identifies the client device. The processor authenticates the client device based on the identification information, and if the authentication is successful, it determines whether the update is necessary. The server device according to claim 1.
3. The aforementioned location information includes signature information that has an expiration date. The server device according to claim 1.
4. The client device includes a plurality of client devices, The interface receives identification information that identifies itself from each of the multiple client devices. The processor determines whether the update is necessary by referring to condition information indicating update conditions defined for each of the plurality of client devices based on the identification information. The server device according to claim 1.
5. The interface receives instructions to change the update conditions from at least one of the plurality of client devices. The server device according to claim 4.
6. A computer program executable by a processor installed in a server device capable of communicating with a client device on which an application for providing drug prescription services is executed, By being executed, the server device will The client device receives version information that can identify the version of the aforementioned application. Based on the aforementioned version information, determine whether an update to the application is necessary. If it is determined that the update is necessary, location information indicating the location of the update file is sent to the client device. Computer program.
7. An application management method, which is performed by a client device on which an application for providing drug prescription services is executed and a server device installed at a location separate from the client device, Version information that can identify the version of the aforementioned application is transmitted from the client device to the server device. The server device determines whether an update to the application is necessary based on the version information. When it is determined that the update is necessary, location information indicating the location of the update file is transmitted from the server device to the client device. The client device uses the location information to obtain the update file. Data management methods.
Citation Information
Patent Citations
Medication management system, management server, and management server control program
JP2024055808A