> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/wip-integrated-beneficiary-registry-v1.0.0/ibr/1.-crvs/data/code-directory/cd.ibr.01-enrolment_status.md).

# CD.IBR.01 enrolment\_status

Beneficiary's status with a specific programme:

<table><thead><tr><th width="148.5">Code Number</th><th width="160">Value </th><th>Explanation</th></tr></thead><tbody><tr><td>1</td><td>Active</td><td>The beneficiary is currently receiving benefits.</td></tr><tr><td>2</td><td>Deceased</td><td>The beneficiary is deceased.</td></tr><tr><td>3</td><td>Graduated</td><td>The beneficiary has met the criteria to graduate from the programme.</td></tr><tr><td>4</td><td>Suspended</td><td>The beneficiary has been suspended from the programme.</td></tr><tr><td>5</td><td>Inactive</td><td>The beneficiary is temporarily not receiving benefits, but has not been formally suspended or exited the programme. This could be due to administrative issues, temporary ineligibility, or the beneficiary's personal request.</td></tr><tr><td>6</td><td>Reinstated</td><td>The beneficiary was previously suspended or exited, but has been reinstated in the programme, typically after meeting certain conditions or upon resolution of the issues that led to their suspension or exit.</td></tr><tr><td>7</td><td>Awaiting Renewal</td><td>The beneficiary's enrolment period is nearing its end, and they are in the process of renewal, subject to reassessment and continued eligibility.</td></tr></tbody></table>

### JSON-LD File on GitHub

{% embed url="<https://schema.spdci.org/extensions/ibr/v1/code/EnrollmentStatusEnum.jsonld>" %}


---

# 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://standards.spdci.org/standards/dci-standards/wip-integrated-beneficiary-registry-v1.0.0/ibr/1.-crvs/data/code-directory/cd.ibr.01-enrolment_status.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.