What this category of data looks like
Daily business documents for this category include medical insurance settlement lists, expense details, medical record homepages, prescriptions, rejection lists, and settlement reconciliation statements. Data sources are the national medical security information platform, hospital HIS and medical insurance interfaces, medical insurance catalog and coding libraries, and cross-regional medical settlement platforms. The update frequency is daily.
Data fields cover diagnosis and treatment item and drug and consumable codes, expense amounts, insured person identifiers, settlement status, and more. Units include yuan, items, dates, and others. The number and structure of fields per document vary slightly based on specific business scenarios.
Constraints imposed on deployment and upgrade
Daily updated data sources require configuring scheduled synchronization tasks during deployment to ensure that same-day settlement documents, rejection lists and other business data can be pulled into storage in a timely manner. Differences in the structure of multiple types of documents require index configurations to adapt to parsing rules for different fields, to avoid field matching errors. Data docking requirements from multiple sources need multiple storage and interface connection parameters to be configured, to ensure the stability of data pulling. At the same time, the data involves sensitive information of medical insurance funds and insured persons, so deployment and upgrade processes must strictly follow data security specifications to avoid leakage of sensitive information.
How to configure parameters
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 concurrent connections | Matches concurrent access demands for daily batch settlement documents, prevents database connection exhaustion |
STORAGE_S3_ENDPOINT | Endpoint address of the institution’s private storage, quota set to 1000 MB | Connects to batch documents such as settlement bills and rejection lists exported from hospital HIS, meets single-day data storage requirements |
REDIS_URL | Local private Redis instance, connection timeout set to 600 seconds | Caches frequently accessed medical insurance catalog coding data, reduces frequency of external interface calls |
MONGODB_URI | Points to the storage repository for batch settlement audit historical datasets | Stores daily updated settlement reconciliation statements and appeal records, supports business retrospective queries |
FILE_TOKEN_KEY | Configured according to the institution’s own key generation rules | Encrypts stored sensitive information of insured persons, complies with data security specifications |
Three common misconfigurations
- Issue: After upgrading FastGPT v4.17.0, an error "field parsing failed" is prompted when importing a medical insurance settlement list CSV file. Cause: The new version updated the column name verification rules for CSV files, and does not support the non-standard column name order used in older version settlement lists.
- Issue: Pulling the fastgpt-minio image times out during deployment, returns status code 504. Cause: No acceleration node for the private image repository is configured, leading to slow cross-region pulling speed.
- Issue: No image dataset add option appears in the privately deployed knowledge base interface. Cause: The
STORAGE_S3_ENDPOINTparameter is not configured correctly, causing the image storage function to not be enabled.
How to confirm configuration is complete
- Run the preset scheduled synchronization task, check whether daily settlement document data can be pulled from the national medical insurance information platform interface, and confirm that there are new data entries in the storage repository pointed to by
MONGODB_URI. - Call the cache query interface, check whether the Redis instance corresponding to
REDIS_URLcan normally return cached medical insurance catalog coding data, with no timeout or connection errors. - Upload a prescription image to the knowledge base for testing, confirm that the
FILE_TOKEN_KEYconfiguration takes effect, and the image can be stored normally and displayed on the interface. - View database connection logs, confirm that the concurrent connection count for
DB_MAX_LINKdoes not exceed the set threshold, and no connection exhaustion related errors occur.
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.