> 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/v1.7/product-specifications/core-functions.md). # Core functions Overview of core functions

Function	Description
Notify event	User or external system sends a vital event notification to an assigned office. The notification appears in the 'In Progress' workqueue for follow-up and completion.
Declare event	User completes declaration form in an office or roaming (mobile) and either sends for review or registers it
Validate event	User reviews submitted declaration form against supporting documents
Register event	User registers vital event
Print certificate	User prints certificate
Issue certificate	User issues a certificate
Search for a record	User searches and retrieves a vital event record
View record	User views a record
Correct record	User corrects a record, providing a reason for the correction
Verify record	User is able to verify the existence of a birth record and see relevant details
Archive record	User archives a record
Vital statistics export	User is able to view vital statistics data and download in required format

--- # 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/v1.7/product-specifications/core-functions.md?ask=&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.