Comment on page
Implementation Checklist
This checklist can help you plan your implementation. Besides technical and operational details, it covers server setup, QR code, certificate template changes, and updating and verifying certificates.
Section | Checklist | Description |
---|---|---|
Create QR code | Change the value in context section. |
|
Create QR code | The Id field in "credentialSubject" should be in a URI format. |
|
Create QR code | The date value passed in the payload in the 'vaccination' section should match with the value in the 'evidence' section of the QR code and it should follow the YYYY-MM-DD format. |
|
Create QR code | The 'issuer' is mapped correctly as per the requirement. |
|
Create QR code | The vaccine list provided by a country is available in the master list. |
|
Create QR code | The vaccine and prophylaxis mapping is as per the country requirements. |
|
Create QR code | Vaccine 'manufacturer,' 'batch' values shared in the payload are getting reflected in the QR code. | |
Create QR code | The addressCountry value in the evidence section captures the 3-digit country code from here. | |
Create QR code | 'dose' and "totalDoses" value shared in the payload are getting reflected in the QR code. | |
Create QR code | The 'Id' part in the evidence section is in a URI format. |
|
Section | Checklist | Description |
---|---|---|
Update a certificate | Update limits are set according to a country's requirement. The details to configure the update limit are available here. | |
Revoke a certificate | The system should be able to generate a certificate for a revoked dose. | For example, if the dose 2 certificate has been removed from the system, the user should be allowed to generate another/correct dose 2 certificate. Click here to know more on DIVOC's revocation services. |
Revoke a certificate | The system is only revoking the earlier certificate which existed for the specified dose value. | For example, If dose 2 certificate has been removed from the system, the user should be allowed to generate another/correct dose 2 certificate. |
Section | Checklist | Description |
---|---|---|
Create certificate template | QR code size is 2.5x2.5 inch on a printed A4 size paper. | |
Create certificate template | Does the printed certificate show the minimal values based on the WHO-DDCC standard? | |
Create certificate template | If the certificate template has a table which shows the current and the previous dose details (if available), then the table should be configured to be scalable to capture details of both the current and the previous dose details in required combinations. | For example, the certificate template should have only one template file to refer to for the generation of certificates with a combination of dose 1, dose 1 and 2, dose 1, 2, and 3, etc. This should be up to a maximum feasible limit based on the template design. |
Section | Checklist | Description |
---|---|---|
Verify a certificate | SSL certificate has been applied to the verification page. | The SSL certificate is required to open the camera in the browser. |
Verify a certificate | The verification page has been configured to provide the necessary guidance to the user for the verification component. | For example, the verification page should include following messaging/guidelines/ information:
|
Section | Checklist | Description |
---|---|---|
Server setup | Infrastructure estimation guide. | For example, if the load goes up, then the system should be configured for scalability. |
Server setup | The production environment should support the following recommendations:
| |
Server setup | System is configured to handle network crash or infrastructure crash. | For example, if the master/slave nodes go down, are they configured to autostart/auto-deploy? Click here to know more. |
Server setup | Back up of the following:
| |
Server setup | The section should cover activities to be performed to ensure security of data and application. For example,
|
Section | Checklist | Description |
---|---|---|
Privacy policy | Privacy policies are based on the recommendations made to implementing partners. They are advised to share it with citizens regarding their personally identifiable information and how it is managed in DIVOC. | As the application contains citizen data, access rights (read/write) should be agreed between parties for staging/production/other environments. Click here to know more. |
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Last modified 7mo ago