What data for this category looks like
Data sources for this category include the Chinese Center for Disease Control and Prevention Information System, medical institution HIS and infectious disease reporting systems, laboratory testing systems, as well as disease control policy interpretations and party building work guidance documents related to party building learning. Daily documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Data is updated daily. Data fields cover basic case information, diagnosis classification, reporting time limit, correction flag, clustered epidemic association flag, and more. Field units include dates, case counts, institution codes, diagnosis codes, and more. There is no unified fixed multi-field combination format. Fields must be matched according to legal reporting rules.
What constraints do these characteristics impose on the forms and interactions link
Multi-source data access requires forms to support automatic pulling and verification of cross-system fields, to avoid manual entry errors. The daily updated data feature requires form interactions to support real-time synchronization of the latest case data, to ensure retrieved content aligns with daily updated epidemic information. The strong compliance requirement for legally reported documents requires forms to set required fields, format verification, and exception reminders, to prevent underreporting and delayed reporting. Field differences across documents require forms to support dynamic switching of control types, to adapt to entry needs for different documents such as report cards and correction records. Hard requirements from legal infectious disease reporting rules limit the custom scope of form controls, and must strictly match official specified fields and verification logic. The party building learning Q&A requirement requires that party building related content retrieval can be triggered at any time in form interactions. An independent Q&A trigger control must be configured, either separated from or linked to form entry controls.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput | Match controls by field type; set a 1000–1500 character limit for text areas | Adapt to long text entry needs for documents such as infectious disease report cards and epidemiological investigation reports, and avoid content truncation that affects retrieval |
userSelect | Pre-set options for disease control institutions, medical institutions, public health departments, and health commission disease control divisions | Match the reporting identity selection scenario for typical entities in this category, and reduce manual input errors |
| Form validation rules | Set according to legal reporting requirements; verify that onset date is no later than report date, and required fields are not empty | Comply with compliance standards for infectious disease information reporting, and mitigate risks of underreporting and delayed reporting |
| Knowledge base recall limit | Top 8 entries | Balance retrieval efficiency and information completeness, and adapt to the document volume of daily updated data |
| Party building Q&A trigger configuration | Set an independent trigger button linked to the party building knowledge base | Meet the independent retrieval needs of party building learning Q&A, and do not interfere with the form entry process |
| Custom control switch | Enable | Cover special fields not covered by built-in controls, such as case correction reasons and clustered epidemic descriptions |
| Data synchronization timeout | 300 seconds | Adapt to response times for multi-system data pulling, and prevent form loading failures caused by synchronization failures |
Three Common Mistakes
- Symptom: After official release, a prompt indicates no knowledge base selected, but debugging preview works normally. Cause: The knowledge base binding relationship configured is not synchronized in the production environment, or application permissions do not grant access to the corresponding data source.
- Symptom: Long input content cannot complete knowledge base retrieval, and the number of recalled results is abnormal. Cause: The character limit configuration for
formInputis not adjusted, and content exceeds the built-in limit, leading to truncation that prevents complete matching with knowledge base documents. - Symptom: Custom input controls cannot be used to enter special fields. Cause: The application's custom control permission is not enabled, or the control configuration does not match exclusive fields for infectious disease reports, such as case correction descriptions.
How to Confirm Configuration is Complete
- Enter a simulated infectious disease report card data set, trigger form validation, and check if non-compliant inputs such as a report date earlier than the onset date are blocked.
- Call the custom control configured for
formInput, enter content for special fields such as case correction reasons, and confirm that the control renders normally and data submission is completed. - Click the party building Q&A trigger button, retrieve party building related documents, and confirm that results are returned normally.
- Trigger knowledge base retrieval, and check that recalled documents include category-specific documents such as infectious disease report cards and epidemic analysis reports.
- Use the official API to trigger form submission and Q&A retrieval, and verify that external interaction processes complete normally.
- Verify cross-system data synchronization, and confirm that the form can pull the latest case data from the Chinese Center for Disease Control and Prevention Information System, with no timeout errors.
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.