Nuclear power plant infectious disease prevention and control daily report automatic generation system and method

Abstract

This application belongs to the field of infectious disease prevention and control technology in nuclear power plants. It aims to solve the problems of low efficiency, error-proneness, and disconnect between approval and publication in existing technologies for manually generating daily infectious disease prevention and control reports. The application discloses an automatic daily infectious disease prevention and control report generation system and method for nuclear power plants. This system includes a main module for automatic daily report generation, a risk database module, a region subscription module, a risk calculation module, an attachment management module, an approval chain module, and a message notification module. These modules automatically compile and generate a PDF file containing the date, control requirements for various risk areas, a customized list of yellow-lined risk areas, risk categories and control requirements for surrounding areas, and push the report to the system. This method utilizes this system to automatically generate daily infectious disease prevention and control reports for nuclear power plants. This application achieves automatic daily generation and message push of infectious disease prevention and control reports, greatly improving the efficiency of report production and facilitating employee self-checking before travel.

Description

Technical Field

[0001] This application belongs to the field of infectious disease prevention and control technology in nuclear power plants, and in particular relates to an automatic daily reporting system and method for infectious disease prevention and control in nuclear power plants. Background Technology

[0002] With the continuous mutation of novel viruses and the dynamic changes in the surrounding infectious disease situation, nuclear power plants need to enable employees to quickly grasp the infectious disease risk levels and control policies of their city, surrounding cities, and cities with business connections, so that they can complete self-checks and fulfill the corresponding approval procedures before traveling.

[0003] Taking nuclear power plants as an example, employees typically need to monitor the infectious disease risk in the county, city, and province where the power plant is located, as well as in cities with business connections (such as headquarters and partner locations) and surrounding major cities in real time. In the traditional model, this information is scattered across multiple channels, including national and local disease control platforms, government announcements, and news media. Disease control management personnel must manually summarize, organize, and format this information daily before creating a daily report and distributing it via email or instant messaging. This process suffers from the following technical shortcomings: (1) Data acquisition is scattered and delayed: multiple official platforms are manually browsed, data is not captured in time, and the update delay is large; (2) Low efficiency in matching risk level with control requirements: Risk level classification standards and control measures vary in different regions, and manual matching is prone to errors; (3) Daily report production involves a lot of repetitive work: daily layout, data filling, PDF conversion, attachment and other operations are mechanical and repetitive, which consumes a lot of manpower; (4) Disconnect between approval and publication: When the content of the daily report involves high-risk areas, it needs to go through multiple levels of approval. However, in the traditional model, the daily report document and the approval process are separated, and the approval status cannot be automatically embedded into the daily report. (5) Single and difficult to trace push channels: manual push cannot guarantee full coverage, reading status is difficult to count, and historical daily reports are difficult to retrieve. Summary of the Invention

[0004] The purpose of this application is to provide an automatic daily report generation system and method for infectious disease prevention and control in nuclear power plants, which solves the problems of low efficiency, error-proneness, and disconnect between approval and publication in the existing technology of manually generating daily reports for infectious disease prevention and control. It realizes automatic aggregation of risk data, intelligent risk calculation of subscribed areas, automatic formatting and generation of daily report documents, automatic triggering and embedding of hierarchical approval, and automatic push and ledger recording through multiple channels.

[0005] To achieve the above objectives, this application provides the following technical solution: In a first aspect, this application provides an automatic daily reporting system for infectious disease prevention and control in nuclear power plants, comprising: The main module for automatic daily report generation is deployed on the internal server of the nuclear power plant and is responsible for data aggregation, template filling, PDF generation and full-process task scheduling. The risk database module is used to connect with the national, provincial, and municipal official disease control platforms through standardized data interfaces, and automatically update infectious disease risk level data and control policies daily. The regional subscription module is used to support the tree-structured configuration and storage of administrative divisions; The risk calculation module is used to match and calculate the risk level of each subscribed region with the real-time data of the risk database, and encapsulate it into standardized data. The attachment management module is used to receive attachment files and embed attachments at specified locations in the PDF daily report; The approval chain module is used to automatically identify risk levels and match corresponding approval processes based on the content of the daily report, and embed the approval information into the homepage of the daily report; The message notification module is used to push daily reports through two channels after approval and generate a release ledger.

[0006] As an feasible approach, the main module for automatic daily report generation includes: The template management unit is used to store standardized daily report templates and allows configuration of format, font, color scheme, and section order; The data aggregation unit is used to receive data returned by each module through a standardized data interface and perform data mapping and population according to the fields defined in the template. A PDF rendering engine used to convert filled templates into A4-sized PDF files and generate headers, footers, page numbers, and table of contents bookmarks; The version management unit is used for version control of the daily generated reports, and for historical version backtracking and difference comparison; The scheduled task scheduler is used to configure daily preset times to automatically trigger daily report generation tasks, and is used for resubmission, pause, and retry in case of abnormalities.

