CN111489801A - Report query method and device - Google Patents
Report query method and device Download PDFInfo
- Publication number
- CN111489801A CN111489801A CN201910250385.XA CN201910250385A CN111489801A CN 111489801 A CN111489801 A CN 111489801A CN 201910250385 A CN201910250385 A CN 201910250385A CN 111489801 A CN111489801 A CN 111489801A
- Authority
- CN
- China
- Prior art keywords
- user
- role
- determining
- patient
- report
- 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.)
- Pending
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
- G16H15/00—ICT specially adapted for medical reports, e.g. generation or transmission thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/332—Query formulation
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Health & Medical Sciences (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The embodiment of the application discloses a report query method and a device, wherein the method comprises the following steps: receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient; determining the role of the user according to the login information of the user; when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient; determining a target diagnostic report from the list of diagnostic reports for the patient; displaying the content of the target diagnosis report. By the embodiment provided by the invention, the electronic version query report can be provided for the user in real time according to the role of the user, and convenience is provided for the user to use.
Description
Technical Field
The application relates to the technical field of medical treatment, in particular to a report query method and device.
Background
In traditional medicine, after a patient goes to a hospital for a doctor, the patient can make a diagnosis of various medical instruments according to the doctor's advice.
After a preset time period, the patient also needs to queue to a preset place to print a paper diagnosis result, and the diagnosis result is sent to a doctor to analyze the state of the disease according to the diagnosis result. If the patient does not accept the current disease analysis result, the medical instrument diagnosis is required to be carried out again when the patient goes to other hospitals for examination.
From the above, the existing diagnosis process is still a paper office, which brings much trouble to the user.
Disclosure of Invention
The embodiment of the application provides a report query method and device, which can provide an electronic version of query report for a user according to the role of the user in real time and provide convenience for the user to use.
In a first aspect, an embodiment of the present application provides a method for reporting a query, where the method includes:
receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient;
determining the role of the user according to the login information of the user;
when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient;
determining a target diagnostic report from the list of diagnostic reports for the patient;
displaying the content of the target diagnosis report.
Optionally, determining the role of the user according to the login information of the user includes:
acquiring the identification of the user from the login information of the user;
matching the user's identification with the doctor's identification in a medical database;
if the matching fails, determining the role of the user as a first role;
and if the matching is successful, determining the role of the user as a second role.
Optionally, before displaying the content of the target diagnosis report, the method further includes:
acquiring diagnostic data in the target diagnostic report;
judging whether the diagnosis data are normal or not;
if abnormal data exist in the diagnosis data, determining a risk level according to the magnitude of the abnormal data value;
determining a target color corresponding to the risk level;
marking the anomalous data with the target color.
Optionally, after the marking the abnormal data with the target color, the method further includes:
determining a data source for each of the diagnostic data;
and marking the data source of each piece of diagnostic data after the corresponding diagnostic data.
Optionally, the method further includes:
when the role of the user is the second role, determining a diagnosis report list of the patient according to the identification of the patient;
displaying a list of diagnostic reports of the user in chronological order;
determining a diagnosis report selected by the user from the diagnosis report list;
and displaying the selected diagnosis report content.
The second aspect of the present invention discloses an apparatus for reporting queries, the apparatus comprising:
the system comprises a receiving unit, a judging unit and a processing unit, wherein the receiving unit is used for receiving a diagnosis report query request input by a user, and the diagnosis report query request comprises an identifier of a patient;
the role determining unit is used for determining the role of the user according to the login information of the user;
the first report determining unit is further used for determining a diagnosis report list of the patient according to the identification of the patient when the role of the user is a first role;
the first report determination unit is further used for determining a target diagnosis report from the diagnosis report list of the patient;
and the display unit is used for displaying the content of the target diagnosis report.
Optionally, the role determination unit is specifically configured to obtain an identifier of the user from login information of the user; matching the user's identification with the doctor's identification in a medical database; if the matching fails, determining the role of the user as a first role; and if the matching is successful, determining the role of the user as a second role.
Optionally, the apparatus further comprises:
an acquisition unit, configured to acquire diagnostic data in the target diagnostic report;
a judging unit for judging whether the diagnostic data is normal;
the risk grade determining unit is used for determining a risk grade according to the magnitude of the abnormal data value and determining a target color corresponding to the risk grade if the abnormal data exists in the diagnostic data;
a first marking unit for marking the abnormal data with the target color.
Optionally, the apparatus further comprises:
a data source determination unit for determining a data source of each piece of the diagnostic data;
and the second marking unit is used for marking the data source of each piece of diagnostic data behind the corresponding piece of diagnostic data.
Optionally, the apparatus further comprises a second report determining unit;
the second report determining unit is further configured to determine a diagnosis report list of the patient according to the patient identifier, display the diagnosis report list of the user in a time sequence, and determine a diagnosis report selected by the user from the diagnosis report list when the role of the user is the second role; the display unit is used for displaying the selected diagnosis report content
In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing steps in any method of the first aspect of the embodiment of the present application.
In a fourth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program makes a computer perform part or all of the steps described in any one of the methods of the first aspect of the present application.
In a fifth aspect, the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform some or all of the steps as described in any one of the methods of the first aspect of the embodiments of the present application. The computer program product may be a software installation package.
It can be seen that, in the embodiment of the present application, a diagnosis report query request input by a user is received, where the diagnosis report query request includes an identifier of a patient; determining the role of the user according to the login information of the user; when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient; determining a target diagnostic report from the list of diagnostic reports for the patient; displaying the content of the target diagnosis report. By the embodiment provided by the invention, the electronic version query report can be provided for the user in real time according to the role of the user, and convenience is provided for the user to use.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a system architecture diagram of a diagnostic report query system according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating a method for reporting queries according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating another method for reporting queries provided by embodiments of the present application;
FIG. 4 is a flow chart illustrating another method for reporting queries provided by embodiments of the present application;
FIG. 5 is a block diagram illustrating functional units of a report query apparatus according to an embodiment of the present disclosure;
FIG. 6 is a block diagram illustrating functional units of another report query apparatus according to an embodiment of the present disclosure;
FIG. 7 is a block diagram illustrating functional units of another report query apparatus according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Referring to fig. 1, fig. 1 shows a diagnosis report query system, which includes a user login interface, a report query interface, a medical database (a database for storing medical staff information), a user identity database (which may be understood as a database for storing patient information), and a medical record database. The system can traverse the two databases according to the login information of the user to determine whether the matching is successful, and if the matching is successful, the system can log in. After logging in, performing role confirmation according to the matched database, for example, if matching with the medical database is successful, the user is a doctor, then inquiring and displaying a diagnosis report according to the authority of the doctor, and if matching with the medical database fails or matching with the user identity database is successful, the user is a traditional user role (for example, a patient or a relative of the patient) and inquiring and displaying the diagnosis report according to the traditional user role.
Referring to fig. 2, fig. 2 is a schematic flowchart illustrating a method for reporting query, applied to an electronic device according to an embodiment of the present disclosure; as shown in the figure, the method for reporting and querying comprises the following steps:
101. receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient;
it should be noted that the execution subject of this embodiment includes various electronic devices with communication functions, and the electronic devices may include handheld devices, vehicle-mounted devices, wearable devices, computer devices or other processing devices connected to wireless modems, and various forms of User Equipment (UE), Mobile Stations (MS), terminal devices (terminal device), and the like.
In addition, it should be noted that the query interface for the diagnosis report is opened through a web page or an application program. Then, after logging in the system through the account password, query information (such as a diagnosis report query request) is input. It is understood that the query information may be manually entered, or may be voice entered, or may be selected.
It should be noted that the rights of different users and the interfaces after login are different. For example, if a patient logs in according to the patient's number and password, the patient can only inquire about his or her diagnosis report. If a doctor logs in according to his job number and password, the doctor can inquire the diagnosis report of the patient according to his authority, and if the doctor is higher in level (such as a courtyard), the doctor can inquire the reports of all patients; if the doctor is attending, the doctor can only inquire the report of the patient.
102. Determining the role of the user according to the login information of the user;
it should be noted that determining the role of the user according to the login information of the user includes: acquiring the identification of the user from the login information of the user; matching the user's identification with the doctor's identification in a medical database; if the matching fails, determining the role of the user as a first role; and if the matching is successful, determining the role of the user as a second role.
For example, the first persona is typically a patient or a relative of a patient, etc., and the second persona is a doctor persona.
In addition, it should be noted that after the user identifier is obtained from the login information of the user, the amount of data in the user identity database and the medical database can be further determined, and if the data in the medical database is less than the data in the user identity database, the user identifier is matched with the identifier of the doctor in the medical data; otherwise, matching the user identification with the doctor identification in the user identity database.
In addition, it should be noted that the first role and the second role are merely illustrative. Of course a third role (nurse), a fourth role (theatre) etc. may also be included.
103. When the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient;
it should be noted that, when the role of the user is the first role, the medical record database is traversed according to the identification of the patient to determine all the diagnosis reports of the patient, and the diagnosis report list of the patient is determined according to the diagnosis reports.
In addition, optionally, the method further includes: when the role of the user is the second role, determining a diagnosis report list of the patient according to the identification of the patient; displaying a list of diagnostic reports of the user in chronological order; determining a diagnosis report selected by the user from the diagnosis report list; and displaying the selected diagnosis report content.
It should be noted that the doctor can also select several data reports for data analysis, such as a preset time period and a diagnosis dimension. For example, a patient is selected for a blood routine within three months. The system acquires blood routine data for the patient over three months and plots the blood routine data for the patient over the three months to present changes in the patient's blood routine for approximately three months. Of course, diagnostic data for routine abnormalities in blood during the three months are also flagged.
104. Determining a target diagnostic report from the list of diagnostic reports for the patient;
it will be appreciated that the patient's diagnostic reports may be sorted chronologically (e.g., from near to far) and the first (i.e., most recent) sorted diagnostic report may then be identified as the target diagnostic report.
It is understood that the diagnosis reports of the patients may be sorted according to chronological order (such as from near to far), and then the diagnosis reports within a preset time period may be determined as the target diagnosis reports. The preset time period may be user selected, and may be a system default. The preset time may be 3 days, 7 days, one month, three months, etc., without limitation.
105. Displaying the content of the target diagnosis report.
Wherein, before displaying the content of the target diagnosis report, the method further comprises: acquiring diagnostic data in the target diagnostic report; judging whether the diagnosis data are normal or not; if abnormal data exist in the diagnosis data, determining a risk level according to the magnitude of the abnormal data value;
determining a target color corresponding to the risk level; marking the anomalous data with the target color.
It should be noted that the diagnostic data may be one or more pieces.
For example, normal persons with fasting blood glucose concentration of 3.61-6.11 mmol/L. fasting blood glucose concentration over 7.0 mmol/L are regarded as abnormal data, which is called hyperglycemia, such as 7.0 mmol/L-11.0 mmol/L is marked as yellow (general risk), more than 11.0 mmol/L is marked as red (high risk), and in addition, possible symptoms such as 7.0 mmol/L-11.0 mmol/L can be marked behind the corresponding abnormal data, such as symptoms such as visual deterioration, skin itch, numbness of hands and feet, pain, walking such as cotton treading, and mental disorder, coma, etc. can occur such as more than 11.0 mmol/L.
Optionally, after the marking the abnormal data with the target color, the method further includes: determining a data source for each of the diagnostic data; and marking the data source of each piece of diagnostic data after the corresponding diagnostic data.
For example, each data source may be marked, such as a piece of blood routine data, and it may be noted later which responsible person the data is, what the model of machine is, and the calibration parameters and environment of the machine. The method is convenient for other doctors to determine whether the test data is reasonable according to the data source, and even if other hospitals are reached, other doctors can conveniently judge whether the diagnosis data is available according to the data source, and if the diagnosis data is available, the test of the data is not needed to be repeatedly carried out.
It can be seen that, in the embodiment of the present application, a diagnosis report query request input by a user is received, where the diagnosis report query request includes an identifier of a patient; determining the role of the user according to the login information of the user; when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient; determining a target diagnostic report from the list of diagnostic reports for the patient; displaying the content of the target diagnosis report. By the embodiment provided by the invention, the electronic version query report can be provided for the user in real time according to the role of the user, and convenience is provided for the user to use.
Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a method for reporting query according to an embodiment of the present application, where the method for reporting query includes:
201. receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient;
202. determining the role of the user according to the login information of the user;
it should be noted that determining the role of the user according to the login information of the user includes: acquiring the identification of the user from the login information of the user; matching the user's identification with the doctor's identification in a medical database; if the matching fails, determining that the role of the user is a patient role (namely, a non-doctor role, and of course, the user may also be a family or a friend of the patient); and if the matching is successful, determining that the role of the user is a doctor role.
203. When the role of the user is a patient role, determining a diagnosis report list of the patient according to the identification of the patient;
204. determining a target diagnostic report from the list of diagnostic reports for the patient;
205. acquiring diagnostic data in the target diagnostic report, and judging whether the diagnostic data are normal or not;
206. and if abnormal data exist in the diagnosis data, determining a risk level according to the magnitude of the abnormal data value.
207. Determining a target color corresponding to the risk level, and labeling the anomaly data with the target color.
208. Determining a data source for each of the diagnostic data; marking the data source of each piece of diagnostic data behind the corresponding diagnostic data;
209. displaying the content of the target diagnosis report.
In addition, the related description or explanation may refer to the above embodiments.
It can be seen that, in the embodiment of the present application, if the role of the user is a patient role, a target diagnosis report of the patient is obtained, if the diagnosis data of the target diagnosis report is abnormal, the risk level of the abnormal data is determined, and the abnormal data is marked according to the color corresponding to the risk level so that the user pays attention to the abnormal data, in addition, the data source of each piece of diagnosis data is marked so that a subsequent medical worker determines whether the diagnosis data is real according to the data source, or determines whether the diagnosis data is common by referring to the data source (if the types of medical instruments used for diagnosing the same disease in different hospitals are the same, the data tested by the medical instruments of the same type can be common).
Referring to fig. 4, fig. 4 is a schematic flowchart illustrating a method for reporting query according to an embodiment of the present application, where the method for reporting query includes:
301. receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient;
302. determining the role of the user according to the login information of the user;
303. when the role of the user is a doctor role, determining a diagnosis report list of the patient according to the identification of the patient;
304. displaying a list of diagnostic reports of the user in chronological order;
305. determining a diagnosis report selected by the user from the diagnosis report list;
306. determining an inspection dimension selected by the user;
for example, if ten recent diagnosis reports of a patient are selected and the selected viewing dimension is blood glucose concentration, the system extracts blood glucose data from the ten diagnosis reports and plots the extracted ten blood glucose values to show the variation of blood glucose in the last ten diagnoses.
For example, the viewing dimension may be a leukocyte concentration, a platelet concentration, etc., and is not intended to be limiting and non-limiting.
307. Performing data analysis according to the diagnosis report selected by the user and the examination dimension to generate an analysis result;
308. and displaying the selected diagnosis report content and the analysis result.
It should be noted that, for the related explanation of the present embodiment, reference may be made to the contents of the two embodiments.
It can be seen that, in the embodiment of the application, if the role of the user is a doctor role, the user can view the diagnosis report of the patient in any time period, and select the examination dimension in the diagnosis report to perform system analysis, so that the recent change process of a certain body parameter of the patient is presented, the doctor can conveniently and intuitively know the body condition of the user, and the office efficiency of the doctor is improved.
Fig. 5 is a block diagram showing functional units of the report query apparatus 400 according to the embodiment of the present application. The mobile terminal comprises the following functional units:
a receiving unit 401, configured to receive a diagnosis report query request input by a user, where the diagnosis report query request includes an identifier of a patient;
a role determination unit 402, configured to determine a role of the user according to login information of the user;
optionally, the role determining unit 402 is specifically configured to obtain the identifier of the user from the login information of the user; matching the user's identification with the doctor's identification in a medical database; if the matching fails, determining the role of the user as a first role; and if the matching is successful, determining the role of the user as a second role.
A first report determining unit 403, configured to determine a diagnosis report list of the patient according to the identifier of the patient when the role of the user is a first role;
a first report determination unit 403, further configured to determine a target diagnosis report from the diagnosis report list of the patient;
a display unit 404, configured to display the content of the target diagnosis report.
In addition, optionally, the apparatus 400 further includes:
an acquisition unit, configured to acquire diagnostic data in the target diagnostic report;
a judging unit for judging whether the diagnostic data is normal;
the risk grade determining unit is used for determining a risk grade according to the magnitude of the abnormal data value and determining a target color corresponding to the risk grade if the abnormal data exists in the diagnostic data;
a first marking unit for marking the abnormal data with the target color.
Optionally, the apparatus 400 further comprises:
a data source determination unit for determining a data source of each piece of the diagnostic data;
and the second marking unit is used for marking the data source of each piece of diagnostic data behind the corresponding piece of diagnostic data.
Optionally, the apparatus further comprises a second report determining unit;
the second report determining unit is further configured to determine a diagnosis report list of the patient according to the patient identifier, display the diagnosis report list of the user in a time sequence, and determine a diagnosis report selected by the user from the diagnosis report list when the role of the user is the second role;
and the display unit is used for displaying the selected diagnosis report content.
The above units may be used to execute the method described in step 101-105 in embodiment 1, and the detailed description is given in embodiment 1 for the description of the method, which is not repeated herein.
Fig. 6 is a block diagram showing functional units of the report query apparatus 500 according to the embodiment of the present application. The mobile terminal comprises the following functional units:
a receiving unit 501, configured to receive a diagnosis report query request input by a user, where the diagnosis report query request includes an identifier of a patient;
a role determination unit 502, configured to determine a role of the user according to the login information of the user;
it should be noted that determining the role of the user according to the login information of the user includes: acquiring the identification of the user from the login information of the user; matching the user's identification with the doctor's identification in a medical database; if the matching fails, determining that the role of the user is a patient role (namely, a non-doctor role, and of course, the user may also be a family or a friend of the patient); and if the matching is successful, determining that the role of the user is a doctor role.
A first report determining unit 503, configured to determine a diagnosis report list of the patient according to the patient identifier when the user role is a patient role; and determining a target diagnostic report from the list of diagnostic reports for the patient;
an obtaining unit 504, configured to obtain diagnostic data in the target diagnostic report;
a judging unit 505, configured to judge whether the diagnostic data is normal;
a risk level determining unit 506, configured to determine a risk level according to a size of the abnormal data value and determine a target color corresponding to the risk level if abnormal data exists in the diagnostic data;
a marking unit 507, configured to mark the abnormal data with the target color.
A data source determining unit 508, configured to determine a data source of each piece of diagnostic data in the diagnostic data;
a marking unit 507, further configured to mark the data source of each piece of diagnostic data after the corresponding piece of diagnostic data;
and the display unit is also used for displaying the content of the target diagnosis report.
The above units may be used to execute the method described in step 201-209 in embodiment 2, and the detailed description is given in embodiment 2 for the description of the method, which is not repeated herein.
Fig. 7 is a block diagram showing functional units of the report query apparatus 600 according to the embodiment of the present application. The mobile terminal comprises the following functional units:
a receiving unit 601, configured to receive a diagnosis report query request input by a user, where the diagnosis report query request includes an identifier of a patient;
a role determination unit 602, configured to determine a role of the user according to the login information of the user;
a second report determination unit 603, configured to determine a diagnosis report list of the patient according to the patient identifier when the role of the user is a doctor role;
a display unit 604 for displaying a diagnosis report list of the user in chronological order;
a diagnosis report determination unit 605, configured to determine a diagnosis report selected by the user from the diagnosis report list and determine a viewing dimension selected by the user;
for example, if ten recent diagnosis reports of a patient are selected and the selected viewing dimension is blood glucose concentration, the system extracts blood glucose data from the ten diagnosis reports and plots the extracted ten blood glucose values to show the variation of blood glucose in the last ten diagnoses.
For example, the viewing dimension may be a leukocyte concentration, a platelet concentration, etc., and is not intended to be limiting and non-limiting.
A generating unit 606, configured to perform data analysis according to the diagnosis report selected by the user and the examination dimension to generate an analysis result;
a display unit 604, configured to display the selected diagnosis report content and the analysis result.
The above units may be used to execute the method described in steps 301-308 in embodiment 3, and the detailed description is given in embodiment 3 for the description of the method, which is not repeated herein.
Referring to fig. 8, fig. 8 is a schematic structural diagram of a report query apparatus 700 according to an embodiment of the present application, as shown in the figure, the report query apparatus 700 includes an application processor 710, a memory 720, a communication interface 730, and one or more programs 721, where the one or more programs 721 are stored in the memory 720 and configured to be executed by the application processor 710, and the one or more programs 721 include instructions for:
receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient;
determining the role of the user according to the login information of the user;
when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient;
determining a target diagnostic report from the list of diagnostic reports for the patient;
displaying the content of the target diagnosis report.
Optionally, determining the role of the user according to the login information of the user includes:
acquiring the identification of the user from the login information of the user;
matching the user's identification with the doctor's identification in a medical database;
if the matching fails, determining the role of the user as a first role;
and if the matching is successful, determining the role of the user as a second role.
Optionally, before displaying the content of the target diagnosis report, the executing process further includes:
acquiring diagnostic data in the target diagnostic report;
judging whether the diagnosis data are normal or not;
if abnormal data exist in the diagnosis data, determining a risk level according to the magnitude of the abnormal data value;
determining a target color corresponding to the risk level;
marking the anomalous data with the target color.
Optionally, after the marking the abnormal data with the target color, the executing process further includes:
determining a data source for each of the diagnostic data;
and marking the data source of each piece of diagnostic data after the corresponding diagnostic data.
Optionally, the executing process further includes:
when the role of the user is the second role, determining a diagnosis report list of the patient according to the identification of the patient;
displaying a list of diagnostic reports of the user in chronological order;
determining a diagnosis report selected by the user from the diagnosis report list;
and displaying the selected diagnosis report content.
It can be seen that, in the embodiment of the present application, a diagnosis report query request input by a user is received, where the diagnosis report query request includes an identifier of a patient; determining the role of the user according to the login information of the user; when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient; determining a target diagnostic report from the list of diagnostic reports for the patient; displaying the content of the target diagnosis report. By the embodiment provided by the invention, the electronic version query report can be provided for the user in real time according to the role of the user, and convenience is provided for the user to use.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It is understood that the electronic device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Embodiments of the present application also provide a computer storage medium, where the computer storage medium stores a computer program for electronic data exchange, the computer program enabling a computer to execute part or all of the steps of any one of the methods described in the above method embodiments, and the computer includes an electronic device.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods as described in the above method embodiments. The computer program product may be a software installation package, the computer comprising an electronic device.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit may be stored in a computer readable memory if it is implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the above-mentioned method of the embodiments of the present application. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, which can store program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash Memory disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the above description of the embodiments is only provided to help understand the method and the core concept of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A method of reporting a query, the method comprising:
receiving a diagnosis report query request input by a user, wherein the diagnosis report query request comprises an identifier of a patient;
determining the role of the user according to the login information of the user;
when the role of the user is a first role, determining a diagnosis report list of the patient according to the identification of the patient;
determining a target diagnostic report from the list of diagnostic reports for the patient;
displaying the content of the target diagnosis report.
2. The method of claim 1, wherein determining the role of the user based on the login information of the user comprises:
acquiring the identification of the user from the login information of the user;
matching the user's identification with the doctor's identification in a medical database;
if the matching fails, determining the role of the user as a first role;
and if the matching is successful, determining the role of the user as a second role.
3. The method of claim 2, wherein prior to displaying the content of the target diagnostic report, the method further comprises:
acquiring diagnostic data in the target diagnostic report;
judging whether the diagnosis data are normal or not;
if abnormal data exist in the diagnosis data, determining a risk level according to the magnitude of the abnormal data value;
determining a target color corresponding to the risk level;
marking the anomalous data with the target color.
4. The method of claim 3, wherein after said marking said anomalous data with said target color, said method further comprises:
determining a data source for each of the diagnostic data;
and marking the data source of each piece of diagnostic data after the corresponding diagnostic data.
5. The method of any of claims 1 to 4, further comprising:
when the role of the user is the second role, determining a diagnosis report list of the patient according to the identification of the patient;
displaying a list of diagnostic reports of the user in chronological order;
determining a diagnosis report selected by the user from the diagnosis report list;
and displaying the selected diagnosis report content.
6. An apparatus for reporting queries, the apparatus comprising:
the system comprises a receiving unit, a judging unit and a processing unit, wherein the receiving unit is used for receiving a diagnosis report query request input by a user, and the diagnosis report query request comprises an identifier of a patient;
the role determining unit is used for determining the role of the user according to the login information of the user;
the first report determining unit is further used for determining a diagnosis report list of the patient according to the identification of the patient when the role of the user is a first role;
the first report determination unit is further used for determining a target diagnosis report from the diagnosis report list of the patient;
and the display unit is used for displaying the content of the target diagnosis report.
7. The apparatus according to claim 6, wherein the role determination unit is specifically configured to obtain the identifier of the user from login information of the user; matching the user's identification with the doctor's identification in a medical database; if the matching fails, determining the role of the user as a first role; and if the matching is successful, determining the role of the user as a second role.
8. The apparatus of claim 7, further comprising:
an acquisition unit, configured to acquire diagnostic data in the target diagnostic report;
a judging unit for judging whether the diagnostic data is normal;
the risk grade determining unit is used for determining a risk grade according to the magnitude of the abnormal data value and determining a target color corresponding to the risk grade if the abnormal data exists in the diagnostic data;
a first marking unit for marking the abnormal data with the target color.
9. The apparatus of claim 8, further comprising:
a data source determination unit for determining a data source of each piece of the diagnostic data;
and the second marking unit is used for marking the data source of each piece of diagnostic data behind the corresponding piece of diagnostic data.
10. The apparatus according to any one of claims 6 to 9, wherein the apparatus further comprises a second report determining unit;
the second report determining unit is further configured to determine a diagnosis report list of the patient according to the patient identifier, display the diagnosis report list of the user in a time sequence, and determine a diagnosis report selected by the user from the diagnosis report list when the role of the user is the second role;
and the display unit is used for displaying the selected diagnosis report content.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2019100856556 | 2019-01-29 | ||
| CN201910085655 | 2019-01-29 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111489801A true CN111489801A (en) | 2020-08-04 |
Family
ID=71794322
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910250385.XA Pending CN111489801A (en) | 2019-01-29 | 2019-03-29 | Report query method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111489801A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116992418A (en) * | 2023-09-25 | 2023-11-03 | 深圳市赛义德信息技术有限公司 | Account safety protection system for medical inquiry terminal |
-
2019
- 2019-03-29 CN CN201910250385.XA patent/CN111489801A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116992418A (en) * | 2023-09-25 | 2023-11-03 | 深圳市赛义德信息技术有限公司 | Account safety protection system for medical inquiry terminal |
| CN116992418B (en) * | 2023-09-25 | 2024-01-05 | 深圳市赛义德信息技术有限公司 | Account safety protection system for medical inquiry terminal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10790063B2 (en) | Computer-aided multiple standard-based functional evaluation and medical reporting system | |
| US6708057B2 (en) | Method and system for processing electrocardiograms | |
| US8805483B2 (en) | Method and system for processing electrocardiograms | |
| US20030233250A1 (en) | Systems and methods for managing biological data and providing data interpretation tools | |
| CN104823211B (en) | Medical examination device displaying result and its working method | |
| US20090204437A1 (en) | System and method for improving diagnoses of medical image reading | |
| US20100049548A1 (en) | Medical image system, electronic medical record terminal, and computer-readable medium | |
| CN108074649B (en) | Electrocardiogram detection data acquisition and analysis system and method | |
| DE102006000713A1 (en) | Medical image viewing management and status system | |
| JP5150142B2 (en) | Medical information management system | |
| US20100204596A1 (en) | Method and system for providing remote healthcare | |
| CN104331778A (en) | Intelligent management control method for clinical blood transfusion electronic information system | |
| CN103268422A (en) | Multi-user multi-parameter wireless detection, diagnosis, service and monitoring system | |
| CN103279665A (en) | Multi-user and multi-parameter wireless detection, diagnosis, service and monitoring method | |
| JP5342113B2 (en) | Medical information management system | |
| CN106991292A (en) | A kind of health guidance method and system | |
| DE112012006037T5 (en) | Biological information distribution server, program and medical support system using it | |
| JP2003167960A (en) | Health control system | |
| WO2019047366A1 (en) | Artificial intelligence-based image recognition system and method | |
| CN111180027A (en) | Patient portrait correlation rule screening method and device based on medical big data | |
| CN111489801A (en) | Report query method and device | |
| JP2015056094A (en) | Medical care information display control apparatus, method, and program | |
| JP3914024B2 (en) | Diagnosis / guidance support system and diagnosis / guidance support method for home-medical adaptation patients | |
| JPWO2019102949A1 (en) | Medical support device and its operation method and operation program | |
| JP2014038529A (en) | Handy terminal of medical checkup computer, and data processing method employing handy terminal of medical checkup computer |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200804 |
|
| WD01 | Invention patent application deemed withdrawn after publication |