.. _integrations:

Integrations
============
.. note::
    This page describes what openFHIR Engine can integrate to for support in its mappings. If you're looking for instructions on how to invoke openFHIR Engine itself and
    how to integrate engine into your flow, see :ref:`architecture`.

openEHR Repository
------------------
openFHIR Engine can be integrated with an existing openEHR Repository for the purpose of getting operational templates needed for the mappings.
In this case, operational templates do not need to be populated as part of the state configuration.

//todo

Terminology server
------------------
As describe in the :ref:`terminology`, an important aspect to efficient mapping is access to a terminology service providing bidirectional
mappings between openEHR and FHIR terminologies. For this purpose, openFHIR Engine can be integrated with an external FHIR terminology server
compliant with the following IG https://build.fhir.org/terminology-service.html

Required operations that the external terminology server needs to support are:

- $translate

// todo