Aller au contenu principal

Treatment Planning

Category: AI & ML
Node id: treatment-planning

Standards: HIPAA

AI-powered evidence-based treatment plan generation

What it does​

  • Evidence-based treatment plan generation
  • Multi-provider LLM support (OpenAI, Anthropic)
  • Alternative treatment options with trade-offs
  • Cost estimation for treatment options
  • Short-term and long-term planning horizons
  • Patient preference and insurance awareness

Use cases​

  • Generate treatment plans from confirmed diagnoses
  • Compare alternative treatment approaches
  • Estimate treatment costs for patient counseling
  • Create guideline-based care recommendations

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
diagnosistextYesDiagnosis information
patient_contextjsonNoPatient context (sub-keys: patient_data, medications, allergies, lab_results, conditions, preferences, insurance, age, gender)

Output ports​

NameTypeRequiredDescription
resultjsonNoMain result containing treatment_plan, summary, timeline, alternatives, cost_estimates, and disclaimer
metadatajsonNoExecution metadata including tokens, treatment_count, essential/recommended/optional counts
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
ProviderproviderenumNoopenaiopenai, anthropicLLM provider
ModelmodelstringNo""Model name (auto-selected if empty)
Guideline Levelguideline_levelenumNostandardstandard, evidence-based, experimentalClinical guideline level
TimeframetimeframeenumNoshort-termshort-term, long-term, bothTreatment plan timeframe
Include Alternativesinclude_alternativesbooleanNotrueInclude alternative treatment options
Include Cost Estimateinclude_cost_estimatebooleanNofalseInclude rough cost estimates

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
API Keyapi_keysecretNoAPI key for the LLM provider
Base URLbase_urlstringNo""Custom API base URL

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
TemperaturetemperaturenumberNo0.3min 0; max 1Sampling temperature
Max Tokensmax_tokensnumberNo4000min 1Maximum tokens for response

Errors​

CodeDescription
DIAGNOSIS_REQUIREDNo diagnosis text provided in inputs
INVALID_PROVIDERProvider must be openai or anthropic
LLM_REQUEST_FAILEDLLM API call failed or returned error
PARSE_ERRORFailed to parse LLM response as structured treatment plan

Runtime notes​

  • result always includes a disclaimer string — do not suppress it when displaying to users
  • patient_context sub-keys map internally: patient_data, medications, allergies, lab_results, conditions, preferences, insurance
  • If LLM response cannot be parsed as JSON, a fallback single-treatment plan is returned with the raw text as rationale
  • Latency is variable and depends on LLM provider; plan for 5-30s execution time

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.