[0007] As an implementable approach, the risk database module includes: The data acquisition unit is used to configure multiple data adapters to connect to the public APIs or data push interfaces of the national, provincial, and municipal disease control platforms, and is compatible with multiple transmission protocols such as HTTP / HTTPS, FTP, and SFTP. The data cleaning unit is used to deduplicate, filter outliers, and encode the collected raw data, and generate a data quality report. The risk level mapping unit is used to map risk level descriptions from different sources to a unified risk category within the enterprise. The mapping rules are configured in JSON format and can be hot-updated. The control rules library is used to store in a structured format the detailed control requirements, approval process rules, quarantine periods, and nucleic acid testing requirements corresponding to each risk level. The version management unit is used to record the timestamp, data source, and number of updated entries for each data update, and is used to trace back historical risk data by date.

[0008] As an feasible approach, the regional subscription module includes: The region configuration unit provides a visual configuration interface for visual configuration of regions of interest. Hierarchical management units are used to store three-level administrative division data of province-city-district / county / street in a tree structure. Each node stores the administrative division code, region name and the ID of the parent node. The subscription relationship database is used to store the three types of regions of interest configured by the enterprise, as well as the corresponding subscription time, effective status, and priority. The change monitoring unit is used to listen for configuration change events based on database triggers or message queues. When the subscription list changes, it automatically sends a change notification to the main daily report generation module.

[0009] As an feasible approach, the risk calculation module includes: The matching engine is used for matching calculations based on fuzzy matching algorithms of administrative division codes, and is compatible with exact matching and upward merge matching. The risk assessment unit is used to determine the overall risk level of the subscribed area according to the priority of "high risk > low risk > other". The control requirements associated unit is used to retrieve the corresponding control requirements details, approval path and isolation period from the control rule base based on the determined risk level; The data encapsulation unit is used to encapsulate the risk level, control requirements, details of local risk areas, and control start date of each subscribed region into a standardized data packet in JSON format.

[0010] As an feasible approach, the attachment management module includes: The file receiving unit provides a web upload interface and supports batch uploading of multiple files. The format verification unit is used to verify the format and integrity of uploaded files and to perform virus scanning. The PDF embedding unit is used to embed verified attachment files into a specified page range at the end of the daily report PDF file, and supports automatic generation of the attachment table of contents page; The hyperlink management unit is used to add attachment description text to the corresponding section of the daily newspaper article and generate internal jump links pointing to the page number where the attachment is located.

[0011] As an implementable approach, the approval chain module includes: The workflow configuration unit is used to pre-configure multi-level approval process nodes, node approvers, and flow conditions based on the workflow engine. The risk identification unit is used to analyze the daily report content and identify whether there are keywords related to high-risk areas, which are used as a judgment condition for the branch of the approval process. The approval task push unit is used to push approval tasks to the approver's mobile device in the form of card messages via WeChat Work API or DingTalk API. The status tracking unit is used to record the status of each approval node in real time and automatically send reminders when approval is not completed within the time limit. The electronic signature embedding unit is used to embed the names of approvers at all levels, approval time, and approval opinions into the signature field on the first page of the daily report in the form of text watermarks or digital signatures after the final approval is completed.

[0012] As an implementable approach, the message notification module includes: The channel adaptation unit is used to encapsulate the calling interfaces of WeChat Enterprise API and internal office platform API, and supports multiple message types such as text message, image and text message and file message; The message assembly unit is used to assemble different message bodies according to the push target, including daily report PDF files, update reminder text and release summary; The push recording unit is used to record the message ID, push time, push channel, target audience range, and sending status of each push. The statistical analysis unit is used to statistically analyze the number of people who viewed the daily report, the viewing rate, and the distribution of the first reading time through the read receipt interface; The ledger storage unit is used to store publishing records in a structured form on the enterprise server. Fields include daily report date, version number, approval chain information, publishing time, push channel, number of views, and attachment list.

[0013] Secondly, this application provides a method for automatically generating daily infectious disease prevention and control reports for nuclear power plants, including: S1. Daily Report Initialization Steps: The daily report is automatically triggered at a preset time each day by the scheduled task scheduler, generating the daily report publication date and version number; S2. Risk data synchronization steps: Obtain risk level adjustment information and control policy change information, and after cleaning and mapping, convert them into standardized risk categories and control requirements; S3. Steps for generating the list of low-risk areas: Retrieve the enterprise's pre-configured list of low-risk areas and convert it into standardized tabular data; S4. Risk Calculation Steps for Subscribed Regions: Retrieve the pre-configured list of subscribed regions, use the administrative division code as the matching unit, match and calculate with the real-time data in the risk database, determine the risk level of each subscribed region, and split and label cities with local risk areas. S5. Daily Report Generation and Approval Steps: Automatically format the content of each section generated from S2 to S4 according to the preset template to generate a PDF daily report file. At the same time, identify whether there is information about high-risk areas in the daily report content, match the corresponding approval process according to the identification results, and embed the approval information into the daily report homepage in the form of a digital signature after approval is completed. S6. Push and Release Steps: After approval, the final version of the daily report is pushed through both the enterprise instant messaging platform and the office platform, and a release log is automatically generated.

