CN115274038B - Electronic medical record processing method, device, server and storage medium - Google Patents
Electronic medical record processing method, device, server and storage medium Download PDFInfo
- Publication number
- CN115274038B CN115274038B CN202211186440.1A CN202211186440A CN115274038B CN 115274038 B CN115274038 B CN 115274038B CN 202211186440 A CN202211186440 A CN 202211186440A CN 115274038 B CN115274038 B CN 115274038B
- Authority
- CN
- China
- Prior art keywords
- file
- medical record
- server
- record file
- target
- 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
Images
Classifications
-
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Public Health (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Health & Medical Sciences (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Epidemiology (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure relates to the field of electronic medical record technologies, and in particular, to an electronic medical record processing method, an electronic medical record processing apparatus, a server, and a storage medium. The method comprises the following steps: determining target medical history files to be downloaded from a server, wherein each medical history file corresponds to a first characteristic value, and the first characteristic value stored by the server is calculated by the server according to the content of the corresponding medical history file; determining a target medical record file to be downloaded from the target medical record file based on a first characteristic value of the medical record file in the target medical record file of the server; the target medical record file is as follows: during the period from the last time of downloading the target course file to the current time by the client, the medical record file with changed file content in the target course file of the server and/or the medical record file newly added in the target course file of the server; and downloading the target medical record file from the server. The method provided by the disclosure can save network flow, improve the response speed of medical record operation and improve the efficiency.
Description
Technical Field
The present disclosure relates to the field of electronic medical record technologies, and in particular, to an electronic medical record processing method, an electronic medical record processing apparatus, a server, and a storage medium.
Background
In the medical field, different disease course documents are generally established for each patient based on the hospitalization information of each patient, and the disease course documents include a disease course homepage, daily disease course records, ward round records and the like. And the medical history file is obtained by combining a plurality of medical history files, and different medical history files are different medical history information of the patient. The medical history file is stored in the server, each client can download the medical history file from the server, and meanwhile, each client can edit and modify the medical history file in the medical history file and upload the modified medical history file to the server for updating, so that the latest medical history file is stored in the server, and other clients can download the latest medical history file from the server.
Wherein, according to the standard of Wei Jian, the patient needs to be checked and printed in a disease course file. Based on this, in the related art, when one medical record file in the medical record files of the server is modified, the client needs to download all medical record files in the medical record files from the server, and merge and assemble the medical record files at the client again.
In the related technology, the method for processing the medical record files requires more network traffic, has slower response speed of medical record operation and lower efficiency.
Disclosure of Invention
The present disclosure provides an electronic medical record processing method, an electronic medical record processing device, a server, and a storage medium, so as to at least solve the problems of a large network traffic, a slow response speed of medical record operation, and a low efficiency of the electronic medical record processing method in the related art.
The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided an electronic medical record processing method, including:
determining a target course file to be downloaded from a server, wherein the server stores at least one course file, the course file comprises at least one medical record file, each medical record file corresponds to a first characteristic value, the first characteristic values stored by the server are obtained by calculating the content of the corresponding medical record file of the server, and when the file content in the medical record file stored by the server changes, the first characteristic values corresponding to the medical record file stored by the server also correspondingly change;
determining a target medical record file to be downloaded from the target medical record file based on a first characteristic value of the medical record file in the target medical record file of the server; wherein, the target medical record file is as follows: during the period from the moment when the client downloads the target course file last to the current moment, the medical record file with changed file content in the target course file of the server and/or a medical record file newly added in the target course file of the server;
and downloading the target medical record file from a server.
According to a second aspect of the embodiments of the present disclosure, there is provided a screen adapting apparatus including:
the system comprises a first determining module and a second determining module, wherein the first determining module is used for determining a target course file to be downloaded from a server, the server stores at least one course file, the course file comprises at least one medical record file, each medical record file corresponds to a first characteristic value, the first characteristic values stored by the server are obtained by calculating the content of the corresponding medical record file of the server, and when the file content in the medical record file stored by the server changes, the first characteristic values corresponding to the medical record file stored by the server also correspondingly change;
the second determining module is used for determining a target medical record file to be downloaded from the target medical record file based on a first characteristic value of the medical record file in the target medical record file of the server; wherein, the target medical record file is as follows: during the period from the moment when the client downloads the target course file last to the current moment, the medical record file with changed file content in the target course file of the server and/or a medical record file newly added in the target course file of the server;
and the downloading module is used for downloading the target medical record file from the server.
According to a third aspect of the present application, there is provided a server comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the electronic medical record processing method of any one of claims 1 to 6.
According to a fourth aspect of the present application, there is provided a storage medium, wherein instructions of the storage medium, when executed by a processor of a server, enable the server to execute the electronic medical record processing method according to the first aspect.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a flow diagram illustrating a method of electronic medical record processing according to an exemplary embodiment;
FIG. 2 is a block diagram illustrating an electronic medical record processing apparatus according to an exemplary embodiment;
FIG. 3 is a block diagram illustrating a server in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating an electronic medical record processing method according to an exemplary embodiment, which is executed by a client, and as shown in fig. 1, the electronic medical record processing method may include the following steps:
in step S11, the target course file to be downloaded is determined from the server.
The server stores at least one medical history file, different medical history files correspond to different patients, each medical history file comprises a plurality of medical history files, and different medical history files are used for recording different medical history information of the patients.
And in the embodiment of the disclosure, a first characteristic value is correspondingly set for each medical record file, and the first characteristic value is calculated by the server based on the content of the corresponding medical record file, wherein when the file content of a certain medical record file stored by the server changes, the server calculates to obtain a new first characteristic value based on the changed file content of the medical record file, and replaces and updates the original first characteristic value by using the new first characteristic value. That is, during the period of storing the medical record file, the first characteristic value corresponding to the medical record file changes with the change of the file content of the medical record file.
Meanwhile, in the embodiment of the disclosure, a second characteristic value is correspondingly set for each course file, and the second characteristic value is calculated by the server based on the content of the corresponding course file, wherein when the file content of a certain course file stored by the server changes, the server calculates to obtain a new second characteristic value based on the changed file content of the course file, and replaces and updates the original second characteristic value by using the new second characteristic value. That is, during the period of storing the disease course file, the second feature value corresponding to the disease course file changes with the change of the file content of the disease course file.
The first and second eigenvalues described above may be 16-bit values of md 5.
Further, it should be noted that the disease course file includes, but is not limited to, at least one of a storage path, a disease course file name, and a second feature value; the medical record file includes, but is not limited to, at least one of a patient identification ID, a number of hospitalizations, an outpatient number, a medical record file number, a storage path, a medical record file name, a doctor, and a first characteristic value.
When the client downloads the course file for the first time, the course file is downloaded to the client based on the storage path of the course file stored by the server, and the course file is named based on the course file name and a second characteristic value corresponding to the course file by adopting a second preset naming mode; wherein the second preset naming mode is as follows: and taking the disease course file name as the file name of the disease course file, and taking the second characteristic value as the extension of the disease course file.
Similarly, when the medical record file is downloaded by the client for the first time, the medical record file is downloaded to the client based on the storage path of the medical record file stored by the server, and the medical record file is named based on the name of the medical record file and the first characteristic value corresponding to the medical record file by adopting a first preset naming mode; the first preset naming mode is as follows: and taking the name of the medical record file as the file name of the medical record file, and taking the first characteristic value as the extension of the medical record file.
For example, taking a medical record file as an example (the same medical record file), assuming that the medical record file name of the medical record file is emr01 and the first eigenvalue is 1f7e5da00e8782f1, when the medical record file is downloaded to the client for the first time, the name of the medical record file based on the first preset naming mode is: emr01.1f7e5da00e8782f1. That is, the name of the medical record file at the client is: emr01.1f7e5da00e8782f1.
Then, as can be seen from the above, the name of the medical record file at the client is related to the second eigenvalue, and the name of the medical record file at the client is related to the first eigenvalue. The second characteristic value is related to the file content of the medical record file stored by the server, and the first characteristic value is related to the file content of the medical record file stored by the server. Based on the above, when the naming name determined for the medical record file stored in the server based on the first preset naming mode is different from the naming name of the local medical record file at the client, it is indicated that the medical record file stored in the server is changed, the local medical record file at the client is not changed in synchronization with the server, and the medical record file stored at the client is not the latest medical record file. Similarly, whether the course file stored locally at the client is the latest course file may also be determined by determining whether the name determined for the course file stored at the server based on the second preset naming mode is the same as the name of the local course file at the client.
The execution method of "determining the target course file to be downloaded from the server" in step S11 will be described in detail based on the above description.
Specifically, the step of determining the target course file to be downloaded from the server may include:
step a, determining a disease course file required to be used from a server.
Different course files correspond to different file identifiers, and when the client determines the course file to be used, the server searches the course file to be used on the basis of the file identifier of the course file to be used.
For example, suppose that a course file a of a patient a needs to be searched, where a file identifier corresponding to the course file a of the patient a is "001", at this time, the client may search the course file a that needs to be used at the server based on the file identifier 001.
And b, naming the disease course file to be used by adopting the second preset naming mode to obtain a second name.
Wherein the second default naming method is as follows: and taking the disease process file name corresponding to the disease process file required to be used as a file name, and taking the second characteristic value corresponding to the disease process file required to be used as an extension.
And c, determining whether the disease course file with the same second name as the disease course file needing to be used by the server exists locally at the client, if so, executing the step d, and if not, executing the step e.
And d, directly using the disease course file which is local at the client and has the same name as the second name without downloading the disease course file to be used from the server.
If the disease course file with the same second name as the disease course file needing to be used by the server exists locally at the client, the file contents of the disease course file local at the client are consistent with those of the disease course file at the server, and at the moment, the disease course file local at the client can be directly used without additionally downloading the disease course file from the server, so that the network flow can be saved, the response speed of medical record operation is increased, and the efficiency is higher.
And e, determining the disease course file required to be used by the server as a target disease course file.
If the client does not locally have the course file with the same second name as the course file needing to be used by the server, it is indicated that the course file needing to be used may not be locally stored by the client, or the local course file needing to be used by the client is inconsistent with the file content of the course file of the server (i.e., the local course file needing to be used by the client is not the latest file content), at this time, the course file needing to be used is determined as the target course file, and then steps S12 to S13 follow to download the target course file.
In step S12, the target medical record file to be downloaded is determined from the target medical record file based on the first feature value of the medical record file in the target medical record file of the server.
The target medical record file to be downloaded specifically comprises: and during the period from the moment when the client downloads the target course file last to the current moment, the medical record file with changed file content in the target course file of the server and/or the medical record file newly added in the target course file of the server.
Specifically, the specific execution method of step S12 includes the following steps:
step 1, naming each medical record file in a target medical record file of a server side by adopting a first preset naming mode to obtain a first name corresponding to each medical record file.
Wherein the first predetermined naming scheme is substantially: and taking the medical record file name of the medical record file of the server as the file name of the medical record file, and taking the first characteristic value corresponding to the medical record file of the server as the extension of the medical record file.
Step 2, determining a medical record file with the same file name but different extension name as that of a medical record file of the client side in a target medical record file of the server side as a target medical record file; and/or determining the medical record file of which the file name does not exist in the client side in the target medical record file of the server side as the target medical record file.
When the file names of the medical record files of the server and the client are the same but the extensions of the medical record files are different, the server changes the medical record files from the last time the medical record files are downloaded by the client to the current time, and at the time, the medical record files of the client and the medical record files of the server are not changed synchronously, so that the medical record files of the target medical record files of the server, which are the same as the file names of the medical record files of the client but different from the extensions of the medical record files of the client, need to be determined as the target medical record files, so that the target medical record files are downloaded from the server, and the unseen contents of the medical record files of the client and the medical record files of the server are kept synchronous.
And when the file name in the medical record file in the target course of the server does not exist in the medical record file of the client, the medical record file is newly added to the server after the target course file is downloaded last time by the client, and at this time, the medical record file of which the file name does not exist in the client needs to be determined as the target medical record file, so that the target medical record file is downloaded from the server, and the medical record file of the client and the medical record file of the server are ensured to be synchronous in invisible content.
For example, it is assumed that the client downloads the course file a from the server last time, the course file a includes three medical record files, which are divided into a medical record file 1, a medical record file 2, and a medical record file 3, and after the client downloads the course file a from the server last time, the server changes the medical record file 1 in the course file a, and adds a medical record file 4 in the course file a. At this time, the first characteristic value of the medical record file 1 changes, and thus the extension of the naming name obtained for the medical record file 1 based on the first preset naming mode also changes, so that the medical record file 1 stored by the server and the medical record file 1 stored by the client have the same file name but different extensions, and thus the medical record file 1 of the server can be determined as the target medical record file. And because the medical record file 4 is newly added to the server, wherein the medical record file 4 does not exist in the client, the file name of the medical record file 4 also does not exist in the client, and the medical record file 4 can also be determined as the target medical record file at this time.
In step S13, the target medical record file is downloaded from the server.
Wherein, the step may specifically include:
and responding to the target medical record file and the medical record file of the client, wherein the file name of the target medical record file is the same as the file name of the medical record file of the client, but the extension name of the medical record file is different from the extension name of the medical record file of the client, and the medical record file is downloaded to the client based on the storage path corresponding to the target medical record file, named with the first name of the target medical record file, and deleted. For example, suppose the client stores a name for medical record file 1: emr01.1f7e5da00e8782f1, the server side modifies the medical record file 1 after the medical record file 1 is downloaded last time from the client side, and the modified medical record file 1 is named according to a first preset naming mode: emr01.E9dc8f15c57f3c03. At this time, if the client does not have emr01.e9dc8f15c57f3c03, the file with the same file name under the corresponding path is deleted, namely, emr01.1f7e5da00e8782f1 is deleted, and then emr01.e9dc8f15c57f3c03 is stored, so that the redundancy of the file can be prevented.
And in response to the fact that the file name of the target medical record file does not exist in the client, the medical record file is directly downloaded to the client based on the storage path corresponding to the target medical record file, and the first name is used for naming the target medical record file.
In summary, in this embodiment, when the target course file is to be downloaded, the medical record file that changes in the target course file of the server or the newly added medical record file is mainly downloaded to the client, and other medical record files that do not change in the target course file are not downloaded, so that network traffic can be saved, response speed of medical record operation is increased, and efficiency is improved.
In addition, it should be noted that, after the client downloads the target medical record file, a new medical record file may be obtained by merging and combining the downloaded target medical record file and other medical record files in the client, and the second name is determined as the name of the new medical record file.
For example, suppose that the client downloads the medical history file a from the server last time, and the medical history file a includes three medical history files, which are divided into a medical history file 1, a medical history file 2, and a medical history file 3. After the client downloads the course file A, the name of the course file A is determined based on a second preset naming mode: emr01.E9dc8f15c57f3c04; and determining the respective names of the medical record file 1, the medical record file 2 and the medical record file 3 based on a first preset naming mode: emr01. E9d8f15c57f3c05, emr01. E9d8f15c57f3c06, and emr01. E9d8f15c57f3c07. And after the medical record file A is downloaded from the server last time at the client, the server changes the medical record file 1 in the medical record file A. The medical record file 1 after the change is named based on a first preset naming mode: emr01.E9dc8f15c57f3c10, and the file content of the disease course file A is changed due to the change of the file content of the medical record file 1, and the changed disease course file A is named based on a second preset naming mode: emr01. E9d8f15c57f3c11. At this time, if the client needs to use the medical procedure file a, the medical procedure file a needs to be determined from the server first, and the medical record file 1 in the medical procedure file a is determined to be the target medical record file based on the name, at this time, only the changed medical record file 1 is downloaded from the server, and the changed medical record file 1 is named by using emr01.E9dc8f15c57f3c10, and the previously stored medical record file 1 named "emr01. E9dc8f15c573c05" is deleted at the same time. And the downloaded changed medical record file 1, the previously stored medical record files 2 and 3 are recombined and combined to obtain a new medical record file, and the new medical record file is named as: emr01.E9dc8f15c57f3c11.
Fig. 2 is a block diagram illustrating an electronic medical record processing apparatus according to an exemplary embodiment. Referring to fig. 2, the apparatus includes:
the system comprises a first determination module, a second determination module and a third determination module, wherein the first determination module is used for determining a target medical procedure file to be downloaded from a server, the server stores at least one medical procedure file, the medical procedure file comprises at least one medical record file, each medical record file corresponds to a first characteristic value, the first characteristic values stored by the server are obtained by calculating the content of the medical record file corresponding to the server, and when the file content in the medical record file stored by the server changes, the first characteristic values corresponding to the medical record file stored by the server also change correspondingly;
the second determination module is used for determining a target medical record file to be downloaded from the target medical record file based on the first characteristic value of the medical record file in the target medical record file of the server; wherein, the target medical record file is: during the period from the moment when the client downloads the target course file last to the current moment, the medical record file with changed file content in the target course file of the server and/or a medical record file newly added in the target course file of the server;
and the downloading module is used for downloading the target medical record file from the server.
In summary, in some or related embodiments, when the target course file is to be downloaded, the medical record file that changes in the target course file of the server or the newly added medical record file is mainly downloaded to the client, and other medical record files that do not change in the target course file are not downloaded, so that network traffic can be saved, response speed of medical record operation is increased, and efficiency is improved.
Optionally, the medical record file includes, but is not limited to, at least one of a patient identifier ID, a number of hospitalizations, an outpatient number of hospitalization, a medical record file number, a storage path, a medical record file name, a doctor, and a first characteristic value;
when the medical record file is downloaded by the client for the first time, the medical record file is downloaded to the client based on the storage path of the medical record file stored by the server, and the medical record file is named based on the name of the medical record file and a first characteristic value corresponding to the medical record file by adopting a first preset naming mode; wherein the first preset naming mode is as follows: and taking the medical record file name as the file name of the medical record file, and taking the first characteristic value as the extension of the medical record file.
Optionally, the second determining module is configured to:
naming each medical record file in the target medical record file of the server side by adopting the first preset naming mode to obtain a first name;
determining a medical record file with the same file name and different extension name as a medical record file of a client in the target medical record file of the server as the target medical record file; and/or determining the medical record file of which the file name does not exist in the client side in the target medical record file of the server side as the target medical record file.
Optionally, the downloading module is configured to:
in response to the fact that the file names of the target medical record file and the medical record file of the client are the same but the extension names of the target medical record file and the medical record file of the client are different, the medical record file is downloaded to the client based on the storage path corresponding to the target medical record file, the target medical record file is named by the first name, and the medical record file which is the same as the file name of the target medical record file but the extension name of the target medical record file is deleted;
and responding to the fact that the file name of the target medical record file does not exist in the client, directly downloading the medical record file to the client based on the storage path corresponding to the target medical record file, and naming the target medical record file by using the first name.
Optionally, the disease course file includes, but is not limited to, at least one of a storage path, a disease course file name, and a second feature value; the second characteristic value is obtained by calculating the content of the disease course file corresponding to the server side, and when the file content in the disease course file stored by the server side changes, the second characteristic value corresponding to the disease course file stored by the server side also changes correspondingly;
when the client downloads the course file for the first time, the course file is downloaded to the client based on a storage path of the course file stored by the server, and the course file is named based on the course file name and a second characteristic value corresponding to the course file by adopting a second preset naming mode; wherein the second preset naming mode is as follows: and taking the disease process file name as the file name of the disease process file, and taking the second characteristic value as the extension of the disease process file.
Optionally, the second determining module is configured to:
determining a course file to be used from the server, and naming the course file to be used from the server based on a second preset naming mode to obtain a second name;
determining whether the client locally has a disease course file with the same name as the second name;
if the disease course file exists, the disease course file which needs to be used does not need to be downloaded from the server, and the local disease course file with the same name as the second name of the client is directly used;
if not, determining the disease course file required to be used by the server as a target disease course file.
FIG. 3 is a block diagram illustrating a server in accordance with an example embodiment. As shown in fig. 3, the server includes: a memory 301 and a processor 302. In addition, the server includes necessary components such as a power component 303, a communication component 304, and the like.
The memory 301 is used for storing computer programs and may be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device.
The memory 301, which may be implemented by any type of volatile or non-volatile memory device or combination thereof, may include, for example, static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A communication component 303 for data transmission with other devices.
The processor 302 may execute computer instructions stored in the memory 301 for performing the above-described method.
Correspondingly, the embodiment of the application also provides a computer readable storage medium storing the computer program. The computer-readable storage medium stores a computer program, and the computer program, when executed by one or more processors, causes the one or more processors to perform the steps in the method embodiment of fig. 1.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
The above are merely exemplary embodiments of the present application and are intended to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice in the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (9)
1. An electronic medical record processing method is applied to a client and comprises the following steps:
determining a target medical procedure file to be downloaded from a server, wherein the server stores at least one medical procedure file, the medical procedure file comprises at least one medical record file, each medical record file corresponds to a first characteristic value, the first characteristic value stored by the server is obtained by calculating the content of the medical record file corresponding to the server, and when the file content in the medical record file stored by the server changes, the first characteristic value corresponding to the medical record file stored by the server also changes correspondingly;
determining a target medical record file to be downloaded from the target medical record file based on a first characteristic value of the medical record file in the target medical record file of the server; wherein, the target medical record file is as follows: during the period from the moment when the client downloads the target course file last to the current moment, the medical record file with changed file content in the target course file of the server and/or a medical record file newly added in the target course file of the server;
and downloading the target medical record file from a server.
2. The method of claim 1, wherein the medical record file includes, but is not limited to, at least one of a patient Identification (ID), a number of hospitalizations, an outpatient number, a medical record file number, a storage path, a medical record file name, a doctor, a first characteristic value;
when the medical record file is downloaded by the client for the first time, the medical record file is downloaded to the client based on a storage path of the medical record file stored by the server, and the medical record file is named by adopting a first preset naming mode based on the name of the medical record file and a first characteristic value corresponding to the medical record file; wherein the first preset naming mode is as follows: and taking the medical record file name as the file name of the medical record file, and taking the first characteristic value as the extension of the medical record file.
3. The method according to claim 2, wherein determining the target medical record file to be downloaded from the target medical record file based on the first characteristic value of the medical record file in the target medical record file comprises:
naming each medical record file in the target medical record file of the server side by adopting the first preset naming mode to obtain a first name;
determining a medical record file with the same file name but different extension name as that of a medical record file of a client side in a target medical record file of the server side as the target medical record file; and/or determining the medical record file of which the file name does not exist in the client side in the target medical record file of the server side as the target medical record file.
4. The method of claim 3, wherein the downloading the target medical record file from the server comprises:
in response to the fact that the file names of the target medical record file and the medical record file of the client are the same but the extension names of the target medical record file and the medical record file are different, the medical record file is downloaded to the client based on the storage path corresponding to the target medical record file, the target medical record file is named by the first name, and the medical record file which is the same as the file name of the target medical record file but different in extension name is deleted;
and responding to the fact that the file name of the target medical record file does not exist in the client, directly downloading the medical record file to the client based on the storage path corresponding to the target medical record file, and naming the target medical record file by using the first name.
5. The method of claim 1, wherein the course file includes, but is not limited to, at least one of a storage path, a course file name, a second feature value; the second characteristic value is obtained by calculating the content of the disease course file corresponding to the server side, and when the file content in the disease course file stored by the server side changes, the second characteristic value corresponding to the disease course file stored by the server side also changes correspondingly;
when the client downloads the course file for the first time, the course file is downloaded to the client based on a storage path of the course file stored by the server, and the course file is named based on the course file name and a second characteristic value corresponding to the course file by adopting a second preset naming mode; wherein the second preset naming mode is as follows: and taking the disease process file name as the file name of the disease process file, and taking the second characteristic value as the extension of the disease process file.
6. The method according to claim 5, wherein the determining the target course file to be downloaded from the server comprises:
determining a course file to be used from the server, and naming the course file to be used from the server based on a second preset naming mode to obtain a second name;
determining whether the client locally has a disease course file with the same name as the second name;
if yes, the disease course file which needs to be used is not required to be downloaded from the server, and the local disease course file with the same name as the second name of the client is directly used;
and if not, determining the disease course file required to be used by the server as a target disease course file.
7. An electronic medical record processing apparatus, comprising:
the system comprises a first determination module, a second determination module and a third determination module, wherein the first determination module is used for determining a target medical procedure file to be downloaded from a server, the server stores at least one medical procedure file, the medical procedure file comprises at least one medical record file, each medical record file corresponds to a first characteristic value, the first characteristic values stored by the server are obtained by calculating the content of the medical record file corresponding to the server, and when the file content in the medical record file stored by the server changes, the first characteristic values corresponding to the medical record file stored by the server also change correspondingly;
the second determination module is used for determining a target medical record file to be downloaded from the target medical record file based on the first characteristic value of the medical record file in the target medical record file of the server; wherein, the target medical record file is as follows: during the period from the last time of downloading the target course file to the current time by the client, the medical record file with changed file content in the target course file of the server and/or the medical record file newly added in the target course file of the server;
and the downloading module is used for downloading the target medical record file from the server.
8. A client, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the electronic medical record processing method of any one of claims 1 to 6.
9. A storage medium in which instructions, when executed by a processor of a client, enable the client to perform the electronic medical record processing method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211186440.1A CN115274038B (en) | 2022-09-28 | 2022-09-28 | Electronic medical record processing method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211186440.1A CN115274038B (en) | 2022-09-28 | 2022-09-28 | Electronic medical record processing method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115274038A CN115274038A (en) | 2022-11-01 |
| CN115274038B true CN115274038B (en) | 2022-12-16 |
Family
ID=83757599
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211186440.1A Active CN115274038B (en) | 2022-09-28 | 2022-09-28 | Electronic medical record processing method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115274038B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022161273A1 (en) * | 2021-01-28 | 2022-08-04 | 维沃移动通信有限公司 | File saving method and apparatus, device, and storage medium |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106681863B (en) * | 2016-12-30 | 2019-09-17 | 北京天健源达科技股份有限公司 | Save the method and terminal device of electronic health record content of edit |
| US11269816B2 (en) * | 2019-03-25 | 2022-03-08 | Parallels International Gmbh | Recent file synchronization and aggregation methods and systems |
| CN110911010A (en) * | 2019-11-25 | 2020-03-24 | 深圳安泰创新科技股份有限公司 | Diagnosis and treatment scheme generation method, electronic equipment and computer-readable storage medium |
| US11507541B2 (en) * | 2020-01-21 | 2022-11-22 | Microsoft Technology Licensing, Llc | Method to model server-client sync conflicts using version trees |
| CN112002384A (en) * | 2020-07-14 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Method and device for summarizing medical record information, computer equipment and storage medium |
| CN111916170A (en) * | 2020-07-22 | 2020-11-10 | 北京致医健康信息技术有限公司 | Medical history reminding method, management server and electronic medical record management system |
| CN111863171A (en) * | 2020-07-22 | 2020-10-30 | 北京致医健康信息技术有限公司 | Electronic medical record management method, management server and electronic medical record management system |
| CN114528148A (en) * | 2020-10-30 | 2022-05-24 | 伊姆西Ip控股有限责任公司 | Method, electronic device and computer program product for storage management |
-
2022
- 2022-09-28 CN CN202211186440.1A patent/CN115274038B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022161273A1 (en) * | 2021-01-28 | 2022-08-04 | 维沃移动通信有限公司 | File saving method and apparatus, device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115274038A (en) | 2022-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109145205B (en) | Cross-chain data operation method and device based on block chain | |
| RU2673403C2 (en) | Website access method, device and website system | |
| US11741046B2 (en) | Method and apparatus for creating system disk snapshot of virtual machine | |
| US20200241870A1 (en) | Version management automation and consistent application builds for different target systems | |
| US8195608B2 (en) | File synchronization between multiple nodes | |
| US20200073575A1 (en) | Integrated hierarchical storage management | |
| CN108616599B (en) | Method and device for registering and updating application service | |
| CN104820602A (en) | Method, device and system for publishing software package | |
| US20090288077A1 (en) | Runtime versioning and distribution of dynamic web-elements | |
| US9146841B2 (en) | Proxy server assisted product testing | |
| CN112148678B (en) | File access method, system, device and medium | |
| CN105183760A (en) | Webpage component loading method and apparatus | |
| RU2544774C2 (en) | Database application navigation | |
| CN112783848A (en) | Data synchronization method and device and electronic equipment | |
| CN110597764B (en) | File downloading and version management method and device | |
| CN115274038B (en) | Electronic medical record processing method, device, server and storage medium | |
| CN107291524B (en) | Remote command processing method and device | |
| CN112559118A (en) | Application data migration method and device, electronic equipment and storage medium | |
| CN107103001B (en) | Method, device and system for acquiring target front-end resource file based on browser | |
| CN112445986A (en) | Cache information updating method, cache information pushing method, cache information updating device, cache information pushing device and cache information pushing medium | |
| CN115586872A (en) | Container mirror image management method, device, equipment and storage medium | |
| US20170255534A1 (en) | Processing file modifications in a networked storage system | |
| CN111400243B (en) | Development management system based on pipeline service and file storage method and device | |
| CN111625397A (en) | Service log backup method, cluster, device, electronic equipment and storage medium | |
| US20220405244A1 (en) | Batch deletion method and apparatus for cache contents, device and readable storage medium |
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 |