Messages and notices A–Z
Every notice, chip, banner and dialog text Atlas can show, apart from the problems in the Problems
dock (those are in Problems). Find a message by its first word, or search this
page for a few words of it. Parts in angle brackets (<model>, <n>) stand for what Atlas fills
in.
Each entry says where the message appears, what it means and what to do about it.
Note
Where error texts come from. Many errors show the explanation the backend or the engine gave. Only when there is none does Atlas show its own short text (“Save failed”, “Upload failed.”, “Could not push”). If the text you see isn’t on this page, it is most likely the engine’s own message: read it for the cause, and see Support if it doesn’t help.
Note
A few failures show no message at all. The Engine state page shows its welcome screen (“There’s nothing here yet”) both when the engine is empty and when Atlas couldn’t read the engine’s state; the Terminology page shows “No ConceptMaps yet.” also when it couldn’t list them. If you expected content, reload the page and check that the engine is reachable.
Numbers and names · A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · R · S · T · U · V · W · Y
Starting with a number or a name
<branch> has <n> commits the engine hasn’t pulled yet.
Where: Versioning → Remote, and the versioning badge tooltip. After a refused Push it reads “<branch> has commits the engine hasn’t pulled yet. Pull first, then push.” with a Pull… button.
Others pushed to the branch. A push never takes their changes into the engine, so it waits until you have pulled them.
What to do: Click Pull… (Push, pull and conflicts).
<branch> has no commits (never connected, or deleted). Connect the engine to it to write its state, then push.
Where: Versioning → Remote (amber), after Push (code connect-required), with a link to
the Git remote settings.
The branch is empty: the engine was never connected to it, or it was deleted. A push only adds the unpushed changes, so it would leave out the rest of the engine’s state.
What to do: Open the Git remote settings and click Connect (Connect a Git repository), then push.
<branch> no longer contains the engine’s last push: its history was rewritten (e.g. force-pushed).
Where: Versioning → Remote (amber). After a refused Push it ends with “Pull first, then push.” and a Pull… button.
The branch was rewritten after Atlas’s last push. The engine can’t tell which of its changes are new there, so it doesn’t push until it has pulled.
What to do: Pull to compare everything, then decide which side wins.
“<mapping>” comes from the core model <core>; this extension doesn’t override it.
Where: Engine state, mapping detail of an extension model, with Open <core>.
The mapping you picked belongs to the model the extension extends.
What to do: Click Open <core> to edit it there.
<model> maps <type>, not <scope>.
Where: Editing sheet, under Slot archetype, with Wrap in a reference to <type>.
The slotted model maps another FHIR resource than the one in scope at this mapping, so the engine skips the slot (slot-resource-mismatch: slot into a model of another resource).
What to do: Click Wrap in a reference to <type>; see Connect models: slots, links, references.
<n> change(s) not pushed — the release only contains pushed changes.
Where: Release wizard check (amber), with Push now.
Unpushed changes won’t be in the release.
What to do: Click Push now (Release a template).
<n> error(s), <n> warning(s) in the mappings.
Where: Release wizard check.
The template has problems (Problems).
What to do: Fix them in the Workspace before releasing, or release knowingly.
<n> profile(s) not loaded
Where: Next to the validation chip (amber link).
The produced FHIR claims profiles whose IG packages aren’t loaded, so it was validated without them (tooltip “Validated without <profiles> (not loaded). Upload the package that defines it.”).
What to do: Click it to go to FHIR packages and add the package (Use FHIR profiles and IG packages).
<n> uploaded · <n> skipped · <n> failed
Where: Engine state (and Terminology), after an upload, with a row per file.
The result per file: green check uploaded, amber skipped (not a supported or recognisable file, or unchanged), red failed (with the reason).
What to do: Read the failed rows (below) and fix those files.
<name>#<version> not found in <registry> (<status>)
Where: FHIR packages, fetch.
The registry has no package with that id and version.
What to do: Check the spelling and version (id#version).
<file>: packages are limited to 15 MB
Where: FHIR packages upload and the create-model wizard, under the listed files (red).
The package file is larger than 15 MB; Upload stays disabled. The same place says
<file>: files are limited to 60 MB for any larger file and <file>: not a .tgz, .json or .zip
for a file of another type.
What to do: Leave the file out (the cross next to it). Fetch a large package by id#version
from the registry instead.
<file>: <reason>
Where: FHIR packages upload and the create-model wizard (red).
The file named couldn’t be stored, so nothing of the upload was. The reason follows the colon, for
example Not a FHIR npm package (.tgz with package/package.json): ….
What to do: Leave the file out or fix it, then upload again; the files stay listed. The reasons are explained in Use FHIR profiles and IG packages.
‘<name>’ is no package name: use letters, digits, ‘.’, ‘-’ and ‘_’, for example local.my-profiles
Where: FHIR packages upload and the create-model wizard, under the package name (red).
The package name for the loose resources has other characters, or starts with ., - or _.
What to do: Change the name, or clear it to let Atlas name the package.
<unit> has no model to hold the slot — choose a start / map it first
Where: Slot placement list (add-mapping dialogs, wizard), next to a greyed occurrence.
That place in the template sits in an archetype no model maps yet, so there is no model to put the slot mapping in.
What to do: Pick another occurrence, choose Don’t slot it now, or first map the enclosing archetype (or choose the start).
<model> already maps elements inside <occurrence> — a model slotted in would map them twice
Where: Slot placement list (add-mapping dialogs, wizard), next to a greyed occurrence.
The enclosing model maps elements of this archetype occurrence itself (inline, through its own paths). A model slotted in there would map the same elements a second time. A mapping that only leads into a slot there (every branch below it ends in a Slot archetype, as in a reference + slot) doesn’t count. The coverage tree offers no + Slot on such an occurrence for the same reason.
What to do: Pick another occurrence or choose Don’t slot it now. To give the occurrence a model of its own, first remove the inline mappings from the enclosing model.
<url> (not found)
Where: ConceptMap list in the Terminology row.
The mapping names a ConceptMap the engine doesn’t have.
What to do: Pick an existing one or upload it (Manage ConceptMaps).
A
A model named ‘<name>’ already exists
Where: Create-model wizard.
Model names are unique in the engine.
What to do: Pick another name.
A version like 1.2.0
Where: Release wizard, version field (red).
The version isn’t in the major.minor.patch form.
Added <name>#<version>; its profiles are still loading or it has none for FHIR <version>.
Where: Create-model wizard.
The package was added, but no profile of the chosen FHIR version is available yet.
What to do: Wait and look again, or check the package’s FHIR version.
Adding <model> to this context…
Where: Editing sheet, under Slot archetype.
You picked a model from another template; Atlas is adding it to this one.
Already up to date: <branch> has nothing the engine hasn’t pushed or pulled.
Where: Pull from the remote dialog (green).
Nothing to pull.
Another mapping here is also named “<name>”.
Where: Note in the move or duplicate toast.
The mapping now has a sibling with the same name (mapping-name-duplicate \).
What to do: Rename one of them.
Another versioning operation is running. Try again in a moment.
Where: Versioning actions (code busy).
A push, pull or other operation is in progress.
What to do: Wait and try again.
Applied all at once: if anything can’t be imported, nothing is, unless you import despite the errors.
Where: Engine state, upload preview.
The engine imports the whole upload as one change.
What to do: Review the plan, then click Apply. If the plan has errors, see Import despite these errors. The engine imports what it can store ….
Archive contained no supported files
Where: Upload result row for a ZIP (skipped).
The ZIP holds nothing Atlas can import.
Asking the engine about versioning…
Where: Versioning and Git remote pages.
Atlas checks whether the engine versions mappings.
Auto-save is off — edits stay local and the openEHR & FHIR panes go stale until …
Auto-save is off — edits stay local and the openEHR & FHIR panes go stale until you click Save (or press Ctrl+S).
Where: Under the model editor, next to Auto save.
Auto-save is off: edits stay in your browser until you save, and the example panes show the last saved state.
What to do: Click Save in the top bar or press Ctrl+S.
Auto-save is on — edits save automatically
Where: Workspace top bar, a short hint after Ctrl+S.
You pressed Ctrl+S while auto-save is on; any pending edit is saved now.
Auto-saves to the engine shortly after you stop editing, then re-runs.
Where: Under the model editor, next to Auto save.
Auto-save is on: each pause in editing saves the model and converts the example again.
What to do: Untick Auto save to collect edits and save them yourself. Auto-save is on again at each visit to the Workspace.
Available on dedicated instances only
Where: Integrations and Multitenancy pages.
These capabilities need a dedicated openFHIR instance and aren’t available on a shared one.
What to do: Use Contact us on the page (Dedicated instances).
B
Building the FHIR profile set failed: <cause>
Where: Path suggestions, checks or validation, while packages load (code warming).
Atlas couldn’t read the loaded packages.
What to do: Check the packages on FHIR packages for a not loaded chip.
C
Checking what the upload changes…
Where: Engine state, upload panel.
Atlas asks the engine for a preview of what the upload would change.
Choose a start archetype for this template
Where: Template overview, where the start model would be.
The template’s context mapper has no start yet, so nothing is mapped.
What to do: Click it and pick the archetype where conversion begins (Start mapping a template).
Closed without merging: the engine still has these changes, <branch> doesn’t (<n> artefact(s)).
Where: Versioning → Reviews (amber), with Revert the engine to <branch>.
The review was closed, so the branch lacks changes the engine still has.
What to do: Resubmit, or revert the engine to the branch (Submit for review).
Connect or pull first: the engine hasn’t synced with this branch.
Where: Versioning: a push from a dialog (Checkpoint and push, the release wizard’s
Push now), when the engine gave no explanation of its own (code pull-required, remote state
untracked).
The engine never pushed to or pulled from the branch: the repository was never connected, or the repository URL or branch setting changed.
What to do: Usually open the Git remote settings and click Connect (Connect a Git repository). Pull only if the repository should replace the engine: a pull plans to delete every engine artefact the repository lacks.
Context not found for template: <template id>
Where: Saving the context mapper, or adding a model to a template.
The template has no context mapper.
What to do: Start mapping the template first (Start mapping a template).
Context YAML has no `context` block to set `start` on
Where: Start picker dialog (red).
The context mapper has no context: section.
What to do: Add it in the context mapper, then choose the start again.
Converting to FHIR…
Where: Over the FHIR example pane (“Converting to openEHR…” over the openEHR pane).
A conversion is running.
Core FHIR definitions are built in; don’t upload <name>
Where: FHIR packages upload.
The FHIR core package is part of Atlas already.
Could not classify YAML as a context or model mapper (expected a top-level …
Could not classify YAML as a context or model mapper (expected a top-level ‘context:’ or ‘mappings:’ key, or ‘type: context|model|extension’)
Where: Upload result row (skipped).
A YAML file is neither a context mapper nor a model.
What to do: Check the file is a FHIRConnect file (FHIR Connect).
Could not fetch from <registry>: <message>
Where: FHIR packages, fetch.
The registry couldn’t be reached.
What to do: Try later, or upload the .tgz.
Could not load the API documentation from the openFHIR engine.
Where: API access (red).
The engine’s API description couldn’t be loaded.
What to do: Reload; check the engine is reachable.
Could not load the extensions.
Where: + Ext extension picker (amber).
The extension list couldn’t be loaded.
What to do: Try again.
Could not load the history
Where: History (red).
The history couldn’t be read.
What to do: Click reload.
Could not read the template as of <ref>
Where: Template coverage, compare strip (red).
The version you picked to compare with couldn’t be read.
What to do: Pick another version, or Stop comparing.
Couldn’t load the engine state
Where: Workspace, in place of the panes, with the error below it and a Retry button.
Atlas couldn’t read the templates and models from the engine: the engine is down, unreachable, or refused the request. The line under it is the reason the backend gave (or “The engine state could not be loaded.”).
What to do: Click Retry. If it keeps failing, check that the engine is running and reachable from Atlas; the reason line tells you more.
Couldn’t open <template id or model>
Where: Workspace, red strip under the middle pane’s header.
Loading the template or model failed; the backend’s own message replaces this text when there is one.
What to do: Try again; if it persists, reload the page.
Couldn’t parse the model’s YAML — use raw editing (<code icon>) to fix it. <parser message>
Where: Engine state, mapping detail.
The model’s YAML doesn’t parse, so the detail can’t show it.
What to do: Open raw editing (the code icon) and fix the YAML.
Couldn’t parse the YAML for the visual editor — showing raw code. <parser message>
Where: Under the model editor (amber), after the editor switched to Code.
The model’s YAML isn’t valid, so the visual editor can’t show it.
What to do: Fix the line the message names in the Code view, then switch back to the visual editor. See yaml-syntax \.
D
Delete client
Where: API access, confirmation.
“Permanently delete client “<client id>”? This cannot be undone and its credentials will stop working immediately.”
What to do: Make sure no system still uses it.
Delete failed
Where: Delete model dialog (red).
Removing or deleting the model failed.
What to do: Try again.
Delete operational template?
Where: Engine state, template menu → Delete template….
“Are you sure you want to delete <template id>? This action cannot be undone.” With Also delete all archetypes (model mappers) in the context mapper tied to this template. ticked, the models go too; otherwise only the OPT and its context mapper.
What to do: Tick or untick the models option, then Delete. Export the template first if you may need it (Export and move mappings).
Delete this ConceptMap?
Where: Terminology page.
“This permanently removes the ConceptMap from the engine. This cannot be undone.”
What to do: Check Used by first: mappings that use it then pass codes through untranslated.
Deleted “<name>”
Where: Toast at the bottom of the outline, with Undo (also “Moved “<name>” …”, “Duplicated “<name>””).
Your last delete, move or duplicate. The toast stays a few seconds (longer when it has notes).
What to do: Click Undo to take it back. Undo covers only this last action (Edit mappings in the Workspace).
Disconnect the git remote
Where: Git remote, confirmation.
“Disconnect the git remote? The engine keeps its journal; nothing is deleted from the remote.”
Don’t slot it now
Where: Slot placement list.
“The model is added to the context, but nothing runs it until a slot links it.”
What to do: Use Slot it in… on its card later.
E
Engine rejected file: <message>
Where: Upload result row (failed) (also “Engine rejected OPT: …”, “Engine rejected ConceptMap: …”, “Engine rejected FHIR package: …”).
The engine refused the file; the message is the engine’s reason.
What to do: Fix what the message names and upload again.
Entry exceeds size limit (52428800 bytes)
Where: Upload result row for a ZIP (failed) (also “Archive uncompressed size exceeds limit”, “Archive has too many entries (limit 1000)”).
The ZIP is larger than Atlas accepts.
What to do: Split it into smaller uploads.
Every archetype is mapped.
Where: Start picker dialog.
There is no unmapped archetype left to start from.
Exception trying to convert due to: <message>
Where: Red strip above an example pane.
The engine couldn’t convert the example with the saved mappings; the message is the engine’s reason.
What to do: Read the message, fix the mapping it points at (the Problems dock usually has the cause) and save.
Expected FHIR npm packages (.tgz), conformance resources (StructureDefinition, ValueSet, CodeSystem … as .json or a Bundle), ConceptMaps, or a .zip of them
Where: FHIR packages upload (red).
Nothing in the upload can be stored: the files are neither packages nor conformance resources.
What to do: Pick the IG’s package.tgz, or its StructureDefinition, ValueSet and CodeSystem .json files (Use FHIR profiles and IG packages).
Export failed
Where: Export dialog (red).
The ZIP couldn’t be built.
What to do: Try again; see Export and move mappings.
F
Failed to add <model> to the context
Where: Editing sheet under Slot archetype.
Referencing the model into this template failed.
What to do: Try again; the backend’s message, when there is one, replaces this text.
Failed to add the profile
Where: Create-model wizard (red).
Uploading or fetching the package failed; the backend’s reason replaces this when there is one.
What to do: Check the file or the id#version.
Failed to create model
Where: Create-model wizard (red).
The engine refused the new model.
What to do: Read the backend’s reason if shown; check the name isn’t taken.
Failed to load context mapper
Where: Context mapper editor (red).
The context mapper’s YAML couldn’t be loaded.
What to do: Close and open it again.
Failed to load FHIR types
Where: Create-model wizard (red).
The resource and data type list couldn’t be loaded.
What to do: Close the wizard and open it again.
Failed to load problems
Where: Problems dock (red).
The problems couldn’t be loaded.
What to do: Click Refresh in the dock.
Failed to load the ConceptMap
Where: ConceptMap peek (red).
The ConceptMap couldn’t be read.
What to do: Close and open the peek again.
Failed to load the model
Where: Engine state, mapping detail (red) (also “Failed to load model” in raw editing).
The model’s YAML couldn’t be loaded.
What to do: Try again.
Failed to load the template tree
Where: Template coverage tab (red).
Loading the coverage failed.
What to do: Reopen the template.
Failed to obtain a bearer token for client “<client id>”.
Where: API access, a browser alert after Get Token.
The identity provider didn’t issue a token for the client.
What to do: Try again; if it persists, generate a new client (Connect your system to the API).
Failed to reference model
Where: Reuse dialog (red).
Adding the existing model to this template failed.
What to do: Try again.
Failed to set start
Where: Start picker dialog (red).
Saving the start failed.
What to do: Try again.
Failed to slot <model> in
Where: Dialog Slot <model> in (red), when the backend gave no reason.
Adding the slot failed.
What to do: Try again.
Fetching packages from a registry is disabled
Where: FHIR packages, fetch.
This installation doesn’t fetch from packages.fhir.org.
What to do: Download the .tgz elsewhere and upload it.
FHIR condition kept as written: check it still applies.
Where: Note in the move toast.
Conditions aren’t rewritten when you move a mapping.
What to do: Check the condition (Map only when… (conditions)).
FHIR path kept as written: it now resolves from “<parent>”.
Where: Note in the move toast (also “… from the model root.”, and the same for the openEHR path).
The moved mapping’s relative path wasn’t rewritten, so it now continues from its new parent.
What to do: Check the path still points where you mean; Undo if not.
G
Generating example…
Where: Over the openEHR example pane.
Atlas is generating a new openEHR example from the template.
Greyed out means a mapping was not applied.
Where: Insights, the applied mappings table.
Grey rows are mappings the conversion didn’t apply.
What to do: See Understand a conversion (Insights).
H
Hide recurring issues from the problems panel (eye icon on a validation problem).
Where: Validation settings menu, under Ignored for this template (0).
No validation issue is ignored for this template.
What to do: See Quick actions \.
I
Import despite these errors. The engine imports what it can store …
Where: Engine state, upload preview (amber), when the engine found errors in the plan.
The upload has errors (listed in red above). Unticked, Apply stays disabled: the engine imports nothing while there are errors. Ticked, the engine imports what it can store, broken references included, and leaves out the files it can’t store (Won’t be imported: the engine can’t store it in the preview, Not imported in the result).
What to do: Fix the files and upload them again, or tick the box and click Apply.
Invalid OPT XML: <message>
Where: Upload result row (failed).
The .opt file isn’t a readable operational template.
What to do: Export the OPT again from your template tool.
Invalid YAML: <message>
Where: Upload result row (failed), or saving a model in raw editing.
The YAML doesn’t parse.
What to do: Fix the line named in the message.
J
JSON is not a FHIR ConceptMap (resourceType must be “ConceptMap”)
Where: Upload result row (skipped).
The .json file is neither a ConceptMap nor a StructureDefinition, ValueSet or CodeSystem (on Terminology, only ConceptMaps are accepted).
What to do: Leave it out. Upload StructureDefinitions, ValueSets and CodeSystems on FHIR packages or the Engine state upload.
K
keeps <k> of <n> <element> in the example — check the criteria
Where: Editing sheet, under a condition.
The condition keeps none of the example’s elements (”— check the criteria” appears only when it keeps 0).
What to do: Check the criteria; the example may also just not contain a match.
L
Leave without saving?
Where: A dialog in three places: the Workspace (opening another template or model, or leaving, with unsaved edits: auto-save off, or after a failed save), the Engine state page (leaving with unsaved edits in a mapping detail) and the ConceptMap editor (closing it with unsaved changes).
Your edits would be lost. The Workspace says “You have unsaved changes to this mapping. If you leave now they will be lost. Leave anyway?”; Engine state names the models (“You have unsaved mapping changes to <models>. …”); the ConceptMap editor says “You have unsaved changes to this ConceptMap. …”.
What to do: Stay (in the ConceptMap editor Keep editing) to go back and save; Leave discards the edits. Closing or reloading the browser tab shows the browser’s own “leave site?” question instead.
Live for <model> — the rest reflects the last save.
Where: Problems dock header.
Load the demo mappings?
Where: A dialog on the Engine state page, after clicking Load demo mappings while the engine is empty and its git remote has commits it hasn’t pulled.
The remote most likely holds your mappings. Demo mappings loaded now would have to be reconciled with them when you import them.
What to do: Cancel, then Import from the remote in the notice above the welcome card (The engine is empty, but its git remote may not be). Load the demo only if you want it alongside what the remote has.
Loading models… <template id>
Where: Template overview.
The template’s models are loading.
Loading templates…
Where: Workspace, over the whole work area when you enter it.
Atlas is reading the engine’s templates and models.
What to do: Wait. If it ends in Couldn’t load the engine state, see that entry.
M
Mapping not in engine tree
Where: Highlight chip in an example pane header.
The engine has no mapping by that name for this model (tooltip “The engine has no mapping “<mapping>” for this model.”). For example, the model isn’t reached from the start model.
What to do: Check the Problems dock for model-unreached \ or openehr-not-in-template \.
Mirror deletes every template, model, context and ConceptMap the upload doesn’t contain.
Where: Engine state, upload preview, when Mirror is selected (red).
Mirror makes the engine match the upload exactly: everything else is deleted.
What to do: Read the plan’s delete rows before you click Apply (mirror). Choose Merge to only add and update (Bring your material in).
Missing dependencies
Where: FHIR packages page (amber), listing “<name>#<version> needed by <packages>”.
“Profiles from these packages (extensions, base profiles, value sets) can’t be resolved until they’re added.”
What to do: Click Fetch next to each one (when the registry is enabled), or upload them (Use FHIR profiles and IG packages).
Model <model> isn’t part of <template id>.
Where: Workspace, red strip under the middle pane’s header, after opening a link.
The link names a model that the template’s context mapper doesn’t list.
What to do: Open the template’s overview and pick the model there, or reference the model into the template (Connect models: slots, links, references).
Model has no id, cannot update: <model>
Where: Saving a model in raw editing.
The engine returned the model without an id.
What to do: Re-upload the model on Engine state.
Model not found: <model>
Where: Saving or editing a model.
The model no longer exists in the engine (deleted or renamed elsewhere).
What to do: Reload the page.
N
New — not recorded yet
Where: Editing sheet, blame line (versioning).
The mapping isn’t in the version history yet.
What to do: It is recorded on save.
No API base URL is stored for <provider>, so reviews and releases can’t reach it. …
No API base URL is stored for <provider>, so reviews and releases can’t reach it. Save to use the default, or enter the URL of your own server.
Where: Git remote settings (amber).
Reviews and releases need the provider’s API address.
What to do: Click Save, or enter your server’s API URL.
No API clients found for your tenant.
Where: API access.
No client exists yet.
What to do: Click Generate Client (Connect your system to the API).
No ConceptMap found for url: <url>
Where: Terminology page (red), after opening a link with ?conceptmap=.
No ConceptMap has that URL.
What to do: Check the link; pick from the list.
No ConceptMaps yet.
Where: Terminology page.
The engine has no ConceptMaps. Atlas also shows this when it can’t list them, so an unreachable engine looks the same.
What to do: Create one (+ New ConceptMap) or upload .json files (Manage ConceptMaps).
No context mapper exists for this template.
Where: Export dialog.
There is nothing but the OPT to export.
No context mapper yet
Where: Engine state, template list.
The template has no context mapper, so nothing of it is mapped.
What to do: Click Start mapping → (Start mapping a template).
no coverage changes
Where: Template coverage, compare strip.
Nothing changed in coverage since the version you compare with.
No data in example for <mapping>
Where: Highlight chip in an example pane header.
The mapping is in the engine’s tree, but the example has nothing at its path (tooltip “The mapping matched, but the example has nothing at its path.”).
What to do: Not necessarily an error: the generated example may not fill that element. Check the paths if you expected data (See your mapping in action).
No existing models map this archetype.
Where: Create-model wizard, extends step.
There is no model to extend.
No extension fits this element.
Where: + Ext extension picker (also “No extension matches.”).
No known extension’s context names this element.
What to do: Show all to list extensions with another context.
No git remote is connected yet.
Where: Versioning actions (code not-configured).
As above.
What to do: Connect a remote (Connect a Git repository).
No git remote is connected yet. Connect one to push the history, make releases and compare versions.
Where: Versioning page (every tab but History), with Connect one.
The history is kept, but nothing goes to Git until a remote is connected.
What to do: Click Connect one (Connect a Git repository).
No groups yet. Add one to start mapping codes.
Where: ConceptMap editor.
The ConceptMap is empty.
What to do: Click + Add group.
No mapped archetypes yet.
Where: Start picker dialog.
No archetype has a model yet.
No mapping matches “<filter>”.
Where: Mapping outline, and the Move to… picker.
The filter hides every mapping.
What to do: Clear the filter.
No mappings yet.
Where: Mapping outline of an empty model, with + Add mapping.
The model has no mappings (model-without-mappings \).
What to do: Click + Add mapping.
No model mappers belong to this template yet.
Where: Engine state, model mappers of a template.
No model is listed in the template’s context mapper.
What to do: Open the template in the Workspace and add mappings.
No model of this template names a FHIR resource or profile. A model’s profile is …
No model of this template names a FHIR resource or profile. A model’s profile is its structureDefinition, or the profile it writes into meta.profile; load the package defining it from the FHIR packages.
Where: Profile coverage tab.
No model says which resource or profile it produces, so there’s nothing to count.
What to do: Set the models’ resource or profile (Start mapping a template).
No packages yet. Paths are checked and FHIR is validated against base FHIR only.
Where: FHIR packages page.
No IG package is loaded.
What to do: Add a package.
No problems found.
Where: Problems dock.
The template has no problems.
No problems match the filters.
Where: Problems dock.
Filters hide every problem.
What to do: Turn the severity toggles back on, choose All sources, or clear the mapping scope.
No profile is loaded for this resource, so this is the base FHIR definition. Load …
No profile is loaded for this resource, so this is the base FHIR definition. Load an IG from the FHIR packages to see its required and must-support elements instead.
Where: Profile coverage tab.
Coverage is counted against base FHIR.
What to do: Load the IG package (Use FHIR profiles and IG packages).
No profiles loaded for FHIR <version> yet — add one below.
Where: Create-model wizard.
No IG package for that FHIR version is loaded.
What to do: Upload a package or fetch it by id#version in the wizard, or pick a base resource.
No recorded changes for this mapping.
Where: Editing sheet, History tab.
The history has no entry for this mapping.
No recorded changes yet.
Where: History (dock tab or Versioning page).
Nothing is in the history yet.
What to do: Changes are recorded on save.
No supported files selected (.zip, .opt, .yaml, .yml, .json, .tgz).
Where: Engine state, upload panel (red).
None of the files has an accepted extension.
What to do: Pick .zip, .opt, .yaml/.yml, .json or .tgz files.
No templates available yet. Upload one below to get started.
Where: Workspace template gallery.
The engine has no templates.
What to do: Upload an OPT or an exported ZIP in the panel below, or load the demo data (Your first mapping in 15 minutes).
No templates match “<filter>”.
Where: Engine state, template list (also “No templates in this view.”).
The search or the context filter hides every template.
What to do: Clear the search or choose All.
No unsaved changes
Where: Workspace top bar, a short hint after Ctrl+S.
Auto-save is off and there is nothing to save.
None of its child mappings find anything in the example.
Where: Example values of the editing sheet.
The mapping only hands over to children, and none of them finds a value.
Not a FHIR npm package (.tgz with package/package.json): <message>
Where: FHIR packages upload.
The .tgz isn’t an npm FHIR package.
What to do: Download the package from the registry again.
not applied yet
Where: Terminology badge (also “changed”, “removed”).
The terminology edit isn’t saved, so the example values went through the saved one (or none).
What to do: Save to apply.
Not FHIR
Where: Validation chip in the FHIR pane header (amber). Hover for the parser message.
The FHIR pane’s text isn’t FHIR JSON the validator can read (hover the chip for the parser’s message).
What to do: Fix the JSON in the FHIR pane, or convert again.
Not found in the engine: <urls>
Where: Export dialog (amber).
These ConceptMaps are referenced but not in the engine.
What to do: Upload them, or fix the references.
Not in any stored package: <profiles>
Where: Export dialog (amber).
These profiles aren’t in a loaded package, so they can’t be bundled.
What to do: Load the packages first if you want them in the ZIP.
Not in the engine tree yet — Save to preview its values.
Where: Editing sheet, Example values tab.
The mapping is new or renamed; the engine knows it only after a save.
What to do: Save.
Not in the engine tree yet — Save to resolve it.
Where: Editing sheet, under a path.
New or renamed mapping: the engine resolves it after a save.
What to do: Save.
Not in the template: <rest>
Where: Editing sheet, under the openEHR path (warning).
The live check didn’t find these nodes in the template.
What to do: See openehr-not-in-template \.
not linked · <model>
Where: Template coverage tab, on an archetype’s unit (amber, dashed).
The model for this archetype exists, but the model around it has no slot mapping to it, so these elements are never converted.
What to do: Use + Slot on the unit rather than mapping the same elements again (Find what isn’t mapped yet).
Not linked · nothing slots it in from the start, so it never runs
Where: Template overview, strip at the bottom of a model card, with Slot it in….
No chain of slot mappings leads from the start model to this model, so the engine never runs it. The Problems dock lists it as model-unreached \.
What to do: Click Slot it in…, pick where the archetype sits in the template and click Add slot (Connect models: slots, links, references).
Not linked · runs only with <core model>, which nothing slots in
Where: Template overview, strip on an extension model’s card.
The extension merges into its core model, and nothing slots the core in. Neither runs.
What to do: Slot the core model in (on its own card).
Not linked: no model slots <models> in, so the engine never runs its mappings and …
Not linked: no model slots <models> in, so the engine never runs its mappings and it produces nothing. Add the slot mapping in the enclosing model (openEHR tab, “+ Slot”).
Where: Profile coverage tab (amber).
The resource’s producing model is never reached.
What to do: Add the slot (Connect models: slots, links, references).
not loaded
Where: Chip on a package on FHIR packages (red); hover for the reason, for example “Could not be loaded: <reason>”.
The package is stored but Atlas couldn’t read its profiles. Models using them fall back to base FHIR.
What to do: Upload a correct package, or one for the right FHIR version.
not mergeable
Where: Versioning → Reviews, on a review (amber).
The provider reports the pull request can’t be merged.
What to do: Resolve it on the provider (for example, update its branch there).
Nothing imported. Planned: <n> to create · …
Where: Above the plan of a pull or restore, with an older engine that refuses errors.
The plan has errors (listed below the line), and this engine imports nothing while there are any. Current engines import despite them. The counts say what the import would have done.
What to do: Fix the errors where the artefacts come from (usually the repository: add the model a mapping references, say), then pull or restore again, or update the engine.
Nothing matches the filters.
Where: Coverage tabs (also “Nothing matches the search.”).
Filters or search hide everything.
What to do: Turn off Unmapped only / Required only, or clear the search.
Nothing slots <model> in from the start, so the engine never runs its mappings. …
Nothing slots <model> in from the start, so the engine never runs its mappings. Choose where it goes; the enclosing model gets a slot mapping to it.
Where: Dialog Slot <model> in (from Slot it in…).
Choose the place to slot the model into.
What to do: Pick an occurrence and click Add slot.
Nothing to export for template: <template id>
Where: Export dialog.
None of the chosen parts exists for this template.
What to do: Tick another part.
Nothing to import
Where: Engine state, upload preview summary.
The upload matches what the engine has; Apply is disabled.
Nothing to import: the engine already matches <branch>. Pulling records it as pulled.
Where: Pull from the remote dialog footer.
The content is the same; pulling only records the sync.
Nothing to preview for this mapping.
Where: Editing sheet, Example values tab.
The mapping selects no value (no paths).
Nothing to restore: the engine already matches <version>.
Where: Restore dialog footer.
The chosen version equals the engine’s state.
Nothing was imported: <errors>
Where: Git remote settings after The repository — import it into the engine, or the Engine state notice after Import from the remote (red).
The repository has errors (a model referencing one it doesn’t contain, say), and the engine is an older version that imports nothing while there are any. Current engines import despite them.
What to do: Fix the errors in the repository and import again, or update the engine.
O
Only .json FHIR ConceptMap files are accepted.
Where: Terminology upload (red).
Only ConceptMap JSON files go here.
Only .opt files are supported.
Where: Update operational template dialog (Replace OPT…).
Replacing a template needs an .opt file.
Open the Workspace on a larger screen
Where: Instead of the Workspace on a small screen (narrower than 768 px), with ‹ Back to Atlas.
The mapping designer needs a desktop or laptop screen. The message continues: “The mapping designer needs the room of a desktop or laptop. Please switch to a wider screen to build and edit mappings.”
What to do: Use a wider window or screen. ‹ Back to Atlas returns to Engine state.
openEHR path made absolute: it isn’t under the new parent’s node.
Where: Note in the move toast.
The new parent’s openEHR node doesn’t contain the mapping’s node, so Atlas wrote the full path.
openFHIR Atlas is your workspace for building and managing FHIR Connect mappings …
openFHIR Atlas is your workspace for building and managing FHIR Connect mappings between openEHR and FHIR. There’s nothing here yet — pick one of the options below to get started.
Where: Engine state page, when the engine has no templates.
The engine is empty. Atlas also shows this page when it couldn’t read the engine’s state at all, so an engine problem can look like an empty engine.
What to do: Click Load demo mappings, upload your material (Bring your material in), or open API access. If you expected templates, reload the page and check the engine is reachable.
Opening model… <model>
Where: Workspace, over the work area or the middle pane.
The model named in the link or picked from the overview is being fetched.
Opening template… <template id>
Where: Workspace, over the work area.
Atlas is loading the template’s models, example and template tree. No pane is usable until everything is in.
Out of date with your edits
Where: Over the openEHR and FHIR example panes, with Save & refresh.
Auto-save is off and you have unsaved edits: the panes still show the conversion of the last saved mappings. The overlay continues: “This pane won’t reflect your mapping changes until you save.”
What to do: Click Save & refresh to save and convert again (Edit mappings in the Workspace).
P
Page Not Found
Where: Any unknown address, with “The page you’re looking for doesn’t exist.” and Go to Engine State.
The link is wrong or the page no longer exists.
What to do: Click Go to Engine State. For link formats see Links you can share.
Paths unchanged
Where: Move to… picker preview.
Moving there changes no path.
Pull first: the remote has changes the engine hasn’t taken.
Where: Versioning: a push from a dialog (Checkpoint and push, the release wizard’s
Push now), when the engine gave no explanation of its own (code pull-required).
The branch has changes to mapping files the engine hasn’t pulled, commits the engine never synced with, or a rewritten history, so the engine won’t push onto it. On the Remote tab the same refusal says why, with a Pull… button.
What to do: Open Versioning → Remote, click Pull… and pull, then push again (Push, pull and conflicts).
R
Reading the template structure…
Where: Slot placement list.
Atlas is still loading the template tree it needs to list the places.
Remove package
Where: FHIR packages, confirmation.
“Remove <name>#<version>? Models using its profiles fall back to base FHIR.”
What to do: Check used by before removing.
Review <id> is <state>; only a review closed without merge can be resubmitted
Where: Versioning → Reviews, above the list, after Resubmit (code invalid-state).
The engine checked the pull request with the provider first: it is still open, or it was merged meanwhile.
What to do: Reload the list. An open review takes more changes with Add my unpushed changes; a merged one needs nothing (Submit for review).
S
Save failed
Where: Workspace top bar (save status), and as the error under the editor when the backend gave no reason.
The engine refused the model or couldn’t be reached. The red line under the editor says why (usually the engine’s validation message).
What to do: Read the message under the editor, fix the model (the Problems dock’s Schema problems show what the engine would reject, see Problems) and save again. Leaving the model now asks Leave without saving?.
Save to update highlights
Where: Highlight chip in an example pane header (auto-save off). With auto-save on it reads “Updates after auto-save”.
The selected mapping is new or renamed; the engine’s tree still reflects the last save, so Atlas can’t highlight it yet.
What to do: Save (or wait for auto-save).
Saved
Where: Workspace top bar, save status.
The last save worked.
Saved. The token was removed because the host changed.
Where: Git remote settings, after Save.
The save sends the token to a host it wasn’t given for, and no new token was typed: another repository host, a provider API base on a host of its own, or the first repository for a token stored before any. The engine binds the token to the hosts it was given for, so it dropped it.
What to do: Type the token for the new host and save again (Move to another repository host).
Saving & running…
Where: Workspace top bar, save status (on narrow windows only the dot shows; the text is its tooltip).
Your edits are being saved to the engine; afterwards the example is converted again.
Select a mapping to edit it · ↑ ↓ then Enter · drag or Alt+arrows to move
Where: Editing area when no mapping is selected.
Nothing is selected.
What to do: Click a row, or use the arrow keys and Enter.
Stored when the upload is applied
Where: Upload preview row of a FHIR package.
Packages are stored only when you click Apply. A StructureDefinition, ValueSet or CodeSystem
.json says Packaged as <package>. Stored when the upload is applied: Atlas stores the loose
resources of the upload together as that package.
Stored <package>#<version>, … · <n> ConceptMap(s) added to Terminology · <n> files skipped
Where: FHIR packages, after an upload.
What the upload stored, with the files it skipped and why listed below (examples or other files in a ZIP that are no conformance resources).
What to do: Nothing, unless a skipped file should have been stored.
T
Template <template id> isn’t loaded in the engine.
Where: Workspace, red strip under the middle pane’s header, after opening a link.
The link names a template the engine doesn’t have (deleted, renamed, or a link from another installation).
What to do: Pick a template from the gallery, or upload it on Engine state (Bring your material in).
The branch already has content. Which side wins?
Where: Git remote settings, first connection.
The branch already holds mappings, and the engine has its own.
What to do: The engine — commit its state over the branch, or The repository — import it into the engine (imports right away: the engine becomes a copy of the repository).
The branch has no commits yet. Connect the engine to it (Git remote settings) to write its state.
Where: Versioning: a push from a dialog (Checkpoint and push, the release wizard’s
Push now), when the engine gave no explanation of its own (code connect-required).
The branch was never connected, or it was deleted. Nothing was pushed.
What to do: Open the Git remote settings, click Connect, then push (Connect a Git repository).
The context YAML doesn’t parse: <message>
Where: Start picker dialog (red).
Atlas couldn’t set the start because the context mapper’s YAML is broken.
What to do: Fix it in the context mapper (code icon in the overview’s middle pane header).
The editor has changes to this mapping that aren’t recorded yet.
Where: Editing sheet, History tab.
Unsaved edits aren’t in the history.
What to do: Save.
The engine answered <status>
Where: Any error line.
The engine failed without an explanation.
What to do: Try again; if it persists, look at the engine’s logs or contact support (Support).
The engine changed since the preview. Review the new plan.
Where: Versioning actions and Git remote import (code plan-mismatch).
The engine changed between preview and apply; nothing was applied.
What to do: Review the new plan and apply again.
The engine changed since the preview. This is the new plan — check it and apply again.
Where: Engine state, upload preview (amber).
Someone (or something) changed the engine between your preview and Apply, so Atlas didn’t apply the old plan. The plan shown is recomputed.
What to do: Review the new plan and click Apply again.
The engine changed since the preview. This is the new plan — review it before restoring.
Where: Restore dialog (amber).
The engine changed after the preview; the new plan is shown.
What to do: Review it and click Restore again.
The engine could not resolve this path against the template.
Where: Editing sheet, under the openEHR path (warning).
The engine flagged this openEHR path as not in the template.
What to do: See openehr-not-in-template \.
The engine data reflects the last save — Save to resolve the edited path.
Where: Editing sheet, under a path (resolved paths).
The resolved path shown is the engine’s, from the last save; your edited path is estimated (unsaved).
What to do: Save.
The engine has no ConceptMap with this url, so it can’t translate anything: codes …
The engine has no ConceptMap with this url, so it can’t translate anything: codes are kept as they are.
Where: ConceptMap peek.
See terminology-conceptmap-unknown \.
What to do: Upload the ConceptMap on Terminology, or pick another.
The engine has no secret key configured (openfhir.versioning.secret-key), so it …
The engine has no secret key configured (openfhir.versioning.secret-key), so it can’t store an access token.
Where: Git remote settings (amber).
The engine can’t store tokens securely.
What to do: Ask whoever runs the engine to configure the key.
The engine is empty, but its git remote may not be
Where: Engine state page, above the welcome card, when versioning is set up and the remote has commits the engine hasn’t pulled. The notice names the repository and branch and says why they differ (for example “The engine hasn’t pushed to or pulled from main yet …”).
The engine holds no template, but the repository it versions to does have content: typically a fresh engine connected to an existing repository. Its mappings show up here only once the engine imports them.
What to do: Click Import from the remote. The repository wins, as when choosing The repository — import it into the engine in the Git remote settings (Connect a Git repository): its errors (an artefact referencing one it doesn’t have, say) don’t stop the import.
The engine hasn’t pushed to or pulled from <branch> yet, so it can’t tell whether they match.
Where: Versioning → Remote (amber). After a refused Push it ends with “Connect the engine to it, or pull first, then push.” with Git remote settings and Pull….
No sync has happened yet, and the branch has commits: the repository was never connected, or the repository URL or branch setting changed. The engine doesn’t push onto them until it knows what they hold.
What to do: Usually connect: open the Git remote settings and click Connect, which asks whether the engine or the repository wins (Connect a Git repository). Pull only if the repository should replace the engine: a pull plans to delete every engine artefact the repository lacks (its preview shows them).
The engine only applies a slot whose model maps <holder type>; this one maps <type>.
Where: Under FHIR resource in Slot <model> in, the reuse dialog and the create wizard, when Same resource is picked for a model of another resource.
A plain slot into this model is skipped by the engine (slot-resource-mismatch: slot into a model of another resource).
What to do: Pick Enters a new <type> resource, unless you’ll write the reference yourself (Connect models: slots, links, references).
The engine or the remote changed since the preview. This is the new plan — review it before pulling.
Where: Pull from the remote dialog (amber).
Something changed after the preview; the new plan is shown.
What to do: Review it and click Pull again.
The engine refused Atlas’ credentials. Sign in again; if it persists, check the …
The engine refused Atlas’ credentials. Sign in again; if it persists, check the engine’s authentication settings.
Where: Any error line, when the engine refuses Atlas.
The engine rejected the credentials Atlas uses to call it (code engine-unauthorized).
What to do: Sign out and in again. If it continues, the Atlas–engine authentication needs fixing by whoever runs the installation (Authentication).
The engine’s helper tree couldn’t be read, so its checks are missing: <reason>
Where: Problems dock.
The example has <n> FHIR value(s) but <m> openEHR node(s) for it — a missing [n] …
The example has <n> FHIR value(s) but <m> openEHR node(s) for it — a missing [n] / iteration or a condition that selects too much or too little?
Where: Editing sheet status chip (info) and values chip tooltip.
The two sides of the example disagree on how many values the mapping carries.
What to do: Check the openEHR path for a missing [n]/iteration, and the conditions (Map only when… (conditions)). A translation can also explain different codes, not different counts.
The example has no <path> (at <mapping>).
Where: Example values of the editing sheet (also “Nothing in the example at <path> matches the condition”).
The example has nothing where the mapping (or the named parent mapping) points.
What to do: Check the path and the condition; the example may simply lack that element.
The FHIR packages are still loading; try again in a moment.
Where: + Ext extension picker (also “FHIR packages are still loading — try again shortly.” in the Export dialog).
Atlas is still reading the loaded IG packages (after a start or an upload).
What to do: Wait a moment and open it again.
The git remote could not be reached.
Where: Versioning actions (codes remote-error, provider-error).
Atlas’s engine couldn’t talk to the Git provider.
What to do: Use Test connection on Git remote (Connect a Git repository).
The last conversion failed — values reflect the panes as they are.
Where: Values chip tooltip and stale badge in the editing sheet.
The example values come from panes the last conversion couldn’t update.
What to do: Read the red error above the pane, fix the mapping and save.
The merged result differs from the engine for <n> file(s): <files>
Where: Versioning → Reviews (amber).
The merge on the provider produced something else than the engine has.
What to do: Take the merged version or Keep the engine’s (Submit for review).
The open model has unsaved edits. Pulling reloads it from the engine and discards them.
Where: Pull from the remote dialog (amber) (“Restoring reloads it…” in the Restore dialog).
The model open in the Workspace has unsaved edits that the pull or restore would overwrite.
What to do: Cancel and save first if you want to keep them.
The openFHIR engine could not be reached.
Where: Versioning and Git remote pages, and versioning errors (code engine-unreachable).
Atlas couldn’t contact the engine.
What to do: Try again later; check the engine is running.
The packages are still being loaded; their profiles appear shortly.
Where: FHIR packages page (amber), with Refresh.
Atlas is still reading the tenant’s packages (after a start or an upload). Until it finishes, suggestions and checks use base FHIR.
What to do: Wait a moment and refresh.
The profile closes the extension slicing here: only its own extensions are allowed.
Where: + Ext extension picker (amber).
The profile allows only the extensions it defines at this element.
What to do: Pick one of those; anything else wouldn’t conform (Add a FHIR extension).
The profile isn’t loaded.
Where: Profile coverage tab (amber).
The model’s profile has no loaded package.
What to do: Load it on FHIR packages.
The remote already has content. Choose which side wins.
Where: Connecting a remote (code remote-not-empty).
The branch isn’t empty.
What to do: Choose the engine or the repository (Connect a Git repository).
The remote branch <branch> has no commits; connect (POST /versioning/connect) to write the engine’s state to it
Where: Checkpoint and push, and Push now in the release wizard (the engine’s own text,
code connect-required). On the Remote tab the same refusal links to the Git remote settings.
The branch was never connected, or it was deleted. Nothing was pushed; the unpushed changes stay, and a checkpoint made in the same step is kept.
What to do: Open the Git remote settings, click Connect, then push (Connect a Git repository).
The remote has changes the engine hasn’t pulled; pull (POST /versioning/pull) before pushing
Where: Checkpoint and push, and Push now in the release wizard (the engine’s own text,
code pull-required). The engine words the other two cases the same way: “The remote no longer
contains the engine’s last push (its history was rewritten); pull …” and, for a branch it never
synced with, “The engine hasn’t pushed to or pulled from this branch yet; connect (POST
/versioning/connect) or pull (POST /versioning/pull) before pushing”. On the Remote tab the same
refusal reads “<why>. Pull first, then push.” with a Pull… button (for a branch never synced
with: “… Connect the engine to it, or pull first, then push.” with Git remote settings first).
For a branch never synced with, connecting is usually right: see the entry The engine hasn’t pushed to or pulled from <branch> yet.
A push never takes the remote’s changes into the engine; only a pull does, after showing you what it changes. Nothing was pushed; a checkpoint made in the same step is kept.
What to do: Open Versioning → Remote, click Pull… and pull, then push again (Push, pull and conflicts).
The remote changed <n> artefact(s) that the engine also changed (not pushed yet, …
The remote changed <n> artefact(s) that the engine also changed (not pushed yet, or in an open review):
Where: Pull from the remote dialog (amber).
A pull would touch artefacts you also changed.
What to do: Choose Keep the engine’s version (the next push overwrites the remote) or Take the remote’s version (discards the engine’s changes); the plan updates.
The remote changed <n> file(s) the engine also changed:
Where: Versioning → Remote, after Push (amber).
Both sides changed these files since the last sync.
What to do: Keep the engine’s version (overwrite the remote), or Take the remote’s version (update the engine) (asks to confirm). See Push, pull and conflicts.
The remote changed the same files. Choose which side wins.
Where: Push or pull (code conflict).
Both the remote and the engine changed the same files.
What to do: See the conflict choices (Push, pull and conflicts).
The remote is not reachable.
Where: Git remote, Test connection result.
Atlas’s engine couldn’t reach the repository.
What to do: Check the URL and the token.
The remote kept moving while pushing. Try again.
Where: Push (code remote-moved).
Others pushed to the branch while Atlas was pushing.
What to do: Push again.
The stored token was given for <host>. Changing the host removes it; enter a token for <host>.
Where: Git remote settings, under Access token (amber), while the repository URL points
to another host than the saved one, or the provider API base to a host of its own (not the
repository’s, and not the provider’s default API such as api.github.com). For a token stored
before any repository it reads “The stored token was given before any repository was set. Saving
one removes it; enter a token for <host>.”
Saving without a token removes the stored one.
What to do: Type the new host’s token. You can also save first and add the token afterwards (Move to another repository host).
The target root isn’t on this mapping’s path, so the condition tests the whole …
The target root isn’t on this mapping’s path, so the condition tests the whole resource rather than picking elements.
Where: Editing sheet, under a FHIR condition (amber).
The condition’s target root isn’t an element on the mapping’s own FHIR path, so it gates the whole mapping instead of filtering elements.
What to do: If you meant to pick elements, set the target root to the mapping’s path (Map only when… (conditions)).
The template has no occurrence of <archetype> to slot it into.
Where: Dialog Slot <model> in.
The template doesn’t contain the model’s archetype anywhere, so it can’t be slotted in.
What to do: Check the model’s archetype; see archetype-not-in-template \.
The template’s tree couldn’t be read.
Where: Template coverage tab.
Atlas couldn’t build the template’s tree, so coverage can’t be shown.
What to do: Reload the template; check the Problems dock’s banner.
the token may not push
Where: Git remote, Test connection result (amber).
The token can read but not push.
What to do: Use a token with write access.
There are no changes since the last checkpoint.
Where: Checkpoint (code nothing-to-checkpoint).
Nothing to name in a commit.
These settings apply to the whole tenant <tenant>. Everyone who signs in to it …
These settings apply to the whole tenant <tenant>. Everyone who signs in to it pushes to this repository and branch with this token, and a change here changes it for all of them.
Where: Git remote settings (amber).
The Git remote is shared by every user of the tenant.
What to do: Change it only in agreement with your team (Connect a Git repository).
This model can’t be edited live (no id).
Where: Under the model editor, after a save attempt.
The engine returned this model without an id, so Atlas can’t save it.
What to do: Edit and re-upload the model on Engine state instead.
This model has no id and can’t be edited live.
Where: Under the model editor (amber).
Same as above, shown before you try to save.
This openFHIR engine does not version mappings. Git versioning needs openFHIR Enterprise.
Where: Versioning and Git remote pages.
The engine Atlas is connected to has no versioning.
What to do: See When is versioning available? \.
This page is best viewed on a wider screen. Some tables and panels may overflow on small displays.
Where: Engine state page, on a small screen.
A hint only; the page still works.
What to do: Use a wider window if tables are cut off.
This remote uses the review workflow: submit the changes for review instead of pushing.
Where: Push (code review-required).
The Git remote is set to the review workflow, so direct pushes aren’t allowed.
What to do: Use Submit for review… (Submit for review).
Translates codes <summary>
Where: Editing sheet header, below the name.
This mapping’s codes go through a terminology (inline rows or a ConceptMap) and where it comes from.
What to do: Click it for the Translation tab (Translate codes).
U
Unknown mode ‘<mode>’; expected merge or mirror
Where: Upload error.
An upload asked for a mode other than Merge or Mirror.
What to do: Choose Merge or Mirror.
Unlock FHIR to reload the openEHR example
Where: Tooltip of the disabled Reload example button.
FHIR is locked as the source, so the openEHR example can’t be replaced.
What to do: Unlock FHIR (the lock button in the FHIR pane header) first.
Unsaved changes
Where: Workspace top bar, save status (the Engine state mapping detail and the ConceptMap editor show the same words, with their own Save).
The open model has edits that aren’t saved. With auto-save on they are saved shortly after you stop typing; with it off, they wait for Save or Ctrl+S.
Unsupported file type (expected .opt, .yaml, .yml, .json, .tgz or .zip)
Where: Upload result row (skipped).
The file type isn’t accepted.
Updates after auto-save
Where: Highlight chip in an example pane header.
As Save to update highlights, with auto-save on: it resolves by itself after the next save.
Upload failed.
Where: Engine state, upload panel (red), when the backend gave no reason.
The upload or preview failed.
What to do: Try again; check the per-file messages.
Uploading and validating…
Where: Engine state, upload panel (also “Uploading and validating…” on the Terminology page).
The files are being sent. On engines that can’t import everything at once, files are uploaded one by one and there is no preview.
Use an existing mapping?
Where: Dialog when you add a mapping for an archetype that existing models already map (NOT YET MAPPED, or + Slot in the template coverage).
“These model mappings already map <archetype>. Pick one, or create a new model.”
What to do: Pick one to reuse it, or New model… (Start mapping a template).
Use as the extension url: <url>
Where: + Ext extension picker, when you type a URL.
“exactly as typed; no loaded package defines it, so it isn’t checked”.
What to do: Use it only if the URL is right; better, load the package that defines it.
V
valid
Where: Validation chip in the FHIR pane header (green, with a check).
No errors or warnings. Hover for what it was validated against (“Validated by Atlas against base FHIR + <profiles> in <ms> ms.”).
Validated by Atlas (HAPI) against base FHIR and the loaded packages; the engine …
Validated by Atlas (HAPI) against base FHIR and the loaded packages; the engine itself doesn’t validate.
Where: Validation settings menu, footer.
Validation runs in Atlas, never in the engine: conversions aren’t blocked by it.
Validating…
Where: Validation chip in the FHIR pane header.
The FHIR example is being validated.
Validation failed
Where: Validation chip in the FHIR pane header (amber). Hover for the reason.
The validation request failed.
What to do: Click Validate to retry.
Validation timed out
Where: Validation chip in the FHIR pane header (amber).
The validator took too long on this example.
What to do: Click Validate to try again.
Validator busy
Where: Validation chip in the FHIR pane header (amber).
Too many validations at once (tooltip “Too many validations at once; run it again shortly.”).
What to do: Click Validate again in a moment.
Validator starting…
Where: Validation chip in the FHIR pane header.
The validator is loading the FHIR definitions; this takes a few seconds, once.
What to do: Wait.
Values reflect the last save — Save to re-run the conversion.
Where: Values chip tooltip, stale badge, condition tally.
You have unsaved edits; the example values and counts are from the last saved conversion.
What to do: Save.
Versioning is not available in the public demo.
Where: Versioning and Git remote pages, with When is versioning available?.
The public demo doesn’t offer versioning.
What to do: See When is versioning available? \.
W
Will be slotted into <holder> at <path>
Where: Create-model wizard.
The new model will be slotted in there when it is created.
Y
You’re exploring openFHIR Atlas as a demo user. Sign up for individual access to …
You’re exploring openFHIR Atlas as a demo user. Sign up for individual access to unlock additional features.
Where: Sidebar footer, when you aren’t signed in (public demo), with Login and Sign up.
You are using Atlas as the shared demo user: some features (for example versioning) aren’t available.
What to do: Sign in, or sign up for your own access (Before you start).
Your account may not read the version history (scope versioning.r).
Where: Versioning and Git remote pages.
Your account lacks the right to read the history.
What to do: Ask your administrator for access. See When is versioning available? \ and Access and permissions.