Overview
Some organizations embed the AI scribe directly into their own platforms and use section keys to map content generated by Corti Assistant into predefined sections of their EHR or internal systems.
With the introduction of the Template Assembler, users can generate documents with sections that are not mapped to fields in the embedding platform. This introduces important considerations for embedded integrations to ensure a smooth embedded flow
This article explains:
Why section keys may matter in embedded workflows
What changes when the Template Assembler is used
Three potential options embedded customers can explore
Why Section Keys Matter in Embedded Setups
In embedded workflows, section keys are often used to:
Route generated text from a template section into specific EHR fields
Maintain consistent downstream data handling
Support automation, analytics, or compliance requirements
What Changes with the Template Assembler
With the template assembler, users can generate documents using any section in the section library. While an integrator could map all possible sections in advance, Corti can and will expand our library of sections at any point.
This can cause:
Unmapped content
Additional engineering or support overhead
For embedded customers, this means the Template Assembler requires an explicit decision on how sections should be handled.
Options for Embedded Customers
We've worked to outline some options for customers using Corti Assistant Embedded. Some options outlined below:
Option 1: Implement a Mapping Strategy for Sections
For embedded customers who want to use the Template Assembler without losing automated routing into their EHR or internal systems, a dynamic mapping strategy is the most robust option.
This approach requires customer-side implementation.
Read more about dynamic mapping for embedded assistant here.
Option 2: Use Copy-Paste Workflows
In this approach:
Users generate notes using the Template Assembler
Section content is copied and pasted manually into the target system
Section keys are not relied on for automated mapping
Best suited for:
Low-volume usage
Teams prioritizing flexibility over automation
Early evaluation of the Template Assembler
Trade-offs:
Manual effort for users
No automated section-level integration
Option 3: Turn Off the Template Assembler
In this approach:
The Template Assembler is disabled for end users
Users continue to use existing templates, and the list of section keys remains static
Existing mappings remain unchanged
Best suited for:
Highly controlled embedded environments
Customers with strict EHR integration requirements
Teams that want to avoid any risk of unmapped data
Trade-offs:
No access to Template Assembler flexibility
Slower iteration on templates
Choosing the Right Option
There is no one-size-fits-all answer. The right choice depends on:
How tightly integrated your platform is with the EHR
Whether dynamic mappings are feasible
How much flexibility end users need
Your Activation team can help you:
Evaluate your current embedding setup
Decide which option fits your technical and operational constraints
Coordinate enablement or disablement of the Template Assembler accordingly
Have a question for our team?
Click Support in the bottom-left corner of the console to submit a ticket or reach out via email at help@corti.ai and we'll be happy to assist you.