Event Notification clients

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 birth or death applications into an OpenCRVS' office "In Progress" or "Ready For Review" workqueue. Usually these clients are Hospitals, but technically these clients could be any system and the "Health system" label on the workqueue tab could be content managed accordingly.

An Event Notification in the OpenCRVS In Progress view

When Event Notifications are received in OpenCRVS, they are audited accordingly as being received from one of your automated clients.

Record Audit view for an Event Notification

You can use our Postman collections to test Event Notification API functionality. Postman is a tool you can download to test API access before building your integrations.

Submitting an Event Notification

To submit an Event Notification, your client must first request an authorization token using your client_id and client_secret.

Event Notification Requests

With the token as an authorization header, the following request will submit a minimal birth declaration in FHIR. To learn more about our FHIR standard, read the standards section.

Parameters in handlebars must be substituted with specific data that requires further explanation below. Other data is given as an example, but you can refer to our standards to set the values correctly depending on the birth or death.

Refer to our Postman collections to see a payload for a full birth declaration, minimal and full death declaration. Pay attention to the parameters that are dynamically provided from the Postman "Environments" to understand where to configure your URLs and other variables listed below. You should use the FHIR Location API in tandem with the Event Notification API in order to find the required FHIR IDs for locations used in addresses, places of birth, office of registration etc.

Parameter	Description
token	An authorization token
officeId	This is an important parameter. It is a FHIR Location uuid for a Civil Registration Office that you wish this notification to arrive in the jurisdiction / workqueue of. You can retrieve these ids using our open Location API. Your offices are customised for your country needs in this step.
districtId	If you are submitting addresses, then this is an optional FHIR Location uuid for the locationLevel2, technically expressed as a "district". You can retrieve these ids using our open Location API. Your location levels are customised for your country needs in this step.
stateId	If you are submitting addresses, then this is an optional FHIR Location uuid for the locationLevel1, technically expressed as a "state". You can retrieve these ids using our open Location API. Your location levels are customised for your country needs in this step.
facilityId	A FHIR Location id for a facility that is already in the OpenCRVS database to track places of births or deaths in health institutions. You can retrieve these ids using our open Location API. Your health facilities are customised for your country needs in this step.
countryCode	The Alpha-3 country code for the address. E.G. UGD for Uganda, FAR for our fictional country Farajaland.

Event Notification Response

If the notification has been successfully processed by OpenCRVS, you will receive a 200 OK response and a full FHIR Composition payload back.

If the request fails, you will receive a 500 Error and you must check the payload you are sending for errors. No error codes or explanations currently exist. We welcome pull requests to improve the developer experience here.