Get started with Templates in Corti Console

​

Overview

Clinical documents, such as notes, letters, and summaries, are generated using templates and sections that you control. You can build and manage these via the API or in the new Templates feature in Corti Console, then put them to work in your integration. This starter guide covers what you can do in Corti Console: build and test templates and sections in a visual editor, organize your library, and, if you use the Embedded Assistant, control which customers and users can access them. It introduces the core ideas:

• What is a section?
• What is a template?
• How they work together to produce a document.
• How to use Corti standards and find what you need in your library.
• How to manage who can access your templates and sections.

When you are ready to build, the Build a template and Build a section guides walk through each step. For the API-level reference on how sections and templates work as resources, see the Sections & Templates overview.

​

What is a section?

A section is a single part of a clinical document, such as Chief Complaint, Allergies, or Plan. Each section defines:

• A heading: the title used in the generated document.
• Instructions: the prompts that tell the model what to write and in what style.
• An output schema: the shape of the output, from a single paragraph of free text to structured data such as a list or a set of labeled fields.

Sections are reusable. A single well-written section can be used across many templates. To create one, see Build a section.

​

What is a template?

A template is the structure of a complete clinical document. It brings together a set of sections in the order you want them to appear, along with a top-level instruction that applies to the whole document. For example, a Post-Consultation Note template might combine a Chief Complaint section, a History of Present Illness section, an Assessment section, and a Plan section. To create one, see Build a template.

​

How they work together to make clinical documents

Sections are the building blocks. Templates arrange them into a finished document. Generation ties the two together:

1. You provide the clinical context, such as a transcript, a set of facts, or free text.
2. You choose a template.
3. Corti generates a structured document, producing content for each section in the order the template defines.

The result can be generated through the API inside your own application, or surfaced to clinicians through the Embedded Assistant. For the technical detail of generating documents through the API, see Guided Document Synthesis.

​

Corti standards: a library to start from

Corti provides a curated set of standard sections and templates out of the box. These cover the common building blocks of clinical documentation and are the recommended starting point. Corti standards are read-only. You cannot change them directly, but you can:

• Use them as-is.
• Copy one and adjust it (Edit a copy), which is the fastest way to a working template or section.

Corti standards are available across the languages, regions, and specialties Corti supports.

​

Finding templates and sections in your library

Open Templates in Corti Console to view your library. A tab switcher moves between the Templates and Sections libraries. Both show your own resources alongside Corti standards. As your library grows, use properties to find what you need. Built-in properties such as Languages, Regions, and Specialty, along with any custom properties you add, let you filter the library to the right starting point. See Manage your templates and sections library.

​

Managing access

Access controls who can see and use a template or section. By default, a new template or section is available only to API clients in your project. It is not exposed to Embedded Assistant customers or end users until you assign access. If you use the Embedded Assistant, you manage two groups in Corti Console:

• Customers: your customers, such as hospitals.
• Users: the end users of the Embedded Assistant, such as clinicians and doctors. Users belong to a customer.

You can then assign access at three levels: Corti standards are a special case. They are available to all customers in a project, and this access cannot be changed. To assign access, see Manage your templates and sections library.

​

Where to go next