What this category of data looks like
This category of data comes from the Chinese Center for Disease Control and Prevention Information System, medical institution HIS and infectious disease reporting systems, and laboratory testing systems. The update frequency is daily. Daily documents include infectious disease report cards, epidemic analysis reports, case correction records, clustered epidemic reports, and epidemiological investigation reports. Data fields include case unique identifiers, diagnosis time, reporting unit, correction status, and similar items. Document structures are mostly structured tables paired with professional analysis text, with no additional redundant non-business fields.
What constraints do these characteristics impose on the citation sources and traceability link
Multiple system data sources require that corresponding system unique identifiers must be associated during traceability to avoid cross-system data confusion. The daily update frequency requires that the knowledge base synchronization cycle matches the business rhythm, otherwise the traceability content cannot reflect the latest corrected case information. The document structure combining structured content and text requires that traceability must accurately locate a single report card or analysis chapter. Vague association with the entire document cannot meet business verification needs. Legal reporting rules require that traceability results must be traceable back to the original business documents to ensure citation compliance.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the core content length of a single business document, ensuring complete citations without exceeding context limits |
responseData | Enabled | Mandatorily returns metadata of citation sources, including business identifiers such as document source system and report number |
detail | Enabled | Displays specific chapters and fields of cited content, matching the structured characteristics of business documents |
| Knowledge base synchronization cycle | Daily | Matches the daily update frequency of business data, ensuring traceability content reflects the latest corrected information |
| Upper limit of recalled associated documents | Top 3 entries | Avoids interference from excessive irrelevant citations, focusing on core policy and business basis |
| Citation source display format | Structured fields + document number | Corresponds to the unique identifier rules of business documents, enabling quick verification |
Reference only; verify against the target FastGPT release and deployment documentation.
Three common configuration errors
- Phenomenon: The output does not display any citation source metadata, or the citation fields are empty. Cause: The
responseDataconfiguration item is not enabled, and the source metadata return function is not activated. - Phenomenon: Traceability cannot locate specific case report cards or analysis chapters, only vague document titles are displayed. Cause: The
detailconfiguration item is not enabled, and specific chapters and field information of cited content are not extracted. - Phenomenon: The total word count of the associated knowledge base exceeds the system limit, causing some core business documents to fail to be recalled for traceability. Cause: The total word count limit of the associated knowledge base is not checked in advance, and core business documents are not filtered during configuration.
How to verify a successful configuration
Initiate a conversation containing questions related to infectious disease reports. Confirm whether the reply includes metadata fields of citation sources, such as report number, system source, and similar items. Select the citation display area in the reply. Confirm that navigation to the specific chapter of the original uploaded document is available, and that it matches the structured fields of the business document. Review the knowledge base synchronization log. Confirm that the synchronization cycle is daily, and that no delayed updates have occurred. Adjust the number of associated knowledge bases. Verify whether the system prompts that the association limit has been exceeded. Confirm that the configuration complies with platform rules.
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.