> 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.md).

# CRVS Systems

Successful OpenCRVS implementations begin with a strong understanding of the civil registration domain—not the software.

This section introduces the principles, terminology, and operating models that underpin effective Civil Registration and Vital Statistics (CRVS) systems. It explains both **what a well-functioning CRVS system looks like** and **why digital technology alone is not enough** to achieve better registration outcomes.

Whether you are a Business Analyst, Systems Integrator, Solution Architect, or Project Manager, these pages will help you build the domain knowledge needed to translate legislation, policy, and operational processes into successful OpenCRVS implementations.

In this section you will learn:

* [**Understanding CRVS**](/v2.0/general/crvs-systems/quickstart.md) – the fundamentals of civil registration, key concepts, international standards, and recommended learning resources.
* [**Effective Digital CRVS Systems**](/v2.0/general/crvs-systems/publish-your-docs.md) – the organisational, legal, operational, and governance foundations required for sustainable digital transformation.

A solid understanding of these concepts will make the configuration, implementation, and long-term support of OpenCRVS significantly more effective.


---

# 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.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.