What this category of data looks like
The data sources for this category are the Chinese Center for Disease Control and Prevention Information System, hospital HIS systems, and laboratory testing systems. The update frequency is daily. Common documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Most data consists of structured fields, including legally required fields such as unique case identifiers, diagnosis time, infectious disease classification, reporting institution, and correction status. Some documents include unstructured attachments, and field content must be processed in strict accordance with legal infectious disease reporting rules.
What constraints do these characteristics impose on HTTP interfaces and external systems
Daily updated data requires interfaces to adapt to scheduled call rhythms to avoid frequent calls that exceed system limits. The need to connect multiple data sources requires interfaces to support field format adaptation for different systems, ensuring extracted fields meet legal reporting requirements. The existence of case correction records requires interfaces to match the unique identifiers of original reports to avoid duplicate or incorrect summaries. The rigor of legal reporting requires reliable interface calls to prevent regulatory risks from missed or delayed reports.
How to set configurations
These configurations apply to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Authorization | Bearer {CDC system API access key} | Adapts to the standard authentication method for official CDC system interfaces |
variables | {"data_range": "Yesterday 00:00 to Today 00:00"} | Matches the daily updated infectious disease case data range for this category |
responseData | Extract fields: Unique case identifier, diagnosis time, infectious disease classification, reporting institution, correction marker | Corresponds to the required field requirements for legal infectious disease reports |
| Timeout duration | 600 seconds | Bulk data pulls from CDC systems take processing time; prevents early request termination |
| Failure retry count | 3 times | Ensures interface call stability and reduces the risk of missed data extraction |
Three common mistakes
- The interface returns data but the extracted fields are empty. Cause: Failed to explicitly specify the fields to extract in
responseData, or the field names do not match the actual fields returned by the CDC system. - The number of results from bulk data pulls is far lower than the actual number of cases. Cause: Failed to configure the correct data range via
variables, or the interface call frequency did not adapt to the daily update rhythm, resulting in some data not being pulled. - Interface calls return a 401 Unauthorized error. Cause: The key configured in
Authorizationhas expired or has insufficient permissions, and the authentication rules of the CDC system were not followed.
How to confirm the configuration is correct
- Call the test interface and check if the returned
responseDataincludes the preset required fields. - Adjust the data range parameter in
variablesto verify that the interface can return case data for the corresponding time period. - Simulate interface timeout or authentication failure scenarios to check if the preset retry logic is triggered.
- Configure a scheduled task to verify that the interface can be called at the preset frequency.
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.