RLM Clinical Notes
Category: AI & ML
Node id: rlm-clinical-notes
Maturity: beta
Risk tier: B
Standards: HIPAA
Single-call LLM presets for clinical notes: SOAP generation, structuring, entity extraction, summarization, coding suggestions. One chat completion per run — use rlm-query for the recursive RLM loop
What it does
- SOAP note generation from encounter transcripts or data
- Clinical note structuring into standard formats
- Entity extraction (diagnoses, medications, procedures, vitals, lab results)
- Clinical note summarization
- ICD-10-CM and CPT code suggestion with confidence levels
- Configurable note format (SOAP, H&P, etc.)
Use cases
- Generating SOAP notes from physician-patient encounter transcripts
- Structuring unstructured clinical notes into standard formats
- Extracting structured entities from free-text clinical documentation
- Suggesting billing codes from clinical documentation
- Summarizing lengthy clinical notes for quick review
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
clinical_note | text | No | Existing clinical note for processing |
encounter_data | json | No | Encounter data for note generation |
transcript | text | No | Encounter transcript for note generation |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Clinical note result containing output, operation, note_format, and http_status |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| LLM Endpoint | llm_endpoint | string | Yes | Base URL of the LLM API | ||
| Model | model | string | No | gpt-4o | Model name to use | |
| Operation | operation | enum | No | generate_soap | generate_soap, generate_note, structure, extract_entities, summarize, code_suggest | Clinical notes operation |
| Note Format | note_format | string | No | SOAP | Clinical note format |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| API Key | api_key | secret | No | API key for the LLM provider |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Temperature | temperature | number | No | 0.3 | min 0; max 2 | Sampling temperature |
| Max Tokens | max_tokens | number | No | 4096 | Maximum tokens to generate |
Errors
| Code | Description |
|---|---|
ENDPOINT_REQUIRED | llm_endpoint is not configured |
INPUT_REQUIRED | Required input missing for the selected operation |
UNSUPPORTED_OPERATION | Operation must be generate_soap, generate_note, structure, extract_entities, summarize, or code_suggest |
LLM_REQUEST_FAILED | LLM API call failed during clinical note processing |
HTTP_ERROR | LLM endpoint returned an HTTP error status |
Runtime notes
- generate_soap and generate_note require either transcript or encounter_data input
- structure, extract_entities, summarize, and code_suggest require clinical_note input
- The output field is free-text LLM content; for extract_entities it may contain JSON embedded in text
- LLM timeout is 120s; large notes may need higher max_tokens config
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..