A method for mandatory monitoring and reporting of infectious disease symptoms in electronic medical records
By employing a two-tiered strategy in the electronic medical record system—combining coarse screening with ICD coding intervals and precise matching with diagnostic name keywords—along with forced pop-ups and save-lock operations, the accuracy and completeness issues of infectious disease symptom monitoring data collection in existing technologies have been resolved. This has achieved a closed-loop technology process, improving data quality and reporting rate.
Patent Information
- Application Number
- CN202611306659.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-26
- Publication Date
- 2026-11-10
AI Technical Summary
Existing electronic medical record systems suffer from problems in infectious disease symptom monitoring, such as inaccurate triggering mechanisms, lack of mandatory technical linkage between the reporting process and medical record storage, insufficient scalability of symptom dimensions, lack of verification of the integrity of reported data, and fragmented data flow at each stage. These issues result in low reliability of the system's assisted intervention and prevent the formation of a complete technical closed loop.
A two-tiered progressive strategy is adopted, which combines coarse screening of ICD coding intervals with precise matching of diagnostic name keywords. This is combined with forced pop-up triggering and medical record saving lock operations to ensure that the filling interface is triggered only when both levels of matching are successful. Furthermore, an integrity verification mechanism forces doctors to complete the selection of six symptom dimensions, and the data is only saved after it is written to the database.
It significantly reduced the false trigger and missed trigger rates, improved the accuracy of case identification, ensured the integrity and structure of monitoring data, achieved seamless connection from case identification to data entry, and improved data quality and reporting rate.
Smart Images

