OpenCRVS
v1.7
v1.7
  • 👋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
    • User roles & scopes
      • 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 roles
      • Declaration forms
      • Certified Copies 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 certified copy
    • 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 employee users, and scopes, for testing or production
          • 4.2.3.1 Prepare source file for employees
          • 4.2.3.2 Configure roles and scopes
        • 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. Quality assurance testing
    • 6. Go-live
      • 6.1 Pre-Deployment Checklist
    • 7. Operational Support
    • 8. Monitoring
      • 8.1 Application logs
      • 8.2 Infrastructure health
      • 8.3 Routine monitoring checklist
      • 8.4 Setting up alerts
      • 8.5 Managing a Docker Swarm
  • General
    • Community
    • Contributing
    • Migration notes
    • Releases and upgrades
    • Release notes
    • Product roadmap
Powered by GitBook
On this page
  • Configuration options:
  • Pre-condition
  • Triggers
  • Standard flow
  • Post conditions
  • Variations/Exceptions
  1. Product Specifications
  2. Core functions

5. Print certificate

A vital event certificate is a critical legal document, proving the occurrence and pertinent details of the vital event. A birth certificate is a child's first right and proof of legal identity.

OpenCRVS provides an issuance process that checks the collector's ID, provides for the collection of payment and printing of a paper certificate either issuance for a customer in-person or in advance.

Configuration options:

  • Customise any number of certified copy templates

  • Enable/disable printing off in advance of issuance

  • Set certification fees for printing within legally specified time, delayed and late

Pre-condition

A record is in the Ready for print workqueue with the status ‘Registered’

Triggers

A user with thescope:record.registration-print&issue-certified-copies assigns and downloads the record in the Ready to print workqueue

Standard flow

  1. User navigates to Ready for Print workqueue

  2. User assigns themselves to the record

  3. Record is downloaded and is now available to be printed and issued offline

  4. User clicks “Print”

  5. User selects the certified copy template type

  6. User selects who is collecting the certified copy

    1. For a birth record this could be the Mother, Father or Informant

    2. If Someone else is collecting the certificate. Then the user captures their details.

  7. User checks the collectors ID against the details captured in the record

  8. User confirms the collectors proof of ID match

    1. If they don’t the user is warned that by proceed, they will be responsible for issuing a certificate without the necessary proof of ID from the collector

  9. User is prompted to collect payment if fess are required (based on system configuration)

  10. User reviews the certificate preview

  11. User confirms certificate details are correct and clicks “Print”

  12. A new tab opens with the certificate as a pdf for the user to print

  13. User is navigated back to Ready to Print workqueue

  14. Record is sent to the Outbox for processing

  15. Once processed the record status is updated to ‘Issued’

Post conditions

  • Record is removed from all workqueues but can be search for using tracking id, reg no. etc.

  • Record audit is updated to show that the record has been ‘Certified’ and ‘Issued’

Variations/Exceptions

A user can choose to print in advance of issuance at step 5 in the flow above. This allows them to print the certificate in order for it to be collected and issued at a future date.

Print in advance flow:

  1. User selects the type of certified copy template

  2. User select print in advance of issuance

  3. User reviews the certificate preview

  4. User confirms certificate details are correct and clicks “Print”

  5. A new tab opens with the certificate as a pdf for the user to print

  6. User is navigated back to Ready to print workqueue

  7. Record is sent to the Outbox for processing

  8. Once processed the record status is updated to ‘Certified’

  9. Record is sent to the Ready to issue workqueue

  10. Record audit is updated to show that the record has been ‘Certified’

Previous4. Register eventNext6. Issue certificate

Last updated 2 months ago