What the data for this category looks like
Data sources for this category include the Chinese Center for Disease Control and Prevention Information System, hospital HIS systems, infectious disease reporting systems, and laboratory testing systems. The update frequency is daily. Daily documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered outbreak reports, and epidemiological investigation reports. Data fields must comply with legal infectious disease reporting rules, and include core items such as case classification, onset date, and diagnosis date. The date format is uniformly YYYY-MM-DD. Case statistics use "cases" as the unit.
Constraints from data characteristics on deployment and upgrade
The daily update frequency requires deployment processes to ensure stable service operation and avoid interrupting data synchronization workflows. Multiple heterogeneous data sources require adaptation to different system interface formats. Upgrades must maintain compatibility with legacy data import rules. Diverse document types require the system to support mixed storage of structured and unstructured data. Legal reporting rules require built-in field validation logic during deployment to prevent non-compliant data from entering the system. Cross-version upgrades must retain compatibility with historical report card formats to avoid historical data becoming unqueryable due to format changes. Routine time-consuming tasks such as case verification and correction require the system to be configured with fast validation rules during deployment to reduce manual intervention costs.
Configuration recommendations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 connections | Adapts to connection requirements for daily batch import of multi-source data, prevents synchronization failures caused by exhausted connection pools |
MONGODB_URI | Configure read/write permissions per case correction record format | Stores unstructured documents such as epidemiological investigation reports and clustered outbreak reports |
PG_URL | Bind to a dedicated database instance | Stores structured fields of infectious disease report cards, ensures stability for high-frequency queries |
REDIS_URL | 600-second timeout configuration | Caches temporary calculation results of daily epidemic analysis reports, reduces database load from repeated queries |
FE_DOMAIN | Deploy an internal network access domain name | Adapts to access restriction requirements of disease control institution internal office networks |
STORAGE_S3_ENDPOINT | Connect to a self-owned object storage address with capacity over 500 GB | Stores large files such as epidemic analysis reports and epidemiological investigation reports |
FILE_TOKEN_KEY | 32-bit random string | Used to generate file access tokens, ensures access security for sensitive documents |
Three common configuration errors
- Issue: Database migration failure errors occur during cross-version upgrades, with a 500 status code returned. Cause: Skipped versions that include database script updates, and did not execute necessary table structure change operations.
- Issue: Daily data synchronization tasks time out, with connection timeout prompts in logs. Cause: The
DB_MAX_LINKconfiguration was not adjusted, and the connection pool capacity is insufficient to support simultaneous import of multi-source data. - Issue: Case correction records cannot be written normally, with corresponding fields showing empty. Cause: The read/write permissions for
MONGODB_URIwere not configured correctly, preventing corrected case data from being written to storage media.
How to verify correct configuration
- Execute the local upgrade script in a FastGPT v4.17.0 environment, confirm no database migration-related errors appear in the console.
- Trigger a single-day data synchronization task, check that the synchronization logs contain no connection timeout or permission denial prompts.
- Access the internal network page corresponding to
FE_DOMAIN, confirm that the imported list of infectious disease report cards loads normally. - Upload a test epidemiological investigation report, confirm the file storage path matches the storage address configured in
STORAGE_S3_ENDPOINT. - Verify server resource configuration, confirm it meets the basic operating requirements for private deployment.
The values provided 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.