Ways to use openFHIR and Atlas

Atlas runs next to an openFHIR engine. You can try it in a shared demo, work in a free sandbox of your own, or run it on your own infrastructure. This page says who each option is for and how to get it.

Public demo

Sandbox

Your own installation

Dedicated instance

Who it’s for

A first look

Evaluating, learning, a small proof of concept

Production use on your infrastructure

Organisations that need integrations or several isolated tenants

Your own isolated data

No, shared by everyone

Yes, per user

Yes

Yes

Versioning (Git)

Not available

When the engine and your account allow it (Access and permissions)

When the engine and your account allow it

When the engine and your account allow it

Cost

Free

Free

A license that includes Atlas

Ask us

Service level

None

None, and it may be cleared

Ask us

Ask us

Public demo

For: anyone who wants to see Atlas before signing up.

Open open-fhir.com/portal. There is nothing to install and no account to create. The demo runs in public mode: everyone works on the same engine state through one shared service account, so anything you change is visible to the next visitor and may be changed by them. Versioning is not available there. Don’t enter real or private data. See Access and permissions.

Sandbox, with individual sign-up

For: evaluating Atlas and the openFHIR engine with your own templates and mappings, following the engine’s Tutorial, or running a limited proof of concept.

  • Free. Atlas is at sandbox.open-fhir.com/atlas, the engine at https://sandbox.open-fhir.com.

  • Isolated per user. Your templates, mappings, ConceptMaps, packages and API clients are your own tenant’s; nobody else sees them.

  • No SLA. There is no uptime guarantee, and the sandbox may be cleared without advance notice. Keep your mappings elsewhere too: export them (Export and move mappings) or connect a Git remote when versioning is available.

How to get it: sign up for individual access (the Sign up button Atlas shows when you aren’t signed in opens the sandbox registration), or request access at open-fhir.com#access; access comes by e-mail. If you already have sandbox API credentials (a client id and secret), tell us at info@open-fhir.com after signing up and we can link that client to your Atlas user. Once signed in, API access lets you create clients for your own systems (Connect your system to the API). The engine side is described in Public sandbox.

Your own installation

For: teams that run openFHIR in their own environment, for production or for data that can’t leave it.

Atlas is delivered as the Docker image openfhir/openfhir-atlas. It needs an openFHIR Enterprise engine and a license that includes Atlas; without that option Atlas doesn’t start and says “License doesn’t cover openFHIR Atlas. Please contact us at info@open-fhir.com to obtain a license for openFHIR Atlas.” To get a license, write to info@open-fhir.com. The engine’s installation is described in Installation.

Dedicated instance

For: organisations that want an openFHIR instance of their own, connected to their openEHR CDR, terminology server and other systems, optionally with several isolated tenants.

These capabilities are listed in Atlas under Dedicated instances in the sidebar. See Dedicated instances for what they include, and use Contact us there or write to info@open-fhir.com.