> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow.md).

# Integration Patterns & Workflow

## Overview

This section provides detailed workflows for standard and exceptional integration scenarios between MOSIP and external systems. The documented flows serve as reference patterns that illustrate [core integration principles](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context/core-integration-principles.md) in action.

### Important Considerations

* **Patterns, Not Prescriptions**: The workflows documented here are illustrative examples that demonstrate integration principles. They are not exhaustive catalogs of all possible scenarios.
* **Context Matters**: Every country operates within unique legal frameworks, operational contexts, and cultural factors. Your implementation may require adaptations to meet local requirements.
* **Apply the Framework**: Use the [Core Integration Principles](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context/core-integration-principles.md) and risk assessment methodology as your guide when designing scenarios not explicitly covered here.

#### Integration Flows

* [Birth Registration & UIN Issuance](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/integration-flows/birth-registration-and-uin-issuance.md)
* [Death Registration & Identity Status Update](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/integration-flows/death-registration-and-identity-status-update.md)
* [Demographic Data Updates](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/integration-flows/demographic-data-updates.md)

#### Rare Scenarios

* [Fraudulent Birth Registrations - National ID Deactivation Request from CRVS](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/rare-scenarios/fraudulent-birth-registrations-national-id-deactivation-request-from-crvs.md)
* [Reactivation of Deactivated National ID](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/rare-scenarios/reactivation-of-deactivated-national-id.md)
* [Fraud Death Case - Reversal of the Death Flag](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/rare-scenarios/fraud-death-case-reversal-of-the-death-flag.md)

> **Note**: These are the currently supported scenarios. The [rare scenarios](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow/rare-scenarios.md) involve manual verification processes and are not fully automated. Additional use cases will be introduced as the integration evolves and expands based on country-specific requirements and feedback.

***

### Learn More

* [Core Integration Principles](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context/core-integration-principles.md)
* [Integration Boundaries, Limitations and Implications](/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-overview-and-context/integration-boundaries-and-real-world-implications.md)

***


---

# 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://docs.mosip.io/1.2.0/interoperability/integrations/mosip-crvs-integration/integration-patterns-and-workflow.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.