OpenCRVS
v1.4
v1.4
  • 👋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 HTTPS & Networking
        • 4.3.3 Create a Github environment
          • 4.3.3.1 Environment secrets and variables explained
        • 4.3.4 Provision environments
          • 4.3.4.1 Building, pushing & releasing your countryconfig code
        • 4.3.5 Deploy
    • 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.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.* 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
  • Application
  • Declaration forms
  • Certificate
  • User roles
  1. Product Specifications
  2. Admin functions

24. Config management

OpenCRVS is engineered for adaptability, allowing for configuration to comply with diverse country-specific laws and regulations. The different interfaces are described below on how the you can configure how the system looks and functions.

Some configuration is done in the back-end, such as uploading administrative data. For back-end tasks, explore 4.2 Set-up your own, local, country configuration for detailed step-by-step guidance.

Application

From the Application configuration screen general system settings can be set.

General:

  • Name: Sets the name of the application

  • Logo: Sets the logo used on the login screen and review screen

  • Login background: Choose from an image or colour for the login screens

  • Currency: Set the currency symbol used in performance and fee collection screens

  • Phone regex: Sets the phone number validation rules for phone number inputs

  • NID regex: Sets the national id rules for phone number inputs

  • Registration number format: Sets the format of registration numbers generated by the system on registration (developer)

Registration time periods:

OpenCRVS tracks when a registration occurred and compares this to the date of the vital event. This gives a view of the time that has elapsed known as the registration time periods. These time periods are used in performance management for users track registrations against, but also trigger fee collection procedures, if for instance a registration late.

Time periods:

  • Within legally specified (eg. within 30days of the event)

  • Delayed (Birth events only)

  • Late

Fees:

  • Within legally specified

  • Delayed

  • Late

To learn about application settings please refer to 3.3 Define your application settings

Declaration forms

The declaration form for each event (births, deaths, marriages) can be configured by a developer. Each form is split into pages also known as sections. On each page you can choose to use different input types (text, select, number, radio, checkbox, text area) to aid the user to complete the form.

To learn more please refer to 3.4 Designing event declaration forms

Certificate

Each vital event can have a paper certificate that is printed and issued to the informant. To create a certificate template a designer can create the desired design and export as an .svg for the National System Admin to upload in the certificate configuration screen.

Configuration options:

  • Create any layout

  • Add any logos and/or images

  • Select what registration data you want to show

  • Use different font

  • Add a QR code to verify the certificate

From the Certificate configuration screen, a National System Admin can preview and print the certificate so that can test if it is correctly populating registration data and printing correctly.

For detailed instructions on how to configure your own certificates please see: 3.5 Designing a certificate template 4.2.6 Configure certificate templates

User roles

OpenCRVS has system roles which reflect common actors involved in civil registration services around the world. The system roles have defined responsibilities and capabilities in the system.

On the User roles system configuration screen a National System Admin can map these system roles to custom user type names as required. For example a Field Agent who is responsible for creating declarations and sending them to Registration Offices can be mapped to a Healthcare Worker and Police Officer. For detailed instructions on how to map user roles please see: 3.2 Mapping offices and user types 5.3 Managing system users

Previous23. Content managementNextData functions

Last updated 1 year ago