# Page Not Found

The URL `files/-MdXqvpJkWYJwVxndxcu` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Architecture](https://guides.ohie.org/arch-spec/architecture-specification/overview-of-the-architecture.md)
- [OpenHIE Terminology Service (TS)](https://guides.ohie.org/arch-spec/openhie-component-specifications-1/openhie-terminology-service-ts.md)
- [Expand Value Set](https://guides.ohie.org/arch-spec/introduction/terminology-service-workflow/expand-value-set.md)
- [OpenHIE Shared Health Record (SHR)](https://guides.ohie.org/arch-spec/openhie-component-specifications-1/openhie-shared-health-record-shr.md)
- [OpenHIE Interoperability Layer (IOL)](https://guides.ohie.org/arch-spec/openhie-component-specifications-1/openhie-interoperability-layer-iol.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://guides.ohie.org/arch-spec/architecture-specification/overview-of-the-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://guides.ohie.org/arch-spec/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://guides.ohie.org/arch-spec/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/arch-spec/architecture-specification/overview-of-the-architecture.md`).

You may also use `Accept: text/markdown` header for content negotiation.