[0014] As an feasible approach, S2 standardizes risk categories into three types: high risk, low risk, and other regions. Risk level representations from different sources are uniformly converted through mapping rules.

[0015] As an feasible approach, in S4, the list of subscribed regions includes three categories: the local region, surrounding cities, and business-related cities.

[0016] As an feasible approach, in S4, the matching calculation adopts a fuzzy matching algorithm based on administrative division codes, which is compatible with both exact matching and upward merging matching.

[0017] As an feasible approach, in S4, risk level determination follows the priority of "high risk > low risk > other".

[0018] As an feasible approach, the approval process in S5 includes: If the daily report contains information about high-risk areas, it will be subject to a five-level approval process. If no high-risk area information is available, a three-tier approval process will be applied. Once the approval process is complete, the information on writing, proofreading, reviewing, and approving the documents, along with the name of the approver, will be embedded in the homepage of the daily report in the form of a digital signature.

[0019] As an feasible approach, the release log in S6 is stored in a structured form on the enterprise server for multi-dimensional tracing and statistics by date, version number, approver, and risk level.

[0020] As an feasible approach, the number of views and read rate can be counted through the read receipt interface during the push process.

[0021] Compared with existing technologies, the automatic daily reporting system and method for infectious disease prevention and control in nuclear power plants provided in this application have the following advantages: This application realizes the automatic aggregation and standardization of multi-source heterogeneous risk data: by connecting to multi-level official platforms through the risk database module, scattered and unstructured policy texts are transformed into structured management and control rules, and the data update delay is controlled within 2 hours.

[0022] This application realizes intelligent risk calculation and local risk decomposition of the subscribed area: the fuzzy matching algorithm based on administrative division code can accurately identify local risk areas in the subscribed city, avoid the "one-size-fits-all" city-level risk assessment, and improve the accuracy of management and control.

[0023] This application achieves fully automated generation of daily report documents: from data scraping, risk calculation, template filling, PDF rendering to approval embedding, the entire process is automated without manual intervention, significantly improving production efficiency.

[0024] This application achieves deep integration of the approval process and daily report generation: the approval chain module dynamically matches the approval level according to the content of the daily report, and the approval status is embedded in the daily report file in real time, solving the problem of disconnect between approval and publication.

[0025] This application enables precise multi-channel push and full lifecycle traceability: it supports push through both instant messaging platforms and internal office platforms, and automatically generates a release log to facilitate subsequent auditing and effectiveness evaluation.

[0026] This application has good versatility and portability: through the flexible configuration of the regional subscription module, it can be adapted to the localization needs of different nuclear power plants or large industrial enterprises and can be directly replicated and promoted. Attached Figure Description

[0027] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the technical description will be briefly introduced below.

[0028] Figure 1 A structural diagram of the automatic daily report generation system for infectious disease prevention and control in nuclear power plants provided in this application; Figure 2 A flowchart of the method for automatically generating daily infectious disease prevention and control reports for nuclear power plants provided in this application; Figure 3 A schematic diagram of the PDF daily newspaper layout provided for this application. Detailed Implementation

[0029] The following detailed description provides further details on specific implementation methods.

[0030] like Figure 1 As shown, this application provides an automatic daily report generation system for infectious disease prevention and control in nuclear power plants, including a main module 101 for automatic daily report generation, and risk database module 102, region subscription module 103, risk calculation module 104, attachment management module 105, approval chain module 106, and message notification module 107, all of which are communicatively connected to the main module 101. Details are as follows: Daily Report Automatic Generation Main Module 101: Deployed on the internal server of the nuclear power plant, it serves as the core hub. It has built-in standardized daily report templates, a PDF rendering engine, a version management unit, and a scheduled task scheduler. It communicates with other modules through standardized interfaces and is responsible for data aggregation, template filling, PDF generation, and full-process task scheduling. Risk Database Module 102: It connects with the national, provincial and municipal official disease control platforms through standardized data interfaces. It has built-in data collection units, data cleaning units, risk level mapping units and control rule bases. It is used to automatically update infectious disease risk level data and control policies daily, and to convert unstructured policy texts into structured control rules. Regional Subscription Module 103: It has a built-in regional configuration unit, hierarchical management unit, subscription relationship database and change monitoring unit. It supports the tree structure configuration and storage of three-level administrative divisions of province-city-district / county / street. When the configuration changes, it automatically triggers the daily report content update. Risk Calculation Module 104: It has a built-in matching engine, risk judgment unit, control requirement association unit and data encapsulation unit. It is used to perform fuzzy matching based on administrative division code between the list of subscribed regions and the real-time data of the risk database, calculate the risk level of each subscribed region, split the local risk area information and encapsulate it into standardized data. Attachment Management Module 105: Includes a built-in file receiving unit, format verification unit, PDF embedding unit, and hyperlink management unit. It is used to receive uploaded attachment files, verify their format and size, embed attachments at specified locations in the PDF daily report, and generate internal jump links. Approval Chain Module 106: It has built-in process configuration unit, risk identification unit, approval task push unit, status tracking unit and electronic signature embedding unit. It is used to automatically identify the risk level and match the corresponding approval process according to the daily report content, drive multi-level approval, and embed the approval information into the daily report homepage. Message Notification Module 107: It has built-in channel adaptation unit, message assembly unit, push record unit and statistical analysis unit. It is used to push daily reports through the enterprise instant messaging platform and internal office platform after approval and automatically generate release ledger.

