What This Category of Data Looks Like
Data for this category comes from the China Disease Prevention and Control Information System, hospital HIS systems, infectious disease reporting systems, and laboratory testing systems. It is updated daily. Daily business documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Data structures include fields such as institution code, basic case information, diagnosis result, correction time, and clustered epidemic scale. All data must comply with legal infectious disease reporting specifications, and no additional custom statistical fields are included.
What Constraints These Characteristics Impose on HTTP Interfaces and External Systems
Because data comes from multiple systems and is updated daily, HTTP interfaces must support multi-source data pulling and scheduled trigger logic, and adapt to authentication and data format requirements of different systems. Because business document types are diverse and must strictly follow legal reporting rules, interfaces must support return data of varying structures, and provide field filtering capabilities to extract core business information. Because errors can lead to delayed epidemic alerts and regulatory notifications, interfaces must include data verification and exception alert mechanisms. They must also support precise queries by time range, institution code and other dimensions to improve efficiency of case verification and correction.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
Authorization | Bearer {Exclusive API Key for Disease Control Platform} | Matches authentication requirements of multi-source systems, ensures secure data access |
variables | {"report_date": "yesterday's date", "org_code": "this institution's code"} | Adapts to daily updated data pulling requirements, accurately locates same-day report data |
responseData | Only retain core fields of report cards and correction records | Filters irrelevant data, reduces transmission overhead, adapts to business verification scenarios |
| Interface timeout threshold | 600 seconds | Covers data pulling time across multiple systems, prevents request interruptions |
| Batch query limit | First 1000 entries | Matches typical scale of daily infectious disease report data, prevents interface overload |
| Data format | JSON | Compatible with data output and parsing requirements of multiple systems |
Three Common Misconfigurations
- Symptom: The number of returned results when calling the interface does not match expectations, and the offset parameter does not function as intended. Cause: The starting value of the offset parameter was not set per the interface documentation requirements, leading to chaotic pagination query logic.
- Symptom: HTTPS certificate verification failure error occurs during interface requests. Cause: The FastGPT access address was not configured as the HTTPS endpoint required by the disease control system, and HTTP protocol was used to send the request.
- Symptom: When retrieving the conversation record list, user questions cannot be accurately matched with corresponding AI reply content. Cause: The session ID association parameter was not included in the interface request, resulting in returned data not being grouped and displayed by session.
How to Confirm Proper Configuration
- Call the interface to pull same-day infectious disease report data, and verify that returned fields include core business fields such as institution code and case diagnosis result.
- Initiate a batch query request, and check whether the pagination logic of returned results matches the set offset and query quantity requirements.
- Verify the HTTPS protocol configuration, and confirm that the interface request address is the secure access endpoint specified by the disease control system.
- View interface return logs, confirm that authentication parameters have been correctly carried, and no permission-related errors have occurred.
Reference only; verify against the target FastGPT release and deployment documentation.
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.