What data looks like for this category
This category's data primarily comes from China's national Center for Disease Control and Prevention information system, hospital HIS systems, infectious disease reporting systems, and laboratory testing systems. The update frequency is daily. Documents processed daily include infectious disease reporting cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Fields include basic patient information, diagnosis results, reporting timelines, laboratory testing data, and more. Different documents must match corresponding fields per regulatory rules. There are no unified fixed units, and field requirements must be adapted separately per document type.
Constraints during deployment and upgrade
Daily updated bulk data requires support for high-concurrency batch processing tasks to avoid overall delays caused by single-item processing delays. Multi-source data integration needs adaptation to different system output formats, so flexible data parsing rules must be configured during deployment. Document fields must strictly match statutory reporting rules. Historical verification logic must be retained during upgrades to avoid compromising existing compliance. Storage and transmission of large volumes of sensitive public health data must comply with security standards, and strict access controls must be configured during deployment.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
REDIS_URL | redis://:custom password@deployment host IP:6379/0 | Used to cache temporary results of daily batch verification, reduce redundant computation overhead, and improve processing efficiency |
STORAGE_S3_ENDPOINT | http://local object storage service IP:9000 | Used to store large volumes of case materials such as infectious disease reporting cards and epidemiological investigation reports, ensuring stable large-file read and write operations |
FILE_TOKEN_KEY | 32-character randomly generated string | Generates secure access tokens for uploaded case materials to prevent unauthorized access to sensitive public health data |
DB_MAX_LINK | 20–30 | Adapts to the daily batch processing volume of case data, controls database connection count to avoid resource exhaustion |
PG_URL | postgresql://business username:custom password@database host IP:5432/CDC business database | Persistently stores historical records and verification results of case reviews to support compliance traceability |
Three common mistakes
- Symptom: The case review interface displays "File access denied", and uploaded infectious disease reporting cards fail to load. Cause:
FILE_TOKEN_KEYis not configured correctly, so the system cannot generate valid access tokens to verify file permissions. - Symptom: Tasks time out when processing daily case data in bulk. System logs show "Database connection pool exhausted". Cause: The value of
DB_MAX_LINKis lower than the number of concurrent tasks, so database connections cannot be allocated for all processing requests. - Symptom: When deployed on Windows Server 2022, the object storage fails to mount properly, and the system prompts "Connection timed out". Cause: Network access permissions for
STORAGE_S3_ENDPOINTare not configured, so the system cannot establish communication with the storage service.
How to confirm proper configuration
- Access the domain corresponding to
FE_DOMAIN, log in to the system, and attempt to upload a standard infectious disease reporting card. Confirm that the file can be stored normally and displayed correctly in the interface. - Execute a batch verification task, check the system logs, and confirm that the database connection count does not exceed the set value of
DB_MAX_LINK. - Check the cache service corresponding to
REDIS_URL, confirm that temporary verification data can be read and written normally, and there are no read/write failure logs. - Check the storage bucket corresponding to
STORAGE_S3_ENDPOINT, confirm that uploaded case materials have been successfully written to the corresponding directory.
The values given 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.