Repertoire is designed to keep generated text useful without letting template controls silently overwrite wording you have already changed. It also stores the workspace locally in the browser rather than in an application account.
Those two design choices are related: they keep the note flexible and the current setup simple, but they also make it important to understand ownership, reloads, exports, and domain changes.
Browser-local storage is not a substitute for an organization-approved clinical system, access controls, retention policy, or backup process. Before real-world use, be sure to obtain approval from your IT department. If you have questions, please 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 edits such as:
- Rewording a generated assessment
- Adding patient-specific context
- 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 note—not the template—is the source of truth.
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 problem card.
- Read the resulting block in the note.
- Rewrite, remove, or expand the text for the individual encounter.
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 persistent workspace information, including:
- The current note and selected starting document
- Named starting-note presets
- Custom templates and built-in template overrides
- Reusable repertoire content
- Output, 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, device, or domain 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.
What a reload does not restore
Active problem cards and their linked controls are session state. Reloading the page preserves the generated text already stored in the note, but it does not reconstruct those temporary controls.
The one-line assessment input is temporary as well and clears after a successful build.
This means a reload can leave you with readable note text but no live template controls for the blocks created before the reload. Continue editing the text directly, or begin a fresh note when appropriate. Do not assume that reloading resets the workspace for a new patient.
New patient, clear note, and reload are different
These actions serve different purposes:
| Action | What it does | What remains |
|---|---|---|
| New patient | Clears the current note and active problem cards, then restores the selected starting note | Reusable templates, customizations, preferences, and starting-note presets |
| Clear note | Creates a blank clinical document | Reusable workspace content and preferences |
| Reload browser | Reloads the application and preserves stored note text | Persistent browser data remains, but active problem controls are not reconstructed |
Use New patient for the normal boundary between encounters. Keep its confirmation enabled until you are confident about the effect.
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:
- Remove all 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 New patient 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 Browse → Export to download a versioned Repertoire workspace backup. The export contains the supported persistent workspace settings in a format that Repertoire can validate during import.
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.
- Export before moving from a preview URL to a production domain.
- Store the file according to applicable organizational policies.
Import validates the full bundle and checks recognition conflicts before changing the local workspace. It replaces local workspace settings only after validation succeeds.
Do not rely on editing the exported file manually. Keep the most recent known-good export and make template changes through the application.
Pay special attention when the domain changes
Browser storage is separated by origin. For example, a Vercel preview address, a production vercel.app address, and a new custom domain can each have independent local storage even when they display the same application.
Before switching to a new production domain:
- Open the existing deployment where your customizations are available.
- Export the workspace.
- Open Repertoire at the new domain.
- Import the workspace.
- Confirm the starting note, custom templates, and important preferences.
- Test automatic recognition with non-patient sample text.
Keep the old export until the new workspace has been verified.
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 with New patient rather than relying on reload.
- Insert templates and make selections before rewriting generated blocks.
- Review every statement in the final note.
- Copy the note and verify it in the destination system.
- Start a new patient only after the previous note 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. Workspace exports protect the reusable setup you build around that workflow. Understanding both makes the application more predictable—and makes it easier to recover when a browser or domain changes.
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.