> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.6/technology.md).

# Technology

- [Architecture](https://documentation.opencrvs.org/v1.6/technology/architecture.md)
- [Performance tests](https://documentation.opencrvs.org/v1.6/technology/architecture/performance-tests.md): Overview of results from performance tests conducted on OpenCRVS
- [Standards](https://documentation.opencrvs.org/v1.6/technology/standards.md): Overview of how OpenCRVS uses best-practice technology standards
- [FHIR Documents](https://documentation.opencrvs.org/v1.6/technology/standards/fhir-documents.md)
- [Event Composition](https://documentation.opencrvs.org/v1.6/technology/standards/fhir-documents/event-composition.md)
- [Person](https://documentation.opencrvs.org/v1.6/technology/standards/fhir-documents/person.md)
- [Registration Task](https://documentation.opencrvs.org/v1.6/technology/standards/fhir-documents/registration-task.md)
- [Event Observations](https://documentation.opencrvs.org/v1.6/technology/standards/fhir-documents/event-observations.md)
- [Locations](https://documentation.opencrvs.org/v1.6/technology/standards/fhir-documents/locations.md)
- [Security](https://documentation.opencrvs.org/v1.6/technology/security.md)
- [Interoperability](https://documentation.opencrvs.org/v1.6/technology/interoperability.md): An introduction describing how OpenCRVS interoperates
- [Create a client](https://documentation.opencrvs.org/v1.6/technology/interoperability/create-a-client.md): How to create and manage access to OpenCRVS' interoperability functionality
- [Authenticate a client](https://documentation.opencrvs.org/v1.6/technology/interoperability/authenticate-a-client.md): Authenticating with your client details to retrieve an access token using OAuth 2.0
- [Event Notification clients](https://documentation.opencrvs.org/v1.6/technology/interoperability/event-notification-clients.md): Submitting full or partial event applications into OpenCRVS from an external service such as a health institution or public portal.
- [Record Search clients](https://documentation.opencrvs.org/v1.6/technology/interoperability/record-search-clients.md): Perform an advanced search of civil registration records from a trusted, external e-Gov service
- [Webhook clients](https://documentation.opencrvs.org/v1.6/technology/interoperability/webhook-clients.md): Business functionality and API endpoints available to a "Webhook" client.
- [National ID client](https://documentation.opencrvs.org/v1.6/technology/interoperability/national-id-client.md): Business functionality associated with a National ID client and instructions to setup a MOSIP enabled National ID integration.
- [FHIR Location REST API](https://documentation.opencrvs.org/v1.6/technology/interoperability/fhir-location-rest-api.md): Create, read, update or archive administrative areas, civil registration offices or health facilities using FHIR.
- [Other ways to interoperate](https://documentation.opencrvs.org/v1.6/technology/interoperability/other-ways-to-interoperate.md): Direct interoperability with OpenHIM


---

# 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://documentation.opencrvs.org/v1.6/technology.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.