# Glossary The words Atlas uses on screen, in alphabetical order. {doc}`/start/key-ideas` explains the central ones (template, context, model, mapping, slot) together, with a picture. (glossary-a)= ## A–C API client : A machine login for your tenant, made on **API access** with **Generate Client**. Your systems use its client id and secret to get a token and call the engine. See {doc}`/reference/access` and {doc}`/operate/connect-api`. AQL path : The openEHR path of a node as an AQL query would write it (`/content[…]/data[at0001]/…`). One of the resolved paths the inspector shows with a copy button. See {doc}`/map/paths`. Archetype : A reusable openEHR building block (`openEHR-EHR-OBSERVATION.blood_pressure.v2`). A template is assembled from archetypes; in Atlas each archetype you map gets a model. Auto save : The checkbox under the mapping editor. On: edits are saved to the engine shortly after you stop typing, and the examples re-run. Off: a **Save** button appears and the example panes go stale until you save ({kbd}`Ctrl+S`). It is on at every visit. See {doc}`/map/edit-in-workspace`. Blame : Who changed each mapping last, and when, from the version history. Shown as a column in the outline and a line in the inspector when versioning is available. See {doc}`/ship/history`. Checkpoint : Names the changes made since the last checkpoint with a message: it becomes the commit that carries them to the Git remote (pushed right away with **Push to now**, or through a review). See {doc}`/ship/history`. Code view : The model as raw YAML, with schema completion (the **Raw YAML editor** button above the editor). The other view is the visual editor (**Visual mapping editor**). Both edit the same model. Composition : One openEHR record built from a template. The openEHR example pane shows one as flat JSON; `$composition` in a path starts from its root. ConceptMap : A FHIR resource that translates codes from one code system to another. Mappings use one for `local` terminology; you manage them on **Terminology**. See {doc}`/codes-and-profiles/conceptmaps`. Condition : "Map only when…": a **FHIR condition** or **openEHR condition** under **Only when** limits a mapping to the elements or cases that match. It has a **Where** (target root), a field, an operator and criteria. See {doc}`/map/conditions` and {doc}`/reference/paths-cheat-sheet`. Context mapper : The file that ties a template to its models: which template, which archetype mapping starts from, and which models take part. One per template (plus sub-contexts). You edit it from the Workspace overview. See {doc}`/start/key-ideas`. Core model : A model that maps an archetype on its own, as opposed to an extension model that changes it. Coverage : How much of a template (Template view) or of a FHIR profile (Profile view) your mappings reach, with what is still unmapped and what is required. See {doc}`/check/coverage`. (glossary-d)= ## D–L Deep link : A URL that opens Atlas on a given template, model, mapping, ConceptMap, Versioning tab or insight. See {doc}`/reference/deep-links`. Dismiss : Hides an info problem for this template, in this browser only. See {doc}`/check/fix-problems`. Engine : The openFHIR engine that stores the mappings and runs the conversions. Atlas is its editor. Engine state : Everything the engine holds for your tenant: templates, context and model mappers, ConceptMaps. Also the name of the Atlas page that lists them. See {doc}`/reference/screens/engine-state`. Example panes : The openEHR pane (left) and the FHIR pane (right) of the Workspace. One is the source; Atlas converts it with the current mappings and shows the result in the other. See {doc}`/check/see-in-action`. Extension (FHIR) : An extra element a FHIR profile adds, identified by its url. Atlas marks extension suggestions `ext` and adds them in the Profile view with **+ Ext**. See {doc}`/codes-and-profiles/add-extension`. Extension model : A model that `extends` a core model instead of mapping from scratch. Each of its mappings says how it changes the core: `add` (a new mapping), `overwrite` (replaces the core mapping of the same name) or `append` (adds its **Followed by** children under the core mapping named in **Append to**). See {doc}`/map/fixed-values`. FHIR package : An implementation guide (IG) package (`.tgz`) with FHIR profiles, extensions and value sets, loaded per tenant on **FHIR packages**. See {doc}`/codes-and-profiles/fhir-packages`. Flat path : The openEHR path in the engine's flat format (segments joined by `/`, attributes after `|`), as in the keys of the openEHR example pane. One of the resolved paths. See {doc}`/map/paths`. Followed by : Child mappings that continue from their parent's FHIR element and openEHR node, with relative paths. Shown indented under their parent in the outline. Helper tree : The engine's own walk of a template's mappings, with every path resolved. Atlas reads it for highlights, resolved paths, coverage and problems; it reflects the last save. Insight : A record the engine keeps of one conversion: direction, status, the payloads, and which mappings applied. See {doc}`/operate/insights`. Leaf attribute : A part of an openEHR data value that isn't a template node, such as a quantity's magnitude or a coded text's code. Every spelling of it (`value/magnitude`, `magnitude`, `|magnitude`) works in every field; see {doc}`/reference/paths-cheat-sheet`. Live problems : Problems Atlas recomputes in the browser from your unsaved edits, marked "unsaved" in the dock. The others are "from last save". See {doc}`/check/fix-problems`. Lock as source : The lock on an example pane: that pane stays the source of every conversion and is never overwritten. See {doc}`/check/see-in-action`. (glossary-m)= ## M–R Manual : Fixed path/value pairs a mapping writes on one side, relative to the mapping (for example a fixed LOINC code). See {doc}`/map/fixed-values`. Mapping : One rule of a model: a FHIR path and an openEHR path that correspond, with optional conditions, terminology, manual values and children. Mapping code : The name of a programmed mapping, custom logic built into the engine that the mapping runs (for example `generateNarrative`, which writes a FHIR narrative). Add it with **+ Property** (group **Advanced**). See {external+openfhir:doc}`programmedmappings`. Merge / Mirror : The two ways to upload into the engine. **Merge** adds and updates what the upload contains; **Mirror** also deletes what it doesn't contain. See {doc}`/map/bring-material-in`. Model (model mapper) : The FHIR Connect file that maps one archetype to one FHIR resource or data type: its metadata, the FHIR side (`spec`) and its mappings. Created with the **Create a model** wizard. See {doc}`/map/start-mapping`. Must support (MS) : A profile's flag that a system has to be able to handle an element. Shown as the `MS` badge in suggestions and counted in profile coverage. Not linked : A model of the template that no slot leads to, so conversions never reach it. Fixed with **Slot it in…**. See {doc}`/map/connect-models`. Not modelled : Archetypes of the template that no model maps yet, listed separately in the Template view. OPT (operational template) : The openEHR template file (`.opt`) the engine maps against. "Template" in Atlas. Outline : The list of a model's mappings in the Workspace, with the editing sheet below it. Problem : Something Atlas or the engine found wrong or suspicious in the mappings, with a severity (error, warning, info) and a source. Listed in the Problems dock; every code is in {doc}`/reference/problems`. Profile : A FHIR StructureDefinition that narrows a resource (required elements, slices, bindings). A model's profile drives suggestions, checks, coverage and validation. See {doc}`/codes-and-profiles/fhir-packages`. Reference : A mapping that continues in another FHIR resource the engine creates and points to (`reference` with `resourceType`), with `$reference` as its openEHR path. Release : A tagged version of a template's mappings in the Git remote, made with the release wizard. See {doc}`/ship/release`. Remote : The Git repository the engine pushes the version history to. Set up on **Git remote**. See {doc}`/ship/git-remote`. Resolved paths : Where a mapping really lands once its parents are taken into account: the engine path, the flat path and the AQL path. "unsaved" marks an estimate made from your edits. Review : A pull request on the Git remote with your changes, when the workflow is **Review — changes go through pull requests**. See {doc}`/ship/reviews`. RM attributes : Attributes every openEHR record has from the reference model (time, language, subject …). Counted in coverage only with **Show and count RM attributes (time, language, subject …)**. (glossary-s)= ## S–Z Scope : A permission in a sign-in token (`fc.r`, `versioning.w` …). The engine checks scopes on every call. See {doc}`/reference/access`. Slice : A named, restricted part of a repeating FHIR element in a profile (`slice: ` in suggestions). Picking one writes the condition that selects it. Slot : The place in a template where another archetype sits. A mapping with **Slot archetype** hands that part over to the model of that archetype. See {doc}`/map/connect-models`. Source : The example pane a conversion starts from (openEHR → FHIR or FHIR → openEHR). Click a read-only pane to make it the source. Start archetype : The archetype of the template where the context starts mapping. Chosen when you start mapping a template. Sub-context : A context mapper with `scope: sub`, entered through a mapping's `slotContext` instead of by template id. See {external+openfhir:doc}`fhirconnect`. Template : An openEHR operational template (OPT), the shape of one kind of record. Everything in Atlas is organised per template. Tenant : Your organisation's isolated space on the engine. Everything you see belongs to your tenant. Terminology : How a mapping translates codes: `inline` (pairs written in the mapping), `local` (a ConceptMap), or, at model level, also `none` and `external`. Also the Atlas page that manages ConceptMaps. See {doc}`/codes-and-profiles/translate-codes`. Unidirectional : A mapping that runs in one direction only: `openehr->fhir` or `fhir->openehr`. Without it a mapping runs both ways. Validation : Checking the FHIR example against base FHIR and the loaded profiles. It runs in Atlas, not in the engine. See {doc}`/check/validate`. Versioning : The engine's history of every change to the mappings, pushed to a Git remote: history, blame, reviews, releases, compare. See {doc}`/ship/index`. Workspace : The full-screen editor: the template's models, the mapping editor, both example panes and the Problems dock. See {doc}`/reference/screens/workspace`. ## Related - {doc}`/start/key-ideas` - {doc}`/reference/paths-cheat-sheet`