Figure CN123072601A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of medical information processing technology, and in particular to a method for mandatory monitoring and reporting of infectious disease symptoms in electronic medical records. Background Technology
[0002] With the development of medical informatization, some electronic medical record systems have integrated infectious disease reporting auxiliary functions, and various disease monitoring information collection methods based on electronic medical records have been disclosed in relevant patent literature. However, analysis of existing electronic solutions reveals the following common technical shortcomings:
[0003] First, the triggering mechanism is crude and the matching accuracy is insufficient. Existing systems typically use only a single matching method to identify cases that need to be reported, such as performing simple keyword fuzzy matching on the diagnosis name, or judging whether the ICD code belongs to a specific coding segment. This single matching method has two typical problems in practical applications: First, when the diagnosis name contains modifiers such as "suspected," "to be investigated," or "to be ruled out," the system may still falsely trigger and generate a reminder, interfering with the normal diagnosis and treatment process; second, when doctors directly enter the ICD code or use non-standard abbreviations, the system may miss the trigger because the keywords cannot be matched. Both false triggers and missed triggers directly reduce the system's auxiliary effect, and even cause doctors to habitually close the system due to frequent false alarms, thus losing the original meaning of technical intervention.
[0004] Second, the reporting process and medical record retention process lack mandatory technical constraints. Although existing systems can pop up reporting windows or reminders after recognizing cases that need to be reported, these reminder windows usually allow doctors to choose "close," "report later," or "skip," meaning there is no mandatory technical connection between the reporting behavior and whether the medical record can be successfully retained. In other words, the auxiliary reporting function of the existing system is "bypassable" rather than "mandatory." When doctors choose to close the reminders under high-intensity patient volume, the system cannot form an effective technical loop, and the guarantee of reporting rate still depends on the doctor's personal willingness to comply.
[0005] Third, the configurability of symptom monitoring dimensions is insufficient. The symptom collection fields of existing systems are usually fixed in the early design, such as only including traditional symptom items such as fever, diarrhea, jaundice, rash, and conjunctival redness. As the spectrum of infectious diseases evolves, new symptom monitoring requirements (such as vomiting) cannot be flexibly added without modifying the underlying data structure of the system, which restricts the scalability of the monitoring system.
[0006] Fourth, the completeness of the submitted data lacks a system-level verification mechanism. Even when doctors access the data entry interface, existing systems typically only require optional or partial completion, without mandating the selection of all symptom items. This soft constraint results in a large number of missing items in the data entering the monitoring database, making it impossible to guarantee data integrity from a technical perspective.
[0007] Fifth, the data flow between reporting triggering, data entry, and medical record storage is fragmented. In existing technical solutions, the triggering judgment, reporting interface call, reporting data storage, and medical record storage of infectious disease reporting functions are usually loosely coupled or even completely separated by independent modules. There is a lack of a unified technical link to connect the various links into a closed-loop process, resulting in insufficient reliability of the entire link from trigger recognition to final data entry. Summary of the Invention
[0008] This application provides a mandatory monitoring and reporting method for infectious disease symptoms in electronic medical records, aiming to solve the problems in the existing technology during the data collection process of infectious disease symptom monitoring. These problems include inaccurate trigger identification, lack of mandatory technical linkage between the reporting process and medical record storage, insufficient scalability of symptom dimensions, lack of verification of the integrity of the reported data, and fragmented data flow at each stage. As a result, the reliability of system-assisted intervention is low and a complete technical closed loop from identification to data entry cannot be formed.
[0009] Firstly, a method for mandatory monitoring and reporting of infectious disease symptoms in electronic medical records is provided, including:
[0010] The system captures diagnostic data entered by doctors in the electronic medical record editing interface in real time. The diagnostic data includes at least the International Classification of Diseases (ICD) code and the text of the diagnosis name.
[0011] The ICD code is subjected to a first-level coarse screening and matching to determine whether the ICD code falls into a preset set of ICD infectious disease classification code intervals;
[0012] If the first-level coarse screening match is successful, then the second-level precise matching is performed on the diagnostic name text to determine whether the diagnostic name text matches the keywords in the preset legal infectious disease catalog keyword database.
[0013] If the second-level exact match is found, the forced pop-up trigger operation and the medical record saving lock operation are executed simultaneously.
[0014] The forced pop-up triggering operation includes: displaying the infectious disease symptom detection registration card filling interface in the form of a modal window at the forefront of the doctor's workstation screen. The filling interface includes negative / positive mutually exclusive check boxes for six symptom dimensions: fever, diarrhea, jaundice, rash, conjunctival redness and swelling, and vomiting, and does not contain skip or close controls.
[0015] The medical record saving lock operation includes: injecting a lock signal into the medical record saving interface of the electronic medical record system to prohibit the saving operation of the current medical record;
[0016] In response to the doctor completing the selection of the six symptom dimensions and submitting the form on the form interface, the integrity of the form data is verified.
[0017] If the verification passes, the locking signal is revoked, the reported symptom detection data is written into the database, and the current case is allowed to be saved.
[0018] Optionally, in the above scheme, before performing the first-level coarse screening matching on the ICD encoding, a fault-tolerance processing step is also included:
[0019] Determine whether the ICD code in the diagnostic data is empty;
[0020] If the ICD code is empty, the first-level coarse screening matching step is skipped, and the second-level precise matching is performed directly with the diagnostic name text.
[0021] In the above scheme, optionally, the preset set of ICD infectious disease classification coding intervals and the database of keywords for legally notifiable infectious disease names are both stored in a configuration database that can be remotely updated;
[0022] The keyword database for the list of legally notifiable infectious diseases contains the standard Chinese names of all legally notifiable infectious diseases of Class A, Class B, and Class C as stipulated in the Law of the People's Republic of China on the Prevention and Control of Infectious Diseases, as well as commonly used alternative names recognized by the health administration department. Each keyword in the database is associated with an effective timestamp.
[0023] Optionally, in the above scheme, the infectious disease symptom detection registration card filling interface also includes an optional checkbox for "suspected cluster outbreak";
[0024] After performing integrity verification on the entered data, the process also includes:
[0025] If the optional checkbox for "suspected cluster outbreak" is selected, the data will be written into the database and simultaneously pushed to the front-end machine of the local disease prevention and control center in real time through the disease prevention and control information network interface.
[0026] Optionally, in the above scheme, injecting a locking signal into the case storage interface of the electronic medical record system includes:
[0027] The interceptor pattern of Aspect-Oriented Programming (AOP) is used to dynamically weave before advice into the case saving interface method of the electronic medical record system;
[0028] Before executing the save logic, the pre-notification checks whether the current case ID is locked in the cache;
[0029] If a locked state exists, a business exception will be thrown and a prompt message "Please complete the infectious disease symptom detection registration card first" will be returned to prevent the execution of the save operation.
[0030] Optionally, in the above scheme, the method further includes an audit log generation step:
[0031] While performing the medical record saving and locking operation, an audit log record is generated and written.
[0032] The audit log records include at least: trigger timestamp, diagnostic ICD code, diagnostic name text, unique identifier of the operating physician, unique identifier of the current case, and lock operation type.
[0033] Optionally, the above scheme further includes a timeout handling step:
[0034] Record the injection timestamp of the locking signal;
[0035] If the difference between the current time and the injection timestamp exceeds a preset threshold, the locking signal will be automatically revoked, the incomplete reporting event will be recorded in the exception log, and a reporting timeout notification will be sent to the doctor.
[0036] Optionally, in the above scheme, the step of performing integrity verification on the entered data includes:
[0037] Iterate through the reported status values for the six symptom dimensions;
[0038] If the status value of any dimension is empty, the verification is deemed to have failed, and the user is prompted to "Please complete the selection of all symptom detection items", while keeping the filling interface displayed and the lock signal valid;
[0039] If all six dimensions have a status value of "negative" or "positive", the verification is considered successful.
[0040] In a second aspect, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described above.
[0041] Thirdly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.
[0042] Compared with the prior art, this application has at least the following beneficial effects:
[0043] This application, based on further analysis and research into the problems of existing technologies, recognizes that existing technologies suffer from low reliability in system-assisted intervention and the inability to form a complete technical loop from identification to data entry during the collection of infectious disease symptom monitoring data. This is due to issues such as inaccurate trigger identification, lack of mandatory technical linkage between the reporting process and medical record preservation, insufficient symptom dimension expansion, lack of verification of the integrity of the reported data, and fragmented data flow at each stage. To address these issues, a two-tiered progressive matching strategy of "ICD coding interval coarse screening + precise matching of diagnosis name and disease name keywords" is adopted. Subsequent processes are only triggered when both levels of matching are successful. Compared to a single matching method, this significantly reduces the false trigger and missed trigger rates and improves the accuracy of case identification. Furthermore, by simultaneously executing a mandatory pop-up trigger operation and a medical record preservation lock operation after both levels of matching are successful, the symptom reporting settings are optimized. As a prerequisite for medical record preservation, a modal window without skip or close controls forces doctors to complete the data entry, completely eliminating the possibility of circumventing or omitting reports at the system architecture level. By pre-setting a data entry interface with six symptom dimensions, each configured with mutually exclusive negative / positive checkboxes, flexible expansion of symptom monitoring dimensions is achieved without modifying the underlying system data structure. Simultaneously, an integrity verification mechanism mandates that all six dimensions be checked before submission, fundamentally ensuring the integrity and structure of the monitoring data. By atomically executing the writing of data to the database and the unlocking, release, and saving, a seamless technical loop is formed from case identification, data entry triggering, data entry to final database storage. Data flow at each stage is continuous within the same system, avoiding data quality loss caused by fragmented multi-system operations. Therefore, this application achieves systematization, mandatory implementation, and automation of the entire process of infectious disease symptom monitoring data collection. Without changing doctors' existing electronic medical record operating habits, it ensures the reporting rate and data quality of symptom monitoring data from a technical rather than a managerial perspective. Attached Figure Description
[0044] Figure 1 A flowchart illustrating a method for mandatory monitoring and reporting of infectious disease symptoms in an electronic medical record, provided as an embodiment of this application;
[0045] Figure 2 This is a timing interaction diagram of a forced pop-up window, a locking signal, and a waiting-for-verification-unlocking process provided in one embodiment of this application. Detailed Implementation
[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0047] In the description of this application: unless otherwise stated, the terms "first," "second," "third," etc., are intended to distinguish the objects they refer to and do not have any special meaning in terms of technical connotation (e.g., they should not be construed as an emphasis on importance or order). Expressions such as "comprising," "including," and "having" also mean "not limited to" (certain units, components, materials, steps, etc.).
[0048] The purpose of this invention is to overcome the shortcomings of the prior art mentioned in the background section, and to provide a method for automatic identification of infectious disease diagnostic information and mandatory blocking of electronic medical records. This method realizes a comprehensive digital transformation of the "XX City Infectious Disease Symptom Monitoring Registration Card" from manual paper-based reporting to mandatory reporting within the electronic medical record system. It also expands the symptom monitoring dimensions from the original five items (fever, diarrhea, jaundice, rash, conjunctival erythema) to six items (with the addition of vomiting). At the same time, it innovatively transforms the triggering mechanism from the current workflow of "symptom-driven + manual cluster judgment" to "diagnosis name-driven + automatic system identification and mandatory blocking". Through a complete method chain of "ICD coding interval coarse screening → precise matching of disease name keywords → injection of a lock signal after both levels are matched → cancellation of the lock after the symptom reporting integrity verification is passed", this method solves the technical problems of high underreporting rate, uncontrollable data quality, and inability to systematically execute triggering conditions that rely on manual judgment in the paper-based mode.
[0049] To achieve the above objectives, in one embodiment, a method for automatic identification of infectious disease diagnostic information and mandatory blocking of electronic medical records is provided, comprising the following steps:
[0050] Step S1: Capture the input data of the diagnosis name field in the electronic medical record editing interface in real time.
[0051] An event listener is attached to the diagnosis name input control in the electronic medical record system. When a doctor completes the input or selection of a diagnosis name and triggers the "temporarily save diagnosis" or "confirm diagnosis" operation, the complete data of the diagnosis name field is captured in real time. This complete data includes at least the International Classification of Diseases (ICD) code and the diagnosis name text. Specifically, it can be obtained through the standard application programming interfaces (APIs) provided by the electronic medical record system, such as the Observation or Condition resource interface based on the HL7 FHIR standard, or the SOAP / REST interface based on Web Services.
[0052] Step S2: Perform the first-level coarse screening matching on the ICD code.
[0053] The ICD codes obtained in step S1 are compared with a preset set of ICD infectious disease classification coding intervals. This set of ICD infectious disease classification coding intervals is pre-configured based on the coding ranges of chapters related to infectious diseases in the World Health Organization's ICD-11 (or ICD-10, depending on the version currently used by the medical institution) standard. For example, in ICD-11, the coding intervals covered by the chapter "certain infectious diseases or parasitic diseases" can be used as coarse screening intervals.
[0054] If the ICD code obtained in step S1 falls into any interval of the ICD infectious disease classification code interval set, it is determined that the first-level coarse screening match has been hit, and the process proceeds to step S3.
[0055] If the ICD code obtained in step S1 does not fall into any range, it is determined that the first-level coarse screening match has failed, the process terminates, and the case can be saved normally.
[0056] Step S3: Assuming the first-level coarse matching is successful, perform a second-level precise matching on the diagnostic name text.
[0057] The diagnostic name text obtained in step S1 is matched one by one with each keyword in the preset keyword database of legally notifiable infectious diseases. The keyword database of legally notifiable infectious diseases contains the standard Chinese names of all legally notifiable infectious diseases of Class A, Class B, and Class C as stipulated in the Law of the People's Republic of China on the Prevention and Control of Infectious Diseases, as well as commonly used aliases recognized by the health administration department.
[0058] If the diagnostic name text is precisely matched with at least one keyword in the keyword database of the legally recognized infectious disease catalog, it is determined to be a second-level precise match and proceeds to step S4.
[0059] If no match is found, it is determined that the second-level exact match has not been found, the process is terminated, and the case can be saved normally.
[0060] Step S4: Generate a forced pop-up trigger command to call the preset symptom detection registration card filling interface.
[0061] When both the first-level coarse matching and the second-level precise matching are successful, a forced pop-up trigger command is generated, invoking the interface rendering module of the electronic medical record system to display the preset infectious disease symptom detection registration card filling interface in the form of a modal window at the forefront of the doctor's workstation screen. The filling interface includes six symptom detection dimensions: fever symptom (with mutually exclusive negative and positive single-select controls), diarrhea symptom, jaundice symptom, rash symptom, conjunctival redness and swelling symptom, and vomiting symptom. Each dimension provides two mutually exclusive negative / positive options, and the interface does not contain controls such as "skip," "close," or "fill in later" that allow bypassing the filling process.
[0062] Step S5: Inject a locking signal into the electronic medical record system's save interface to prevent the current case from being saved.
[0063] This is performed synchronously with step S4. A lock signal is injected into the medical record storage interface of the electronic medical record system. Specific methods may include:
[0064] (a) Insert a temporary interception rule into the permission verification layer of the case saving interface, so that the save request corresponding to the current case ID is rejected and a prompt "Please complete the infectious disease symptom detection registration card first" is returned; or
[0065] (b) Set a save lock flag for the current case record at the database transaction layer. When the database write operation detects that the lock flag is locked, it refuses to execute the write and returns an error code.
[0066] The effective range of the locking signal is the current editing session of the current case, and it does not affect the normal saving operation of other cases.
[0067] Step S6: After receiving the signal indicating that the symptom detection registration card has passed the integrity verification, remove the lock signal and release the case for storage.
[0068] During the waiting phase following steps S4 and S5, the system listens for submission events from the symptom registration card entry interface. Once the user (doctor) has completed the selection of all six symptom dimensions (each item is set to either negative or positive, with no item left unselected) and clicks the submit button, a completeness check is performed.
[0069] Iterate through the reporting status values of the six symptom dimensions. If the status value of any dimension is "not reported" (i.e., empty), the verification fails. Prompt the user to "please complete the selection of all symptom detection items". Keep the reporting interface displayed, keep the lock signal in place, and return to the waiting state.
[0070] If all six dimensions have a status value of "negative" or "positive" (i.e., no null values), the validation passes. Upon receiving the validation pass signal, perform the following operations:
[0071] (a) Serialize the symptom detection data (including the status values of the six dimensions, the submission timestamp, the submitting doctor ID, the case ID, the triggering diagnosis name and the ICD code) submitted this time into a structured data record and write it into the symptom detection supplementary table of the electronic medical record database;
[0072] (b) Cancel the locking signal injected in step S5 - if the interception rule method is used, remove the temporary interception rule; if the lock flag method is used, update the lock flag to the unlocked state.
[0073] (c) Return a save release signal to the electronic medical record system, and the doctor's case save request can be executed normally.
[0074] In one embodiment, in step S2, the ICD infectious disease classification coding interval set is stored in a remotely updatable configuration database. When the World Health Organization releases an update to the ICD coding standard, or the National Health Commission of China issues a notice adjusting the applicable coding range, the system administrator can remotely update the coding interval set through the configuration management interface without modifying the main flow code of the method.
[0075] In one embodiment, in step S3, the keyword database for the legally notifiable infectious disease list is stored in a remotely updatable configuration database. When the list of legally notifiable infectious diseases is revised or adjusted according to the Law of the People's Republic of China on the Prevention and Control of Infectious Diseases, the system administrator can remotely update the keyword database. Each keyword in the keyword database can be accompanied by an effective timestamp to support the scheduled effective date of newly included infectious diseases.
[0076] In one embodiment, the following fault-tolerant processing logic is set between steps S2 and S3: if the ICD code field in the diagnostic name data obtained in step S1 is empty (for example, the diagnostic name field in some electronic medical record systems is not forcibly associated with ICD codes), then step S2 is skipped, and the exact matching in step S3 is performed directly using the diagnostic name text. This fault-tolerant logic ensures that it can work normally under the different data integrity levels of various electronic medical record systems.
[0077] In one embodiment, in step S4, the symptom detection registration card filling interface also includes an optional checkbox for "suspected cluster outbreak". When the doctor checks this option, the system's subsequent processing priority is increased, and the symptom data is written to the local Center for Disease Control and Prevention (CDC) front-end machine in real time through the dedicated network interface while being written to the local database.
[0078] In one embodiment, in step S5, the injection of the locking signal is implemented using an interceptor pattern based on AOP (Aspect-Oriented Programming). A before-advance notification is dynamically woven into the case saving interface method of the electronic medical record system. This before-advance notification checks whether the current case is in the "symptom registration card to be filled" state before executing the saving logic: if so, a business exception is thrown and the system returns to the filling interface in step S4; otherwise, the saving logic is executed normally. This implementation does not require intrusion into the original saving logic code of the electronic medical record system and has good system compatibility.
[0079] In one embodiment, the method further includes: simultaneously injecting the locking signal in step S5, generating and writing an audit log record, the record content including at least: trigger timestamp, diagnostic ICD code, diagnostic name text, unique identifier of the operating physician, unique identifier of the current case, and locking operation type. This audit log is used to meet the compliance requirements of the "Law of the People's Republic of China on the Prevention and Control of Infectious Diseases" regarding the traceability of infectious disease monitoring operations, and can also be used for internal hospital quality control and performance evaluation.
[0080] In one embodiment, the method further includes timeout handling logic: if the waiting time in step S6 exceeds a preset threshold (e.g., 30 minutes), the locking signal is automatically revoked, and the incomplete reporting event is recorded in the anomaly log and a pop-up notification is sent to the doctor in the infectious disease information monitoring system: "The infectious disease symptom registration card for case CASE-2026-XXXX has not been completed due to timeout. Please follow up and complete the reporting."
[0081] In one embodiment, a method for automatic identification of infectious disease diagnostic information and mandatory blocking of electronic medical records is provided and deployed in the hospital infectious disease information monitoring system and electronic medical record system environment of a tertiary-level general hospital. This method completely replaces the previous workflow of doctors manually filling out paper-based "Beijing Infectious Disease Symptom Detection Registration Card".
[0082] Reference Figure 1 The method includes the following steps:
[0083] S1: Real-time capture of input data in the diagnostic name field.
[0084] A JavaScript event listener is attached to the diagnosis name input control (usually a drop-down selection box or a search-style input box, associated with the ICD-11 encoding library) in the electronic medical record system. This listener monitors for click events on the "Diagnosis Confirmation" button or the "blur" (loss of focus) event of the diagnosis name input box. When the event is triggered, the latest diagnosis data for the current case is retrieved via the HL7 FHIR interface exposed by the electronic medical record system (GET / Observation?category=diagnosis&patient={patientId}&encounter={encounterId}), from which the ICD-11 encoding (e.g., 1A00) and the diagnosis name text (e.g., "cholera") are parsed.
[0085] S2: ICD encoding first-level coarse screening matching.
[0086] The parsed ICD-11 code 1A00 is compared with the preset set of ICD-11 infectious disease classification code intervals. See Table 1 below for an example of this set.
[0087] ;
[0088] If the ICD-11 code 1A00 falls within interval 1 (1A00-1H0Z), the first-level coarse screening match is successful, and the process proceeds to step S3.
[0089] If the diagnosis is a non-infectious disease (e.g., brain malignancy corresponding to ICD-11 code 2A00), and its code does not fall into any infectious disease range, then the first-level coarse screening match will not be successful, the process will terminate directly, the case can be saved normally, and the user will not be aware of it.
[0090] S3: Second-level exact match of diagnostic name text.
[0091] Assuming a successful initial screening match, the diagnostic text "cholera" is compared precisely with the keyword database of legally notifiable infectious diseases listed in the 2025 Law on Prevention and Control of Infectious Diseases. This keyword database currently contains:
[0092] Category A: Plague, cholera.
[0093] Category B: Severe Acute Respiratory Syndrome (SARS), AIDS, viral hepatitis, poliomyelitis, human infection with highly pathogenic avian influenza, measles, epidemic hemorrhagic fever, rabies, epidemic encephalitis B, dengue fever, anthrax, bacterial and amoebic dysentery, tuberculosis, typhoid and paratyphoid fever, epidemic cerebrospinal meningitis, pertussis, diphtheria, neonatal tetanus, scarlet fever, brucellosis, gonorrhea, syphilis, leptospirosis, schistosomiasis, malaria, human infection with H7N9 avian influenza, and novel coronavirus infection.
[0094] Category C: Influenza, mumps, rubella, acute hemorrhagic conjunctivitis, leprosy, epidemic and endemic typhus, leishmaniasis, echinococcosis, filariasis, infectious diarrhea (excluding cholera, bacterial and amoebic dysentery, typhoid and paratyphoid fever), and hand-foot-mouth disease.
[0095] The diagnostic name text "cholera" was successfully matched precisely with the Class A infectious disease "cholera" in the keyword database. The second-level precise match was hit, and the process proceeds to step S4.
[0096] S4: Generate a forced pop-up trigger command to call the symptom detection registration card filling interface.
[0097] After both levels of matching are successful, the backend service generates a forced pop-up trigger command, which is pushed to the doctor's workstation frontend via a WebSocket long connection. Upon receiving the command, the frontend calls the browser's native window.showModalDialog() or a custom modal window component to display the infectious disease symptom detection registration card filling interface on top of the screen.
[0098] The interface does not contain a "Close" button, a "Skip" button, or a "Fill in later" link. Window closing events (including clicking the browser tab close button, pressing the Esc key, etc.) are all blocked to ensure that doctors cannot bypass the form filling process.
[0099] The "negative" and "positive" radio buttons for each symptom dimension should be set to the same radio group to ensure they are mutually exclusive—negative and positive cannot be selected simultaneously for the same dimension.
[0100] The "Submit" button is initially grayed out and unclickable (CSS properties pointer-events: none and opacity: 0.5). The front-end JavaScript listens for changes in the six radio button groups in real time: the "Submit" button is switched to an available state only when all six dimensions have selected items (removing pointer-events: none and opacity: 0.5).
[0101] S5: Inject a locking signal into the electronic medical record system's storage interface to prevent saving.
[0102] Synchronizing with S4, the backend service injects a lock signal into the electronic medical record system's case storage interface. This embodiment uses the AOP interceptor pattern for implementation:
[0103] On the case saving interface method of the electronic medical record system (e.g., EMRService.saveCase(caseId, caseData)), a before advice (@Before aspect) is dynamically woven in using the Spring AOP framework. The logic of this before advice is as follows:
[0104] @Before("execution(* com.hospital.emr.service.EMRService.saveCase(..)) && args(caseId, ..)")
[0105] public void blockIfPendingReport(String caseId) {
[0106] if (symptomReportLockTable.isLocked(caseId)) {
[0107] throw new PendingSymptomReportException(
[0108] "Please complete the Infectious Disease Symptom Detection Registration Card first, then save the case file." );
[0110] }
[0111] }
[0112] Here, `symptomReportLockTable` is a lock status table in the Redis cache, with the case ID as the key and the lock flag and lock timestamp as the value. When triggered in step S4, a lock record for the current case ID is written to this table, and the lock status becomes effective.
[0113] When the doctor attempts to click the "Save" button on the electronic medical record system, the save request is intercepted by the aforementioned pre-notification after reaching the backend, resulting in a business exception. The frontend displays the message "Please complete the infectious disease symptom detection registration card before saving the case," and the case saving operation is blocked.
[0114] S6: Wait for the verification pass signal, then unlock, release and save.
[0115] The doctor completes the selection of six symptom dimensions in the symptom detection registration card form (e.g., fever - negative, diarrhea - positive, jaundice - negative, rash - negative, conjunctival redness and swelling - negative, vomiting - positive). The "Submit" button becomes available. The doctor clicks the "Submit" button, and the front end sends a submission request to the back end.
[0116] After receiving the submission request, the backend performs a data integrity check:
[0117] For each symptom in [fever, diarrhea, jaundice, rash, conjunctival erythema, vomiting]:
[0118] IF symptom.status == NULL OR symptom.status == "Not filled in":
[0119] RETURN verification failed, returning the error message "Please complete the selection of all symptom detection items".
[0120] BREAK
[0121] RETURN verification passed.
[0122] In this embodiment, the status values for the six symptom dimensions are negative, positive, negative, negative, negative, and positive, with none being empty, thus the verification passed.
[0123] After successful verification, the backend performs the following operations:
[0124] (a) Write symptom detection data into the database:
[0125] INSERT INTO symptom_report_card (
[0126] case_id, icd_code, diagnosis_name, doctor_id,
[0127] fever_result, diarrhea_result, jaundice_result,
[0128] rash_result, conjunctivitis_result, vomiting_result,
[0129] report_time, trigger_source
[0130] VALUES
[0131] 'CASE-2026-001234', '1A00', 'Cholera', 'DOC-05678',
[0132] 'Negative', 'Positive', 'Negative', 'Negative', 'Positive',
[0133] '2026-06-20 14:35:22', 'AUTO_TRIGGER' );
[0135] (b) Unlock the lock in Redis: symptomReportLockTable.unlock(caseId).
[0136] (c) Return a success response to the doctor's workstation front end and close the modal window. At this time, the doctor clicks the "Save" button again. The AOP forward notification checks the lock table and finds that the case has been unlocked. The normal save logic is allowed and the case is saved successfully.
[0137] In one embodiment, based on the previous embodiment, the following implementation is added:
[0138] Error handling: Before executing step S2, check if the ICD code obtained in step S1 is empty or a "NULL" string. If the ICD code is empty (for example, some primary healthcare institutions' electronic medical record systems do not require the diagnosis name to be associated with the ICD code), then skip step S2 and directly perform the exact matching in step S3 using the diagnosis name text. After skipping, the input conditions for step S3 no longer depend on the hit signal in S2, but directly proceed to keyword comparison.
[0139] Timeout Handling: When injecting the lock signal in step S5, the lock timestamp is recorded simultaneously. A scheduled inspection task is set up in the background (executed every 5 minutes) to scan records in the symptomReportLockTable where the lock duration exceeds 30 minutes (configurable). For timeout records, the following steps are executed automatically: revoke the lock → record the exception log → send a pop-up notification to the doctor in the infectious disease information monitoring system: "The infectious disease symptom registration card for case CASE-2026-XXXX has not been completed within the timeout period; please follow up and complete the submission."
[0140] Suspected Cluster Outbreak Checklist: A checklist will be added to the bottom of the symptom detection registration card entry interface in step S4: "Suspected Cluster Outbreak (≥n cases of infectious diseases with the same symptoms appearing in the same department / ward within 24 hours)". If the doctor checks this option, in the data writing stage after verification in step S6, in addition to writing the data to the local database, the data will also be pushed to the dedicated personnel of the Disease Prevention and Control Department in real time through the dedicated network interface of the Disease Prevention and Control Information System, and a "Cluster Outbreak Warning" label will be marked in the data packet, triggering a red warning.
[0141] In one embodiment, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described in the above embodiments.
[0142] In one embodiment, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method described in the above embodiments.
[0143] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
Claims
1. A method for mandatory monitoring and reporting of infectious disease symptoms in electronic medical records, characterized in that, include: The system captures diagnostic data entered by doctors in the electronic medical record editing interface in real time. The diagnostic data includes at least the International Classification of Diseases (ICD) code and the text of the diagnosis name. Perform a first-level coarse screening and matching on the ICD code to determine whether the ICD code falls into a preset set of ICD infectious disease classification code intervals; If the first-level coarse screening match is successful, then the second-level precise matching is performed on the diagnostic name text to determine whether the diagnostic name text matches the keywords in the preset legal infectious disease catalog keyword database. If the second-level exact match is found, the forced pop-up trigger operation and the medical record saving lock operation are executed simultaneously. The forced pop-up triggering operation includes: displaying the infectious disease symptom detection registration card filling interface in the form of a modal window at the forefront of the doctor's workstation screen. The filling interface includes negative / positive mutually exclusive check boxes for six symptom dimensions: fever, diarrhea, jaundice, rash, conjunctival redness and swelling, and vomiting, and does not contain skip or close controls. The medical record saving lock operation includes: injecting a lock signal into the medical record saving interface of the electronic medical record system to prohibit the saving operation of the current medical record; In response to the doctor completing the selection of the six symptom dimensions and submitting the form on the form interface, the integrity of the form data is verified. If the verification passes, the locking signal is revoked, the reported symptom detection data is written into the database, and the current case is allowed to be saved.
2. The method according to claim 1, characterized in that, Before performing the first-level coarse screening matching on the ICD encoding, a fault-tolerance processing step is also included: Determine whether the ICD code in the diagnostic data is empty; If the ICD code is empty, the first-level coarse matching step is skipped, and the second-level precise matching is performed directly with the diagnostic name text.
3. The method according to claim 1, characterized in that, The preset set of ICD infectious disease classification coding intervals and the database of keywords for legally notifiable infectious disease names are both stored in a configuration database that can be remotely updated. The keyword database for the list of legally notifiable infectious diseases contains the standard Chinese names of all legally notifiable infectious diseases of Class A, Class B, and Class C as stipulated in the Law of the People's Republic of China on the Prevention and Control of Infectious Diseases, as well as commonly used alternative names recognized by the health administration department. Each keyword in the database is associated with an effective timestamp.
4. The method according to claim 1, characterized in that, The infectious disease symptom detection registration card filling interface also includes an optional checkbox for "suspected cluster outbreak"; After performing integrity verification on the entered data, the process also includes: If the optional checkbox for "suspected cluster outbreak" is selected, the data will be written into the database and simultaneously pushed to the front-end machine of the local disease prevention and control center in real time through the disease prevention and control information network interface.
5. The method according to claim 1, characterized in that, The process of injecting a lock signal into the case storage interface of the electronic medical record system includes: The interceptor pattern of Aspect-Oriented Programming (AOP) is used to dynamically weave before advice into the case saving interface method of the electronic medical record system; Before executing the save logic, the pre-notification checks whether the current case ID is locked in the cache; If a locked state exists, a business exception will be thrown and a prompt message "Please complete the infectious disease symptom detection registration card first" will be returned to prevent the execution of the save operation.
6. The method according to claim 1, characterized in that, The method also includes an audit log generation step: While performing the medical record saving and locking operation, an audit log record is generated and written. The audit log records include at least: trigger timestamp, diagnostic ICD code, diagnostic name text, unique identifier of the operating physician, unique identifier of the current case, and lock operation type.
7. The method according to claim 1, characterized in that, The method also includes a timeout handling step: Record the injection timestamp of the locking signal; If the difference between the current time and the injection timestamp exceeds a preset threshold, the locking signal will be automatically revoked, the incomplete reporting event will be recorded in the exception log, and a reporting timeout notification will be sent to the doctor.
8. The method according to claim 1, characterized in that, The integrity verification of the entered data includes: Iterate through the reported status values for the six symptom dimensions; If the status value of any dimension is empty, the verification is deemed to have failed, and the user is prompted to "Please complete the selection of all symptom detection items", while keeping the filling interface displayed and the lock signal valid; If all six dimensions have a status value of "negative" or "positive", the verification is considered successful.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 8.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method as described in any one of claims 1 to 8.
