Skip to main content

RLM Healthcare

Category: AI & ML
Node id: rlm-healthcare
Maturity: beta
Risk tier: C

Standards: HIPAA

Single-call clinical LLM presets: Q&A, medication review, diagnosis assist, treatment planning, lab interpretation. One chat completion per run — use rlm-query for the recursive RLM loop

What it does​

  • Clinical query answering with patient data context
  • Medication review for interactions and contraindications
  • AI-assisted differential diagnosis generation
  • Evidence-based treatment planning recommendations
  • Laboratory result interpretation in clinical context

Use cases​

  • Answering clinical questions about specific patients
  • Reviewing medication lists for safety and appropriateness
  • Generating ranked differential diagnoses from symptoms
  • Planning evidence-based treatments for diagnosed conditions
  • Interpreting lab panels in the context of patient history

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
querytextNoClinical query (overrides config query)
patient_datajsonNoPatient data as structured JSON
clinical_contexttextNoClinical context narrative

Output ports​

NameTypeRequiredDescription
resultjsonNoHealthcare query result containing answer, operation, query, and http_status
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
LLM Endpointllm_endpointstringYesBase URL of the LLM API
ModelmodelstringNogpt-4oModel name to use
OperationoperationenumNoclinical_queryclinical_query, medication_review, diagnosis_assist, treatment_planning, lab_interpretationHealthcare operation to perform
QueryquerytextNoStatic clinical query (overridden by input)

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
API Keyapi_keysecretNoAPI key for the LLM provider

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
TemperaturetemperaturenumberNo0.3min 0; max 2Sampling temperature
Max Tokensmax_tokensnumberNo4096Maximum tokens to generate

Errors​

CodeDescription
ENDPOINT_REQUIREDllm_endpoint is not configured
LLM_REQUEST_FAILEDLLM API call failed during healthcare query
HTTP_ERRORLLM endpoint returned an HTTP error status

Runtime notes​

  • The query input takes precedence over the static query in config
  • patient_data and clinical_context are both optional but improve answer quality
  • The answer field is free-text LLM prose; it is not structured JSON
  • All responses include a disclaimer that information should be verified by a healthcare professional

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Something unclear? Send documentation feedback by email.