Data Profile for This Category
This category covers end-to-end production workflows for single-use medical supplies, implantable/interventional devices, and diagnostic equipment manufacturers. Daily documents include production process specifications, batch production records, clean zone operation records, sterilization batch records, test reports, software version records, adverse event and traceability materials. Data sources include design history files, device and material batch ledgers, MES systems, clean environment monitoring equipment, sterilization equipment, and test and calibration systems. Updates follow batch, per-unit product, or environmental monitoring schedules.
Constraints for Workflow Orchestration
This category’s data requires batch binding. Workflows must associate unique device or material identification fields to avoid cross-batch data confusion. Multi-source heterogeneous data sources require standardized conversion nodes in workflows. These nodes adapt to output formats from systems such as MES and clean environment monitoring equipment. Update frequencies follow batch, per-unit, or monitoring schedules. Workflows must support scheduled triggering and batch triggering modes. Compliance rules apply to adverse events and traceability materials. Workflows must retain complete node execution logs. Historical configurations cannot be deleted or modified arbitrarily.
Configuration Guidelines
| Configuration Item | Recommended Practice | Rationale |
|---|---|---|
variables configuration | Set batch number, sterilization batch, and clean zone number as global variables, with scope limited to the current workflow | This category’s data updates per batch. Global variables uniformly pass core identifiers and avoid cross-batch confusion |
| Node timeout settings | Set single-node timeout to 10–15 seconds | Covers conventional operations such as HTTP requests and data validation. It adapts to response delays from multi-source systems |
| Trigger mode settings | Trigger on batch completion events, support manual trigger for supplementary audits | Matches the per-batch data update rhythm of this category. It adapts to supplementary audit needs for abnormal batches |
| Log retention policy | Retain all node execution logs, set retention duration to 30–90 days | Meets adverse event traceability and compliance requirements. It fully records the entire audit process |
nodeId binding rules | Bind a unique nodeId to each data source node, and associate it with the corresponding batch ledger | Avoids confusion across multi-source data nodes. It ensures accurate data traceability |
| Request header configuration | Carry 1–3 core fields from global variables as authentication parameters | Adapts to multi-system authentication requirements. It ensures the legitimacy of data requests |
This document is compatible with FastGPT v4.17.0.
Three Common Configuration Mistakes
- Workflow execution displays "Failed to fetch global variables". The cause is failure to correctly bind core fields such as batch number and sterilization batch to the
variablesconfiguration, or incorrect global variable scope settings that prevent nodes from reading the variables. - Publishing channels still execute old logic after workflow configuration is updated. The cause is failure to sync the updated workflow version to bound publishing channels, or failure of publishing channels to associate with the latest workflow
nodeId. - Request timeouts occur after multi-node orchestration. The cause is failure to reasonably set node timeout thresholds, with single-node timeout set too short, leading to termination of time-consuming operations such as HTTP requests before completion.
How to Verify Successful Configuration
- Manually trigger the workflow, check whether core fields in
variablesare correctly passed to each node, and confirm there are no null values or incorrect fields. - View node execution logs, confirm that each node’s timeout setting matches actual business response durations, and there are no timeout errors.
- Compare workflow configurations before and after modification, confirm that publishing channels are bound to the latest workflow version, and no old configuration remains.
- Simulate triggers for abnormal batches, confirm that the workflow supports batch triggering and supplementary audit modes, and aligns with data update rhythms.
The values provided here are common starting points, and should be evaluated against the reader’s own samples.