# Support (support-contact)= ## How to reach us - In Atlas: **Contact support** at the bottom of the sidebar opens an e-mail to [info@open-fhir.com](mailto:info@open-fhir.com). - Or write to [info@open-fhir.com](mailto:info@open-fhir.com) directly. For a license, a sandbox account or a dedicated instance, use the same address; see {doc}`/offer/ways-to-use`. Before you write, the answer may already be here: every problem in the Problems dock has its own section in {doc}`/reference/problems`, and every other message is in {doc}`/reference/messages`. (support-report)= ## What to put in a report The more of these you include, the faster we can reproduce what you see. | Include | Where to find it | |---|---| | **Where you are**: the link | Copy the address bar. In the Workspace and on Engine state it names the template, the model and the mapping you have open ({doc}`/reference/deep-links`). | | **The template id** | The template's name on **Engine state** and in the Workspace's template gallery (the `templateId=` part of the link). | | **The model and mapping** | The model's name in the Workspace's model selector, and the mapping's name in the outline (the `modelName=` and `mapping=` parts of the link). | | **The problem** | The message exactly as the Problems dock shows it, with its source tag (Engine, FHIR path, …). Hover the row and copy the address of its help link ("What this problem means and how to fix it"), shown when documentation links are on: it ends in `#problem-`, the problem's code. | | **The message** | Any other notice, chip or dialog text, copied exactly, or a screenshot. | | **The conversion** | For a conversion that went wrong: the insight's id, shown as "Insight ()" in the detail view on **Insights**, and its "Request id" (or the `insightId=` part of the link). | | **What you did and what you expected** | The steps, what happened, and what you expected instead. | | **When** | The date and time, with your time zone, so we can find it in the logs. | | **Your environment** | Public demo, sandbox, or your own installation; and your tenant (under your name in the sidebar). | :::{warning} Never send a client secret, an access token or a Git token. Don't send real patient data: if an example is needed, replace the personal details first. ::: :::{tip} For a mapping question, an export of the template (YAML files, the OPT and the ConceptMaps it uses) lets us reproduce it exactly. See {doc}`/ship/export`. Check first that it holds nothing you may not share. ::: ## Related - {doc}`/reference/problems` - {doc}`/reference/messages` - {doc}`/reference/deep-links` - {doc}`/operate/insights`