openFHIR Atlas

Atlas is where you build, check and ship the mappings that let the openFHIR engine translate between openEHR compositions and FHIR resources. You pick an openEHR template, say which FHIR resource each part of it becomes, and watch an example convert both ways while you edit. Atlas tells you what is still unmapped, what is wrong, and why, and keeps the history of every change.

Note

Atlas runs on openFHIR Enterprise, with a license that includes Atlas. To try it without an installation, use the public demo or ask for a free sandbox account. Ways to use openFHIR and Atlas lists every way to get it.

What do you want to do?

Map a new template

Bring an openEHR template in, choose where mapping starts and add a model per archetype.

Learn on the demo data

Fifteen minutes from “Load demo mappings” to a fixed problem and a coverage check.

Edit mappings

The outline, the editing sheet, paths with suggestions, conditions, undo.

Fix problems

Read the Problems dock and fix each kind of problem; every code is explained in the reference.

Find what isn’t mapped

Template and profile coverage: what is mapped, partly mapped, required, or not yet touched.

Translate codes

Inline code pairs, ConceptMaps, and checking what a value turns into.

Use FHIR profiles

Load IG packages so suggestions, checks, coverage and validation follow your profiles.

Ship a release

Git history, reviews, releases and comparing two versions.

Debug a conversion

See what a real conversion did, mapping by mapping.

What’s new in this version

See Release notes.