Version release date

January 24, 2023

Release summary

With this release, the DIVOC platform provides a user interface (UI) for tenants to log into the DIVOC platform to create and manage different tenants and schemas required for issuing verifiable credentials (VCs).

Terminology

A list of the common terms used in this document:

• Verifiable credentials (VCs) represent information found in physical credentials, such as birth registration and driving license, as well as objects that have no physical equivalent, such as ownership of a bank account. VCs are typically QR codes whose information is being signed and can only be modified by the issuer making it a tamper-proof QR code. The QR codes can be read and verified by the verifiers using the public key issued by the issuer and by using the libraries/algorithms used by the issuer system. When a digital document (for example, a lab test report) has a normal QR code, anyone can modify its value and generate a new QR code and then replace it with another QR code with different information. Whereas the information in a verifiable QR code cannot be replaced as the original data or information cannot be changed without a “private key.”

• Issuer: Refers to an issuing authority who can issue claims about a particular entity or individual that can be validated. An issuer gathers the information that needs to be contained in the VC from the entities and sends it across to DIVOC through tenant software. Example: Medical Councils.

• Tenant: Refers to any source system of issuers linked to the DIVOC platform to issue VCs. Examples: Council Software, University software, etc.

• Source systems: The tenant software that interacts with the DIVOC platform to issue VCs.

• Schema: A schema is essentially a template that tells the issuer the content, type, and description required for an attribute that needs to be part of the VC.

New Features

Enhancements from the previous platform release

Release notes for supported versions are given below:

• (on-demand EU-DCC and FHIR-DDCC export)

• (minor enhancements and UI fixes)

• (bug fixes and enhancements)

• (UI enhancements and bug fixes)

• (secondary dosage flows and design enhancements)

• (minor enhancements and UI fixes)

• (design enhancements and bug fixes)

• (facility application enhancements)

• (minor enhancements and bug fixes)

• (minor enhancement on appointment)

• (registration and appointment)

• (generic) and

All content on this page by is licensed under a .

Version release date

• March 25, 2022.

Release summary

If your country is implementing DIVOC 2.0, it is important to know the additions/changes that we have made as part of this release:

• Configuration management via etcd: You can make configuration changes to DIVOC’s certificate module via etcd without needing a new deployment. Click here to know more.

• Support for EU compliant digital certificates and Smart Health Cards: DIVOC’s EU-DCC and SHC adapter services facilitate easy travel for residents from DIVOC’s adopter countries. Know more about DIVOC’s EU-DCC and SHC adapter services.

• Print certificates at the facility: We have added the capability to print vaccination certificates when a beneficiary walks into a facility. Click here to know more.

• New API for revocation services: A new Revoke API has been introduced that can be used to revoke an issued certificate for manual revocation use cases. Click here to know more.

• Deployment activities automated reducing installation time:

- Automating our infrastructure setup has reduced our deployment time from about 3 days to 1 day.

- DIVOC’s installation process has been streamlined with the introduction of the new scripts. The details of the scripts are given below:

1. Install the prerequisites and set up the various hardware clusters.

2. Push the docker images to the appropriate registry.

3. Deploy the code from the registry into the Kubernetes cluster.

• Enhanced performance of PDF certificate generation: We have fine-tuned our PDF generating algorithms, which has lowered the consumption of system resources.