What Atlas remembers
Your mappings, ConceptMaps, packages and history live in the openFHIR engine and are the same for everyone in your tenant. A few choices about how you work are kept by your browser instead. This page lists all of them, so you know what a teammate won’t see and how to start fresh.
Important
Everything on this page stays in this browser, on this computer. Dismissed problems and ignored validation issues are not shared with your teammates, and they don’t follow you to another browser.
Kept in this browser (until you clear it)
Stored in the browser’s local storage. They survive closing the tab and restarting the browser.
What |
Where you set it |
Default |
Storage key |
|---|---|---|---|
Which view the openEHR pane shows: Template or Example |
The tabs on top of the Workspace’s openEHR pane |
Template |
|
Which view the FHIR pane shows: Profile or Example |
The tabs on top of the Workspace’s FHIR pane |
Example |
|
Height of the outline above the editing sheet |
Drag the sheet’s handle (“Drag to resize · double-click to reset”) |
45 % outline |
|
Height of the Problems dock |
Drag the dock’s handle; double-click resets |
30 % |
|
Validate after each conversion |
Validation settings next to Validate |
on |
|
Terminology checks (codes & bindings) |
Validation settings |
off |
|
Validation issues ignored for a template (“Ignore this kind of issue here for this template”; listed under Ignored for this template with Stop ignoring) |
The eye icon on a FHIR validation problem |
none |
|
Dismissed info problems (Dismiss) |
The eye icon on an info problem in the Problems dock |
none |
|
The blame column of the outline (“Show who changed each mapping last”) |
The history icon above the outline, when versioning is available |
off |
|
A pane tab that Atlas switches to by itself, for example when you click a validation problem that lives in the FHIR example, doesn’t change what is remembered.
Kept in this tab (until you close it)
Stored in the browser’s session storage: they survive a reload, and are gone when you close the tab. A new tab starts without them.
What |
Default |
Storage key |
|---|---|---|
The mapping last selected in each model, and which outline rows are expanded. Opening the model again without a mapping in the link selects it again. |
nothing selected, all rows expanded |
|
Show and count RM attributes (time, language, subject …) in the Template view |
off |
|
Extensions added with + Ext in the Profile view that no mapping produces yet (drafts) |
none |
|
Warning
An extension added with + Ext is only a draft until a mapping produces it. Map it (+ Map) before you close the tab, or it is gone. Once a mapping writes it, the mapping is what keeps it.
Not remembered
What |
What happens instead |
|---|---|
Auto save |
On at every visit to the Workspace, even if you switched it off last time. |
What is open (template, model, mapping, Engine state selection, Versioning tab, insight) |
Kept in the page’s address, not in storage. See Links you can share. |
Lock FHIR as the source / Lock openEHR as the source, Unmapped only, Required only, the coverage search, the filters of the Problems dock |
Not stored. A reload or a new tab starts with their defaults. |
Unsaved edits |
Only in the page. With Auto save off (or after a failed auto-save), switching model or leaving the Workspace asks first, and the browser warns before you close or reload the tab. |
Your sign-in is a session with the Atlas server, not one of these settings.
Start fresh
To reset everything on this page, clear this site’s data in your browser (in Chrome and Edge: the padlock or site icon in the address bar → Site settings → Delete data; in Firefox: the padlock → Clear cookies and site data…). This also signs you out.
To reset one thing, open the browser’s developer tools (Application → Local storage or Session storage in Chrome and Edge, Storage in Firefox), pick this site and delete the key from the tables above. For a single item there is usually a button in Atlas too: Stop ignoring under Validation settings, double-click a resize handle, or the toggle itself.
For support: highlight diagnostics
Setting the local storage key atlasDebugHighlight to 1 makes the Workspace write one line per
highlight update to the browser console ([highlight] …). Support may ask you for it when the panes
highlight the wrong place. Delete the key to turn it off.