What the data for this category looks like
The data processed in this category comes from the national medical insurance information platform, hospital HIS and medical insurance interfaces, medical insurance catalog and coding database, and cross-regional medical settlement platform. The platform updates data on a daily basis. It processes daily documents including medical insurance settlement lists, expense details, medical record homepages, prescriptions, rejection lists, and settlement reconciliation statements. Data fields include diagnosis and treatment item and drug consumable codes, expense amounts, insured person identity identifiers, medical institution information, and other related items. Coding fields must strictly match the national unified medical insurance standards. Amounts are measured in yuan. The volume of documents processed in a single batch can reach hundreds of megabytes.
What constraints these characteristics impose on deployment and upgrade
The data sources for medical insurance reimbursement audit are diverse and updated frequently. The daily synchronized interface request volume is high, which creates clear requirements for database connection pool stability. Large-volume documents processed in batches will occupy significant storage and upload bandwidth, so targeted adjustments to file upload and storage configurations are necessary. Data formats vary across different sources, so the database and cache services must support multi-format data writing. In addition, the coding matching link relies on the frequently accessed medical insurance catalog database, so an efficient caching mechanism must be configured to avoid repeated interface calls. During deployment and upgrade, the access stability of the internal office system must be prioritized to prevent configuration changes from disrupting daily audit operations for handling staff.
Reference only; verify against the target FastGPT release and deployment documentation.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 connections | Adapt to daily high-frequency medical insurance data synchronization and audit query requests |
MONGODB_URI | mongodb://username:password@host:27017/fastgpt?authSource=admin | Store unstructured documents such as medical insurance settlement lists and rejection lists |
REDIS_URL | redis://:password@host:6379/1 | Cache frequently accessed medical insurance catalog and coding databases to reduce database pressure |
FILE_TOKEN_KEY | 3600 seconds | Extend the token validity period for uploading large-volume medical insurance documents to avoid mid-upload timeouts |
STORAGE_S3_ENDPOINT | http://localhost:9000 | Configure local object storage for batch storage of medical insurance-related documents |
Three common configuration errors
- When uploading a medical insurance settlement list larger than 500MB, a timeout error appears in the interface but the upload has completed in the background. This occurs because the validity period of
FILE_TOKEN_KEYwas not adjusted, causing the front-end upload token to expire prematurely. - After deployment, the built-in model cannot be called normally. This occurs because
MONGODB_URIandREDIS_URLwere not configured correctly, preventing the model service from connecting to the core storage and cache services. - After modifying the administrator password, only a single thread service is restarted, and the new password does not take effect. This occurs because the processes for the web service, worker service, and scheduled task service were not differentiated, and only a subset of services was restarted.
How to verify correct configuration
- Perform a test batch upload of medical insurance settlement lists, observe the front-end upload status and background storage logs, and confirm the upload process is not interrupted.
- Call the diagnosis and treatment item code matching interface, check that the returned result matches the locally cached medical insurance catalog database, and confirm the database and cache configurations are active.
- Access the LAN address bound to
FE_DOMAIN, verify that the login and background management interfaces load normally, and confirm the domain name configuration is correct. - After modifying the administrator password, restart the corresponding service processes, verify that the new password can be used to log in normally, and confirm the service restart configuration is correct.
The values provided are common starting points and should be evaluated 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.