medicalRecordConfiguration) defines the medical record your consultation produces: a map of sections, where each section is a node with an output schema and a prompt strategy.
Lifecycle
- Define the sections (nodes) you need — see Nodes.
- Create it via
POST /v1/medical-record-configurations. Telepatia hashes the content; identical configurations return the sameidwithcreated: false(idempotent). - Reference it on
POST /v1/set-consultation-contextusing one of the two fields below.
Three ways to attach a template to a session
| Mode | Field on set-consultation-context | When to use |
|---|---|---|
| Smart Template inline | medicalRecordConfiguration | Ship the full JSON with each session. Telepatia auto-persists and dedups by content hash. Recommended for client-driven flows. |
| Smart Template by id | medicalRecordConfigurationId | You already created it via POST /v1/medical-record-configurations and want to reuse the id. |
| Session Template | scribeSessionConfigurationId | Legacy curated flows. |
Pass exactly one of the three. A future
scribeTemplates field will accept either kind of template id — no breaking change is planned for the current variants.Create a Smart Template
List Smart Templates
Get a Smart Template by id
Next steps
- Nodes — how prompts are resolved per section.
- Telepatia Nodes catalog — curated
telepatiaPromptIdreference. - OutputSchema reference — types, examples, limits.