Clinical Protocol
Category: Healthcare Standards
Node id: protocol
Standards: HIPAA, GDPR, SOC2
Manages clinical protocol selection, execution, progress tracking, compliance checking, and step recommendations
What it does
- Condition-based clinical protocol selection
- Step-by-step protocol execution with instructions
- Protocol progress tracking across completed steps
- Compliance checking against protocol requirements
- Patient-specific protocol step recommendations
Use cases
- Standardized care pathway enforcement in hospitals
- Clinical trial protocol adherence monitoring
- Chronic disease management protocol tracking
- Nursing workflow protocol guidance
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
conditions | json | No | Patient conditions for protocol selection |
protocol_id | text | No | Protocol ID for execution/tracking |
current_step | text | No | Current step ID in protocol |
completed_steps | json | No | List of completed step IDs or step objects |
patient | json | No | Patient data for personalized recommendations |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Protocol data (selection, execution, tracking, compliance, recommendations) |
status | text | No | Protocol status (matched/executing/in_progress/compliant/non_compliant/recommended) |
success | boolean | No | Operation success flag |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | No | select | select, execute, track, compliance, recommend | Protocol operation to perform |
Errors
| Code | Description |
|---|---|
CONDITIONS_REQUIRED | Patient conditions required for protocol selection |
PROTOCOL_ID_REQUIRED | Protocol ID required for execution/tracking |
PROTOCOL_NOT_FOUND | Specified protocol ID not found |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- Result shape varies by operation: select returns matching_protocols/selected_protocol; execute returns current_step/next_step; track returns progress percentages; compliance returns violations
- The 'status' output reflects the protocol lifecycle: matched, executing, in_progress, completed, not_started, compliant, non_compliant, recommended
- Compliance check reports missed_required and out_of_sequence violations with per-step detail
- Recommend operation returns at most 3 next steps plus patient-specific recommendations for age >= 65
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.