MOSIP Docs 1.2.0
GitHubCommunityTech BlogsWhat's NewChatBot
  • MOSIP
    • Overview
    • License
    • Principles
      • Inclusion
      • Privacy and Security
        • Security
        • Data Protection
        • Privacy
    • Technology
      • Architecture
      • Digital ID DPI Framework
      • Technology Stack
      • API
      • Sandbox Details
    • Standards & Specifications
      • MOSIP Standards
        • 169 - QR Code Specifications
        • 169 - QR Code Specifications 1.0.0
    • Inji
    • eSignet
  • ID Lifecycle Management
    • Identity Issuance
      • Pre-registration
        • Overview
          • Features
        • Develop
          • Developers Guide
          • UI Specifications
        • Test
          • Try It Out
          • End User Guide
          • Pre-registration Collab Guide
      • Registration Client
        • Overview
          • Features
        • Develop
          • Developers Guide
          • UI Specifications
        • Test
          • Try It Out
          • End User Guide
          • Registration Client Collab Guide
        • Deploy
          • Installation Guide
          • Operator Onboarding
          • Configuration Guide
          • Settings page
        • Telemetry from Registration Client
      • Android Registration Client
        • Overview
          • Features
        • Develop
          • Developer Guide
          • UI Specification
          • Technology Stack
        • Test
          • End User Guide
          • Collab Guide
        • Deploy
          • Configuration Guide
      • Registration Processor
        • Overview
          • Features
        • Develop
          • Registration Processor Developers Guide
        • Test
          • Credential Requestor Stage
          • Manual Adjudication and Verification
        • Deploy
          • Configurations Details
          • Deploy
      • ID Repository
        • Credential Request Generator Service Developers Guide
        • Identity Service Developers Guide
        • VID Service Developers Guide
        • .well-known
        • Custom Handle Implementation Guide
    • Identity Verification
      • ID Authentication Services
        • ID Authentication Demographic Data Normalization
        • ID Authentication Service Developers Guide
        • ID Authentication OTP Service Developer Guide
        • ID Authentication Internal Service Developers Guide
        • MOSIP Authentication SDK
      • ID Authentication
    • Identity Management
      • ID Schema
      • Identifiers
      • Resident Portal
        • Overview
          • Features
        • Develop
          • Developers Guide
          • UI Developers Guide
          • UI Specifications
          • Technology Stack
        • Test
          • Functional Overview
          • End User Guide
          • Collab Guide
        • Deploy
          • Deployment Guide
          • Configuration Guide
          • Configuring Resident OIDC Client
          • Browsers Supported
    • Support Systems
      • Administration
        • Develop
          • Admin Services Developers Guide
        • Test
          • Try it out
          • Admin Portal User Guide
          • Admin Portal Collab Guide
        • Masterdata Guide
      • Partner Management System
        • Partners
        • Overview
          • Features
        • Develop
          • Architecture
          • Technology Stack
          • Backend Developers Guide
          • UI Developers Guide
          • Build and Development Guide
          • New Language Support
          • Browsers Supported
        • Test
          • Try It Out
          • Partner Administrator
          • Policy Manager
          • Authentication Partner
          • Device Provider
          • FTM Chip Provider
          • PMS Collab Guide
        • Deploy
          • PMS Configuration Guide
          • API changes with PMS Revamp
        • PMS Legacy
          • Partner Management System
          • Partner Management Portal
          • Auth Partner
          • Device Provider
          • Foundational Trust Provider
          • Partner Management Services Developers Guide
      • Reporting
        • Anonymous Profiling Support
    • Supporting Components
      • Biometrics
        • ABIS
        • ABIS API
        • Biometric SDK
        • Biometric Devices
        • FTM
        • Biometric Specification
        • MDS Specification
        • CBEFF
        • Compliance Tool Kit
      • Commons
        • Commons Developers Guide
        • Audit Manager Developers Guide
        • OpenID-Bridge Developers Guide
        • ID Generator
      • Datashare
      • Keycloak
      • Persistence
        • Postgres DB
        • Object Store
      • Packet Manager
        • Registration Packet Structure
      • Quality Manager
        • Automation
          • API Test Rig Automation
          • DSL Test Rig Automation
          • UI Test Rig Automation
          • Automation Testing
        • Manual
    • Supporting Services
      • Mock Services
      • Key Manager
        • Keys
        • Hadware Security Module (HSM)
        • Key Manager Developers Guide
      • Module Configurations
      • WebSub
        • WebSub Developers Guide
  • Setup
    • Deployment
      • Getting Started
        • Helm Charts
        • Versioning
        • Wireguard
          • Wireguard Bastion Host
          • Wireguard Administrator's Guide
          • Wireguard Client Installation Guide
        • Production
          • Server Hardware Requirements
          • Production Hardening Guide
          • Administration Using Rancher
      • V3 installation
        • On-Prem Installation Guidelines
        • On-Prem without DNS Installation Guidelines
        • AWS Installation Guidelines
        • Testrig
        • MOSIP External Dependencies
        • MOSIP Modules Deployment
    • Implementations
      • Implementations
      • Reference Implementations
    • Upgrade
      • Adopting LTS 1.2.0
        • Upgrade Runbook
          • Deployment Architecture Upgrade
          • Platform Upgrade
          • Additional Information
            • Handling Duplicate Entries
            • Adapting Changes in Administration Roles
            • Identifying Applicant Type
            • Changes in Camel Route
            • Changes in Role Management based on Client IDs
            • Handling Case Insensitive Duplicated User Details
            • Managing Unequal Certificates
            • Update Identity Mapping file in Configuration
            • New Datashare Properties
            • Handling Non-Recoverable Packets
            • Partners' Certificate Expired
            • Handling Partner Organization Name Mismatch Issue
            • Pre-Registration UI Upgrade
            • Registration Client Upgrade
            • Guide to Reprocess Packets Manually
        • Documentation for 1.1.5
      • Java 21 Migration Guide
  • Interoperability
    • Integrations
      • MOSIP - CRVS
        • Scope
        • Approach
          • Technical Details
        • Existing Integrations
          • OpenCRVS
      • MOSIP e-Manas
      • Digital Signature
      • MOSIP Token Seeder
        • MTS Versions
          • Version 1.0.0
          • Version 1.0.1
          • Version 1.1.0 (WIP)
        • MTS Developer Guides
          • Developer Guide 1.0
          • Developer Guide 1.1
        • MTS Connector
        • OpenG2P-registry MTS Connector
      • MOSIP eSignet
        • ID Authentication
        • Partner Management
        • Configuring eSignet
      • Print Service Integration
        • Verified Credentials
  • Community
    • Contributions
    • Code Contributions
      • Code of Conduct
      • MOSIP Release Process
        • Go/No Go Release Checklist
      • MOSIP Branching Strategy
    • Community Calendars
    • Documentation Credits
  • Roadmap and Releases
    • Roadmap
      • Roadmap 2025
      • Roadmap 2024
      • Roadmap 2023
    • Releases
      • PMS Revamp Release 1.2.2.1 (Patch)
      • v1.2.1.0 - Registration Processor
        • Test Report
      • Android Registration Client v0.11.0
        • Test Report
      • API Test Commons Releases
        • v1.3.2
        • v1.3.1
        • v1.3.0
      • 1.2.1.0-beta.1 (Part 3)
        • Test Report
      • Partner Management System 1.2.2.0
        • Test Report
      • Resident Services v0.9.1
        • Test Report
      • 1.2.0.2 - Reg Processor & ID Repo
        • Test Report
      • 1.2.1.0-beta.1 (Part 2)
        • Enhancements and Bug Fixes
        • Test Report
      • 1.2.1.0-beta.1(Part 1)
      • Android Registration Client 0.11.0-beta.1
        • Test Report
      • Partner Management System 1.3.0-dp.1
        • Test Report
      • 1.2.2.0 (Mosip - Config)
      • Api Test Commons Releases
      • Android Registration Client v0.10.0
        • Test Report
      • Resident Services 0.9.0
        • Test Report
      • 1.2.1.0 (ID Authentication)
        • Functional Test Report
      • 1.2.0.2
        • Test Report
      • 1.2.0.1
        • Enhancements and Bug Fixes
        • Test Report
      • Android Registration Client 0.9.0
        • Test Report
      • 1.2.0.1-B4 (Beta)
        • Test Report
      • Android Registration Client DP1
      • Resident Services DP1
      • 1.2.0.1-B3 (Beta)
        • Test Report
      • 1.2.0.1-B2 (Beta)
      • 1.2.0.1-B1 (Beta)
        • Functional Test Report
        • Sonar Report
      • 1.2.0
        • Enhancements
        • Functional Test Report
        • Sonar Scan Report
        • Performance Test Report
        • Security Test Report
        • Feature Health Report
  • General
    • Glossary
    • Resources
    • MOSIP Support Policy
    • Collab Environment Guides
      • Use Cases
        • Loan Application
      • Generating Demo Credentials
    • MOSIP Documentation Style Guide
