Implementation Checklist
Overview
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.
QR code
Create QR code
Change the value in context section.
This value indicates the release version of the certificate schema. This versioning will support in introducing validations (if required) on certificates generated in previous schemas such as "revoking/invalidating certificates with previous schema."
For example: For release 1 - It could be "https://moh.prod/credentials/vaccination/v1" and for release 2 - It could be "https://moh.prod/credentials/vaccination/v2"
Create QR code
The Id field in "credentialSubject" should be in a URI format.
If certify request payload contains “identity,” set it to “did::”
Else, use the “preEnrollmentCode” and set it to “did::”
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.
The format is as per the WHO-DDCC data standard.
Validate the date value as it may have impact due to the vaccination system (external), and DIVOC is deployed in servers with a different timezone (UTC). Border cases to be checked as day/date may change.
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.
Update changes
Update a certificate
Revoke a certificate
The system should be able to generate a certificate for a revoked dose.
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.
Certificate template changes
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.
Certificate verification
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:
How to scan the QR code?
The possible reason for showing a certificate as invalid or revoked?
What steps to follow if a certificate is shown as invalid or revoked, such as information of the contact person.
Setting up the server
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:
Data backup policy.
Authentication and password management.
Error handling and logging.
System configurations.
Server setup
System is configured to handle network crash or infrastructure crash.
Server setup
Back up of the following:
DB/server setup.
Online/offline line.
Server setup
The section should cover activities to be performed to ensure security of data and application.
For example,
Firewall controls should also be in place, such as user management, for better access control.
Generating signed key pairs
Sign key generation
It is done as per the standard.
Sign key generation
Keycloak configuration related to DIVOC.
Operational checklist
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.
Last updated
