Introduction to Templates

Learn how to working with Corti templates for document generation

Documents Classic — deprecated. This guide covers the original templates surface used with POST /interactions/{id}/documents, accessed via GET /templates and templateKey. Classic is deprecated with a sunset date of January 18th, 2027 — see the upcoming changes announcement. A new, more flexible templates and sections API is now available — see Create a Section and Create a Template, or the migration guide.

In the Corti API, Templates define the structure for documents that are generated by Corti AI models from various inputs, such as conversational transcripts, facts, or other medical documents.

Templates are available in different languages and can be specific to your organization. Each template includes sections that set the

• structure (e.g., SOAP Note template consists of the four sections Subjective, Objective, Assessment and Plan)
• a writing style
• and documentation format

This ensures consistency, clarity, and control in use of AI to support medical reporting.

Key Features of Templates

One Interaction, Multiple Documents	Generate multiple types of documentation for a single interaction, e.g., SOAP note and Patient Summary.
Customizable Formats	Use templates tailored for various medical specialties, enabling the generation of various types of clinical notes, letters, discharge summaries, and your unique use case needs.
Flexible Workflows	Use pre-defined templates or cater to more dynamic workflows by selecting the desired, relevant sections.
Template Management	The API lets you retrieve and review a list of available pre-configured templates and the languages those are available in. Use the query filter for organization ?org to only retrieve templates provided to you.

Retrieving Available Templates

To generate a document, you must use a valid templateKey and the template must be available in the desired outputLanguage.

To retrieve a list of available templates use the GET /templates request and use ?lang= to filter for available languages. Without any language filtering, the default returned are templates in en.

JavaScript

// Default templates (en)
const templates = await client.templates.list();

// Templates available for a specific org
const orgTemplates = await client.templates.list({ org: "TestHealth" });

// Templates available in a specific language
const danishTemplates = await client.templates.list({ lang: "da" });

See details for standard out-of-the-box templates here