Powered by GitBook

Copyright © 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.

On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Interoperability
  2. Integrations

MOSIP - CRVS

Last updated 1 month ago

Was this helpful?

Introduction to MOSIP CRVS Integration

Imagine a world where a child's digital identity is created the moment they are born. Through each life milestone, from their first day of school to entering the workforce, this national digital ID ensures seamless access to essential services tailored to their evolving needs. Even at the end of life, the ID is securely managed to ensure that only the entitled beneficiaries receive the rightful government support. This careful management helps make sure that benefits are distributed fairly and accurately, contributing to the overall well-being of society.

Achieving this vision has proven to be a challenge, as civil registration systems often operate in isolation, rarely sharing data with other critical platforms such as digital identity systems. This lack of integration leads to fragmented data systems and inefficiencies in data collection, hindering efficient service delivery.

In an increasingly digital world, integrating Civil Registration and Vital Statistics (CRVS) systems with national digital identity platforms like MOSIP represents a foundational shift in how countries can manage identity and vital statistics. This synergy allows for the seamless management of an individual's identity across life events, starting from birth registration, through education and employment, to end-of-life verification.

Why Integration Matters

Civil registration systems record vital life events such as births, deaths, marriages, and divorces. Meanwhile, national ID systems provide legal and verifiable identities. When these systems operate in isolation, it leads to administrative inefficiencies, fragmented data, and challenges in service access.

