What the data for this category looks like
Data sources for this category include the Chinese Center for Disease Control and Prevention Information System, medical institution HIS systems, infectious disease reporting systems, and laboratory testing systems. The update frequency is daily. Daily processed documents include infectious disease reporting cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Data fields include basic patient information, diagnosis results, reporting time limits, correction status, reporting institution codes, and more. All fields must comply with unified format requirements for statutory infectious disease reporting, with no additional custom statistical indicators.
What constraints these characteristics impose on deployment and upgrade
The data sources for this category are scattered and updated daily. During deployment, it is necessary to connect to interfaces from multiple heterogeneous systems. During upgrades, interface compatibility must be ensured to avoid interrupting daily data synchronization. There are various daily document types, and the field structures of different documents vary greatly. During deployment, it is necessary to configure applicable retrieval rules for different document types to ensure matching accuracy for policy basis Q&A. Statutory reporting requirements are strict. During deployment, it is necessary to build in compliant verification logic. During upgrades, the verification rule version must be updated synchronously to prevent risks of missed or delayed reporting. Additionally, data update frequency is high. During deployment, it is necessary to configure a reasonable incremental synchronization mechanism to avoid excessive system resource usage from full synchronization.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
MONGODB_URI | mongodb://admin:password@host:27017/fastgpt?authSource=admin | Stores structured data such as daily incremental infectious disease reporting cards and correction records. Correct authentication source and port must be configured to ensure stable read and write operations |
REDIS_URL | redis://:auth@host:6379/1 | Caches retrieved policy basis Q&A results to reduce repeated query overhead. Cache expiration time is determined based on actual testing |
DB_MAX_LINK | 15 connections | Adapts to multi-source data concurrent requests from daily synchronization for this category. Limits database connection count to avoid resource exhaustion |
STORAGE_S3_ENDPOINT | https://s3-cn-beijing.aliyuncs.com | Stores large-volume unstructured documents such as epidemiological investigation reports and epidemic analysis reports. A compatible object storage endpoint must be configured |
ROOT_KEY | Custom high-strength random string | Protects access permissions for the FastGPT management backend to prevent unauthorized modification of deployment configurations |
Three common misconfigurations
- Symptom: Unable to create the database normally after deployment, with error prompts for connection timeout or insufficient permissions. Cause: Authentication information for
MONGODB_URIorPG_URLis not configured correctly, or the database service has not opened the corresponding port. - Symptom: The number of results when retrieving policy basis is abnormally low, and complete regulatory documents cannot be matched. Cause: The
DB_MAX_LINKconfiguration is not adjusted, resulting in insufficient database connections and failure to pull full index data. - Symptom: Retrieval results cannot be associated with the latest correction records, and Q&A content is outdated. Cause: No daily incremental synchronization task is configured, or the trigger frequency of the synchronization task does not match the daily update rhythm of this category.
How to confirm configuration completion
- For FastGPT v4.17.0, run the built-in database connection test script to verify that the configurations for
MONGODB_URIandREDIS_URLcan read and write data normally, and confirm that connection stability meets requirements. - Trigger an incremental synchronization task, check that the number of synchronized documents matches the number of newly added statutory reporting data for the day, and confirm that the synchronization logic is working properly.
- Access the FastGPT management backend, complete authentication using
ROOT_KEY, confirm that deployment configurations can be modified normally, with no permission interception issues. - Submit a test question related to policy basis, check that the retrieval results include correct document types and field information, and confirm that the index configuration adapts to the data structure of this category.
The values provided here are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.