> For the complete documentation index, see [llms.txt](https://divoc.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://divoc.digit.org/digital-infrastructure-for-vaccination-open-credentialing/what-divoc-is-and-what-its-not.md).

# What DIVOC is and what it's not

This document will tell you what DIVOC can and cannot do. For example, do not expect DIVOC to correct data fraud or mistakes at the source, or store medical history with high data-storage requirements.

| What DIVOC can do                                                                                | What DIVOC is not meant for                                                                                                              |
| ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Holds information on individual events or claims.                                                | It is not meant to store historical data (for example, a person’s medical history). The size limitation is 1 KB.                         |
| It is tamper-proof, and hence, can ease access to welfare funds linked to identity and a claim.  | Cannot expect it to rectify data errors at the source.                                                                                   |
| The output can be hybrid (PDF plus QR code).                                                     | Not a good idea if the expected verification to issuance ratio is low.                                                                   |
| Modular architecture can support more health credentialing other than COVID-19.                  | Not suitable if there is no purpose on the demand side.                                                                                  |
| DIVOC supports multi-lingual use and multi-distribution methods (such as paper, and smartphone). | Not the best option if the issuer and verifier are in the same network (in such cases, we recommend using simpler, and cheaper options). |

[![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*


---

# 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://divoc.digit.org/digital-infrastructure-for-vaccination-open-credentialing/what-divoc-is-and-what-its-not.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.