> 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/geoprism-registry-key-components/5.2-content-related-capacities-of-geoprism-registry/5.2-content-related-capacities-of-geoprism-registry-1.md).

# 5.2.2. Unique identifier

Critical to data interoperability is the ability to uniquely, and therefore unequivocally, identify each of the geographic objects in GeoPrism Registry and ensure that this unique identifier is used across information systems. Therefore, it may be beneficial to use geography as a neutral platform for the integration of information and data coming from different sources.

While the selection of the appropriate coding scheme associated with each type of geographic object is not a functionality of the platform, GeoPrism Registry has the capacity to capture and maintain such a scheme.

The choice of an appropriate coding scheme to be associated with each type of geographic object is therefore critical, as modifying the scheme once implemented in different systems can not only be costly but also have a significant impact on data compatibility as well as on the trust in the common geo-registry's content.

Please refer to [Ebener (2022)](https://healthgeolab.net/DOCUMENTS/Guidance_Common_Geo-registry_Ve2.pdf), [World Health Organization (2019)](https://www.who.int/publications-detail-redirect/9789241516495) and [Liu *et al.* (2021)](https://www.unicef.org/documents/implementation-support-guide-development-national-georeferenced-community-health-worker) for more guidance on the choice of an appropriate coding scheme.


---

# 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/geoprism-registry-key-components/5.2-content-related-capacities-of-geoprism-registry/5.2-content-related-capacities-of-geoprism-registry-1.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.