[0031] The main module 101 for automatic daily report generation is deployed on an internal server within the nuclear power plant (such as a Linux-based physical server or virtualized container). It is integrated with the enterprise's internal office system and instant messaging platform, serving as the core hub to coordinate the data and instruction flows of the other six modules. The modules communicate asynchronously with each other through RESTful APIs or message queues (such as RabbitMQ / Kafka) to ensure data consistency in high-concurrency scenarios.

[0032] The main module 101 for automatic daily report generation serves as the core control center of the system, responsible for task scheduling, data aggregation, template rendering, PDF generation, and version management.

[0033] Specifically, the main module 101 for automatically generating daily reports includes: Template Management Unit: Built-in standardized daily report templates (supports HTML / XML format). The templates define the order of the daily report sections (risk area types and control requirements, list of low-risk areas, surrounding area types and requirements, attachment descriptions, etc.). The format, font, color scheme and section order can be customized and adjusted through the management backend. Data aggregation unit: Receives risk information returned by risk calculation module 104, attachment metadata returned by attachment management module 105, and approval information returned by approval chain module 106 through standardized data interfaces, and performs data mapping and filling according to the fields defined in the template; PDF rendering engine: Based on open-source PDF generation libraries (such as iText, Apache PDFBox, or Chromium-based headless browser rendering solutions), it converts the filled template into A4-sized PDF files and supports the generation of headers, footers, page numbers, table of contents, and bookmarks. Version Management Unit: Performs version control on the daily generated reports (V1.0 is the initial draft, and after approval and rejection, it is iterated to V1.1, V2.0, etc.), and supports historical version backtracking and difference comparison; Scheduled task scheduler: Based on the Quartz or Spring Scheduler framework, it can be configured to automatically trigger the daily report generation task at 5:00 AM every day, and supports manual resending, pausing, and retrying in case of exceptions.

[0034] After the main module 101 for automatic daily report generation starts, the scheduled task generator generates a unique task ID at the preset time and sends data request instructions to each module in sequence. After each module returns data, the data aggregation unit performs field validation (non-empty validation, date format validation, and risk level enumeration value validation). After the validation passes, the PDF rendering engine is called to generate a draft PDF file, which is stored in the local path of the server, and a risk identification request is sent to the approval chain module 106.

[0035] The risk database module 102 serves as the system's data foundation, responsible for the automatic collection, cleaning, standardized storage, and incremental updates of external risk data.

[0036] Specifically, the risk database module 102 includes: Data acquisition unit: Configured with multiple data adapters to connect to the public APIs or data push interfaces of the national, provincial, and municipal disease control platforms, respectively, supporting multiple transmission protocols such as HTTP / HTTPS, FTP, and SFTP; Data cleaning unit: performs deduplication, outlier filtering (such as missing risk level fields or incorrect date formats) on the collected raw data, converts the encoding (to UTF-8), and generates a data quality report; Risk level mapping unit: Maps risk level descriptions from different sources (such as high, medium, low or Level I, Level II, Level III) to a unified risk category within the enterprise (high risk, low risk, other regions). The mapping rules support JSON format configuration and can be hot-updated. Control rule base: Stores detailed control requirements, approval process rules, quarantine period, and nucleic acid testing requirements corresponding to each risk level in a structured format. The storage medium is a relational database (such as MySQL) or a document database (such as MongoDB). Version Management Unit: Records the timestamp, data source, and number of updated entries for each data update, and supports tracing back historical risk data by date.

[0037] In practice, every morning at dawn, the data collection unit sends data requests to disease control platforms at all levels using a pre-set API key or token to obtain risk level adjustments from the previous 24 hours. The data cleaning unit extracts and validates fields from the returned JSON / XML data. The risk level mapping unit completes standardized conversion based on the latest mapping rules. The approval path rules in the control rule base are as follows: high-risk areas correspond to multi-level approval (applicant → department head → supervisor → company infectious disease prevention and control team leader), low-risk areas correspond to simplified approval (applicant → department head), and other areas correspond to a filing system. All update operations are completed within 2 hours to ensure the timeliness of daily data reports.

