- Overview
- Medical Record Summarization
- About Medical Record Summarization
- A template's lifecycle
- Create a template
- Edit a template
- Deploy a template
- Send documents for processing
- Review a summary
- Medical Record Summarization (MRS) output data
- Manage deployments
- Customize application appearance
- Experimental features
- Template sections reference
- Clinical review reference
- System components
Healthcare Solutions user guide
A template defines the structure of the AI-generated clinical summary: which sections to include, what type of output each section produces, and how the AI is instructed to populate each section. Templates progress through three statuses before they can process records in production, and every change to a template is preserved as a numbered version.
Template statuses
Templates move through a defined lifecycle from creation to production.
| Status | Description |
|---|---|
| Draft | The template is being built or modified. It cannot be connected to a deployment or used to process records automatically. Draft templates can be tested using manual batch runs. |
| Published | The template has been reviewed and is ready for production use. A published template appears in the Deployments page and can be connected to an Orchestrator trigger. Publishing does not process records - it signals readiness. |
| Deployed | The template is connected to an active deployment and is processing records automatically on a configured schedule. |
A published template can be returned to draft by editing it - any saved edit creates a new draft version. A deployed template can be paused or stopped from the Deployments page without changing the template's published status.
Template versioning
Every time a template is saved in the editor, the system creates a new numbered version. Version numbers are sequential and permanent. No version is ever overwritten or deleted when a new version is saved - the full history is always accessible.
The version history is accessible from Version history in the … overflow menu in the template editor. Each entry shows who made the change and when. This audit trail supports compliance requirements in regulated healthcare environments.
When a template is deployed, the deployment is connected to a specific version. If the template is later edited and a new version is published, the deployment continues using the previously connected version until explicitly updated.
Templates list
The Templates page displays aggregate usage metrics across all templates, followed by the template list.
Stats panel
Four metrics appear at the top of the page, scoped to the selected time period using the All time filter.
| Metric | Description |
|---|---|
| Summaries generated | Total number of summaries produced across all templates |
| Pages summarized | Total pages processed across all summarization runs |
| Time saved | Estimated time saved compared to manual review, based on average document length |
| Avg. review time | Average time reviewers spent completing a review |
Template list columns
| Column | Description |
|---|---|
| Template | The template name and current version number |
| Status | Draft, Published, or Deployed |
| Summaries | Number of summaries generated by this template |
| Feedback | Number of reviewer overrides recorded against this template |
| Last updated by | The user who last saved a change to the template |
| Date created | The date the template was created |
| Last run | The date of the most recent summarization run; displays - if no run has occurred |
Filters
| Filter | Description |
|---|---|
| Search | Free-text search across template names |
| Status | Multi-select filter for template status; defaults to all three statuses selected |
| Updated by | Filter by the user who last updated the template; defaults to All |
Template detail view
Selecting a published or deployed template from the list opens the template detail view. The detail view provides three tabs: Overview, Runs, and Overrides.
Overview tab
The Overview tab provides a consolidated view of template quality and recent activity.
Template quality at a glance
An AI-generated summary interprets the override data for the selected time period and produces a headline and a brief description of where reviewer edits are concentrated. The time period is controlled by the date range selector (for example, Last 90 days).
The summary is accompanied by a line chart that plots overrides, documents reviewed, and version updates over the selected period.
Stats panel
| Metric | Description |
|---|---|
| Approval rate | Percentage of reviewed summaries that were approved without rejection, displayed as a circular gauge |
| Average review time | Average time between a reviewer opening a summary and approving or rejecting it |
| Summaries | Total summaries generated by this template |
| Overrides | Total override actions recorded across all summaries for this template |
Sections needing attention
Lists the template sections that have received the most overrides, with the override count and override rate (as a percentage of total reviewed summaries) for each section.
Recent activity
Lists the most recent runs associated with this template, showing the batch name, status, and document count.
Runs tab
Displays all summarization runs associated with this template. Each row in the list represents one batch run.
| Column | Description |
|---|---|
| Name | The name of the run, generated automatically from the run type and date |
| Source | How the run was triggered: Manual upload or the deployment name for scheduled runs |
| Status | The current run status: Completed, In progress, Failed |
| Documents | Number of documents processed in the run |
| Duration | Total elapsed time from run start to completion |
| Created by | The user or system entity that triggered the run |
| Date | The date and time the run was started |
| Deployment | The deployment associated with the run, if applicable |
Runs can be filtered by Status and Source using the dropdowns in the tab header.
Overrides tab
Displays all reviewer overrides recorded against this template, along with AI-generated recommendations for improving the template based on override patterns. See Template overrides and recommendations for details.
Template overrides and recommendations
The Overrides tab surfaces the full history of reviewer edits and uses AI analysis to identify recurring patterns and suggest targeted improvements to the template's section instructions.
Stats panel
| Metric | Description |
|---|---|
| Approval rate | Percentage of summaries approved across the selected time period |
| Overrides | Total number of overrides recorded |
| Recommendations | Number of active AI-generated recommendations |
Filters
| Filter | Description |
|---|---|
| All time | Date range filter scoping the stats and list |
| Section | Filter overrides by template section name |
| Reason | Filter by the reason selected by the reviewer |
| Version | Filter by the template version active at the time of the override |
Recommended actions
When the AI identifies a pattern across multiple overrides in the same section, it generates a recommendation card. Each card includes the section name, a priority level (High, Medium, or Low), a descriptive title, and bullet-point guidance for how to revise the section's AI instructions.
Each recommendation card shows the number of related overrides and the template version it applies to. Two actions are available:
| Action | Description |
|---|---|
| Apply | Opens the template editor with the recommendation pre-loaded as an inline AI suggestion on the relevant section |
| Ignore | Dismisses the recommendation without making changes |
To trigger a fresh analysis of accumulated overrides, select Analyze overrides. Analysis runs on demand each time you select it, and only evaluates overrides on summaries that have reached a terminal state (Approved or Rejected).
Override list
The table lists each individual override record.
| Column | Description |
|---|---|
| Section | The section of the template where the override was made |
| Summary | The filename of the source document; select to open the review detail |
| Reason | The reason selected by the reviewer when submitting the override |
| Review verdict | The final outcome of the review: Approved or Rejected |
| When | Date and time the override was submitted |
| Reviewer | The email address of the reviewer who submitted the override |
| Version | The template version used when the summary was generated |
Each row is expandable. Expanding a row reveals additional detail about the override, including the Feedback for the agent text the reviewer entered when submitting it.
Template editor AI suggestions
When a recommendation from the Overrides tab has been applied to the template editor, an inline AI suggestion panel appears on the relevant section. The panel shows the suggestion priority, a title, and the recommended changes to the section's instructions.
Select Apply to accept the suggestion and update the section instructions, or Dismiss to discard it.