- Overview
- Medical Record Summarization
Healthcare Solutions user guide
A template's lifecycle
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 deployed template shows a different detail view with Runs and Feedback tabs instead of Summary and Template tabs. |
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 available from the version dropdown in the template editor header. Each entry in the history 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. A warning banner appears in the template editor when the displayed Summary tab output was generated by an older version than the current editor version.
Template detail views
The detail view for a template changes depending on its status.
Draft and Published templates show three tabs:
| Tab | Content |
|---|---|
| Summary | The AI-generated summary output from the most recent test run, with inline citations and a source document viewer |
| Template | The list of sections configured in this template and the instructions for each section |
| History | The full version history of the template |
Deployed templates replace the Summary and Template tabs with operational tabs:
| Tab | Content |
|---|---|
| Runs | All batch runs processed by this deployment, with per-run status, document counts, and duration |
| Feedback | Section-level feedback aggregated from reviewer overrides, showing Unchanged and Overridden counts per section |