> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.1-content.md).

# 5.1. Content

GeoPrism Registry is being used to simultaneously host, maintain, update and share **lists** as well as associated **hierarchies** and **spatial data** for the **geographic objects** core to development in general and public health in particular.

The following sections describe in more detail these different elements, as well as those associated with them (geographic features, geographic object types, data elements, classification tables).

Please refer to the latest Health GeoLab Collaborative [guidance](https://healthgeolab.net/DOCUMENTS/Guidance_Common_Geo-registry_Ve2.pdf) on the establishment of a common geo-registry for the simultaneous hosting, maintenance, update and sharing of lists as well as associated hierarchies and spatial data, for specific considerations to take into account when developing such content before uploading it in GeoPrism Registry (quality, unique identifier, master versus non-master list, etc.).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.1-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.