Reference only; verify against the target FastGPT release and deployment documentation.
What this category of data looks like
Data for this category originates from the Chinese Center for Disease Control and Prevention Information System, medical institution HIS systems, infectious disease reporting systems, and laboratory testing systems. Daily generated documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Data updates occur daily. Fields cover notifiable infectious disease categories, basic patient information, diagnosis results, reporting time limits, and other relevant details. Formats must follow notifiable infectious disease reporting rules. No configuration space is available for additional custom extended fields.
What constraints these characteristics impose on forms and interactions
Multi-source data access requires forms to support automatic pulling and verification of cross-system fields, to avoid manual entry errors. Daily update frequency requires interaction workflows to support batch submission and real-time correction operations, to align with the daily reporting rhythm of disease control institutions. Differences between multiple document types require forms to support switching field configurations, to match required fields for different reports. Notifiable reporting rules enforce required fields and verification logic. Interaction links must include built-in mandatory verification mechanisms, and submissions cannot skip required fields. Additionally, time-consuming case verification and time limit checking steps require forms to provide real-time field prompts and exception alerts, to reduce manual verification costs.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput field verification rules | Bind mandatory fields for statutory reports, enable real-time verification | Align with notifiable infectious disease reporting rules, avoid missed or incorrect entries |
userSelect category option configuration | Pre-set fixed options based on notifiable infectious disease categories, disable custom input | Ensure reporting categories comply with standards, reduce format errors |
| Form submission timeout period | 600 seconds | Accommodate time requirements for pulling data from multiple systems, avoid interrupted submissions mid-process |
| Batch submission batch size | First 20 entries | Match daily updated data volume, reduce system pressure from single submissions |
| Template switching configuration | Pre-set 5 commonly used report templates | Match daily document types for this category, reduce manual configuration costs |
| Real-time exception alert threshold | Calibrate based on actual testing | Adapt to differences in verification logic across institutions, avoid false alerts |
Three common misconfigurations
- Symptom: Forms appear as plain text in the conversation interface, with no interactive click functionality. Cause: Rendering configuration for the
formInputcomponent is not enabled, so the form does not load as an interactive component. - Symptom: Submission timeout errors trigger when submitting forms. Cause: Submission timeout period is set too short, unable to complete cross-system data pulling and verification processes.
- Symptom: The
userSelectcomponent does not allow selection of custom categories, and submissions are rejected by the system in special reporting scenarios. Cause: Option configuration is not adjusted, and mandatory use of pre-set categories fails to meet special reporting requirements.
How to confirm proper configuration
- Manually enter mandatory fields for a test case, then check if the system triggers real-time verification prompts after submission.
- Switch between different report templates, confirm that form fields automatically match the mandatory requirements of the corresponding document type.
- Simulate batch submission of 20 entries, confirm that the submission process does not produce timeouts or errors.
- Check that the
userSelectcomponent’s options include all entries for notifiable infectious disease categories.
The values provided above are common starting points, and should be evaluated against actual deployment 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.