> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/dpi-for-education/education-data.md).

# Education Data

Education Data treats education information as shared, standards-based infrastructure — the sector-specific data foundation that education analytics and downstream services depend on.

Education Data treats education information as shared infrastructure rather than as data locked inside individual school or ministry applications. It defines a coherent, standards-based education data layer: how the education system is modeled, how education data is described, reconciled into a trustworthy view, accessed through APIs, and prepared for analysis — decoupled from any single application or vendor. Rather than duplicating capabilities other Building Blocks already provide, it integrates with them, defining only the parts of the stack that are specific to education data. The Education Data Building Block provides a shared, standards-based data foundation for the education sector, defining how data is modelled, reconciled, accessed and exchanged. Reusable capabilities such as the Analytics Building Block can then operate on that trusted, analysis-ready data.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Explore the Analytics Building Block</strong></td><td>The Analytics Building Block turns raw government data into dashboards, scores and decision triggers — a capability that can be reused across sectors and data sources, provided the data underneath it is trustworthy and well-structured. In this example, Education Data supplies that foundation for the education sector: ingestion, reconciliation, registries and APIs that leave education data analysis-ready, and a concrete sector use case for applying the Analytics Building Block. This can lead to many use cases, such as a minister of education tracking at-risk students and attendance patterns.</td><td><a href="https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics-building-block">https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics-building-block</a></td></tr><tr><td><strong>Explore the Education Data Blueprint</strong></td><td>Analytics is reusable, but the data layer underneath it is sector-specific. The Education Data Blueprint is where that education-specific layer — the data model, entities and relationships, registries and APIs, reconciliation and integration patterns — can be explored in practice.</td><td><a href="/experience-digital-transformation/dpi-for-education/education-data/education-data-blueprint.md">Education Data Blueprint</a></td></tr></tbody></table>

<details>

<summary>Technical files and supporting material</summary>

These files support the underlying model and interactive blueprint. They are provided for technical users who want to inspect the source structures, schemas and supporting artefacts directly.

**Diagram source**

* [mermaid-overview.mmd](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2FiHDVaMzxQoayuzTNKwfI%2Fdata-mermaid-overview.mmd?alt=media) — the main record types, required and recommended fields only
* [mermaid-person.mmd](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2Fs11dSe69D6r3IvNZGEgl%2Fdata-mermaid-person.mmd?alt=media) — the learner/person register, all fields
* [mermaid-organisation.mmd](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2FYS1Y068VxRsCJvyFb7l6%2Fdata-mermaid-organisation.mmd?alt=media) — the organisation register, all fields
* [mermaid-record.mmd](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2FLzekSxFsdDDTcUFkdZw8%2Fdata-mermaid-record.mmd?alt=media) — the enrolment/record register, all fields
* [mermaid-reference.mmd](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2FK48ncOCh37vUaQP1Dwlz%2Fdata-mermaid-reference.mmd?alt=media) — the programme/reference register, all fields
* [README.md](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2FNjBfmsznO0Nhrtg2SkT0%2Fdata-README.md?alt=media) — how to read the diagrams above

**Sample records**

* [aisha-otieno-repeats-year-with-support.json](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2F6LSAxL0UpofTzvUipYRs%2Fdata-aisha-otieno-repeats-year-with-support.json?alt=media) — a fictional learner repeating a year with recorded support measures
* [organisation-register-sample.json](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2F4I0VUFQyhXOniy13EzRM%2Fdata-organisation-register-sample.json?alt=media) — worked school and provider organisation records
* [reference-data-sample.json](https://2922521737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoIuaYnEclr8uQFObkak8%2Fuploads%2FAcPQVkZDEsohJbkvRNbL%2Fdata-reference-data-sample.json?alt=media) — a worked grading scheme and programme reference record

All sample records use fictional learners, schools and organisations.

</details>


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/dpi-for-education/education-data.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.
