> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v2.0/general/crvs-systems/quickstart.md).

# Understanding CRVS

### 1. Introduction

Before designing or implementing a CRVS system with OpenCRVS, implementers, Business Analysts, and Systems Integrators must develop a solid understanding of the **civil registration and vital statistics domain**. This includes understanding legal frameworks, administrative workflows, stakeholder responsibilities, data quality principles, and international standards.

A strong domain foundation ensures that system requirements align with country-specific policies, international best practices, and the operational realities of registration offices, health facilities, and statistical offices.

{% hint style="info" %}
**For implementers:** The resources below provide essential context for translating policy and legal requirements into functional specifications, user journeys, and system behaviours that can be reliably implemented and maintained.
{% endhint %}

***

### 2. Recommended learning resources

#### World Bank Group / Global CRVS Group – Self-Paced Online Course

A foundational course covering the principles, benefits, and design of CRVS systems. Free and available online.

**Best for:** New team members, Business Analysts, and project managers who need a comprehensive introduction to CRVS principles.

👉 [Take the course on the World Bank Open Learning Campus](https://www.worldbank.org/en/olc/course/34651)

***

#### UN Handbook on Civil Registration and Vital Statistics Systems

An exhaustive reference covering administrative arrangements, operational functions, quality assurance, interoperability, and digitisation of CRVS systems.

**Best for:** Deep dives into operational processes, data quality standards, and system management. Essential for Business Analysts writing functional specifications.

👉 [Download from the UN Stats website](https://unstats.un.org/unsd/demographic-social/Standards-and-Methods/files/Handbooks/crvs/crvs-mgt-E.pdf)

***

#### Regional CRVS strengthening initiatives

**APAI-CRVS: Africa Programme on Accelerated Improvement of CRVS**

The regional initiative guiding CRVS strengthening across Africa, with country assessments, frameworks, and advocacy materials.

👉 [Visit the APAI-CRVS website](https://apai-crvs.uneca.org/)

**Get Every One in the Picture – Asia–Pacific CRVS Platform**

A regional CRVS strengthening platform offering frameworks, assessments, advocacy materials, and eLearning resources tailored to the Asia–Pacific context.

👉 [Visit the Get in the Picture website](https://www.getinthepicture.org/)

***

#### CRVS Digitisation Guidebook

An online resource providing step-by-step guidance for countries to plan, analyse, design, and implement digitised systems and automated processes for CRVS.

**Best for:** Understanding digitisation strategies, technology assessments, and change management approaches.

👉 [Visit the CRVS Digitisation Guidebook](http://www.crvs-dgb.org/en/)

***

{% hint style="info" %}
**Next steps:** After reviewing these resources, proceed to the functional specification sections of this documentation to understand how OpenCRVS implements CRVS workflows, forms, certificates, and system integrations.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.opencrvs.org/v2.0/general/crvs-systems/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.