This page outlines key deployment and upgrade configuration details for medical insurance expense settlement audit workflows focused on declaration materials and file audits. It is built for FastGPT v4.17.0, and targets state-owned enterprises, government bodies, and public service sectors.
What this category of data looks like
Daily processing documents for this category include medical insurance settlement lists, expense details, medical record homepages, prescriptions, rejection lists, and settlement reconciliation statements. Data sources include the national medical security information platform, hospital HIS and medical insurance interfaces, medical insurance catalog and coding libraries, and cross-regional medical settlement platforms. Update frequency is daily. Data fields include diagnosis and treatment item and pharmaceutical consumable codes, expense amounts, insured person identity identifiers, settlement status, and more. All fields must strictly follow official unified coding rules; no custom field adjustments are allowed.
What constraints do these characteristics impose on deployment and upgrade
Daily updated data sources require configuring stable incremental sync scheduling during deployment. Full data pulls consume excessive system resources and cause delays in processing daily settlement documents. Multi-source data access must adapt to permission verification rules of different interfaces. Corresponding connection parameters must be configured in advance to ensure normal pulling of settlement lists, expense details, and other data. Data must strictly match official unified coding libraries. During deployment, official medical insurance catalog and coding library files must be mounted to specified paths in advance. This prevents audit errors caused by failed code matching. When processing settlement documents in batches, sufficient memory and storage resources must be reserved to support single or batch file audit workflows. A failure retry mechanism must also be configured to handle interface call exceptions and reduce interruption risks in the rejection reconciliation link.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 connections | Adapts to concurrent database access for daily batch settlement document processing, avoids connection exhaustion that impacts audit efficiency |
MONGODB_URI | Enter the full connection string for a local or cloud-hosted MongoDB instance, including authentication information | Stores batch audit file records and rejection reconciliation data; read and write permissions must be ensured |
REDIS_URL | Enter the connection address and port of a Redis instance | Caches medical insurance coding libraries and interface call tokens to reduce latency from repeated requests |
FE_DOMAIN | Public network domain name for the deployed service, or local IP plus port | Used to generate validation domains for file access tokens, and matches frontend access addresses |
FILE_TOKEN_KEY | Custom 32-character random string | Used to encrypt access tokens generated for declaration materials, prevents unauthorized access to file data |
STORAGE_S3_ENDPOINT | Enter a compatible S3 object storage endpoint address | Stores electronic documents such as prescriptions and settlement lists; storage permissions and access link stability must be ensured |
Three common configuration mistakes
- After accessing the frontend page, users cannot enter the model configuration entry, and the interface prompts insufficient permissions or that the configuration entry cannot be found. The cause is that the
ROOT_KEYparameter is not configured correctly, or the current access IP is not added to the allow list, preventing access to the model configuration module. - After local deployment, medical insurance coding library data fails to load, and the console prompts file read failure or non-existent path. The cause is that official coding library files were not mounted to the specified path in advance, or the configured file path does not match the actual storage path, making basic data required for code matching unreadable.
- Interface call timeouts occur during batch audits, returning status code 504 or database connection timeout errors. The cause is that the
DB_MAX_LINKconfiguration value is too low, leading to database connection exhaustion and failure to respond to audit requests for batch settlement documents in a timely manner.
How to confirm proper configuration
- Access the frontend address corresponding to
FE_DOMAIN. After logging in, enter the model configuration page, confirm that API key configurations can be added and saved, with no permission error prompts. - Run the local incremental sync script, check whether daily settlement document records have been generated in the database. No error logs indicate normal data source connectivity.
- Upload a test medical insurance settlement list file, generate a link via the file access token, confirm that the file content can be downloaded and viewed normally.
- Check the Redis monitoring dashboard, confirm that the coding library cache has loaded normally, with no connection timeout or cache invalidation error prompts.
The values provided here are common starting points. They should be evaluated against the user’s own specific 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.