Reference only; verify against the target FastGPT release and deployment documentation.
What the data for this category looks like
Typical processing entities include disease control institutions, public health departments of medical institutions, and disease control divisions of health commissions. Data sources include the Chinese Disease Prevention and Control Information System, medical institution HIS systems, infectious disease reporting systems, and laboratory testing systems. Documents such as notifiable infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports are generated on a daily basis. Data is updated daily. Core fields include notifiable infectious disease categories, basic patient information, diagnosis results, correction flags, and more. Processing must strictly follow statutory reporting rules.
What constraints these characteristics impose on forms and interactions
Since data is updated daily and processing must follow statutory reporting rules, form interactions must support real-time validation of reporting time limits and compliance of infectious disease categories. Multi-source data imports cause differences in field formats, so forms must support compatible input in multiple formats and automatic field alignment. Case correction records require retention of historical version traces, so interaction flows must support field revision logging and version tracing. Clustered epidemic reports require rapid aggregation of multiple patient information, so forms must support batch associated input and automatic anomaly signal alerts. The most time-consuming step involves verifying patient diagnoses and reporting time limits, so forms must support quick location of abnormal fields. Additionally, requirements for multi-system integration mean forms must support fetching initialization information from specified data sources to reduce manual repetitive input.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Form Input Configuration | Supports mixed input of text, single-select, and multi-select options; maximum input length 800–1200 characters | Matches the standard field length of notifiable infectious disease report cards, avoiding exceeding input limits for statutory documents |
| User Selection Component | Preconfigured list of notifiable infectious disease categories, sorted by official classification | Ensures entered infectious disease categories comply with statutory reporting rules, reducing compliance errors |
| Interface Timeout Threshold | 600 seconds | Adapts to latency scenarios for multi-source data integration, preventing form submission failures caused by data fetch timeouts |
| Batch Input Switch | Enabled | Supports batch associated input of multiple patients for clustered epidemic reports, improving processing efficiency |
| Revision Logging Configuration | Enables field revision records | Meets historical tracing requirements for case correction records, satisfying regulatory verification needs |
| Data Source Initialization | Enables formInput to associate specified system fields | Integrates with the Chinese Disease Prevention and Control Information System to reduce manual data entry workload |
Three common misconfigurations
- Issue: Forms cannot connect to collaboration tools normally, and data is lost after submission. Cause: Cross-system connection permission verification rules are not configured, causing the collaboration end to fail to sync infectious disease report data entered via the form.
- Issue: Interfaces cannot fetch application initialization information, including preset form fields and opening remarks content. Cause: The
formInputassociated data source initialization configuration is not enabled, causing the interface to fail to pull the preset statutory report field template. - Issue: Text converted from voice input cannot match the notifiable infectious disease category options, causing submission failure. Cause: Automatic matching verification for the
userSelectcomponent is not enabled, so voice transcription content does not trigger compliance verification logic.
How to confirm successful configuration
- Manually enter standard notifiable infectious disease report card content, check if real-time validation prompts for time limit and category compliance are triggered.
- Call the specified interface, confirm that preset form fields and opening remarks content can be fetched, matching the statutory report template.
- Enable the batch input function, attempt to associate multiple patient information, confirm that the form can normally aggregate and submit data.
- Enable the voice input function, after transcribing content, check if preset category options are automatically matched.
The values provided here are common starting points, and should be evaluated against the user'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.