Through integration with MOSIP (Modular Open Source Identity Platform), CRVS systems can enable:

  • Real-time updates between registration and ID issuance

  • Automated processes to reduce duplication

  • Improved service delivery with more accurate citizen records

  • Enhanced data-driven governance and policy-making

Vision and Impact

The combined capabilities of MOSIP and CRVS systems have the potential to demonstrate a transformative impact across countries. Together, they can provide a holistic framework for:

  • Recognition – Establishing a secure, legal identity from birth

  • Protection – Ensuring privacy, security, and proper authentication mechanisms

  • Provision – Enabling access to services through a Unique Identification Number (UIN)

This vision further aligns with global Sustainable Development Goals (SDGs), including the UN’s SDG Target 16.9: “Provide legal identity for all, including birth registration, by 2030.”

Key Objectives of the Integration

Objectives

The integration of MOSIP with CRVS systems is designed to achieve several key objectives aimed at enhancing the efficiency, security, and accuracy of national identity and civil registration systems. These objectives include:

  1. Streamlining Processes and Enhancing Information Exchange The integration will create a seamless flow of information between MOSIP and CRVS systems, reducing administrative burdens and enabling faster, more efficient processing of civil registration events.

  2. Establishing Secure and Reliable Data Verification Mechanisms A central goal of this integration is to establish robust verification protocols, ensuring that data exchanged between the systems is accurate, reliable, and trustworthy, thereby preventing errors and enhancing security.

  3. Issuance of Unique Identity Numbers Linked to Birth Certificates The integration will facilitate the issuance of unique identification numbers (UINs) linked directly to birth certificates, providing individuals with a verified, digital identity that is consistently updated as they undergo significant life events.

  4. Improving Accuracy in Identification and Reducing Data Duplication By linking civil registration events to the national identity system, the integration will eliminate the risk of duplicate records, ensuring that every individual has a single, verified identity across all government systems.

  5. Maintaining Accurate Records of Deceased Individuals One of the core aims of the integration is to ensure that the identity system is promptly updated with the status of deceased individuals, preventing identity fraud or the misuse of personal data for illicit purposes.

  6. Establishing and Maintaining Accurate Spousal and Marital Status Information The integration will enable accurate recording of spousal relationships by linking marriage registrations with national identity records. This ensures that marital status information is consistently updated and maintained, resulting in more reliable and up-to-date personal identity data for married individuals.

  7. Enhancing Data Quality, Integrity, and Reliability for Better Governance The integration will improve the accuracy, completeness, and timeliness of vital event records across systems, enhancing overall data quality and integrity. This reliable data foundation will support better governance by equipping authorities with accurate statistics for more informed, data-driven decision-making.

  8. Ensuring Strong Security and Privacy Protections The integration will adhere to stringent data protection and cybersecurity standards, ensuring that personal information is safeguarded throughout the data exchange process. Privacy-by-design principles will be embedded to prevent unauthorized access, misuse, or breaches, thereby building public trust and protecting individual rights.

