Saltar al contenido principal

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​

NameTypeRequiredDescription
factsjsonNoMap of fact key-value pairs to evaluate rules against
rulesjsonNoArray of rule objects with conditions and actions
rulejsonNoSingle rule object for validate/explain operations
actionsjsonNoArray of action objects to execute (for execute operation)

Output ports​

NameTypeRequiredDescription
resultjsonNoFull rules engine result with matched rules, actions, or explanations
matched_countnumberNoNumber of rules that matched or actions executed
successbooleanNoWhether the operation completed successfully

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
OperationoperationenumYesevaluateevaluate, validate, execute, explainRules engine operation to perform
Evaluation ModemodeenumNoallall, first, priorityHow to evaluate rules (all matches, first match, or by priority)

Errors​

CodeDescription
INVALID_OPERATIONThe specified rules engine operation is not recognized
MISSING_FACTSFacts input is required for evaluate and explain operations
MISSING_RULESRules input is required for evaluate operation
INVALID_RULEA 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.

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..