CN112055064B - Data synchronization method, device, equipment and storage medium - Google Patents
Data synchronization method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112055064B CN112055064B CN202010873743.5A CN202010873743A CN112055064B CN 112055064 B CN112055064 B CN 112055064B CN 202010873743 A CN202010873743 A CN 202010873743A CN 112055064 B CN112055064 B CN 112055064B
- Authority
- CN
- China
- Prior art keywords
- client
- cloud server
- information
- user
- data synchronization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 239000005441 aurora Substances 0.000 claims description 10
- 238000012795 verification Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 239000003814 drug Substances 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Abstract
The application discloses a data synchronization method, a device, equipment and a storage medium. The method comprises the following steps: the cloud server acquires prescription information reported by at least one first client, wherein the prescription information comprises doctor account information; the cloud server determines a target clinic according to the doctor account information; the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients; the cloud server calls the third party server to push a notification to the second client; after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request.
Description
Technical Field
The embodiment of the application relates to the technical field of medical treatment and health, in particular to a data synchronization method, a device, equipment and a storage medium.
Background
The current medical system flow cannot completely realize paperless, a doctor needs to check, get medicine, pay fee, register and other operations of different projects by means of various documents, and various documents are inconvenient to store and easy to miss or lose due to asynchronous data.
Disclosure of Invention
The embodiment of the application provides a data synchronization method, a device, equipment and a storage medium, which can realize data synchronization between clients in a medical system.
In a first aspect, an embodiment of the present application provides a data synchronization method, applied to a medical system, where the medical system includes: the data synchronization method comprises the following steps of:
the cloud server acquires prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the cloud server determines a target clinic according to the doctor account information;
the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients;
the cloud server calls the third party server to push a notification to the second client;
and after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request.
In a second aspect, an embodiment of the present application further provides a data synchronization device, applied to a medical system, where the medical system includes: the cloud server comprises a data synchronization device, wherein the data synchronization device comprises:
the acquisition module is used for acquiring prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the determining module is used for determining a target clinic according to the doctor account information;
the searching module is used for searching a second client corresponding to the target clinic, and the first client and the second client belong to the target clinic and are different clients;
the pushing module is used for calling the third-party server to push the notification to the second client;
and the sending module is used for sending the prescription information to the second client according to the data synchronization request after receiving the data synchronization request sent by the second client.
In a third aspect, embodiments of the present application further provide a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing a method according to any of the embodiments of the present application when executing the program.
In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, implements a method according to any of the embodiments of the present application.
According to the embodiment of the application, prescription information reported by at least one first client is obtained through the cloud server, wherein the prescription information comprises doctor account information; the cloud server determines a target clinic according to the doctor account information; the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients; the cloud server calls the third party server to push a notification to the second client; and after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request so as to realize data synchronization among clients in the medical system.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a data synchronization method according to a first embodiment of the present application;
fig. 1a is a schematic diagram of multi-terminal synchronization when a third party is an aurora server in the first embodiment of the present application;
fig. 1b is a schematic diagram of multi-terminal synchronization when the third party is a network pipe server according to the first embodiment of the present application;
fig. 2 is a schematic structural diagram of a data synchronization device in a second embodiment of the present application;
fig. 3 is a schematic structural diagram of a computer device in a third embodiment of the present application.
Detailed Description
The application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present application are shown in the drawings.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
Example 1
Fig. 1 is a flowchart of a data synchronization method provided in a first embodiment of the present application, where the method may be applied to a data synchronization situation, and the method may be performed by a data synchronization device in the embodiment of the present application, where the device may be implemented in a software and/or hardware manner, as shown in fig. 1, and the method specifically includes the following steps:
s110, the cloud server acquires prescription information reported by at least one first client, wherein the prescription information comprises doctor account information.
The first client may be an integrated machine, a tablet, or a desktop, which is not limited in this embodiment of the present application.
Specifically, after a doctor inputs prescription information, the first client saves the prescription information locally, then the prescription information is sent to a cloud server, and the cloud server acquires the prescription information reported by at least one first client, wherein the prescription information comprises doctor account information.
S120, the cloud server determines a target clinic according to the doctor account information.
The method for determining the target clinic according to the doctor account information may be that a database related to the correspondence between the doctor account information and the clinic is stored in advance, the database is queried according to the doctor account information carried by the prescription information, and a clinic corresponding to the doctor account information is obtained, and the clinic is used as the target clinic.
Specifically, after the cloud server obtains the information of the treatment place, the target clinic is determined according to the doctor account information carried by the prescription information. In the case where the same doctor works in a plurality of clinics, doctor account information corresponding to each clinic is different, and distinction is made.
S130, the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients.
The second client belongs to the target clinic, the first client also belongs to the target clinic, and the first client and the second client are different clients.
Specifically, the cloud server may search for the second client corresponding to the target clinic, where the first time the client in the clinic enters, perform verification according to the SN code of the device, store the clinic and the corresponding client correspondingly after the verification is passed, search for the client corresponding to the target clinic, remove the first client from the client corresponding to the target clinic, and use the remaining clients as the second client, for example, the cloud server searches for the client X, the client Y, and the client Z corresponding to the target clinic a, where the client X is the first client, and the second client includes: client Y and client Z.
And S140, the cloud server calls the third party server to push the notification to the second client.
The third party server may be an aurora server or a WebSocket server, which is not limited in the embodiment of the present application.
Specifically, as shown in fig. 1a, if the second client is an all-in-one machine or a tablet, the third party server is an aurora server, and the cloud server calls the aurora server to push a notification to the second client; as shown in fig. 1b, if the second client is a desktop computer, the third party server is a WebSocket server, and the cloud server calls the WebSocket server to push a notification to the second client.
And S150, after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request.
Specifically, after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request.
The patient arrives at the clinic, registration is completed through the self-help registration machine, registration information is processed in the application background, and meanwhile, the application background distributes the registration information to a doctor's list to be treated and a cloud screen registration system. In this way, the doctor can be notified of the basic information of the subsequent patient and patient complaints. The patient can pay attention to the display screen for calling numbers and wait for the calling numbers to visit. Or the patient sends the registration information to the cloud server through the mobile phone, and the cloud server distributes the registration information to a doctor's list to be treated and a cloud screen registration system.
When all clients log in for the first time, the clients are verified first, and after the clients pass through, the client information registration and the user relationship binding are carried out. The client login and logout all need to send information to the cloud server for recording, and the cloud server sends prescription information or registration information to which terminal through logic judgment (the logic judgment is distinguished according to organization, user type and equipment type). For example, registration information can be transmitted to an android cloud screen for processing through a three-party aurora scheme. Prescription settlement information can be synchronously given to a pharmacy windows workbench through websocket+redis+background application modes.
Optionally, before the cloud server obtains the prescription information reported by the at least one first client, the method further includes:
the cloud server acquires an SN (sequence number) code sent by at least one client;
the cloud server verifies the at least one client according to the SN;
after verification is passed, the cloud server acquires user registration information, wherein the user registration information comprises: user name, user address, user contact means, and clinic to which the user belongs;
the cloud server correspondingly stores the user registration information and the SN;
the cloud server determines user registration information corresponding to the user name according to the user name and the password input by the user;
the cloud server inquires user information according to the user registration information and sends the user information to a client, wherein the user information comprises: user registration information, user rights information, configuration information of the client, and clinic information.
Wherein, the SN code is a client identification code.
Specifically, the method for verifying the at least one client according to the SN may be that an SN code list is stored in the cloud server in advance, the SN codes are compared with SN codes in the SN code list, and if the same SN codes exist, the verification is passed.
Specifically, the server returns the authority information of the current user when logging in, and is used as a basis for locally judging the authority, and the storage position, the memory or the database is determined according to the asking for money, and the authority is data which can be called for many times and is recommended to be stored in the memory. And right management, firstly judging whether the current user is an administrator or not before entering, and only the administrator has the right to manage, and acquiring all user information and rights of the current clinic from the server at the moment. If there is no authority, the portal is not displayed. Modification of user information, when clicking a certain user in the user list, the right side displays the current detailed information of the user, and can view the required document or input data in detail. For operations, the modification of the data comes from the modification page after clicking, and two operations of cancellation and determination are provided, the data needs to be verified during clicking determination, and the modification interface is requested to modify the user data, and attention needs to be paid to: regarding the problem of user rights, the administrator cannot modify his own rights, and the administrator defaults to have all rights; what the modification rights call is to modify the user rights interface.
The user authority is updated and notified using the aurora. After receiving the notification, the user is forced to be reminded of permission modification, and needs to log in again,
optionally, the third party server includes: an aurora server and/or a network pipe server.
Optionally, the client includes: all-in-one, tablet, and/or desktop.
Optionally, if the client is a desktop;
the cloud server invoking a third party server to push a notification to the second client comprises:
and the cloud server calls a network pipeline server to push a notification to the second client.
Optionally, if the client is an all-in-one machine or a tablet;
the cloud server invoking a third party server to push a notification to the second client comprises:
and the cloud server calls an aurora server to push a notification to the second client.
Optionally, the determining, by the cloud server, the target clinic according to the doctor account information includes:
a database of the corresponding relation between doctor account information and clinics is established in advance;
and the cloud server searches the database according to the doctor account information to obtain a target clinic corresponding to the doctor account information.
Specifically, after the user logs in, the user type is obtained, and if the user is a common user, the module or the interface is hidden; and if the user is an administrator, displaying a module or an interface.
Specifically, after the user logs in, whether the user is an administrator or not is judged, if yes, authority management is carried out, all user information is queried, the user is selected, the authority of the user is modified, verification information is input, after verification is successful, the user information can be modified, and the user information can be modified into a state of being incapable of being modified.
After the data of the server side changes, the data needs to be updated to the client side in time.
The request data is shown in table 1:
TABLE 1
| Name of the name | Data type | Must fill in items | Description of the application |
| Conventional parameters | Is that | ||
| clientVersion | String | Is that | Current version |
The returned data are shown in table 2:
TABLE 2
| Name of the name | Data type | Length of | Description of the application |
| code | Integer | 5 | Error code |
| content | List | * | See the following objects |
The detailed data are shown in table 3:
TABLE 3 Table 3
According to the technical scheme, prescription information reported by at least one first client is obtained through the cloud server, wherein the prescription information comprises doctor account information; the cloud server determines a target clinic according to the doctor account information; the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients; the cloud server calls the third party server to push a notification to the second client; and after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request so as to realize data synchronization among clients in the medical system.
Example two
Fig. 2 is a schematic structural diagram of a data synchronization device according to a second embodiment of the present application. The embodiment can be applied to the case of data synchronization, the device can be implemented in a software and/or hardware mode, and the device can be integrated in any equipment providing a data synchronization function and applied to a medical system, and the medical system comprises: the cloud server comprises a data synchronization device, as shown in fig. 2, and the data synchronization device specifically comprises: the acquisition module 210, the determination module 220, the lookup module 230, the push module 240, and the transmission module 250.
The acquisition module is used for acquiring prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the determining module is used for determining a target clinic according to the doctor account information;
the searching module is used for searching a second client corresponding to the target clinic, and the first client and the second client belong to the target clinic and are different clients;
the pushing module is used for calling the third-party server to push the notification to the second client;
and the sending module is used for sending the prescription information to the second client according to the data synchronization request after receiving the data synchronization request sent by the second client.
The product can execute the method provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method.
According to the technical scheme, prescription information reported by at least one first client is obtained through the cloud server, wherein the prescription information comprises doctor account information; the cloud server determines a target clinic according to the doctor account information; the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients; the cloud server calls the third party server to push a notification to the second client; and after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request so as to realize data synchronization among clients in the medical system.
Example III
Fig. 3 is a schematic structural diagram of a computer device according to a third embodiment of the present application. FIG. 3 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present application. The computer device 12 shown in fig. 3 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present application.
As shown in FIG. 3, computer device 12 is in the form of a general purpose computing device. Components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.
Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Computer device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 3, commonly referred to as a "hard disk drive"). Although not shown in fig. 3, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of embodiments of the application.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the computer device 12, and/or any devices (e.g., network card, modem, etc.) that enable the computer device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. In addition, in the computer device 12 of the present embodiment, the display 24 is not present as a separate body but is embedded in the mirror surface, and the display surface of the display 24 and the mirror surface are visually integrated when the display surface of the display 24 is not displayed. Moreover, computer device 12 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 20. As shown, network adapter 20 communicates with other modules of computer device 12 via bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computer device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing a data synchronization method provided by an embodiment of the present application: applied to a medical system, the medical system comprising: the data synchronization method comprises the following steps of:
the cloud server acquires prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the cloud server determines a target clinic according to the doctor account information;
the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients;
the cloud server calls the third party server to push a notification to the second client;
and after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request.
Example IV
A fourth embodiment of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a data synchronization method as provided by all the embodiments of the present application: applied to a medical system, the medical system comprising: the data synchronization method comprises the following steps of:
the cloud server acquires prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the cloud server determines a target clinic according to the doctor account information;
the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients;
the cloud server calls the third party server to push a notification to the second client;
and after receiving the data synchronization request sent by the second client, the cloud server sends the prescription information to the second client according to the data synchronization request.
Any combination of one or more computer readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present application and the technical principle applied. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, while the application has been described in connection with the above embodiments, the application is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the application, which is set forth in the following claims.
Claims (8)
1. A method of data synchronization, for use in a medical system, the medical system comprising: the data synchronization method comprises the following steps of:
the cloud server acquires prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the cloud server determines a target clinic according to the doctor account information;
the cloud server searches a second client corresponding to the target clinic, wherein the first client and the second client belong to the target clinic and are different clients;
the cloud server calls the third party server to push a notification to the second client;
the cloud server sends the prescription information to the second client according to the data synchronization request after receiving the data synchronization request sent by the second client;
the cloud server determining the target clinic according to the doctor account information comprises:
a database of the corresponding relation between doctor account information and clinics is established in advance;
the cloud server searches the database according to the doctor account information to obtain a target clinic corresponding to the doctor account information;
before the cloud server obtains the prescription information reported by at least one first client, the cloud server further includes:
the cloud server acquires an SN (sequence number) code sent by at least one client;
the cloud server verifies the at least one client according to the SN;
after verification is passed, the cloud server acquires user registration information, wherein the user registration information comprises: user name, user address, user contact means, and clinic to which the user belongs;
the cloud server correspondingly stores the user registration information and the SN;
the cloud server determines user registration information corresponding to the user name according to the user name and the password input by the user;
the cloud server inquires user information according to the user registration information and sends the user information to a client, wherein the user information comprises: user registration information, user rights information, configuration information of the client, and clinic information.
2. The method of claim 1, wherein the third party server comprises: an aurora server and/or a network pipe server.
3. The method of claim 2, wherein the client comprises: all-in-one, tablet, and/or desktop.
4. The method of claim 3, wherein if the client is a desktop;
the cloud server invoking a third party server to push a notification to the second client comprises:
and the cloud server calls a network pipeline server to push a notification to the second client.
5. A method according to claim 3, wherein if the client is a kiosk or tablet;
the cloud server invoking a third party server to push a notification to the second client comprises:
and the cloud server calls an aurora server to push a notification to the second client.
6. A data synchronization device for use in a medical system, the medical system comprising: the cloud server comprises a data synchronization device, wherein the data synchronization device comprises:
the acquisition module is used for acquiring prescription information reported by at least one first client, wherein the prescription information comprises doctor account information;
the determining module is used for determining a target clinic according to the doctor account information;
the searching module is used for searching a second client corresponding to the target clinic, and the first client and the second client belong to the target clinic and are different clients;
the pushing module is used for calling the third-party server to push the notification to the second client;
the sending module is used for sending the prescription information to the second client according to the data synchronization request after receiving the data synchronization request sent by the second client;
the cloud server determining the target clinic according to the doctor account information comprises:
a database of the corresponding relation between doctor account information and clinics is established in advance;
the cloud server searches the database according to the doctor account information to obtain a target clinic corresponding to the doctor account information;
before the cloud server obtains the prescription information reported by at least one first client, the cloud server further includes:
the cloud server acquires an SN (sequence number) code sent by at least one client;
the cloud server verifies the at least one client according to the SN;
after verification is passed, the cloud server acquires user registration information, wherein the user registration information comprises: user name, user address, user contact means, and clinic to which the user belongs;
the cloud server correspondingly stores the user registration information and the SN;
the cloud server determines user registration information corresponding to the user name according to the user name and the password input by the user;
the cloud server inquires user information according to the user registration information and sends the user information to a client, wherein the user information comprises: user registration information, user rights information, configuration information of the client, and clinic information.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 1-5 when the program is executed by the processor.
8. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010873743.5A CN112055064B (en) | 2020-08-26 | 2020-08-26 | Data synchronization method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010873743.5A CN112055064B (en) | 2020-08-26 | 2020-08-26 | Data synchronization method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112055064A CN112055064A (en) | 2020-12-08 |
| CN112055064B true CN112055064B (en) | 2023-11-28 |
Family
ID=73600635
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010873743.5A Active CN112055064B (en) | 2020-08-26 | 2020-08-26 | Data synchronization method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112055064B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407356A (en) * | 2021-05-24 | 2021-09-17 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN116861447A (en) * | 2021-06-07 | 2023-10-10 | 云南力衡医疗技术有限公司 | Prescription control method and system for out-going treatment equipment |
| CN114828004B (en) * | 2022-04-28 | 2024-01-26 | 广州通则康威科技股份有限公司 | Method and device for automatically acquiring IP of wireless network equipment by applet |
| CN114978887A (en) * | 2022-05-12 | 2022-08-30 | 盐城鸿石智能科技有限公司 | Client parameter configuration system and method of MES system |
| CN115102918A (en) * | 2022-06-14 | 2022-09-23 | Oppo广东移动通信有限公司 | Message synchronization method, device and system, related equipment and storage medium |
| CN117473019B (en) * | 2023-12-25 | 2024-03-22 | 阿里云计算有限公司 | Data synchronization method, system, computer equipment and storage medium |
Citations (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1801164A (en) * | 2004-12-30 | 2006-07-12 | 上海雷硕医疗器械有限公司 | Medical prescription system synchronous with pharmacy data |
| CN103906010A (en) * | 2012-12-24 | 2014-07-02 | 三星电子株式会社 | Method for synchronizing messages among plurality of terminals, machine-readable storage medium, and server |
| CN103902836A (en) * | 2014-04-14 | 2014-07-02 | 康博嘉信息科技（北京）有限公司 | Method, device and system for medical information interaction based on cloud service platform |
| CN104301378A (en) * | 2014-08-28 | 2015-01-21 | 小米科技有限责任公司 | User information updating method and device |
| CN105009549A (en) * | 2013-12-10 | 2015-10-28 | 华为终端有限公司 | Synchronization method, terminal and server |
| CN105205766A (en) * | 2015-08-19 | 2015-12-30 | 四川佳缘电子科技有限公司 | Mobile Internet hospital attendance system based on cloud platform |
| CN106020754A (en) * | 2016-05-06 | 2016-10-12 | 北京小米移动软件有限公司 | A synchronous display method and device |
| CN106453619A (en) * | 2016-11-17 | 2017-02-22 | 中国医学科学院生物医学工程研究所 | Intelligent cardiovascular disease follow-up system based on network |
| CN106506502A (en) * | 2016-11-15 | 2017-03-15 | 合肥工业大学 | A kind of multi-modal mobile electron medical records system and its method of work |
| CN108648830A (en) * | 2018-04-24 | 2018-10-12 | 广州市行心信息科技有限公司 | A kind of medical service system and method based on cloud platform |
| CN109585029A (en) * | 2018-12-05 | 2019-04-05 | 广西壮族自治区人民医院 | A kind of patient in hospital information network platform |
| CN109639834A (en) * | 2019-01-25 | 2019-04-16 | 努比亚技术有限公司 | A kind of synchronizing information processing method, system and mobile terminal |
| CN109714420A (en) * | 2018-12-28 | 2019-05-03 | 北京车和家信息技术有限公司 | A kind of method, apparatus and system that data are synchronous |
| CN109830274A (en) * | 2019-02-02 | 2019-05-31 | 四川爱华立康智能科技有限公司 | A kind of electronic prescription shared system and sharing method |
| CN109872788A (en) * | 2019-01-30 | 2019-06-11 | 广州大集科技有限公司 | A kind of electronic prescription processing method and network hospital platform for rehabilitation field |
| CN109889572A (en) * | 2019-01-11 | 2019-06-14 | 杭州电子科技大学 | A kind of this Internet of Things of electronic health record intelligent interactive system and its implementation |
| CN110097938A (en) * | 2018-01-29 | 2019-08-06 | 深圳中科强华科技有限公司 | A kind of diagnosis and treatment method of data synchronization based on COS |
| CN110097977A (en) * | 2019-03-12 | 2019-08-06 | 北京易联网络科技集团有限公司 | A kind of clinic long distance service system based on artificial intelligence |
| CN110148456A (en) * | 2019-05-24 | 2019-08-20 | 武汉武吉智能科技有限公司 | Intelligent medical treatment system, equipment and storage medium |
| CN110211652A (en) * | 2019-06-04 | 2019-09-06 | 苏州工业园区服务外包职业学院 | A kind of medical data management system |
| CN110462743A (en) * | 2018-12-06 | 2019-11-15 | 深圳市全息医疗科技有限公司 | A kind of _ based Patient Records Management Systems and method |
| CN110706764A (en) * | 2019-08-22 | 2020-01-17 | 上海市第六人民医院 | Wisdom hospital information interaction system |
| CN110808106A (en) * | 2019-10-11 | 2020-02-18 | 杭州智团信息技术有限公司 | Method for information interaction between pathology management system and remote consultation system |
| CN111161823A (en) * | 2019-11-20 | 2020-05-15 | 北京海益同展信息科技有限公司 | Information acquisition method and device, storage medium and electronic device |
| CN111240896A (en) * | 2020-01-06 | 2020-06-05 | 深圳市随手科技有限公司 | Terminal data synchronization method, device, server and storage medium |
| CN111261254A (en) * | 2018-11-30 | 2020-06-09 | 熙牛医疗科技(浙江)有限公司 | Method and equipment for generating prescription and medical advice data entry system |
| CN111400381A (en) * | 2020-02-28 | 2020-07-10 | 北京致医健康信息技术有限公司 | Data storage method and device, computer equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10713355B2 (en) * | 2016-10-21 | 2020-07-14 | Qatar University | Method and system for adaptive security in cloud-based services |
-
2020
- 2020-08-26 CN CN202010873743.5A patent/CN112055064B/en active Active
Patent Citations (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1801164A (en) * | 2004-12-30 | 2006-07-12 | 上海雷硕医疗器械有限公司 | Medical prescription system synchronous with pharmacy data |
| CN103906010A (en) * | 2012-12-24 | 2014-07-02 | 三星电子株式会社 | Method for synchronizing messages among plurality of terminals, machine-readable storage medium, and server |
| CN105009549A (en) * | 2013-12-10 | 2015-10-28 | 华为终端有限公司 | Synchronization method, terminal and server |
| CN103902836A (en) * | 2014-04-14 | 2014-07-02 | 康博嘉信息科技（北京）有限公司 | Method, device and system for medical information interaction based on cloud service platform |
| CN104301378A (en) * | 2014-08-28 | 2015-01-21 | 小米科技有限责任公司 | User information updating method and device |
| CN105205766A (en) * | 2015-08-19 | 2015-12-30 | 四川佳缘电子科技有限公司 | Mobile Internet hospital attendance system based on cloud platform |
| CN106020754A (en) * | 2016-05-06 | 2016-10-12 | 北京小米移动软件有限公司 | A synchronous display method and device |
| CN106506502A (en) * | 2016-11-15 | 2017-03-15 | 合肥工业大学 | A kind of multi-modal mobile electron medical records system and its method of work |
| CN106453619A (en) * | 2016-11-17 | 2017-02-22 | 中国医学科学院生物医学工程研究所 | Intelligent cardiovascular disease follow-up system based on network |
| CN110097938A (en) * | 2018-01-29 | 2019-08-06 | 深圳中科强华科技有限公司 | A kind of diagnosis and treatment method of data synchronization based on COS |
| CN108648830A (en) * | 2018-04-24 | 2018-10-12 | 广州市行心信息科技有限公司 | A kind of medical service system and method based on cloud platform |
| CN111261254A (en) * | 2018-11-30 | 2020-06-09 | 熙牛医疗科技(浙江)有限公司 | Method and equipment for generating prescription and medical advice data entry system |
| CN109585029A (en) * | 2018-12-05 | 2019-04-05 | 广西壮族自治区人民医院 | A kind of patient in hospital information network platform |
| CN110462743A (en) * | 2018-12-06 | 2019-11-15 | 深圳市全息医疗科技有限公司 | A kind of _ based Patient Records Management Systems and method |
| CN109714420A (en) * | 2018-12-28 | 2019-05-03 | 北京车和家信息技术有限公司 | A kind of method, apparatus and system that data are synchronous |
| CN109889572A (en) * | 2019-01-11 | 2019-06-14 | 杭州电子科技大学 | A kind of this Internet of Things of electronic health record intelligent interactive system and its implementation |
| CN109639834A (en) * | 2019-01-25 | 2019-04-16 | 努比亚技术有限公司 | A kind of synchronizing information processing method, system and mobile terminal |
| CN109872788A (en) * | 2019-01-30 | 2019-06-11 | 广州大集科技有限公司 | A kind of electronic prescription processing method and network hospital platform for rehabilitation field |
| CN109830274A (en) * | 2019-02-02 | 2019-05-31 | 四川爱华立康智能科技有限公司 | A kind of electronic prescription shared system and sharing method |
| CN110097977A (en) * | 2019-03-12 | 2019-08-06 | 北京易联网络科技集团有限公司 | A kind of clinic long distance service system based on artificial intelligence |
| CN110148456A (en) * | 2019-05-24 | 2019-08-20 | 武汉武吉智能科技有限公司 | Intelligent medical treatment system, equipment and storage medium |
| CN110211652A (en) * | 2019-06-04 | 2019-09-06 | 苏州工业园区服务外包职业学院 | A kind of medical data management system |
| CN110706764A (en) * | 2019-08-22 | 2020-01-17 | 上海市第六人民医院 | Wisdom hospital information interaction system |
| CN110808106A (en) * | 2019-10-11 | 2020-02-18 | 杭州智团信息技术有限公司 | Method for information interaction between pathology management system and remote consultation system |
| CN111161823A (en) * | 2019-11-20 | 2020-05-15 | 北京海益同展信息科技有限公司 | Information acquisition method and device, storage medium and electronic device |
| CN111240896A (en) * | 2020-01-06 | 2020-06-05 | 深圳市随手科技有限公司 | Terminal data synchronization method, device, server and storage medium |
| CN111400381A (en) * | 2020-02-28 | 2020-07-10 | 北京致医健康信息技术有限公司 | Data storage method and device, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 处方共享平台:重构处方药品流通生态;周玉涛;《中国药店》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112055064A (en) | 2020-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112055064B (en) | Data synchronization method, device, equipment and storage medium | |
| US11252252B2 (en) | Installable web applications | |
| US9178746B2 (en) | Browser-based fetch of external libraries | |
| CN110287146B (en) | Method, device and computer storage medium for downloading application | |
| US20190205846A1 (en) | Methods and systems for communicating expense management information | |
| CN113254969B (en) | Business data processing method and device, electronic equipment and storage medium | |
| CN111815421A (en) | Tax policy processing method and device, terminal equipment and storage medium | |
| US20210103993A1 (en) | Inter-frame communication | |
| US11570169B2 (en) | Multi-factor authentication via multiple devices | |
| CN111241043A (en) | Multimedia file sharing method, terminal and storage medium | |
| US20150067491A1 (en) | Intelligent auto complete | |
| CN110737861A (en) | webpage data processing method, device, equipment and storage medium | |
| CN113132400B (en) | Business processing method, device, computer system and storage medium | |
| US20150193580A1 (en) | Electronic medical record system with automated health care services evaluation | |
| CN114254347A (en) | System access method, device, electronic equipment and storage medium | |
| US20200042498A1 (en) | System and Method for Interactive Visual Representation of Metadata within a Networked Heterogeneous Workflow Environment | |
| CN112364268A (en) | Resource acquisition method and device, electronic equipment and storage medium | |
| CN113283850A (en) | Task auditing method, device and system | |
| TW201528169A (en) | System and method for providing isolation boundaries between regulated medical applications and unregulated, non-medical applications | |
| CN111125759A (en) | Database login account shielding method and device and electronic equipment | |
| CN111885152B (en) | Promotion information processing method, electronic device and computer-readable storage medium | |
| CN114285743B (en) | Method, device, electronic equipment and storage medium for updating configuration information | |
| CN110363401B (en) | Integrated viscosity evaluation method and device, computer equipment and storage medium | |
| CN113641966A (en) | Application integration method, system, device and medium | |
| CN113419791A (en) | Office document generation method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |