What this category of data looks like
This category of data originates from 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. Documents routinely generated and processed include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Document fields include basic patient information, diagnosis results, reporting time limits, correction notes, clustered epidemic association information, and more. Units include dates, patient counts, test result values, and more. The overall data is generated around the full process of statutory infectious disease reporting and monitoring.
Constraints imposed by these characteristics on HTTP interfaces and external systems
The daily updated business rhythm requires HTTP interfaces to support incremental synchronization and batch data pulling, to avoid repeated processing of historical data and adapt to the daily reporting frequency of disease control scenarios. Multi-source heterogeneous data sources require interfaces to be compatible with return formats from different systems, and match the dedicated field structures of documents such as infectious disease report cards and correction records. Compliance requirements for statutory infectious disease reporting require interfaces to return complete verification fields, to support the review link in checking compliance items such as reporting time limits and diagnosis matching. The aggregation requirement for clustered epidemics and abnormal signals requires interfaces to support precise data filtering by time range and case type, reducing invalid data transmission volume.
Reference only; verify against the target FastGPT release and deployment documentation.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Authorization | Carry an API access token issued by the disease control system | Comply with identity verification requirements of external systems, prevent unauthorized access |
| Interface timeout period | 300–600 seconds | Adapt to the time consumption of multi-source data pulling, avoid timeouts triggered by large data volumes |
| Batch pull quantity | First 200 entries | Match the daily updated data scale, balance interface load and transmission efficiency |
responseData field parsing rules | Split and map fields by document type | Correspond to the dedicated field structures of different documents such as infectious disease report cards and correction records |
variables configuration | Bind reporting time limit and case type filtering conditions | Support dynamic adjustment of interface request parameters per business rules |
| Retry mechanism configuration | Retry 2 times after failure, 60-second interval | Address temporary network fluctuations or short-term system unavailability scenarios |
Three common misconfigurations
- Symptom: Interface requests return an SSL handshake failure error, prompting that self-signed certificates cannot be verified. Cause: Trust for custom SSL certificates was not configured, and the HTTPS interface of the internal disease control system was called directly.
- Symptom: Interface calls return a 404 Page Not Found error. Cause: The
Authorizationtoken is not configured correctly, or the request path does not match the actual interface address of the external system. - Symptom: The
responseDatafield returned by the interface is empty, and the review link cannot obtain case correction records. Cause: Field mapping rules were not configured by document type, leading to filtering of dedicated fields for correction records during parsing.
How to verify successful configuration
- Initiate a test request, check that the returned HTTP status code is 200, confirm that identity verification has passed.
- Compare the
responseDatafield returned by the interface with the local document template, confirm that the field mapping covers the core information of infectious disease report cards and case correction records. - Configure a scheduled trigger request, verify that the daily pulled data volume matches the actual updated volume, confirm that the incremental synchronization logic is effective.
- Simulate a network fluctuation scenario, check that the interface can normally obtain data after triggering the retry mechanism, confirm that the retry rule configuration is correct.
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.