> For the complete documentation index, see [llms.txt](https://jembi.gitbook.io/instant-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jembi.gitbook.io/instant-v2/vision.md).

# Vision

The Instant OpenHIE project aims to **reduce the costs and skills** required for software developers to deploy applications conforming to an OpenHIE architecture. This will enable quicker initial solution testing, demonstrations. It will also serve as a starting point for faster production implementation and customisation.

Instant OpenHIE is a simple way for semi-technical persons to install and see a complex system working against a real-world use case. It will illustrate how interoperability can work to solve health challenges. It will also show how a national interoperability architecture could be created with open-source software and standards.

Instant OpenHIE aim to provide a simple, portable way to deploy health information exchange systems to facilitate:

1. **Demonstrable reference products** - those that align with the OpenHIE Community's vision for low resource contexts
2. **Rapid software development** of mediators and point-of-service systems by making it possible to launch several applications easily so the developer can focus on their task
3. **Reproducible, version-controlled infrastructure** for user-contributed tests of the OpenHIE Architecture profiles, workflows, and use cases.
4. **Production-ready** containers and orchestratable components that are deployable in any context.
5. **Extensibility** so that anyone may create Instant OpenHIE packages and plug them into the existing Instant OpenHIE functionality.


---

# 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://jembi.gitbook.io/instant-v2/vision.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.