What the data for this category looks like
Data sources for this category include the China Center for Disease Control and Prevention Information System, hospital HIS and infectious disease reporting systems, and laboratory testing systems. The update frequency is daily. Daily processed documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Core fields cover basic case information, diagnosis time, reporting unit, correction status, test results, and other relevant data. Format requirements of legal reporting rules must be strictly matched.
Constraints imposed by these characteristics on deployment and upgrade
Daily updated data sources require configuring stable scheduled synchronization tasks during deployment to avoid data delays. Heterogeneous data from multiple sources requires pre-configuring field mapping rules to ensure case information from different systems can be uniformly entered into the ledger. Diverse business document structures require retaining logic compatible with older report formats during upgrades to prevent parsing failures for documents such as correction records and epidemiological investigation reports. Strict legal reporting requirements mean basic field verification logic must be built into the deployment link to prevent non-compliant content from entering the aggregation process.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 200 per minute | Limits the data source request frequency during daily synchronization to avoid triggering access rate limits from the disease prevention and control system |
MONGODB_URI | mongodb://username:password@host:port/fastgpt_cdc?authSource=admin | Stores structured business data such as case ledgers and correction records. Dedicated database permissions and authentication must be configured |
REDIS_URL | redis://:complexpassword@internal-redis:6379/0 | Caches temporary data from daily synchronization and scheduled task status to reduce overhead from repeated data source queries |
STORAGE_S3_ENDPOINT | http://internal-storage.cdc.gov.cn:9000 | Stores unstructured documents such as epidemiological investigation reports and epidemic analysis reports, adapting to internal compliant storage nodes |
FILE_TOKEN_KEY | Randomly generated 32-character string | Encrypts uploaded report file links to prevent unauthorized access to sensitive business documents |
ROOT_KEY | Custom strong-complexity string of 16 or more characters | Configures system administrator permissions, only used for initial post-deployment configuration and upgrade operations |
Three Common Misconfigurations
- Pulling a new container image results in a login error, with the interface prompting "invalid administrator key". The cause is failing to retain the original deployment's
ROOT_KEYconfiguration; the key change after upgrade causes permission verification failure. - Using a public network storage address when configuring
STORAGE_S3_ENDPOINTleads to a 504 timeout error when uploading large epidemiological investigation reports. The cause is that the internal storage node is network-isolated from the disease prevention and control system, so the public network address cannot be accessed normally. - Not configuring a scheduled synchronization task results in inconsistent ledger data and newly added daily case records. The cause is failing to set automatic synchronization rules according to the daily updated business rhythm, leading to data lag.
How to Verify Configurations Are Correct
- Execute
docker logs fastgpt-cdcto view container startup logs, confirm that core configurations such asMONGODB_URIandREDIS_URLload without errors, and adapt to the log format of FastGPT v4.17.0. - Upload a test infectious disease report card, confirm that the file can be stored normally and a corresponding entry is generated in the ledger management interface.
- Manually trigger a scheduled synchronization task, verify that the synchronized ledger data matches the newly added daily records from the data source.
- Log in to the system backend using the configured
ROOT_KEY, confirm that administrator permissions are normal and configuration items have not been tampered with.
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.