Rules Engine
Category: Healthcare Standards
Node id: rules-engine
Standards: HIPAA, GDPR, SOC2
Evaluates business rules against input facts, supporting condition-based matching, action execution, rule validation, and detailed evaluation explanations
What it does
- Four operations: evaluate, validate, execute, explain
- Three evaluation modes: all matches, first match, priority-based
- Condition-based rule matching with fact evaluation
- Action execution with set_value, flag, notify, and log actions
- Explain mode for detailed rule evaluation trace
Use cases
- Apply clinical decision support rules to patient data
- Evaluate compliance rules against healthcare transactions
- Implement business logic for insurance claim adjudication
- Generate audit-ready explanations of rule evaluation results
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
facts | json | No | Map of fact key-value pairs to evaluate rules against |
rules | json | No | Array of rule objects with conditions and actions |
rule | json | No | Single rule object for validate/explain operations |
actions | json | No | Array of action objects to execute (for execute operation) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Full rules engine result with matched rules, actions, or explanations |
matched_count | number | No | Number of rules that matched or actions executed |
success | boolean | No | Whether the operation completed successfully |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | evaluate | evaluate, validate, execute, explain | Rules engine operation to perform |
| Evaluation Mode | mode | enum | No | all | all, first, priority | How to evaluate rules (all matches, first match, or by priority) |
Errors
| Code | Description |
|---|---|
INVALID_OPERATION | The specified rules engine operation is not recognized |
MISSING_FACTS | Facts input is required for evaluate and explain operations |
MISSING_RULES | Rules input is required for evaluate operation |
INVALID_RULE | A rule object is malformed or missing required fields |
Runtime notes
- Different operations require different inputs: evaluate needs facts+rules, validate needs rule, execute needs actions
- In 'first' mode, evaluation stops after the first matching rule
- Condition logic defaults to AND; set 'logic' field to 'OR' or 'NOT' on individual conditions
- The result shape varies by operation: evaluate has results[], validate has is_valid, execute has actions_executed[]
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.