Business Process Guidance for Infectious Disease Information Reporting and Monitoring: HTTP Interfaces and External Systems

What this category of data 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. Daily documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. The data update frequency is daily. Data fields include case unique identifiers, diagnostic classifications, report times, correction statuses, clustered event association identifiers, and more. All fields follow statutory public health reporting specifications, have no custom units, and the field structure strictly matches the output formats of each data source.

Constraints imposed by these characteristics on the HTTP Interfaces and External Systems link

Multi-source heterogeneous data sources require interfaces to be compatible with output formats of different systems, and support batch pulling and incremental synchronization. The daily update frequency requires interface request frequency to match the data generation cycle of the disease control system, to avoid frequent calls triggering current limiting. Sensitive case data requires interfaces to be configured with strict authentication mechanisms to ensure data transmission security. The real-time synchronization requirement for correction records and report cards requires interfaces to support precise incremental pulling, reducing resource consumption from full data transmission. At the same time, interface response timeout needs to adapt to the batch data processing speed of the disease control system, to avoid data omission or delay caused by timeout.

Configuration Settings

For FastGPT v4.17.0, the HTTP interface configuration items are as follows:

Three Common Configuration Mistakes

• The interface returns a 400 status code, but the request body has no obvious format errors. Cause: The responseData parameter is not passed in the field order required by the disease control system, causing the system to fail to parse the request body.
• Daily synchronization has no updated records, and the interface pulls empty data. Cause: The pull time configured in variables is later than the data generation time of the disease control system, resulting in no valid daily data being obtained.
• Interface calls frequently trigger current limiting interception. Cause: No reasonable request interval is set, and multiple calls initiated in a short time exceed the current limiting threshold of the disease control system.

How to Verify Correct Configuration

• An interface call is manually triggered, and the returned responseData is checked to include daily new infectious disease report cards and correction records.
• The authentication logic of the Authorization parameter is verified: the interface is called with an invalid token, and a 401 status code is confirmed to be returned.
• The pull time in variables is adjusted to a non-peak period, and the interface is confirmed to not trigger current limiting rules of the disease control system.
• FastGPT interface logs are reviewed, and the timeout time of each request is confirmed to be 600 seconds, meeting the configuration requirements.

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.