What the data for this category looks like
Data for this category primarily comes from the Chinese Center for Disease Control and Prevention Information System, hospital HIS systems, and laboratory testing systems, with a daily update frequency. Daily documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Core fields cover basic patient information, diagnosis results, reporting time limits, correction identifiers, and more. Data must be processed strictly in accordance with legal infectious disease reporting regulations.
What constraints do these characteristics impose on the "HTTP Interfaces and External Systems" link
Multi-source data access requires interfaces to support adaptation to return formats of different systems. The daily update rhythm requires ensuring the stability and low latency of interface calls. Core fields must strictly match legal reporting requirements, and interface parameters must cover required items such as basic patient information, diagnosis results, and reporting time limits. Frequent case correction requirements demand that interfaces support incremental synchronization and data update capabilities. The seriousness of legal reporting requires interfaces to have complete error capture and reporting mechanisms to avoid underreporting or delayed reporting risks.
How to set up configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Request timeout | 600 seconds | Adapts to the time consumption requirements of daily batch synchronization of disease control data, to avoid mid-process interruptions |
Authorization | Bearer Token format | Complies with identity authentication specifications of external systems, ensuring data transmission security |
variables | Includes case ID, report date, correction status | Matches core query dimensions of infectious disease report cards, enabling accurate pulling of target data |
responseData | Structured JSON format | Facilitates subsequent verification of fields such as case diagnosis results and reporting time limits, improving office efficiency |
| Retry attempts | 3 | Addresses temporary network fluctuations, reducing the probability of data synchronization failures |
| Data synchronization frequency | 2:00 AM daily | Avoids peak business hours, reducing resource occupation of external systems |
Three common mistakes
- Symptom: The access link returned by the HTTP interface does not carry the
http://prefix, causing access failure when clicked. Cause: The protocol prefix was not completed in the field processing configuration ofresponseData, leading to incomplete link resolution. - Symptom: The external system supports TRACE requests, and the interface returns complete request header information, posing a risk of authentication information leakage. Cause: The TRACE request permission of the external system was not disabled, violating HTTP security usage specifications.
- Symptom: When calling a workflow via API, the dynamically spliced text variables do not return normally, and only fixed text is displayed. Cause: The dynamic fields of case correction records were not correctly bound in the
variablesparameter, resulting in failure to replace variable content during API calls.
How to confirm the configuration is complete
- Call the test interface and check whether the fields returned by
responseDatainclude core information of infectious disease report cards, such as case ID, diagnosis results, and reporting time limits. - Verify that the
Authorizationparameter is carried correctly, call the interface, and confirm that a 200 status code is returned with no authentication failure error messages. - Trigger the daily synchronization task and check whether it is executed during the preset time period, with no timeout or interruption logs.
- Simulate a case correction scenario, call the API, and confirm that the dynamic fields bound in
variableshave been correctly replaced into the text content.
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.