OpenCRVS
v1.3
v1.6v1.5v1.4v1.3
v1.3
v1.6v1.5v1.4v1.3
  • 👋Introduction
  • Product Specifications
    • Functional Architecture
    • Workflow management
    • Status Flow Diagram
    • Users
      • Examples
    • Core functions
      • 1. Notify event
      • 2. Declare event
      • 3. Validate event
      • 4. Register event
      • 5. Print certificate
      • 5. Issue certificate
      • 6. Search for a record
      • 7. View record
      • 8. Correct record
      • 9. Verify record
      • 10. Archive record
      • 11. Vital statistics export
    • Support functions
      • 10. Login
      • 11. Audit
      • 12. Deduplication
      • 13. Performance management
      • 14. Payment
      • 15. Learning
      • 16. User support
    • Admin functions
      • 17. User management
      • 18. Comms management
      • 19. Content management
      • 20. Config management
    • Data functions
      • 21. Legacy data import
      • 22. Legacy paper import
  • Technology
    • Architecture
      • Performance tests
    • Standards
      • FHIR Documents
        • Event Composition
        • Person
        • Registration Task
        • Event Observations
        • Locations
    • Security
    • Interoperability
      • Create a client
      • Authenticate a client
      • Event Notification clients
      • Record Search clients
      • Webhook clients
      • National ID client
      • FHIR Location REST API
      • Other ways to interoperate
  • Default configuration
    • Intro to Farajaland
    • Civil registration in Farajaland
    • OpenCRVS configuration in Farajaland
      • User / role mapping
      • Application settings
      • Declaration forms
      • Certificate templates
    • Business process flows in Farajaland
  • Setup
    • 1. Establish team
    • 2. Gather requirements
    • 3. Installation
      • 3.1 Set-up a local development environment
        • 3.1.1 Install the required dependencies
        • 3.1.2 Install OpenCRVS locally
        • 3.1.3 Starting and stopping OpenCRVS
        • 3.1.4 Log in to OpenCRVS locally
        • 3.1.5 Tooling
      • 3.2 Set-up your own country configuration
        • 3.2.1 Fork your own country configuration repository
        • 3.2.2 Set up administrative address divisions
          • 3.2.2.1 Prepare source file for administrative structure
          • 3.2.2.2 Prepare source file for statistics
        • 3.2.3 Set up CR offices and Health facilities
          • 3.2.3.1 Prepare source file for CRVS Office facilities
          • 3.2.3.2 Prepare source file for health facilities
        • 3.2.4 Set up employees & roles for testing or production
          • 3.2.3.1 Prepare source file for employees
          • 3.2.3.2 Configure role titles
        • 3.2.5 Set up application settings
          • 3.2.5.1 Configuring Metabase Dashboards
        • 3.2.6 Configure certificate templates
        • 3.2.7 Configure declaration forms
          • 3.2.7.1 Configuring an event form
        • 3.2.8 Seeding your local development environment database
          • 3.2.8.1 Clearing your local development environment database
        • 3.2.9 Countryconfig APIs explained
          • 3.2.9.1 Managing language content
      • 3.3 Set-up a server-hosted environment
        • 3.3.1 Provision your server nodes with SSH access
        • 3.3.2 Provision environment
        • 3.3.3 Provision a comms gateway
        • 3.3.4 Set up an SMTP server for OpenCRVS monitoring alerts
        • 3.3.5 Setup DNS A records
        • 3.3.6 Deploy (Automated & Manual)
        • 3.3.7 Seeding & clearing data on a server
        • 3.3.8 Automated & manual backup and manual restore
    • 4. Functional configuration
      • 4.1 Configure application settings
      • 4.2 Configure registration periods and fees
      • 4.3 Create new user roles
      • 4.4 Managing system users
    • 5. Testing
    • 6. Go-live
    • 7. Monitoring
      • 7.1 Application logs
      • 7.2 Infrastructure health
      • 7.3 Routine monitoring checklist
      • 7.4 Setting up alerts
      • 7.5 Managing a Docker Swarm
  • General
    • Contributing
    • Releases
      • v1.3.5: Release notes
      • v1.3.4: Release notes
      • v1.3.2: Release notes
      • v1.3.1: Release notes
      • v1.3.* to v1.3.* Migration notes
      • v1.3.0: Release notes
      • v1.2.* to v1.3.* Migration notes
        • v1.2 to v1.3: Form migration
      • v1.2.1: Release notes
      • Patch: Elasticsearch 7.10.2
      • v1.2.0: Release notes
      • v1.1.* to v1.2.* Migration notes
      • v.1.1.2: Release notes
      • v.1.1.1: Release notes
      • v1.1.0: Release notes
    • Interoperability roadmap
    • Product roadmap
Powered by GitBook
On this page
  1. General

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.

OpenCRVS interoperates out-the-box using the FHIR standard as JSON. The FHIR API is exposed via OpenHIM. The supported FHIR version is: STU3

OpenCRVS v1.0: June 2022:

a) Adopted the OpenHIE architectural framework by design and FHIR standard interoperability reference middleware OpenHIM - FHIR version STU3.

b) Integrated with DHIS2 to standardise event notifications from a hospital setting for civil registration using FHIR in Bangladesh pilot.

OpenCRVS v1.1: Sep 2022

a) Birth registration integration with MOSIP.

b) Death registration integration with MOSIP.

c) Release of OpenCRVS FHIR standard W3C standard WebSub webhooks for subscription.

OpenCRVS v1.2: Jan 2023

a) Release of the Elasticsearch Record Search API for use as part of a social protection interoperability collaboration the Digital Convergance Initiative.

b) Release of the OpenCRVS 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 E-Signet consent.

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

d) Core collaboration of the G2PConnect protocol initiated.

e) Integration with Secure Identity Alliance, OSIA standard Birth Use Case

f) Integration with OpenSPP social protection system, using QR code.

g) Integration with INGroupe National ID system.

OpenCRVS v1.4 - Planned release: Sep 2023:

a) W3C Verifiable Credential integration with MOSIP

b) Correct record integration with MOSIP

c) Revocation of a record integration with MOSIP

d) G2PConnect protocol integration v0.1

e) OpenCRVS civil registration related FHIR extensions published

OpenCRVS v1.5 - Planned release: Jan 2024:

a) G2PConnect protocol integration v1.0

b) Integration with the JeMPI Master Patient index v0.1

OpenCRVS v1.6 - Planned release: May 2024:

a) G2PConnect protocol integration v2.0

b) Integration with the JeMPI Master Patient index v1.0

Previousv1.1.0: Release notesNextProduct roadmap

Last updated 1 year ago