[0038] The regional subscription module 103 is responsible for the configuration management, hierarchical relationship maintenance, and change monitoring of the subscribed regions, enabling the localized customization of daily report content.

[0039] Specifically, the regional subscription module 103 includes: Regional Configuration Unit: Provides a visual configuration interface (Web management backend), allowing epidemic prevention and control personnel to configure regions of interest by selecting or searching; Hierarchical management unit: Administrative division data is stored in a tree structure, supporting a three-level hierarchical relationship of province-city-district / county / street. Each node stores the administrative division code (such as the GB / T 2260 standard code), the region name, and the ID of the parent node; Subscription Relationship Database: Stores the three types of regions of interest configured by the enterprise (local region, surrounding cities, and business-related cities) and their corresponding subscription time, effective status, and priority; Change Listening Unit: Based on database triggers or message queues, it listens for configuration change events. When the subscription list is added, deleted, or modified, it automatically sends a change notification to the daily report automatic generation main module 101, triggering the daily report to be updated immediately or the daily report of the next period to be recalculated.

[0040] Prevention and control management personnel configure three types of areas of interest through the region configuration unit. For example: the local area includes the entire county, city, and province where the power plant is located; surrounding cities include major neighboring cities; and business-related cities include the headquarters location and the location of collaborating units. The region configuration supports precise location through administrative division codes, and can be refined to the district / county / street level for key cities. The configured list of subscribed regions is synchronized in real time to the daily report automatic generation main module 101 and the risk calculation module 104 via a RESTful API. After the configuration is modified, the change monitoring unit automatically triggers an event, and the daily report automatic generation main module 101 adopts the latest subscription list in the next generation cycle.

[0041] The risk calculation module 104 is responsible for real-time matching of subscribed regions with the risk database, intelligent calculation of risk levels, local risk decomposition, and result encapsulation.

[0042] Specifically, the risk calculation module 104 includes: Matching engine: Fuzzy matching algorithm based on administrative division codes, supporting exact matching (district / county / street level) and upward merging matching (city level); Risk assessment unit: Based on the matching results, the overall risk level of the subscribed region is determined according to a preset priority (high risk > low risk > other); Control requirements associated with the unit: Based on the determined risk level, retrieve the corresponding control requirements details, approval path, and quarantine period from the control rule base; Data encapsulation unit: Encapsulates the risk level, control requirements, details of local risk areas, and control start date of each subscribed region into a standardized data packet in JSON format.

[0043] After receiving the list of subscribed regions, the risk calculation module 104 iterates through each subscribed region, extracts its administrative division code, and matches it with the real-time data in the risk database module 102. The matching logic is as follows: If the subscribed area is at the city level, and a district / county / street under the city's jurisdiction is high-risk, then the city is determined to have a high-risk area, and the city is marked as a "high-risk area of ​​concern" in the daily report, with a separate list of the specific high-risk district / county / street and its control requirements; the rest of the city is marked as "other areas".

[0044] If the subscribed region is at the provincial level, then iterate through all the city-level data in that province and make judgments layer by layer according to the above logic.

[0045] For cities with multiple risk levels, the highest risk level will be prioritized for labeling.

[0046] After the calculation is completed, the data encapsulation unit integrates the risk information and control requirements of all subscribed regions into a standardized data packet, which is then sent back to the daily report automatic generation main module 101 via API.

[0047] The attachment management module 105 is responsible for uploading and receiving attachment files, format verification, PDF embedding, and hyperlink management.

[0048] Specifically, the attachment management module 105 includes: File receiving unit: Provides a web upload interface, supports batch upload of multiple files, with a single file size limit (e.g., 50MB), and receives attachments such as the "Detailed Rules for Centralized Isolation and Control" and the "Complete List of Risk Areas Nationwide"; Format verification unit: Verifies the format (supports PDF, DOCX, XLSX), integrity (MD5 checksum), and virus scan of uploaded files; PDF Embedding Unit: Embeds verified attachment files into the specified page range at the end of the daily report PDF file, and supports automatic generation of the attachment table of contents; Hyperlink Management Unit: Adds attachment description text to the corresponding section of the daily report and generates an internal jump link (PDF internal anchor) pointing to the page number of the attachment.

[0049] After epidemic prevention and control personnel upload attachments via the web interface, the format verification unit performs MIME type checks and MD5 hash verification to ensure that the files have not been tampered with. The PDF embedding unit calls the PDF library API to embed the attachments as binary streams into the attachment area of ​​the main PDF file, or adds a new page at the end of the daily report to display a summary of the attachment content. The hyperlink management unit adds internal jump links in the text of the daily report, such as "See Attachment 1" and "See Attachment 2," which automatically redirect employees to the page containing the attachments when clicked.

