Data Characteristics in This Category
Pharmacovigilance data for culture media and consumables originates from production batch reports, quality inspection reports, user complaints, medical literature, and regulatory agency notifications. This data updates frequently; new batch reports and complaints can appear daily. Document structures vary, including structured database records, semi-structured PDF batch reports, and unstructured user feedback emails or transcribed phone recordings. Fields and units are specific, such as BATCH_ID, PROD_DATE, EXP_DATE, component content (e.g., mg/L or IU/mL), specific impurity detection values (e.g., Endotoxin Content (EU/mL)), and adverse event descriptions (AE_DESCRIPTION). Complaint data often includes image or video links, while literature data primarily consists of abstracts and full texts.
Constraints Imposed by These Characteristics on Workflow Orchestration
Data diversity requires workflows to support multi-source data ingestion, especially effective parsing of unstructured text. High update frequency means workflows need real-time or near real-time trigger mechanisms, such as hourly checks for new complaint data. Variable document structures challenge information extraction, requiring flexible parsing tools to identify key fields across different formats, for example, extracting batch IDs and production dates from PDFs. Specific fields and units necessitate standardization and normalization during data preprocessing to ensure accurate subsequent analysis, for instance, converting component content from different units to a standard unit. Additionally, data containing multimedia links requires workflows to process these links and extract relevant contextual information.
Configuration Guidelines
| Configuration Item | Suggested Value | Rationale for This Value |
|---|---|---|
FETCH_INTERVAL_SECONDS | 3600 seconds | Addresses high update frequency, checking for new data hourly |
PARSE_FILE_TYPE_LIST | ['pdf', 'txt', 'docx', 'eml'] | Covers common batch report, complaint email, and literature formats |
CHUNK_SIZE | 800–1200 characters | Balances text semantic integrity with subsequent model processing efficiency |
OVERLAP_SIZE | 100 characters | Ensures contextual continuity, preventing critical information loss during chunking |
EXTRACT_PATTERN_BATCH_ID | Regular Expression | Accurately identifies the BATCH_ID field in various report formats |
SIMILARITY_THRESHOLD | 0.75 | Balances recall and accuracy, avoiding interference from irrelevant information |
Three Common Pitfalls
- After workflow publication, generated password-free links point to
http://localhost:3000/chat/, making them inaccessible to external users. This occurs when the external access address for the service is not correctly configured during publication, leading the link to point to a local development environment. - Tool invocation nodes get stuck, returning no results or errors, such as a database connection timeout. Workflow execution logs show the tool invocation node in a long waiting state. This can be due to incorrect
DB_CONNECTION_STRINGconfiguration or FastGPT server access not being granted through the database firewall. - The online preview function for original files corresponding to cited snippets is unavailable, or the preview content is incomplete. Clicking the preview link displays a blank page or missing content. This happens when the original files are not stored in an accessible path during knowledge base import, or when original file path information is lost during file chunking.
Verification of Configuration
- Upload batch reports and complaint emails in various formats (PDF, TXT, DOCX). Observe if the knowledge base correctly parses and chunks the text. Check if chunked content includes key fields like
BATCH_IDandEXP_DATE. - Configure a query with adverse reaction keywords (e.g., "allergy," "fever," "ineffective"). Compare the recalled results to see if they include batch reports or complaint records related to these keywords. Check the number of recalled items and similarity scores.
- Simulate a new user complaint or batch report update. Observe if the workflow triggers within the configured
FETCH_INTERVAL_SECONDSand successfully processes the new data.
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-21.