Template lifecycle in Medical Record Summarization, covering the Draft, Published, Deployed, and Archived statuses and version history behavior.

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, can be archived once they are no longer needed, and every change to a template is preserved as a numbered version.

Templates move through a defined lifecycle from creation to production.

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.

Archive a template you no longer need from the … menu on its row in the Templates list. Archiving takes effect immediately, with no confirmation prompt, and the template leaves the default list view.

To bring it back, select Archived in the Status filter to display archived templates, then select Restore from the … menu on the template's row. The template returns to Draft status. The … menu on an archived template offers only Duplicate, Restore, and Delete.

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.

The Templates page displays aggregate usage metrics across all templates, followed by the template list.

Four metrics appear at the top of the page, scoped to the selected time period using the All time filter.

Selecting a published or deployed template from the list opens the template detail view. The detail view provides three tabs: Overview, Runs, and Overrides. The Runs and Overrides tabs carry a count badge.

The Overview tab provides a consolidated view of template quality and recent activity.

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.

Until enough reviews have accumulated, the panel reports Not enough reviews yet and names how many summaries were reviewed in the selected period.

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. When no overrides have been recorded, the panel reports No section overrides recorded yet.

Lists the most recent runs associated with this template, showing the batch name, status, and document count.

Displays all summarization runs associated with this template. Each row in the list represents one batch run.

Runs can be filtered by Status and Source using the dropdowns in the tab header.

Displays all reviewer overrides recorded against this template, along with the policy decision feedback reviewers left on Policy sections, and AI-generated recommendations for improving the template based on override patterns. See Template overrides and recommendations for details.

The Overrides tab surfaces the full history of reviewer feedback - both section overrides and policy decision verdicts - and uses AI analysis of the section overrides to identify recurring patterns and suggest targeted improvements to the template's section instructions.

When no feedback has been recorded, the tab reports No feedback has been recorded for this template yet.

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 descriptive title, a badge naming the category of problem found (for example, Prompt gap), and a description of the issue. The priority badge appears once the recommendation is applied to the template editor, not on the card itself.

Each recommendation card shows the number of related overrides and the template version it applies to. Two actions are available:

To trigger a fresh analysis of accumulated feedback, select Analyze overrides. Analysis runs on demand each time you select it, and only evaluates feedback on summaries that have reached a completion status. The analysis looks for patterns rather than individual events, so a single override on a section does not produce a recommendation. Analysis covers section overrides on Summary output only. Policy decision feedback is recorded but is not yet analyzed.

When no recommendations exist, the panel reports No recommendations yet.

The table lists each individual override record.

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.

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 a priority badge (High, Medium, or Low), a title, and a description of the issue.

Under Recommended prompt change, the panel shows the proposed instructions as a diff: text to be removed is struck through and text to be added is highlighted.

Select Apply suggestion to accept the suggestion and replace the section instructions, Dismiss to discard it, or View feedback to open the overrides it was derived from.