DIGIT CORE
Search…
Service Architecture
DIGIT consists of several reusable building blocks on top of which one can develop a citizen service delivery solution. To develop a new service, one needs to create a Microservice and make it available through the API gateway. The API gateway calls the User service for authentication and the Access Service for authorisation. The service developer can configure the roles and map the roles and actions using the Master Data Management Service.
DIGIT Services
The service user interface can be developed as part of the Citizen Dashboard or can be an independent solution. The citizen can log in using mobile number and OTP. Then apply for a new service using the service UI. Relevant documentation can be uploaded which are stored in the File Store.
On submission of the application the service stores the application asynchronously into the registry using Persister. PII is encrypted using Encryption Service before storing. All changes are digitally signed and logged using Signed Audit Service (ongoing). Application data is transformed and enriched using Indexer also all the PII is stripped and sent to the Analytics Data Store(ElasticSearch) by the Indexer. The Dashboard backend operates on top of this data on which it executes the configured queries and makes the aggregated data available to the Dashboard frontend, which can be viewed by the administrator or employee depending on the access(which is also configurable).
Depending on the calculation logic for the given service delivery, the microservice will call the Billing Service to generate a demand. Based on this demand a bill will be generated against which a payment can be made. To pay for the given bill, the citizen can do either online payment or can pay at the counter(offline payment). For online payment, the Payment Gateway Service is called which is integrated with third party service providers. Based on the selected provider the citizen will be routed to the provider's website and after successful payment will be routed back to the Citizen UI. Collection service is the payment registry and records all the successful payments. For Offline payments, a record is made in collection service after collection of the Cash/Cheque/DD/RTGS(Allowed payment modes are configurable). The PDF service is used to generate receipts based on a configurable template.
The service then triggers the Workflow Service to assign tasks for verification and approval. Workflows can be configured. The employees are registered in the Employee service and they can log in using the Employee dashboard. This displays the list of pending applications as per the employee's role. The employee can perform actions on these applications using the employee UI for the service. As status changes the relevant SMS and Email Notification are sent to the applicant. On approval, the applicant can download the final certificate which is generated using PDF service.
DIGIT is multi-tenant. A tenant hierarchy can be configured e.g. Country.State.District or State.Department.SubDepartment in the Location Service. Each tenant can have their own configurations for service, roles, workflows etc. This allows for variations across different agencies as per local context.
To support multiple languages, DIGIT provides Language service which stores translations in different languages.
End to End Citizen Flow
__
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Copy link