What the data for this category looks like
Data processed under this category comes from the national medical insurance information platform, hospital HIS and medical insurance interfaces, medical insurance catalog coding library, and cross-regional medical settlement platform. The update frequency is daily. Daily processed documents include medical insurance settlement lists, expense details, medical record homepages, prescriptions, rejection lists, and settlement reconciliation statements. Data fields cover diagnosis and treatment item and drug consumable codes, expense amounts, medical record-prescription association information, settlement status, and more. Support for batch structured data import and format verification is required to maintain consistency between data and business rules.
What constraints these characteristics impose on the deployment and upgrade process
Daily updated batch structured data requires sufficient database concurrent connections and storage capacity to be configured during deployment, to avoid data processing timeouts. Real-time matching requirements for medical insurance catalog codes require local coding libraries to be updated synchronously during deployment. During upgrades, the coding library version must be consistent with the online version to avoid matching logic errors. Integration of multi-source data requires configuration of multi-data source connection parameters during deployment. During upgrades, existing data connection configurations must be retained to avoid business interruptions. The reconciliation logic for rejection lists and settlement reconciliation statements must be bound to fixed data fields. During upgrades, field mapping relationships must be verified to prevent reconciliation failures caused by configuration changes.
How to set the configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 concurrent connections | Meets the concurrent read requirements of daily batch medical insurance data, prevents database connection exhaustion |
MONGODB_URI | Dedicated MongoDB cluster address bound to medical insurance settlement data | Isolates business data from other system data, ensures access security of settlement data |
REDIS_URL | redis://:custom strong password@cache node:6379/1 | Used to cache frequently accessed medical insurance catalog coding data, reduces database query pressure |
STORAGE_S3_ENDPOINT | Intranet access endpoint of internal object storage | Stores batch-imported medical insurance settlement lists, rejection lists, and other document files |
FE_DOMAIN | Valid HTTPS domain name for the deployed service | Configures the access address of the frontend page, ensures domain name validity after application release |
ROOT_KEY | Random 32-bit key string generated according to the deployment environment | Used for authentication of internal management interfaces, ensures interface access security |
Three common errors
- Phenomenon: Cross-origin errors are returned when calling application interfaces, or voice functions fail to load normally. Cause:
FE_DOMAINis not configured as a valid HTTPS domain name, causing frontend requests to be blocked by browsers. - Phenomenon: Workflows exported from older versions cannot be imported successfully in newer versions, and the system prompts incompatible format. Cause: Underlying configuration fields of workflows have changed after upgrade, and the JSON format exported by older versions is not compatible.
- Phenomenon: Ledger charts display interface return code 500 errors after deployment or upgrade, and logs prompt that a field does not exist. Cause: The database table structure pointed to by
PG_URLis not updated synchronously, causing preset fields for chart queries to not be created.
How to confirm the configuration is complete
- Run the database connection test script to verify that the number of connections configured for
DB_MAX_LINKcan be created and reused normally. - Access the domain name configured for
FE_DOMAINto confirm that the frontend page loads normally and interface requests have no exceptions. - Upload a test medical insurance settlement list document to verify that the storage service configured for
STORAGE_S3_ENDPOINTcan receive and store files normally. - Call the internal management interface, use
ROOT_KEYto complete authentication, and confirm that the interface can normally return current configuration information.
The values given 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.