> 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/v2.0/technical/guides/configuration/integrations/integration-health-notifications-self-service-portal.md).
# Integration: Health notifications / Self-service portal
Submitting full or partial event applications into OpenCRVS from an external service such as a health institution or public portal.
An **Event Notification client** can submit full or partial events to an OpenCRVS office.
When Event Notifications are received in OpenCRVS, they receive the status "Notified", are audited and logged as being received from an automated client, and appear within the Notifications workqueue.
#### Submitting an Event Notification
With an authorised token, first [create an event](https://documentation.opencrvs.org/technical/apis/core-apis/events#post-events).
{% hint style="info" %}
This request will return a response containing the event ID in the `id` field. You must use this `eventId` in the subsequent request.
{% endhint %}
#### Event Notification Requests
Once the event is creaeted, you can submit the [notification](https://documentation.opencrvs.org/technical/apis/core-apis/events#post-events-eventid-notify).
#### Example API integration: DHIS2 Annual Conference 2026
During a demonstration at the [DHIS2](https://dhis2.org/) Annual Conference 2026, [OpenFN](https://www.openfn.org/) ran a cron job to monitor new "Tracked Entities" in DHIS2 every 24 hours, then transform the entities into an OpenCRVS Event Notification payload.
The demonstration used hardcoded CRVS\_OFFICE and HEALTH\_FACILITY ids. These can be dynamically retrieved via the OpenCRVS [Location](/v2.0/technical/apis/core-apis/locations.md) API.
This [repository](https://github.com/opencrvs/event-notification-integration) contains example code to submit the notification to OpenCRVS.
---
# 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/v2.0/technical/guides/configuration/integrations/integration-health-notifications-self-service-portal.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.