[0050] The approval chain module 106 is responsible for configuring and storing the approval process, automatically identifying risk levels, pushing approval tasks, tracking status, and embedding approval information.

[0051] Specifically, the approval chain module 106 includes: Workflow configuration unit: Based on workflow engines (such as Activiti, Flowable), it pre-configures multi-level approval process nodes, node approvers, and flow conditions; Risk identification unit: Analyzes daily report PDF content or structured data to identify whether there are keywords related to high-risk areas, which are used as judgment conditions for branches in the approval process; Approval Task Push Unit: Through the WeChat Work API or DingTalk API, approval tasks are pushed to the approver's mobile device in the form of card messages. The approver can preview the daily report online, fill in comments, and select "Approve" or "Reject". Status tracking unit: Records the status of each approval node in real time (pending approval, under approval, approved, rejected), and automatically sends reminders when approval is not completed within the time limit; Electronic signature embedding unit: After the final approval is completed, the names of the approvers at all levels, the approval time, and the approval opinions will be embedded in the "Compilation, Verification, Review, Approval" column on the homepage of the daily report in the form of text watermarks or digital signatures.

[0052] The approval chain module 106 is pre-configured with two approval processes: a five-level approval process (high-risk daily report): editor → head of the epidemic prevention and control office → department head → supervisor → head of the company's infectious disease prevention and control team; and a three-level approval process (daily report): editor → head of the epidemic prevention and control office → department head.

