Overview
A section is a single part of a clinical document, such as Chief Complaint, Allergies, or Plan. Each section carries a heading, a set of instructions that tell the model what to write, and an output schema that controls the shape of what it produces. Templates are built by arranging sections in order, and a single section can be reused across many templates. To see how the two fit together, see Intro to guided templates and sections. Corti provides a set of standard sections out of the box, so the fastest way to get going is to copy one and adjust it. This guide covers both routes:- Edit a copy of a Corti section (recommended starting point).
- Build a section from scratch (for more customized needs).
Before you begin
In Corti Console, open Templates from the sidebar and switch to the Sections tab to view your section library. You can also work with sections directly in the template builder while composing a template. See Build a template.Edit a copy of a Corti section
Starting from a Corti standard is the quickest way to a working section, and it means you inherit Corti’s ongoing improvements.Open a section
You can edit a copy of a section from a few places:
- From the Sections tab, choose Edit a copy on a section in the table, or from that section’s details page.
- From the template builder, choose Edit a copy on a section that is part of a template.
Make your changes
You can adjust the parts of the section that shape its output:
- Heading: the title used in the generated document. It is also given to the model as context.
- Instructions: the prompts that tell the model what to write. These cover what content to include, the writing style and tone, and any extra guidance. For more on each instruction field, see Create a Section.
- Output schema: controls 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. To choose the right shape, see Designing section output schemas.
About inherited fields: Some fields are highlighted in blue. These inherit their values from the Corti section you copied. Leave them as they are to automatically benefit from Corti’s ongoing improvements, or override them to set your own value. You can revert an override at any time.Overriding a field replaces the inherited value with your own, and that field no longer follows the Corti original. Fields you leave inherited keep reflecting Corti’s updates. Learn more about inheritance.
Test your output as you go
Use the preview pane to see how your changes affect the section’s output. Add your own sample data, such as a transcript, then choose Run to generate output from the section. Keep editing and re-running to see the effect of each change.
The preview uses the same generation engine as the documents API, so what you see here is what your integration produces in production.
Save your section
When you are happy with the result, save the section to your library. Once saved, you can reference it via the API, add it to any of your templates, and, if you use the Embedded Assistant, make it available to your customers and their end users. See Assign access to customers.
New sections are not visible to Embedded Assistant customers or users until you assign access. By default they are available only to API clients in your project.
Build a section from scratch
We recommend starting from a Corti standard and adjusting it. Build from scratch when you need something so unique or customized that no Corti standard is a useful starting point.Start a new section
- From the Sections tab, select + New section at the top of the page to open the builder for a single section.
- Or, from the template builder, add a brand new section while composing a template.
Define the section
Set the heading, write the instructions, and choose an output
schema. Start simple. A plain text output with clear instructions is often
all you need, and you can add structure later. For guidance on each, see
Create a Section and Designing section output
schemas.
Preview and refine
Add sample data and choose Run to generate output, just as you would when
editing a copy. Adjust the heading, instructions, and schema until the output
matches what you need.
Save your section
When the section is ready, choose Save to add it to your library. The builder shows all of a section’s fields up front, including its name and metadata, so make sure you have filled these in before you save. See Add metadata to manage your sections below.
Add metadata to manage your sections
Metadata makes your section easy to find and organize as your library grows.- Name and description: a clear, human-friendly label and summary so you and your team can identify the section at a glance.
- Properties: built-in properties such as Languages, Regions, and Specialty record where the section is intended to be used and let you filter your library.
- Custom properties: define your own property, give it a name and one or more values (for example a property named Department with the value Cardiology), then filter on it to group related sections.
In the API, custom properties appear as labels, where the property name is the key and each value you enter is one of its values.Metadata is for organizing and filtering your library. It is not sent to the model and does not affect the content of generated documents.
What’s next
Build a template
Arrange your sections into a complete document.
Manage your library
Filter your library and assign customer access.
Create a Section
Go deeper on writing instructions.
Designing section output schemas
Shape free text or structured output.
FAQ
Does editing a copy change the original Corti section?
Does editing a copy change the original Corti section?
No. A copy is your own independent section. Corti standards are read-only
and cannot be changed. Note that any fields you leave inherited (highlighted
in blue) will continue to reflect Corti’s updates to the original.
I edited a section and it changed one of my other templates. Why?
I edited a section and it changed one of my other templates. Why?
Sections are shared. When a section is used in more than one template,
editing it changes the output everywhere it is used. To make a change that
applies in only one place, use Edit a copy to create an independent
section.
Who can see a section I create?
Who can see a section I create?
By default, a new section is available only to API clients in your project.
It is not visible to Embedded Assistant customers or end users until you
assign access. See Assign access to
customers.
Do I have to choose an output schema?
Do I have to choose an output schema?
A section produces free text by default, which works well for narrative
parts of a note. You only need to define a structured schema when you want
structured output, such as a list or labeled fields. See Designing section
output schemas.
What is the difference between a section and a template?
What is the difference between a section and a template?
A section is one part of a note, such as Allergies or Plan. A template is
the full document, made by arranging sections in order. See Intro to guided
templates and sections.