# Interoperability roadmap

OpenCRVS has been technically architected from conception to interoperate with other systems. The following outlines the interoperability achievements in previous releases along with the roadmap of future releases planned in 2023/2024.

{% hint style="success" %}
OpenCRVS interoperates out-the-box using the [FHIR](https://www.hl7.org/fhir/overview.html) standard as JSON. The [FHIR API](https://www.hl7.org/fhir/http.html) is exposed via [OpenHIM](http://openhim.org/). **The supported FHIR version is: STU3**
{% endhint %}

**OpenCRVS v1.0: June 2022:**

a) Adopted the [OpenHIE](https://guides.ohie.org/arch-spec/) architectural framework by design and [FHIR](https://www.hl7.org/fhir/overview.html) standard interoperability reference middleware [OpenHIM](http://openhim.org/) - FHIR version STU3.

b) Integrated with [DHIS2](https://dhis2.org/) to standardise [event notifications](https://documentation.opencrvs.org/v1.3/technology/interoperability/event-notification-clients) from a hospital setting for civil registration using [FHIR](https://www.hl7.org/fhir/overview.html) in Bangladesh pilot.

**OpenCRVS v1.1: Sep 2022**

a) Birth registration integration with [MOSIP](https://mosip.io/).

b) Death registration integration with [MOSIP](https://mosip.io/).

c) Release of OpenCRVS [FHIR](https://www.hl7.org/fhir/overview.html) standard W3C standard [WebSub](https://www.w3.org/TR/websub/) [webhooks](https://documentation.opencrvs.org/v1.3/technology/interoperability/webhook-clients) for subscription.

**OpenCRVS v1.2: Jan 2023**

a) Release of the [Elasticsearch](https://www.elastic.co/) [Record Search API](https://documentation.opencrvs.org/v1.3/technology/interoperability/record-search-clients) for use as part of a social protection interoperability collaboration the[ Digital Convergance Initiative](https://spdci.org/).

b) Release of the OpenCRVS [FHIR Location REST API](https://documentation.opencrvs.org/v1.3/technology/interoperability/fhir-location-rest-api) for reading, updating and archiving jurisdictions and facilities.

**OpenCRVS v1.3 - Planned release: June 2023**

a) Authentication and validation of National ID using [MOSIP](https://mosip.io/) [E-Signet](https://docs.esignet.io/) consent.

b) Permanent installation of MOSIP integration at the MOSIP Experience Center in Bangalore, India.

d) Core collaboration of the [G2PConnect](https://g2pconnect.global/) protocol initiated.

e) Integration with [Secure Identity Alliance](https://secureidentityalliance.org/), OSIA standard [Birth Use Case](https://osia.readthedocs.io/en/v4.1/02%20-%20functional.html#birth-use-case)

f) Integration with [OpenSPP](https://openspp.org/) social protection system, using QR code.

g) Integration with [INGroupe](https://ingroupe.com/) National ID system.

**OpenCRVS v1.4 - Planned release: Sep 2023:**

a) [W3C Verifiable Credential](https://www.w3.org/TR/vc-data-model/) integration with [MOSIP](https://mosip.io/)

b) Correct record integration with [MOSIP](https://mosip.io/)

c) Revocation of a record integration with [MOSIP](https://mosip.io/)

d) [G2PConnect](https://g2pconnect.global/) protocol integration v0.1

e) OpenCRVS civil registration related [FHIR](https://www.hl7.org/fhir/extensibility.html) extensions published

**OpenCRVS v1.5 - Planned release: Jan 2024:**

a) [G2PConnect](https://g2pconnect.global/) protocol integration v1.0

b) Integration with the [JeMPI Master Patient index](https://github.com/jembi/JeMPI) v0.1

**OpenCRVS v1.6 - Planned release: May 2024:**

a) [G2PConnect](https://g2pconnect.global/) protocol integration v2.0

b) Integration with the [JeMPI Master Patient index](https://github.com/jembi/JeMPI) v1.0