CN114334111B - Medical information management method, device, server and readable storage medium - Google Patents
Medical information management method, device, server and readable storage medium Download PDFInfo
- Publication number
- CN114334111B CN114334111B CN202111649154.XA CN202111649154A CN114334111B CN 114334111 B CN114334111 B CN 114334111B CN 202111649154 A CN202111649154 A CN 202111649154A CN 114334111 B CN114334111 B CN 114334111B
- Authority
- CN
- China
- Prior art keywords
- service information
- outpatient
- metadata
- medical
- statistics
- 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
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A90/00—Technologies having an indirect contribution to adaptation to climate change
- Y02A90/10—Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation
Landscapes
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The application provides a medical information management method, a device, a server and a readable storage medium, which relate to the technical field of medical information management, are based on the fact that at least one metadata is used for describing service information groups, when medical service information sent by a first client is received, the service information groups with the same metadata as the medical service information are used as first target service information groups, so that the medical service information is stored with the first target service information groups, and when medical service information stored in the server is counted, compared with the prior art, a plurality of service information groups can be distinguished according to different metadata, and the statistical difference among similar service information groups is determined, so that the medical information is convenient to manage.
Description
The application is a divisional application, the application number of the mother application: 201910054770.7, parent case name: medical information management method, device, server and readable storage medium, and the application date of the parent case: 05 month 31 days 2019.
Technical Field
The present application relates to the technical field of medical information management, and in particular, to a medical information management method, a device, a server, and a readable storage medium.
Background
The medical information is similar due to the diversity of the statistical caliber, and the similar medical information is different due to the different statistical caliber, so that large difference exists between the similar medical information, and the actual effective medical information is difficult to determine, so that the medical information is inconvenient to manage.
Disclosure of Invention
The application aims to provide a medical information management method, a medical information management device, a server and a readable storage medium, which are convenient for managing medical information.
In order to achieve the above object, the technical scheme adopted by the embodiment of the application is as follows:
in a first aspect, an embodiment of the present application provides a medical information management method, which is applied to a server, where a plurality of service information groups are stored in the server, where each service information group corresponds to at least one metadata for describing the corresponding service information group; the method comprises the following steps:
receiving medical service information sent by a first client, wherein the medical service information corresponds to at least one piece of metadata;
determining a first target service information group having the same metadata as the medical service information among the plurality of service information groups;
and storing the medical service information in the first target service information group.
In a second aspect, an embodiment of the present application provides a medical information management apparatus, which is applied to a server, where a plurality of service information groups are stored in the server, and each service information group corresponds to at least one metadata for describing the corresponding service information group; the device comprises:
the receiving and transmitting module is used for receiving medical service information sent by the first client, wherein the medical service information corresponds to at least one piece of metadata;
a processing module, configured to determine a first target service information group having the same metadata as the medical service information from the plurality of service information groups;
the processing module is further configured to store the medical service information in the first target service information group.
In a third aspect, embodiments of the present application provide a server including a memory for storing one or more programs; a processor. The above-described medical information management method is implemented when the one or more programs are executed by the processor.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the medical information management method described above.
According to the medical information management method, the device, the server and the readable storage medium, based on the fact that at least one metadata is used for describing the service information groups, when medical service information sent by the first client is received, the service information groups with the same metadata as the medical service information are used as the first target service information groups, the medical service information is stored with the first target service information groups, and therefore when medical service information stored in the server is counted, compared with the prior art, the plurality of service information groups can be distinguished according to the data based on different metadata, the statistical difference among the similar service information groups is determined, and management of the medical information is facilitated.
In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
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 schematic view of an application scenario of a medical information management method according to an embodiment of the present application;
FIG. 2 is a schematic block diagram of a server according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of a medical information management method according to an embodiment of the present application;
FIG. 4 is another schematic flow chart of a medical information management method according to an embodiment of the present application;
FIG. 5 is a schematic flow chart of a medical information management method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a medical information management apparatus according to an embodiment of the present application.
In the figure: 100-server; 110-a first client; 120-a second client; 101-memory; 102-a processor; 103-a communication interface; 300-medical information management device; 301-a transceiver module; 302-a processing module.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
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.
It is noted that relational terms such as first and second, and the like are 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. Moreover, 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 one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
Referring to fig. 1, fig. 1 is a schematic diagram of an application scenario of a medical information management method according to an embodiment of the present application, in an embodiment of the present application, a server 100, a first client 110 and a second client 120 are located in a wireless network or a wired network, and through the wireless network or the wired network, the server 100 performs data interaction with the first client 110 and the second client 120 respectively.
In an embodiment of the present application, the first client 110 or the second client 120 may be a mobile terminal device, which may include, for example, a smart phone, a tablet computer, a laptop computer, a car computer, a wearable mobile terminal, and so on.
The medical information management method provided by the embodiment of the application is applied to the server 100 shown in fig. 1, an application program is installed in the server 100, and corresponds to the first client 110 and the second client 120, and provides services for users. For example, the first client 110 may be an operation terminal used by a staff in a financial room or an operation terminal used by a doctor in an office, and the second client 120 may be an operation terminal used by a staff managing medical information, and interact with data of the server 100 through the first client 110 and the second client 120, respectively, so as to manage the medical information.
As described above, the medical information has a large difference between similar medical information due to the diversity of the statistical aperture, and it is difficult to determine the actual effective medical information.
For example, taking the "outpatient times" for a period of time as an example, a financial department may report 9 tens of thousands of people, but an outpatient department may report 10 tens of thousands of people, which results in the same "outpatient times", and there is a difference of 1 ten thousands of people between two different departments, so that a manager cannot learn which "outpatient times" is exactly.
Then, the inventor found in practical work that in the prior art, similar medical information is not uniform, and the reason is that: different departments may have different statistical apertures for similar medical information, resulting in similar medical information.
For example, in the application scenario of the statistics of "clinic times", 9 tens of thousands of times reported by the financial department may be counted, the counted caliber may be the clinic patient who has already charged and printed the registration fee, and the counted "clinic times" is the angle of standing in possession of the registration record; the outpatient department counts 10 ten thousand reported persons, the counted caliber may be all patients diagnosed and treated in the normal outpatient process, and the counted 'outpatient times' are the angles of the diagnosis and treatment actions of the patients after the outpatient is in the normal outpatient, so that the resources of the outpatient are consumed, and the patients are treated.
Therefore, if some patients are not registered and the registration fee is not paid, the resources of the outpatient are actually consumed, and the patients can be counted by the outpatient department and cannot be counted by the financial department, so that the same statistics of the clinic times is performed, but the medical information of the two departments is different.
However, it is reasonable to analyze the two different "outpatient times", 9 ten thousand "outpatient times" and 10 ten thousand "outpatient times" in practice, so that the manager cannot learn the accurate "outpatient times", because the manager cannot learn the meanings specifically represented by the two "outpatient times", and thus cannot learn the accurate "outpatient times".
Based on the above-mentioned drawbacks, one possible implementation manner provided by the embodiment of the present application is: based on using at least one metadata for describing the service information group, and receiving the medical service information transmitted by the first client, the service information group having the same metadata as the medical service information is used as the first target service information group to store the medical service information with the first target service information group.
Referring to fig. 2, fig. 2 is a schematic block diagram of a server 100 according to an embodiment of the application. In the embodiment of the present application, the server 100 includes a memory 101, a processor 102 and a communication interface 103, where the memory 101, the processor 102 and the communication interface 103 are directly or indirectly electrically connected to each other to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 101 may be used to store software programs and modules, such as program instructions/modules corresponding to the medical information management apparatus 300 provided in the embodiment of the present application, and the processor 102 executes the software programs and modules stored in the memory 101, thereby performing various functional applications and data processing to implement the medical information management method provided in the embodiment of the present application. The communication interface 103 may be used for communication of signaling or data with other node devices.
The Memory 101 may be, but is not limited to, a random access Memory (Random Access Memory, RAM), a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-Only Memory, PROM), an erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
The processor 102 may be an integrated circuit chip with signal processing capabilities. The processor 102 may be a general purpose processor including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processing, DSP)), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
It is to be understood that the structure shown in fig. 2 is merely illustrative, and that the server 100 may also include more or fewer components than shown in fig. 2, or have a different configuration than shown in fig. 2. The components shown in fig. 2 may be implemented in hardware, software, or a combination thereof.
The medical management method provided by the embodiment of the application is exemplified by counting the number of times of clinic.
Referring to fig. 3, fig. 3 is a schematic flowchart of a medical information management method according to an embodiment of the present application, where the medical information management method is applied to the server 100 shown in fig. 1, and includes the following steps:
s201, medical service information sent by a first client is received.
S202, determining a first target service information group with the same metadata as the medical service information from the plurality of service information groups.
And S203, storing the medical service information in the first target service information group.
In the embodiment of the present application, a plurality of service information sets are stored in the server 100, and each service information set corresponds to at least one metadata for describing the corresponding service information set.
For example, the "outpatient times" are exemplified as the service information group, and two "outpatient times" are stored in the server 100, but the two "outpatient times" correspond to different metadata for distinguishing the two "outpatient times". For example, metadata corresponding to each of the two "outpatient times" may be "outpatient statistics registration" and "outpatient statistics visit", respectively.
Accordingly, the first client 110 may be an operation terminal used by a staff member of a financial office or an operation terminal used by a doctor in an office, and the user corresponds to at least one piece of metadata in generating medical service information at the first client 110. For example, taking the above "clinic times" as an example, if the first client 110 is used as an operation terminal for staff in a financial room, when medical service information is generated, metadata corresponding to the medical service information is "clinic statistics registration"; accordingly, if the first client 110 is used as an operation terminal for a doctor in an office, the medical service information is generated such that the metadata corresponding to the medical service information is "outpatient statistics visit".
Accordingly, the server 100 determines a first target service information group having the same metadata as the received medical service information among the stored service information groups according to at least one metadata corresponding to the received medical service information transmitted from the first client 110, thereby storing the medical service information with the first target service information group.
For example, in the above example, if the metadata corresponding to the medical service information received by the server 100 is "outpatient statistics registration", the "outpatient times" corresponding to the metadata is "outpatient statistics registration" is taken as the first target service information group, and the medical service information is stored in the "outpatient times" corresponding to the metadata is "outpatient statistics registration"; alternatively, if the metadata corresponding to the medical service information received by the server 100 is "outpatient statistics visit", the metadata is "outpatient times" corresponding to "outpatient statistics visit", and the medical service information is stored in the "outpatient times" corresponding to "outpatient statistics visit", as the first target service information group.
Thus, in the example described above, for example, in the manner in which the service information group is described based on metadata, two "outpatient times" are described by different metadata ("outpatient statistics registration" and "outpatient statistics visit"), so that a manager determines, when the statistics know that the two "outpatient times" are different, that a difference exists between the two "outpatient times" according to the respective metadata.
Based on the above design, according to the medical information management method provided by the embodiment of the application, based on the use of at least one metadata for describing the service information group, and when receiving the medical service information sent by the first client 110, the service information group having the same metadata as the medical service information is used as the first target service information group, so as to store the medical service information with the first target service information group, thereby, when the medical service information stored in the server 100 is counted, compared with the prior art, the plurality of service information groups can be distinguished according to the data based on different metadata, and the statistical difference between the similar service information groups is determined, so that the medical information can be managed conveniently.
As described above, the method of managing medical information based on metadata can facilitate management of medical information, but as medical information increases, if metadata corresponding to medical service information generated by a certain client is changed due to the influence of a policy, historical medical service information and newly entered medical service information may not be fused, and a fault may occur in medical service information.
Based on this, referring to fig. 4, fig. 4 is another schematic flowchart of a medical information management method according to an embodiment of the present application, as a possible implementation manner, the medical information management method may further include the following steps:
s205, receiving a service information modification instruction sent by the second client.
S206, responding to the service information modification instruction, and modifying metadata corresponding to the second target service information group.
In the embodiment of the present application, the manager may modify the metadata of the service information group according to the actual situation, and then the manager sends a service information modification instruction to the server 100 through the second client 120, where the service information modification instruction is used to instruct to modify metadata corresponding to the second target service information group.
For example, with the influence of national policy, the national macro policy level requires all medical institutions to cancel drug addition, at this time, all service information groups related to drug income should be described as no drug addition, otherwise, if the same drug is used, the drug income before and after the drug addition is cancelled will be different, so that the manager cannot clearly learn the reason of the difference in income.
Therefore, the server 100 modifies the metadata corresponding to the second target service information group according to the received service information modification instruction sent by the second client 120.
As a possible implementation manner, when modifying metadata corresponding to the second target service information group, the server 100 may be: metadata corresponding to at least one second target service information group is added. For example, in the above example, "cancel drug addition" is added to the metadata corresponding to the second target service information group.
Alternatively, as another possible implementation manner, when modifying metadata corresponding to the second target service information, the server 100 may further be: and deleting at least one piece of metadata corresponding to the second target service information. For example, in the above example, if the subsequent policy allows drug addition, the "cancel drug addition" may be deleted from the metadata corresponding to the second target service information group.
It will be appreciated that, correspondingly, when the client generates the medical service information of the second target service information group, the corresponding metadata includes "cancel drug addition".
Based on the above design, according to the medical information management method provided by the embodiment of the application, the metadata corresponding to the medical service information generated by the client and the metadata corresponding to the second target service information group are kept uniform by updating the metadata corresponding to the second target service information group, so that the fusion of the historically stored medical service information and the newly recorded medical service information is ensured, and the continuity of the stored medical service information is ensured.
As a possible implementation, the manager may also make statistics on the healthcare information based on the metadata to learn about the operation of the hospital.
Referring to fig. 5, fig. 5 is a schematic flowchart of a medical information management method according to an embodiment of the present application, as another possible implementation manner, the medical information management method further includes the following steps:
s208, receiving a data statistics request sent by the second client.
S209, determining all third target service information groups containing at least one target metadata of the data statistics request from the plurality of service information groups.
S210, counting the sum of the quantity of the medical service information contained in all the third target service information groups as a target service information statistic value.
S211, the target service information statistical value is sent to the second client.
For example, taking the "outpatient times" corresponding to the "outpatient statistics registration" and the "outpatient times" corresponding to the "outpatient statistics visit" as an example, if at least one target metadata included in the data statistics request received by the server 100 is the "registration", the server 100 takes the "outpatient times" corresponding to the "outpatient statistics registration" as a third target service information group, counts the sum of the number of medical service information included in the "outpatient times" corresponding to the "outpatient statistics registration", for example, 9 ten thousand times, and sends the sum of the number of medical service information included in the "outpatient times" corresponding to the "outpatient statistics registration" as a target service information statistics value to the second client 120, so that the manager on the second client 120 side learns that the total number of registered people is 9 ten thousand; if at least one target metadata included in the data statistics request received by the server 100 is "outpatient statistics visit", the server 100 uses "outpatient times" corresponding to the "outpatient statistics visit" as a third target service information group, and counts the sum of the number of medical service information groups included in the "outpatient times" corresponding to the "outpatient statistics visit", for example, 10 ten thousand times, and sends the sum of the number of medical service information groups as a target service information statistics value to the second client 120, so that a manager on the side of the second client 120 learns that the total number of actual doctor visits is 10 ten thousand.
Fig. 6 is a schematic structural diagram of a medical information management apparatus 300 according to an embodiment of the present application, where the medical information management apparatus 300 is applied to a server 100 as shown in fig. 1, a plurality of service information sets are stored in the server 100, each service information set corresponds to at least one metadata describing the corresponding service information set, and the medical information management apparatus 300 includes a transceiver module 301 and a processing module 302.
The transceiver module 301 is configured to receive medical service information sent by the first client 110, where the medical service information corresponds to at least one piece of metadata.
The processing module 302 is configured to determine a first target service information group having the same metadata as the medical service information from the plurality of service information groups.
The processing module 302 is further configured to store the medical service information in the first set of target service information.
Optionally, as a possible implementation manner, the transceiver module 301 is further configured to receive a service information modification instruction sent by the second client 120, where the service information modification instruction is used to instruct modification of metadata corresponding to the second target service information group.
The processing module 302 is further configured to modify metadata corresponding to the second target service information group in response to the service information modification instruction.
Optionally, as a possible implementation manner, the processing module 302 is specifically configured to, when modifying metadata corresponding to the second target service information group:
adding metadata corresponding to at least one second target service information group; or deleting at least one piece of metadata corresponding to the second target service information group.
Optionally, as a possible implementation manner, the transceiver module 301 is further configured to receive a data statistics request sent by the second client 120, where the data statistics request includes at least one target metadata.
The processing module 302 is further configured to determine all third target service information groups including at least one target metadata of the data statistics request from the plurality of service information groups.
The processing module 302 is further configured to count the sum of the amounts of the medical service information included in all the third target service information groups as the target service information statistics.
The transceiver module 301 is further configured to send the target service information statistics to the second client 120.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, of the flowcharts and block diagrams in the figures that illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, each functional module in the embodiment of the present application may be integrated together to form a separate part, or each module may exist alone, or two or more modules may be integrated to form a separate part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiment of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In summary, according to the medical information management method, device, server and readable storage medium provided by the embodiments of the present application, based on using at least one metadata to describe a service information group, and when receiving medical service information sent by a first client, a service information group having the same metadata as the medical service information is used as a first target service information group, so as to store the medical service information with the first target service information group, when the medical service information stored in the server is counted, compared with the prior art, a plurality of service information groups can be distinguished according to different metadata, and a statistical difference between similar service information groups is determined, so that the medical information is convenient to manage; the metadata corresponding to the medical service information generated by the client and the metadata corresponding to the second target service information group are kept uniform by updating the metadata corresponding to the second target service information group, so that the fusion of the medical service information stored in history and the medical service information newly input is ensured, and the continuity of the stored medical service information is ensured;
the above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (8)
1. The medical information management method is characterized by being applied to a server, wherein the server performs data interaction with a first client and a second client respectively; the server stores two outpatient service information groups, and metadata corresponding to the two outpatient service information groups are outpatient statistics registration metadata and outpatient statistics visit metadata; the method comprises the following steps:
receiving medical service information sent by a first client, wherein the medical service information corresponds to metadata;
if the first client is an operation terminal used by financial staff, the metadata corresponding to the medical service information is the outpatient statistics registration metadata, and the medical service information is stored in an outpatient service information group corresponding to the outpatient statistics registration metadata;
if the first client is an operation terminal used by medical staff, the metadata corresponding to the medical service information is the outpatient statistics visit metadata, and the medical service information is stored in an outpatient service information group corresponding to the outpatient statistics visit metadata.
2. The method of claim 1, wherein the second client is an operator terminal used by a medical information manager; the method further comprises the steps of:
receiving a data statistics request sent by the second client;
if the data statistics request comprises the outpatient statistics registration metadata, taking an outpatient service information group corresponding to the outpatient statistics registration metadata as a third target service information group, and counting the sum of the quantity of medical service information contained in the third target service information group as a target service information statistics value;
and sending the target service information statistical value to the second client.
3. The method of claim 2, wherein after the step of receiving the data statistics request sent by the second client, the method further comprises:
if the data statistics request comprises the outpatient statistics visit metadata, taking an outpatient service information group corresponding to the outpatient statistics visit metadata as a third target service information group, and counting the sum of the quantity of medical service information contained in the third target service information group as a target service information statistics value;
and sending the target service information statistical value to the second client.
4. The medical information management device is characterized by being applied to a server, wherein the server respectively performs data interaction with a first client and a second client; the server stores two outpatient service information groups, and metadata corresponding to the two outpatient service information groups are outpatient statistics registration metadata and outpatient statistics visit metadata; the device comprises:
the receiving and transmitting module is used for receiving medical service information sent by the first client, wherein the medical service information corresponds to metadata;
the processing module is used for if the first client is an operation terminal used by financial staff, the metadata corresponding to the medical service information is the outpatient statistics registration metadata, and the medical service information is stored in an outpatient service information group corresponding to the outpatient statistics registration metadata;
if the first client is an operation terminal used by medical staff, the metadata corresponding to the medical service information is the outpatient statistics visit metadata, and the medical service information is stored in an outpatient service information group corresponding to the outpatient statistics visit metadata.
5. The apparatus of claim 4, wherein the second client is an operation terminal used by a medical information manager;
the transceiver module is further configured to: receiving a data statistics request sent by the second client;
the processing module is further configured to: if the data statistics request comprises the outpatient statistics registration metadata, taking an outpatient service information group corresponding to the outpatient statistics registration metadata as a third target service information group, and counting the sum of the quantity of medical service information contained in the third target service information group as a target service information statistics value;
and sending the target service information statistical value to the second client.
6. The apparatus of claim 5, wherein the processing module is further configured to:
if the data statistics request comprises the outpatient statistics visit metadata, taking an outpatient service information group corresponding to the outpatient statistics visit metadata as a third target service information group, and counting the sum of the quantity of medical service information contained in the third target service information group as a target service information statistics value;
and sending the target service information statistical value to the second client.
7. A server, comprising:
a memory for storing one or more programs;
a processor;
the method of any of claims 1-3 being implemented when the one or more programs are executed by the processor.
8. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111649154.XA CN114334111B (en) | 2019-01-21 | 2019-01-21 | Medical information management method, device, server and readable storage medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111649154.XA CN114334111B (en) | 2019-01-21 | 2019-01-21 | Medical information management method, device, server and readable storage medium |
| CN201910054770.7A CN109830290A (en) | 2019-01-21 | 2019-01-21 | Method for managing medical information, device, server and readable storage medium storing program for executing |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910054770.7A Division CN109830290A (en) | 2019-01-21 | 2019-01-21 | Method for managing medical information, device, server and readable storage medium storing program for executing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114334111A CN114334111A (en) | 2022-04-12 |
| CN114334111B true CN114334111B (en) | 2023-08-18 |
Family
ID=66861770
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910054770.7A Pending CN109830290A (en) | 2019-01-21 | 2019-01-21 | Method for managing medical information, device, server and readable storage medium storing program for executing |
| CN202111649154.XA Active CN114334111B (en) | 2019-01-21 | 2019-01-21 | Medical information management method, device, server and readable storage medium |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910054770.7A Pending CN109830290A (en) | 2019-01-21 | 2019-01-21 | Method for managing medical information, device, server and readable storage medium storing program for executing |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN109830290A (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109830290A (en) * | 2019-01-21 | 2019-05-31 | 四川大学华西医院 | Method for managing medical information, device, server and readable storage medium storing program for executing |
| CN111933267B (en) * | 2020-08-31 | 2023-07-18 | 深圳平安智慧医健科技有限公司 | Medical early warning method, device, computer equipment and computer readable storage medium |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN203849765U (en) * | 2013-01-15 | 2014-09-24 | 中国人民解放军第三军医大学第一附属医院 | Outpatient service registration system |
| CN104378430A (en) * | 2014-11-14 | 2015-02-25 | 小米科技有限责任公司 | Service information providing method and device |
| WO2016201737A1 (en) * | 2015-06-13 | 2016-12-22 | 深圳市共创百业科技开发有限公司 | Visit prompting method based on network hospital platform, and network hospital platform |
| CN106547918A (en) * | 2016-11-30 | 2017-03-29 | 长城计算机软件与系统有限公司 | A kind of integration method and system of statistical data |
| CN106777998A (en) * | 2016-12-19 | 2017-05-31 | 邹春秋 | A kind of medical system big data processing unit and method |
| CN107180472A (en) * | 2016-11-15 | 2017-09-19 | 廖奕熙 | Queuing system of being registered at community medical service center's outpatient service and application apparatus |
| CN107220918A (en) * | 2017-06-30 | 2017-09-29 | 王中显 | Patient medical history management method, device and server |
| CN107527307A (en) * | 2017-08-24 | 2017-12-29 | 杭州悦马爱赏科技股份有限公司 | Hospital admission management method, apparatus and system |
| CN109243043A (en) * | 2017-07-11 | 2019-01-18 | 北京医联蓝卡在线科技有限公司 | A kind of intelligent medical treatment system and method |
| CN109377059A (en) * | 2018-10-27 | 2019-02-22 | 平安医疗健康管理股份有限公司 | A kind of data processing method and equipment based on risk management and control |
| CN109545352A (en) * | 2018-11-23 | 2019-03-29 | 京东方科技集团股份有限公司 | Hospital guide's method of servicing, device, electronic equipment and storage medium |
| CN109830290A (en) * | 2019-01-21 | 2019-05-31 | 四川大学华西医院 | Method for managing medical information, device, server and readable storage medium storing program for executing |
| CN110148440A (en) * | 2019-03-29 | 2019-08-20 | 北京汉博信息技术有限公司 | A kind of medical information querying method |
| CN112328551A (en) * | 2020-11-09 | 2021-02-05 | 医渡云（北京）技术有限公司 | Medical data analysis method, device, medium, and electronic device |
| CN112509681A (en) * | 2020-12-08 | 2021-03-16 | 安徽李悦阳信息技术有限公司 | Intelligent medical service system based on big data |
| CN114334109A (en) * | 2021-12-28 | 2022-04-12 | 卫宁健康科技集团股份有限公司 | Monitoring method, device, equipment and storage medium for emergency green area |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20100058108A (en) * | 2008-11-24 | 2010-06-03 | (주)파인원커뮤니케이션즈 | Mrthod for synchronizing digital contents between digital apparatus |
| KR20110070366A (en) * | 2009-12-18 | 2011-06-24 | 에스케이 텔레콤주식회사 | Statistical system for unique visitor using a meta data and statistical method thereof |
| KR20140029984A (en) * | 2012-08-31 | 2014-03-11 | 한국전자통신연구원 | Medical information management method of medical database operating system |
| US10755369B2 (en) * | 2014-07-16 | 2020-08-25 | Parkland Center For Clinical Innovation | Client management tool system and method |
| CN106296522A (en) * | 2016-08-09 | 2017-01-04 | 浪潮集团有限公司 | Hospital queuing inquiry method based on big data |
| CN108595657B (en) * | 2018-04-28 | 2020-10-09 | 成都智信电子技术有限公司 | Data table classification mapping method and device of HIS (hardware-in-the-system) |
-
2019
- 2019-01-21 CN CN201910054770.7A patent/CN109830290A/en active Pending
- 2019-01-21 CN CN202111649154.XA patent/CN114334111B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN203849765U (en) * | 2013-01-15 | 2014-09-24 | 中国人民解放军第三军医大学第一附属医院 | Outpatient service registration system |
| CN104378430A (en) * | 2014-11-14 | 2015-02-25 | 小米科技有限责任公司 | Service information providing method and device |
| WO2016201737A1 (en) * | 2015-06-13 | 2016-12-22 | 深圳市共创百业科技开发有限公司 | Visit prompting method based on network hospital platform, and network hospital platform |
| CN107180472A (en) * | 2016-11-15 | 2017-09-19 | 廖奕熙 | Queuing system of being registered at community medical service center's outpatient service and application apparatus |
| CN106547918A (en) * | 2016-11-30 | 2017-03-29 | 长城计算机软件与系统有限公司 | A kind of integration method and system of statistical data |
| CN106777998A (en) * | 2016-12-19 | 2017-05-31 | 邹春秋 | A kind of medical system big data processing unit and method |
| CN107220918A (en) * | 2017-06-30 | 2017-09-29 | 王中显 | Patient medical history management method, device and server |
| CN109243043A (en) * | 2017-07-11 | 2019-01-18 | 北京医联蓝卡在线科技有限公司 | A kind of intelligent medical treatment system and method |
| CN107527307A (en) * | 2017-08-24 | 2017-12-29 | 杭州悦马爱赏科技股份有限公司 | Hospital admission management method, apparatus and system |
| CN109377059A (en) * | 2018-10-27 | 2019-02-22 | 平安医疗健康管理股份有限公司 | A kind of data processing method and equipment based on risk management and control |
| CN109545352A (en) * | 2018-11-23 | 2019-03-29 | 京东方科技集团股份有限公司 | Hospital guide's method of servicing, device, electronic equipment and storage medium |
| CN109830290A (en) * | 2019-01-21 | 2019-05-31 | 四川大学华西医院 | Method for managing medical information, device, server and readable storage medium storing program for executing |
| CN110148440A (en) * | 2019-03-29 | 2019-08-20 | 北京汉博信息技术有限公司 | A kind of medical information querying method |
| CN112328551A (en) * | 2020-11-09 | 2021-02-05 | 医渡云（北京）技术有限公司 | Medical data analysis method, device, medium, and electronic device |
| CN112509681A (en) * | 2020-12-08 | 2021-03-16 | 安徽李悦阳信息技术有限公司 | Intelligent medical service system based on big data |
| CN114334109A (en) * | 2021-12-28 | 2022-04-12 | 卫宁健康科技集团股份有限公司 | Monitoring method, device, equipment and storage medium for emergency green area |
Non-Patent Citations (1)
| Title |
|---|
| 顾伟.门诊运营监控系统的设计与开发.《医院数字化》.2016,第31卷(第11期),第91-93页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114334111A (en) | 2022-04-12 |
| CN109830290A (en) | 2019-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Rising et al. | Patient returns to the emergency department: the time‐to‐return curve | |
| US8214232B2 (en) | Healthcare insurance claim fraud detection using datasets derived from multiple insurers | |
| Vest | More than just a question of technology: factors related to hospitals’ adoption and implementation of health information exchange | |
| Ouhbi et al. | Free blood donation mobile applications | |
| US11323395B2 (en) | Computing device and method for message construction and processing based upon historical data | |
| Lewis et al. | Understanding the role of technology in health information systems | |
| US20200321087A1 (en) | System and method for recursive medical health document retrieval and network expansion | |
| Bazel et al. | Blockchain technology in healthcare big data management: Benefits, applications and challenges | |
| US20160378917A1 (en) | Imaging Study Queries Across Multiple Facilities And Repositories | |
| CN110245514B (en) | Distributed computing method and system based on block chain | |
| CN114334111B (en) | Medical information management method, device, server and readable storage medium | |
| US20160232298A1 (en) | Method, Apparatus, And Computer Program Product For Facilitating Query Initiation And Query Response | |
| Donahue et al. | Veterans health information exchange: successes and challenges of nationwide interoperability | |
| EP4160608A1 (en) | Prescription order distribution method, system and device, and storage medium | |
| US20170017758A1 (en) | Integrated system for obtaining information from electronic medical records and method of use | |
| CA3027937A1 (en) | Systems and methods for facilitating communication of health information | |
| CN111694993B (en) | Method, device, electronic equipment and medium for creating data index | |
| US11330474B2 (en) | Method and apparatus for handling sensitive data in machine to machine system | |
| US20230101506A1 (en) | Method and System to Facilitate Provisioning of an Emergency Health Service | |
| Leventhal et al. | Information management in the emergency department | |
| US20140297308A1 (en) | Referral and record sharing systems and methods | |
| US20170185751A1 (en) | Methods and devices for anonymous processing of medical studies | |
| US20130103727A1 (en) | Accessible Information System | |
| Adamkó et al. | Review and requirement specification of telemedicine systems interoperability with common data exchange hub | |
| US12020793B1 (en) | Adherence monitoring and notification 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 |