OpenCRVS
v1.5
v1.5
  • 👋Welcome!
  • CRVS Systems
    • Understanding CRVS
    • Effective digital CRVS systems
    • OpenCRVS within a government systems architecture
    • OpenCRVS Value Proposition
  • 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
      • 6. Issue certificate
      • 7. Search for a record
      • 8. View record
      • 9. Correct record
      • 10. Verify record
      • 11. Archive record
      • 12. Vital statistics export
    • Support functions
      • 13. Login
      • 14. Audit
      • 15. Deduplication
      • 16. Performance management
      • 17. Payment
      • 18. Learning
      • 19. User support
      • 20. User onboarding
    • Admin functions
      • 21. User management
      • 22. Comms management
      • 23. Content management
      • 24. Config management
    • Data functions
      • 25. Legacy data import
      • 26. 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
      • Application settings
      • User / role mapping
      • Declaration forms
      • Certificate templates
    • Business process flows in Farajaland
  • Setup
    • 1. Planning an OpenCRVS Implementation
    • 2. Establish project and team
    • 3. Gather requirements
      • 3.1 Mapping business processes
      • 3.2 Mapping offices and user types
      • 3.3 Define your application settings
      • 3.4 Designing event declaration forms
      • 3.5 Designing a certificate template
    • 4. Installation
      • 4.1 Set-up a local development environment
        • 4.1.1 Install the required dependencies
        • 4.1.2 Install OpenCRVS locally
        • 4.1.3 Starting and stopping OpenCRVS
        • 4.1.4 Log in to OpenCRVS locally
        • 4.1.5 Tooling
          • 4.1.5.1 WSL Support
      • 4.2 Set-up your own, local, country configuration
        • 4.2.1 Fork your own country configuration repository
        • 4.2.2 Set up administrative address divisions
          • 4.2.2.1 Prepare source file for administrative structure
          • 4.2.2.2 Prepare source file for statistics
        • 4.2.3 Set up CR offices and Health facilities
          • 4.2.3.1 Prepare source file for CRVS Office facilities
          • 4.2.3.2 Prepare source file for health facilities
        • 4.2.4 Set up employees & roles for testing or production
          • 4.2.3.1 Prepare source file for employees
          • 4.2.3.2 Configure role titles
        • 4.2.5 Set up application settings
          • 4.2.5.1 Managing language content
            • 4.2.5.1.1 Informant and staff notifications
          • 4.2.5.2 Configuring Metabase Dashboards
        • 4.2.6 Configure certificate templates
        • 4.2.7 Configure declaration forms
          • 4.2.7.1 Configuring an event form
        • 4.2.8 Seeding & clearing your local databases
        • 4.2.9 Countryconfig API endpoints explained
      • 4.3 Set-up a server-hosted environment
        • 4.3.1 Verify servers & create a "provision" user
        • 4.3.2 TLS / SSL & DNS
          • 4.3.2.1 LetsEncrypt https challenge in development environments
          • 4.3.2.2 LetsEncrypt DNS challenge in production
          • 4.3.2.3 Static TLS certificates
        • 4.3.3 Configure inventory files
        • 4.3.4 Create a Github environment
          • 4.3.4.1 Environment secrets and variables explained
          • 4.3.4.2 VPN Recipes
        • 4.3.5 Provisioning servers
          • 4.3.5.1 SSH access
          • 4.3.5.2 Building, pushing & releasing your countryconfig code
          • 4.3.5.3 Ansible tasks when provisioning
        • 4.3.6 Deploy
          • 4.3.6.1 Running a deployment
          • 4.3.6.2 Seeding a server environment
          • 4.3.6.3 Login to an OpenCRVS server
          • 4.3.6.5 Resetting a server environment
        • 4.3.7 Backup & Restore
          • 4.3.7.1 Restoring a backup
          • 4.3.7.2 Off-boarding from OpenCRVS
    • 5. Functional configuration
      • 5.1 Configure application settings
      • 5.2 Configure registration periods and fees
      • 5.3 Managing system users
    • 6. Quality assurance testing
    • 7. Go-live
      • 7.1 Pre-Deployment Checklist
    • 8. Operational Support
    • 9. Monitoring
      • 9.1 Application logs
      • 9.2 Infrastructure health
      • 9.3 Routine monitoring checklist
      • 9.4 Setting up alerts
      • 9.5 Managing a Docker Swarm
  • General
    • Community
    • Contributing
    • Releases
      • v1.5.1: Release notes
      • v1.5.0: Release notes
      • v1.4.1: Release notes
      • v1.4.0 to v1.4.1 Migration notes
      • v1.4.0 Release notes
      • v1.3.* to v1.4.* Migration notes
      • v1.3.5: Release notes
      • v1.3.4: Release notes
      • v1.3.3: Release notes
      • v1.3.1: Release notes
      • v1.3.0: Release notes
      • v1.2.1: Release notes
      • Patch: Elasticsearch 7.10.2
      • v1.2.0: Release notes
      • v.1.1.2: Release notes
      • v.1.1.1: Release notes
      • v1.1.0: Release notes
    • Roadmap
