MOSIP Integration v2

[jpye-finch]

Enables (business requirements):


• Ability for the system user to authenticate the identity of a citizen during the declaration process (multiple methods dependent on the context)
• Pre-population of the form with validated citizen data from MOSIP
• Creation of a UIN in MOSIP for births registered in OpenCRVS
• Issuance of a VID from MOSIP which is shared with OpenCRVS
• Ability to add logic to determine whether the UIN should be created based form data (e.g. in declaration draft) - includes corrections where the UIN should not have been created
• Deactivation of a UIN in MOSIP for associated deaths registered in OpenCRVS
• Update of biographic details of an individual held in MOSIP based on birth record corrections in OpenCRVS
• Deactivation of a UIN in MOSIP when a birth registration is revoked in OpenCRVS
• Re-activation of a UIN in MOSIP when a death registration is revoked in OpenCRVS

Assumptions:


• Offline users by default
• All authentication done as declaration being processed (avoids real-time and on processing approaches)
• OpenCRVS is source of truth at birth / death.
• Interfaces could be configurable for a standard for use by other ID systems
• Authentication component can be used when declaring any vital event.
• (Could this be the unique key for establishing person-centricity?) - yes :-)
• Manual entry of data must be supported (e.g. when no ID). ID integration configured in the form configuration and application settings.
• If data edited after successful ID authentication, then authentication is void
• Options available for both online / offline mode
• Data fields to be returned from MOSIP on successful authentication are configurable and all mandatory
• Consent to use MOSIP data when authenticated is assumed / requested explicitly in form
• There are no optional fields available from MOSIP on successful authentication
• MOSIP processing is asynchronous --> while processing record moves to a status “waiting validation” and is visible in workqueue
• If MOSIP processing is unsuccessful, OpenCRVS processing does not continue (e.g. birth is not registered - birth is either rejected or waiting validation depending on reqs t.b.c)
• Interface is one directional: OpenCRVS creates /deactivates UIN. ID enrolment does not create a birth record.
• Business processes required to handle cases where person already has an ID before registering birth -> otherwise UIN created

[prinzab]

7987 Uganda requirements

(1) MOSIP integration

As a user, I want NSIS-CRS to integrate with MOSIP to:

• Authenticate a NIN for a parent or informant and auto-populate the declaration form with their details
• Create a NIN for a child if at least one parent is Ugandan
• Deactivate a NIN when a person is registered as deceased
• Revoke a NIN if a child’s registration is canceled or revoked
• Reinstate a NIN if a deceased person’s registration is reinstated

So that NIN information remains accurate, complete and current.

(2) Register birth to Ugandan National with no NIN

As a Registration Officer, I want to register a birth and assign a BRN if the Uganda parents have no NINs, so that a unique identifier is provided, and when the parents acquire NINs, the record can then be updated with the child's NIN (MOSIP).