medicalRecordConfiguration) defines the medical record your consultation produces: a map of sections, where each section has an output schema and a prompt strategy.
Lifecycle
- Define the sections you need — see Sections.
- 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
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
Delete a Smart Template
Soft-deletes a template by its public id. It returns204 No Content and drops out of the default list; historical consultations that referenced it are unaffected. Deletion is blocked with 409 while a linked session is still processing, and returns 404 if the id is not found.
Template status
List and detail responses expose astatus per template:
Deleted templates drop from the default list. Use the
?status query parameter to change the view:
Next steps
- Sections — how prompts are resolved per section.
- Telepatia Prompts catalog — curated
telepatiaPromptIdreference. - OutputSchema reference — types, examples, limits.