Powered by GitBook
On this page
  • System Architectures
  • OpenCRVS and Digital Public Infrastructure
  1. CRVS Systems

OpenCRVS within a government systems architecture

How to think about the use of OpenCRVS as an interoperable system within a government's digital landscape

PreviousEffective digital CRVS systemsNextOpenCRVS Value Proposition

System Architectures

OpenCRVS has been designed to be interoperable with other systems so that it can receive and share data in an efficient and secure way. You can find more detailed technical information in the section on . It is important to consider how OpenCRVS will fit within the current digital landscape so that the benefits from interoperability can be fully realised.

In the diagram below you can see a generic view of potential integration points for OpenCRVS with other systems.

Interoperability within the eGov ecosystem

OpenCRVS and Digital Public Infrastructure

At OpenCRVS we are reimagining the way that civil registration systems work. We see the registration of life events as a foundational component of DPI, contributing to inclusive and equitable service delivery in the public and private sectors. The landscape is changing for digital civil registration systems as part of DPI and we must be aware of the key architectural principles which must be upheld to achieve maximum societal value.

The civil registration system plays a crucial role in providing a foundational and verifiable identity for individuals. In fact, you can’t get any more foundational than the system that recognises the very existence of people in a country, hence a well architected civil registration system is a true DPI:

  • Foundational Identity: The civil registration system forms the basis for creating unique digital identities for life. Birth registration for example triggers the creation of a unique identifier within the ID system, providing key biographical data such as name and date of birth.

  • Digitally signed certificates: The creation of verifiable credentials can be an output of the registration process, so that individuals are able to prove who they are to public and private institutions, without needing to request certified copies.

  • Enable access to government services: Civil registration provides the legal and trusted source of life events data and represents the universal data set for the provision of public services, such as social services, healthcare, education, and voting. In simple terms the civil registry answers important questions like:

    • Which families are entitled to a welfare grant (social protection)?

    • Who should be coming to school this year (education)?

    • Which children need to get vaccinated (healthcare)?

  • Population Statistics and Planning: Civil registration provides a critical source of data for demographic analysis, population statistics, and future planning. Governments can use this data to make informed decisions about resource allocation, infrastructure development, and social policies.

OpenCRVS has the potential to be a true DPI and to do so means ensuring the following to unlock its full potential:

  • Interoperability - Open standards and specifications are required to share data in an efficient way and prevent fragmentation and functional silos.

  • Security and privacy by design - Consent management protocols are required to allow safe sharing of personal data across systems and enforce data privacy. With civil registration data in a digital format the consent management process means that data subjects can choose to share their personal data on demand.

  • Modularity - Maintaining civil registration components which are loosely coupled is valuable within a DPI context. Implementers can choose to use OpenCRVS as a fully fledged digital civil registration system or they can leverage modules (e.g. data validation, certificate printing) to incorporate them into their own solutions using open APIs.

Further examples of potential integration points are available , including interoperability with other DPGs like MOSIP and OpenSPP.

Similar to the way that physical infrastructure like railways and roads drives economic development and innovation, Digital Public Infrastructure (DPI) provides the open technology standards and systems required to catalyse and enable countries to safely and efficiently deliver economic opportunities and social services in the digital world. We recommend the website for further guidance, definitions and practical resources on this important topic.

here
Centre for DPI
interoperability
OpenCRVS and DPI