Repertoire is designed to keep generated text useful without letting template controls silently overwrite wording you have already changed. The live writing space is session-only, while reusable template configuration can be stored locally in the browser.
Those two design choices are related: they keep template composition flexible and the current setup simple, but they also make it important to understand ownership, reloads, and exports.
Repertoire is not an EMR. Do not enter PHI, patient-specific information, or any HHS Safe Harbor identifier. Add encounter details only in your approved EMR, and obtain appropriate IT approval before use. Read the data security and HIPAA guide, or contact Repertoire.
What “clinician-owned” text means
When Repertoire inserts a template, it creates a structured generated block linked to the corresponding controls in the Templates area.
At first, that block is system-owned. Changing its linked selections can regenerate the block because Repertoire can still distinguish its original structure from the rest of the note.
The first ordinary manual edit changes that boundary. The block becomes clinician-owned, and Repertoire will not subsequently merge, remove, or rewrite it through the template controls.
This behavior protects common template edits such as:
- Rewording a generated assessment
- Reorganizing reusable sections
- Deleting a statement that does not apply
- Combining generated and manually written content
- Reformatting the block to fit the rest of the note
Once you begin that work, the session text—not the linked template—is the source of truth. It remains temporary and must stay free of PHI.
Make selections before rewriting
The simplest workflow is to complete template selections before manually revising their output:
- Insert or recognize the template.
- Select the relevant options in its active template panel.
- Read the resulting block in the note.
- Rewrite, remove, or expand the reusable wording without adding patient details.
If you manually edit first and then return to the controls, Repertoire preserves the edited block instead of replacing it. That is intentional, but it can be surprising until the workflow becomes familiar.
Structured inline choices behave differently from ordinary typing. Choosing one of the alternatives embedded by the template is considered a supported template action and can keep the containing block system-owned.
What the browser stores
The current version of Repertoire has no application database or user account. It uses the browser profile’s local storage for reusable workspace information, including:
- The selected reusable starting document
- Named starting-note presets
- Custom templates and built-in template overrides
- Personal template reminders
- Timestamped notepad ideas
- Reusable repertoire content
- The selected maintained starting library and its update receipt
- Favorite-template pins and note-output preferences, including problem spacing and Repertoire Line inclusion
- Onboarding, clipboard, inference-detail, confirmation, and theme preferences
Storage is tied to both the browser profile and the site origin. A different browser profile, private browsing window, or device is a different workspace.
Removing site data can remove the workspace. Private browsing storage may disappear when the private session ends. Organization-managed browsers may also enforce their own storage and retention rules.
The active writing area is specifically excluded from local storage and workspace exports. Reusable templates, reminders, notepad entries, and starting-note presets must all remain free of PHI.
What a reload resets
Active text, template controls, and linked blocks are session state. Reloading the page discards them and restores the selected reusable starting template.
Repertoire Line gestures also act only on the session writing space. They do not create a separate saved command or add patient wording to a workspace export.
This means a reload intentionally returns the writing space to a clean reusable starting point. It does not affect custom templates, reminders, notepad entries, named starting-note presets, or preferences stored in the browser.
Reset, clear note, and reload are different
These actions serve different purposes:
| Action | What it does | What remains |
|---|---|---|
| Reset | Clears the active writing space and template controls, then restores the selected starting template | Reusable templates, reminders, notepad entries, customizations, preferences, and starting-note presets |
| Clear note | Creates a blank clinical document | Reusable workspace content and preferences |
| Reload browser | Discards active text and controls, then restores the selected starting template | Reusable templates, reminders, notepad entries, starting-note presets, and preferences |
Use Reset for an explicit session boundary. Keep its confirmation enabled until you are confident about the effect.
Changing the maintained starting library is a separate, more consequential reset. Open Menu → Note Settings → Starting library to choose another available baseline. Repertoire warns that this removes local Template overrides, personal Building Blocks, starting-note presets, favorites, and Library Review decisions. The active writing space, Notepad, agreement, appearance, and output preferences remain. Use Export workspace first before confirming so the old reusable setup can be imported later if needed.
Save a starting note intentionally
Repertoire’s built-in starting note contains an Assessment / Plan heading. You can also save the current document as a named starting-note preset.
Before saving a starting note:
- Confirm that it has never contained PHI or patient-specific information.
- Confirm that every line is appropriate as a reusable starting structure.
- Prefer prompts or headings over statements that might be accepted without review.
- Test Reset and confirm that the expected preset returns.
A starting note should make the next document easier to begin, not carry conclusions forward from the previous encounter.
Export a workspace backup
Use Menu → Approval & Backup → Export workspace to download a versioned Repertoire workspace backup. The export identifies the maintained starting library and version and contains the complete working Template and Building Block snapshots, local Template changes and reminders, the personal and organization-labeled Building Blocks needed for restoration, Library Review decisions, recent-item history, notepad entries, starting-note presets, and supported preferences in a format that Repertoire can validate during import. It does not contain the active writing space.
A useful backup routine is:
- Export after creating or substantially revising templates.
- Export before clearing browser history or site data.
- Export before changing browsers or devices.
- Confirm the reusable configuration contains no PHI, then store the file according to applicable organizational policies.
Import validates and sanitizes the full bundle, checks identifiers, references, aliases, and recognition conflicts, and shows a replacement summary before changing the reusable workspace. When the referenced maintained starting library is available, it is restored with the user's local changes. Browser preferences and the current draft remain unchanged. After confirmation, a same-tab Undo import action can restore the previous reusable workspace.
Do not rely on editing the exported file manually. Keep the most recent known-good export and make template changes through the application.
A safer day-to-day routine
The following routine keeps the important boundaries visible:
- Confirm you are in the correct browser profile and deployment.
- Begin from the selected starting template or use Reset for an explicit reset.
- Insert templates and make selections before rewriting generated blocks.
- Confirm that Repertoire contains only patient-independent template language.
- Copy the reusable structure into the approved EMR and complete patient-specific documentation there.
- Choose Reset only after any reusable work has been handled appropriately.
- Export the workspace after meaningful template or starting-note changes.
Repertoire’s ownership rules protect manual wording from later template updates. Session-only writing reduces accidental retention, and workspace exports protect the reusable setup you build around that workflow. None of those features authorize PHI use; organizational approval and the no-PHI boundary still apply.
If you are new to the workspace, begin with building your first clinical note in Repertoire. If you are ready to adapt the library, see customizing and reusing clinical note templates.