> For the complete documentation index, see [llms.txt](https://jembi.gitbook.io/openhim-platform/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/openhim-platform/packages/fhir-datastore-hapi-fhir/local-development.md).

# Local Development

## Instant OpenHIE FHIR Data Store Component

This component consists of two services:

* Postgres
* HAPI FHIR Server - [HAPI FHIR](https://hapifhir.io/)

### Accessing the services

#### HAPI FHIR

This service is accessible for testing via:

[http://127.0.0.1:3447](http://{BROAD_CAST_IP}:3447)

In a publicly accessible deployment this port should not be exposed. The OpenHIM should be used to access HAPI-FHIR.

### Testing the HAPI FHIR Component

For testing this component we will be making use of `curl` for sending our request, but any client could be used to achieve the same result.

Execute the command below

```bash
curl http://127.0.0.1:3447/fhir/Patient
```


---

# 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/openhim-platform/packages/fhir-datastore-hapi-fhir/local-development.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.