[0053] After the initial draft of the daily report PDF is generated, the risk identification unit scans the risk level field in the content. If a high-risk area is detected, it automatically matches the five-level approval process; otherwise, it matches the three-level approval process. The approval task push unit sends a WeChat approval card to the first-level approver, who then clicks to open an H5 approval page. After each level of approval is completed, the status tracking unit updates the process status and pushes the task to the next node. All approval information (approver's name, approval time, and approval comments) is automatically recorded in the process database. After the final approval is completed, the electronic signature embedding unit writes the information into the PDF metadata and renders the signature area on the homepage, generating the final version of the daily report file.

[0054] The message notification module 107 is responsible for multi-channel push notifications, receipt confirmations, reading statistics, and generation of the publication log for the final daily report.

[0055] Specifically, the message notification module 107 includes: Channel adaptation unit: Encapsulates the calling interfaces of WeChat Work API and internal office platform API, supporting multiple message types such as text messages, image and text messages, and file messages; Message assembly unit: Assembles different message bodies according to the push target (all employees / management personnel), including daily report PDF files, update reminder text, and release summary; Push Recording Unit: Records the message ID, push time, push channel, target audience range, and sending status (success / failure) for each push. Statistical Analysis Unit: Through the read receipt interface of WeChat Work or the reading statistics interface of the internal platform, the daily statistical report shows the number of views, view rate, and first read time distribution. Ledger storage unit: Stores the published records in a structured format (such as JSON or relational database tables) to the enterprise server. Fields include: daily report date, version number, approval chain information, publication time, push channel, number of views, and attachment list.

[0056] After approval, the message notification module 107 calls the channel adaptation unit to push the final version of the daily report PDF to the entire staff group as a file message via the WeChat Work API, and simultaneously pushes it to the internal office platform's epidemic prevention and control section as a text and image message. The message pushed to all employees includes a daily report update reminder (e.g., "Today's Infectious Disease Prevention and Control Daily Report has been published, please check"); the message pushed to epidemic prevention and control management personnel includes a publication completion notification and a statistical summary (e.g., "The daily report was published at 08:30, push scope: all staff, current view count: 3521"). All publication records are written to the database by the ledger storage unit, supporting retrieval and export by date, version number, risk level, approver, and other dimensions, meeting the company's auditing and traceability requirements.

[0057] In addition, such as Figure 2 As shown, this application also provides a method for automatically generating daily infectious disease prevention and control reports for nuclear power plants, the specific steps of which are as follows: Step S1: Daily Report Initialization: Every day at 5:00 AM, the system's scheduled task automatically triggers the daily report generation task, obtains the server's current date (format: YYYY-MM-DD), and marks it as the daily report publication date; generates the version number V1.0 for the day, and combines the date and version number to form a unique identifier for the daily report (e.g., "2023-03-15-V1.0"), and initializes an empty daily report data object.

[0058] Step S2: Risk Data Synchronization: The system synchronizes the latest data from the national, provincial, and municipal disease control platforms via the data acquisition unit of the risk database module 102 through the HTTPS interface. After cleaning and mapping, the system extracts the currently valid risk category definitions (high risk, low risk, other regions), the corresponding control requirements text for each category, and the approval path rules, and stores them in the daily report data object according to the preset module format.

[0059] Step S3: Generation of Low-Risk Area List: The system retrieves the enterprise's pre-configured list of low-risk areas (i.e., the yellow line standard for enterprise travel) from the local database, extracts the province, city, control and traceability date, and remarks information from the list, formats it into a Markdown / HTML table through the data conversion unit, and embeds it into the "Low-Risk Area List" section of the daily report data object.

[0060] Step S4: Risk Calculation for Subscribed Regions: The system retrieves a pre-configured list of subscribed regions (such as the county, city, and province where the power plant is located, surrounding cities, and business-related cities) from the region subscription module 103. The risk calculation module 104 uses the administrative division code as the key value and performs hash matching with the real-time data in the risk database to calculate the risk level for each region. For cities with localized high-risk areas, the risk level, control start date, and control requirements for specific districts / counties / streets are broken down and labeled; other regions are labeled according to the overall risk level. The calculation results are written to the daily report data object in the format of "Region Name: Risk Level, Control Requirements".

[0061] Step S5: Daily Report Generation and Approval: The data aggregation unit of the main module 101 maps and fills in the content of each section generated in S2~S4 and the attachment metadata provided by the attachment management module 105 according to the layout order defined by the template management unit; it calls the PDF rendering engine to generate an A4-sized PDF file; the risk identification unit of the approval chain module 106 scans the content. If a high-risk area is found, a five-level approval process is triggered; otherwise, a three-level approval process is triggered. After the approver completes the online approval via mobile device, the electronic signature embedding unit writes the "writing, checking, reviewing, and approving" information and the approver's name into the first page of the PDF, generating the final version of the daily report file.

[0062] Step S6: Push Release: The message notification module 107 pushes the final version of the daily report PDF file and update reminder messages to all employees via the WeChat Work API and the internal office platform API; at the same time, it pushes a release completion notification and view statistics to the epidemic prevention and control management personnel. The ledger storage unit writes the release date, version number, approval chain, release time, push channel, and view count into the database, completing the entire closed loop.

[0063] like Figure 3 As shown in the figure, this application illustrates the layout of an automatically generated, tamper-proof PDF daily report file, from top to bottom as follows: Header area (including daily report title, publication date, and version number) → Signature area (including four levels of signatures: writing, proofreading, reviewing, and approving; the approver's name and digital signature are automatically embedded after approval) → Section 1: Risk Area Types and Control Requirements (including control requirements and approval paths for high-risk / low-risk / other areas) → Section 2: List of Low-Risk Areas (Yellow Line Standard Table for Enterprise Travel, including province, city, control tracing date, and remarks field) → Section 3: Surrounding Area Types and Requirements (including risk levels and control requirements for each subscribed city; local risk areas are separately marked) → Attachment Description Area (including the name and link of Attachment 1 and the name and link of Attachment 2) → Footer area (including contact information and page number).

[0064] This application enables the automatic aggregation of multi-source risk data, intelligent calculation of risk levels for subscribed regions, automatic generation of standardized daily report documents, automatic triggering of tiered approvals, and multi-channel push notifications. This application achieves the automatic generation and message push of daily infectious disease prevention and control reports, greatly improving the efficiency of daily report production and facilitating employees' pre-trip self-checks.

[0065] This application automatically generates a PDF file containing the date, control requirements for various risk areas, a custom list of yellow-lined risk areas, and risk categories and control requirements for surrounding areas through several modules including daily report regional subscription, risk category calculation, control policy matching, control requirement explanation, and attachment addition. This file is then pushed to users. By changing the subscribed region, this application can automatically update the daily reports for different companies.

[0066] The above description is only a specific embodiment of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application.

Claims

1. An automatic daily reporting system for infectious disease prevention and control in nuclear power plants, characterized in that, include: The main module for automatic daily report generation is used for data aggregation, template filling, PDF generation, and end-to-end task scheduling. The risk database module is used to connect with the national, provincial, and municipal official disease control platforms through standardized data interfaces to update infectious disease risk level data and control policies daily. The regional subscription module is used for configuring and storing the tree structure of administrative divisions; The risk calculation module is used to match and calculate the risk level of each subscribed region with the real-time data of the risk database, and encapsulate it into standardized data. The attachment management module is used to receive attachment files and embed attachments at specified locations in the PDF daily report; The approval chain module is used to identify risk levels based on the content of the daily report and match the corresponding approval process, and embed the approval information into the homepage of the daily report. The message notification module is used to push daily reports and generate a publication log.

2. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The main module for automatically generating daily reports includes: The template management unit is used to store standardized daily report templates; The data aggregation unit is used to receive data returned by each module through a standardized data interface and perform data mapping and population according to the fields defined in the template. A PDF rendering engine used to convert filled templates into PDF files and generate headers, footers, page numbers, and table of contents bookmarks; The version management unit is used for version control of the daily generated reports; The scheduled task scheduler is used to configure daily preset times to trigger the daily report generation task.

3. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The risk database module includes: The data acquisition unit is used to configure multiple data adapters, which are respectively connected to the public APIs or data push interfaces of the national, provincial, and municipal disease control platforms. The data cleaning unit is used to deduplicate, filter outliers, and encode the collected raw data, and generate a data quality report. The risk level mapping unit is used to map risk level descriptions from different sources to a unified risk category within the enterprise. The mapping rules are configured in JSON format and can be hot-updated. The control rules library is used to store in a structured format the detailed control requirements, approval process rules, quarantine periods, and nucleic acid testing requirements corresponding to each risk level. The version management unit is used to record the timestamp, data source, and number of updated entries for each data update, and is used to trace back historical risk data by date.

4. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The regional subscription module includes: The region configuration unit is used for visual configuration of the regions of interest. Hierarchical management units are used to store three-level administrative division data: province-city-district / county / street. Each node stores the administrative division code, region name, and the ID of the superior node. The subscription relationship database is used to store the three types of regions of interest configured by the enterprise, as well as the corresponding subscription time, effective status, and priority. The change listening unit is used to listen for configuration change events based on database triggers or message queues. When the subscription list changes, it sends a change notification to the main daily report generation module.

5. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The risk calculation module includes: The matching engine is used for matching calculations based on fuzzy matching algorithms of administrative division codes, and is compatible with exact matching and upward merge matching. The risk assessment unit is used to determine the overall risk level of the subscribed region according to the priority of the risks. The control requirements associated unit is used to retrieve the corresponding control requirements details, approval path and isolation period from the control rule base according to the determined risk level; The data encapsulation unit is used to encapsulate the risk level, control requirements, details of local risk areas, and control start date of each subscribed region into a standardized data packet.

6. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The attachment management module includes: The file receiving unit is used for batch uploading of multiple files. The format verification unit is used to verify the format and integrity of uploaded files and to perform virus scanning. The PDF embedding unit is used to embed verified attachment files into a specified page range at the end of the daily report PDF file; The hyperlink management unit is used to add attachment description text to the corresponding section of the daily newspaper article and generate internal jump links pointing to the page number where the attachment is located.

7. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The approval chain module includes: The workflow configuration unit is used to pre-configure multi-level approval process nodes, node approvers, and flow conditions based on the workflow engine. The risk identification unit is used to analyze the daily report content and identify whether there are keywords related to high-risk areas, which are used as a judgment condition for the branch of the approval process. The approval task push unit is used to push approval tasks to the approver's mobile device in the form of card messages; The status tracking unit is used to record the status of each approval node in real time and send reminders when approval is not completed within the time limit. The electronic signature embedding unit is used to embed the names of approvers at all levels, approval time, and approval opinions into the signature field on the first page of the daily report in the form of text watermarks or digital signatures after the final approval is completed.

8. The automatic daily reporting system for infectious disease prevention and control in nuclear power plants according to claim 1, characterized in that, The message notification module includes: The channel adaptation unit is used to encapsulate the calling interfaces of WeChat Enterprise API and internal office platform API, and supports multiple message types such as text message, image and text message and file message; The message assembly unit is used to assemble different message bodies according to the push target; The push recording unit is used to record the message ID, push time, push channel, target audience range, and sending status of each push. The statistical analysis unit is used to statistically analyze the number of people who viewed the daily report, the viewing rate, and the distribution of the first reading time through the read receipt interface; The ledger storage unit is used to store publication records in a structured format on the enterprise server.

9. A method for automatically generating daily infectious disease prevention and control reports in nuclear power plants, characterized in that, include: S1: Automatically triggered at a preset time each day via a scheduled task scheduler to generate the daily report publication date and version number; S2: Obtain information on risk level adjustments and changes in control policies, and after cleaning and mapping, transform them into standardized risk categories and control requirements; S3: Retrieve the enterprise's pre-configured list of low-risk areas and convert it into standardized tabular data; S4: Retrieve the pre-configured list of subscribed regions, use administrative division codes as matching units, match and calculate with real-time data in the risk database, determine the risk level of each subscribed region, and split and label cities with local risk areas. S5: Arrange the content of each section generated by S2~S4 according to the preset template, generate a daily report file in PDF format, and at the same time identify whether there is information about high-risk areas in the daily report content. Match the corresponding approval process according to the identification results, and after the approval is completed, embed the approval information into the homepage of the daily report in the form of a digital signature. S6: After approval, push out the final daily report file and generate a release log.

10. The method for automatically generating daily infectious disease prevention and control reports in nuclear power plants according to claim 9, characterized in that, In S5, the approval process includes: If the daily report contains information about high-risk areas, it will be subject to a five-level approval process. If no high-risk area information is available, a three-tier approval process will be applied. Once the approval process is complete, the information on writing, proofreading, reviewing, and approving the documents, along with the name of the approver, will be embedded in the homepage of the daily report in the form of a digital signature.

Images