> 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/v1.9/product-specifications/core-functions/1.-notify-event.md). # 1. Notify event User or external system sends a vital event notification to an assigned office. The notification appears in the Notification workqueue for follow-up and completion. A vital event notification involves the capture of a minimal set of data related to the occurrence of a vital event and transmission of this to the civil registration authority. In OpenCRVS a notification can be sent by a Field Agent by submitting a partially complete declaration, or it can be submitted from a digital health system e.g. DHIS2, both of which can then found in the Notification workqueue for follow-up and action. ### **Configuration** * Add Health System integration ### **Pre-condition** * \- ### **Triggers** * A user with `scope:record.notify[event=event]` is completing a declaration and has not completed all mandatory questions * A health system sends a birth notification ### **Flow (Field Agent)** 1. User starts or opens an incomplete declaration 2. User clicks “Send incomplete” 3. Incomplete declaration is sent to the Outbox for processing 4. Once processed the declaration will show in the Notifications workqueue ### **Flow (Health System)** 1. Health system user enters birth details 2. Health system sends notification to assigned office 3. Notification will show in the Notifications workqueue ### **Post conditions** * Informant receives sms notification with tracking ID if “Notified” {% embed url="" %} --- # 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/v1.9/product-specifications/core-functions/1.-notify-event.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.