> 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.md). # FHIR Datastore HAPI FHIR A FHIR compliant server for the platform. The HAPI FHIR service will be used for two mandatory functionalities: * A validator of FHIR messages * A storage of FHIR message ### A validator Incoming messages from an EMR or Postman bundles are not always well structured and it may be missing required elements or be malformed. HAPI FHIR will use a FHIR IG to validate these messages. It will reject any invalid resources and it will return errors according to the IG. HAPI FHIR is the first check to make sure the data injected in the rest of the system conforms to the requirements. ### A storage Backed by a PostgreSQL database, all the validated incoming messages will be stored. This will allow HAPI FHIR to check for correct links and references between the resources, as well as another storage for backups in case the data is lost. --- # 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://jembi.gitbook.io/openhim-platform/packages/fhir-datastore-hapi-fhir.md?ask=&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.