Integration Architecture and Guidelines

The following is a list of guiding principles for this integration.

Guidelines

  1. Data Verification and Trust:

    1. The initiation of the request with the data will be from CRVS to MOSIP

    2. Data transmitted from CRVS to MOSIP will undergo thorough data/document verification and deduplication before any request is initiated for MOSIP to process.

    3. MOSIP will trust all information provided by CRVS and honor the received requests. MOSIP will ensure that the technical and logical validations are all in place for packet processing.

    4. The integration should define the mandatory attributes to be exchanged between the two systems. It is crucial to agree upon these attributes to ensure consistent and accurate data exchange.

  2. Data consistency:

    1. It is imperative to maintain consistency in data across both platforms, MOSIP and CRVS. This ensures that accurate and up-to-date data is shared between the systems.

  3. Fallback mechanism:

    1. CRVS should initiate the request by calling the create packet API if the failure occurs during creation, CRVS should be able to retry to create the packet.

    2. In the event of technical failures on the MOSIP side during packet processing, reprocessing of the packet should be in place to ensure that the packet is marked appropriately as rejected or approved.

  4. Proof of Authentication:

    1. For any request submitted to MOSIP, it is essential to include the biometric data of the informant or applicant, whenever feasible, to ensure the accurate verification of the individual initiating the request and confirm their legitimacy.

    2. For cases where biometric data is not collected by CRVS, it is recommended for CRVS to use eSignet for the applicant or introducer authentication. Post-authentication user info token should be shared with MOSIP for validation and auditing purposes.

  5. Identity Credential Sharing & Packet status

    1. The identity credential sharing and packet status updates are two separate MOSIP integration points for any CRVS.

    2. MOSIP will generate and share identity credentials for new registration cases via WebSub. Any partner configured according to the policy will receive these notifications automatically.

    3. By default, MOSIP recommends sharing the PSUT token as part of the identity credential returned to CRVS. However, the system also supports sharing UIN, VID, or the PSUT token, based on the country’s specific requirements.

    4. MOSIP will publish packet status updates to a separate WebSub. Any credential partner subscribed to this WebSub topic can filter and track specific packets based on their status.

  6. Multiple CRVS Systems:

    1. If a country deploys multiple CRVS systems, each system will be treated as a separate partner for MOSIP. This allows for independent management and integration with each CRVS system.

    2. Credentials generated/update messages from MOSIP will be sent to all the configured credential partners subscribed to the websub as per policy. It is the responsibility of the country and CRVS systems to manage the sharing of information across multiple CRVS systems

About the Platforms

Assumption: This approach assumes that the CRVS system is recognized as the authoritative source of vital event data and is legally authorized to issue official birth and death certificates in accordance with the laws of the country.

MOSIP is an open-source, modular identity platform designed for scalability, interoperability, and compliance with global standards. It allows countries to customize identity systems tailored to their governance needs. To learn more about MOSIP, click . Civil Registration and Vital Statistics (CRVS) systems are essential for documenting key life events such as births, deaths, marriages, and divorces. These systems provide individuals with legal recognition and play a vital role in ensuring access to rights and services. Additionally, CRVS systems generate important demographic data that supports effective policy-making, governance, and resource planning. In summary, this integration represents a significant stride in building resilient, citizen-centric digital infrastructure. By combining the strengths of CRVS and MOSIP, countries can ensure inclusive access to public services and rights, starting from birth and extending throughout every life milestone.

Refer here for details on the MOSIP-CRVS integration and .

Amongst the various CRVS systems, MOSIP has integrated with , a digital civil registration solution. To know more about this integration, click here. (Link to be updated)

here
scope
approach
OpenCRVS
Birth and Death Registration