Registration
GovStack resources | |
---|---|
GovStack requirements for BB | |
GovStack requirements for registration BB | |
GovStack GitHub Registration | GitHub - GovStackWorkingGroup/bb-registration: Registration Building Block for GovStack |
Registration of the beneficiary candidate and evaluation of eligibility. In this step, citizen is registered to SRIS - Social Registration Information System where eligibility evaluated, linked to the suitable benefit program in BOMS - Beneficiary Operations Management System and payment request created.
Initial plan for involving actual BB candidates:
Payment processing handled by MIFOS BB https://mifos.gitbook.io/docs/payment-hub-ee/overview/example
Payment request initiated by OpenIMIS BB (see Registration | Normal course of registration in MVP )
Materials from here: https://docs.google.com/presentation/d/1IZh5FQIqgmVkk7KU0ui8ETVaFawfsT-DFO8Zql6G-mU/edit#slide=id.g1177a058de2_0_10
Normal course of registration in MVP
Normal course is a description on what happens if the event is triggered and pre-conditions are met. Following table contains the comparison of MVP normal course and fully implemented workflow normal course.
MVP course |
---|
|
Preconditions:
Information mediator IM is installed to the sandbox and enabled
The mocked database acting as the CR (Citizen Registry) is created
The mocked benefit program data is available in BOMS
The User (Civil-servant who fills citizen registration form in SRIS) must be created in SRIS and BOMS to fill and submit registration form.
To create SRIS and BOMS record, Users, Citizen and Benefit program data must be available.
DB | Data |
---|---|
Users |
|
CR - Citizen Registry |
|
SRIS - Social Registry Information System |
|
BOMS - Beneficiary Operations Management System
|
|
IFMS - Integrated Finance Management Information System |
|
Trigger
Trigger is the event that triggers the BB action. In this phase there are four triggers based on user actions in UI:
Create SRIS record - triggered when user submits the record
Provide benefit program data - triggered when user associates the SRIS record to BOMS benefit program record
Create BOMS record - triggered when user submits the SRIS and BOMS association
Send payment request - triggered when user submits the SRIS and BOMS association. (In openIMIS we need to register the notification to get payment information for Payment BB)
Data input and output
NB! All additional backround data that is required for minimum data exchange between BB (RequestID, ResponseID, SourceBBID,….etc.) should be included to the input and output (marked as ……)
Data input | Data output | GovStack API spec |
---|---|---|
|
| 8 Service APIs | bb-registration
|
OpenIMIS resources
| Description | Input | OpenIMIS API spec |
---|---|---|---|
User login | User/Civil servant logs in. To create new record the user must have certain role | User ID | Login:
|
Provide Citizen personal data | Civil servant opens the registration form to fill the beneficiary registration form. Civil Servant enters citizens personal ID. Citizens personal data is pulled from the CR and form filled automatically | Citizen ID | openIMIS citizen/patient API: |
Provide Benefit program details (Product details) |
|
| (Programm ID & Name): |
Request Beneficiary enrollment | Civil Servant enrolls beneficiary New beneficiary record is created and related to suitable benefit program (product) to the OpenIMIS | Citizen ID Program ID (in OpenIMIS Product ID)
| openIMIS API (contract) |
Notify payment BB of new payment request |
| Citizen ID Program ID (in OpenIMIS Product ID) Payment amount Payment due date | In OpenIMIS notification setup must be done to send out the payment https://fhir.openimis.org/StructureDefinition-openimis-invoice-bill.html ? |