Open source digital platform for large scale digital vaccination credentialing programs
Type of Digital Public Good
- Open content
- Open data
- ✅ Open software
- Open standard
- Open AI model
1. Is it relevant to one of the Sustainable Development Goals?
- 3. Good Health and Well-being
Evidence: DIVOC is part of India's Co-WIN platform (used for COVID vaccination) and has been already used at scale within India. DIVOC instance in India has already issued more than 100 million digitally verifiable credentials and continues to issue few million credentials every day as India's vaccination drive scales up.
Link to Evidence: https://divoc.egov.org.in/
2. Does it use an appropriate open license?
Yes, this project is licensed under the following license(s):
3. Is ownership clearly defined?
Is the ownership of the project and everything that the project produces clearly defined and documented?
If yes - please link to the relevant copyright, trademarks, or ownership documentation for the project.
4. Does the license of libraries/dependencies undermine the openess of the project?
Does this open project have mandatory dependencies (i.e. libraries, hardware) that create more restrictions than the original license?
If yes - are the open source components able to demonstrate independence from the closed component(s) and/or are there functional, open alternatives?
If yes - please describe how the open source components are independent and/or list the open alternatives for the closed component:
5. Is there documentation?
Does some documentation exist of the source code, use cases, and/or functional requirements. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For datasets and data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. For content collections, this should indicate any relevant compatible apps, software, hardware required to access the content and any instructions about how to use it.
If yes - please link to the relevant documentation:
6. Is non PII data and/or content accessible?
Does this project collect or use non-personally identifiable information (non-PII) data and/or content?
If yes - is there a mechanism for extracting or importing non-personally identifiable information (non-PII) from the system in a non-proprietary format?
If yes - describe the mechanism for extracting or importing non-personally identifiable information from the system in a non-proprietary format:
A masked format can be provided including the usage details and general stats about treatment
7. Does the project adhere to privacy and other applicable international and domestic laws?
Has this project taken steps to ensure adherence with relevant privacy, domestic, and international laws? For example, the General Data Protection Regulation (GDPR) in the European Union or the Supplementary Act A/SA.1/01/10 on Personal Data Protection for the Economic Community of West African States (ECOWAS) (yes/no)
If yes, please list some of relevant laws that the project complies with:
- GDPR & HIPAA for personalised medicines
- 21 CFR part 11
8. Does the project adhere to standards and best practices?
Does this project support standards? (i.e. Web Content Accessibility Guidelines (WCAG) 2.1 or other standards such as those listed on W3C)
Which standards does this project support (please list)
- ISO/IEC 12207
Can you point to evidence of your support? (i.e. please link to your validator, open test suite, etc.)
- System architecture designs and white-paper.The link https://divoc.egov.org.in/tech-docs has our Implementation and end-user guides, API documentation, Deployment instructions, Setup configuration. Additionally, the link https://divoc.egov.org.in/understand-divoc#divoc-presentations-1 also has a country-adoption guide, for implementation instructions for adopters (e.g. country authorities).
Was this project built and developed according to or in adherence with any design, technical and/or sector best practices or principles? i.e. the Principles for Digital Development?
Which principles and best practices does this project support (please list)
- We comply with and the EUs Falsified Medicines Directive (FMD) and the USAs Drug Supply Chain Security Act (DSCSA) to track serialised packs of medicines
9. Does the project do no harm by design?
Has this project taken steps to anticipate, prevent and do no harm by design?
On the whole, does this project take steps to ensure that it anticipates, prevents and does no harm by design?
Is there any additional information you would like to share about the mechanisms, processes or policies that this project uses to avoid doing harm by design?
All CfA’s media partners, who are the primary platform for the public to access the tools, are governed by their local press/media ombuds oversight mechanisms. This allows for users to lodge complaints that are independently adjudicated and ruled on. There have been no transgressions since the project launched in 2013.
9.a. Data Privacy & Security
Does this project collect or store personally identifiable information (PII) data and/or content?
If yes - please list the types of data and/or content collected and/or stored by the project:
If yes - does this project share this data and/or content with third parties?
Please describe the circumstances with which this project shares data and/or content with third parties. Please add links as relevant.
If yes - does the project ensure the privacy, security and integrity of this data and/or content collection and has it taken steps to prevent adverse impacts resulting from its collection, storage and distribution.
DIVOC is meant for last-mile vaccination administration and credentialing (with the architecture based on data minimalism, well-designed privacy & security). But as highlighted in earlier responses, these measures need to be addressed in the individual privacy policies adopted by the various implementers. The tools are embedded in partner media websites, which are governed by privacy policies and terms of service that comply with local media freedom laws.
9.b. Inappropriate & Illegal Content
Does this project collect, store or distribute content?
If yes - what kinds of content does this project, collect, store or distribute? (i.e. childrens books)
If yes - does this project have policies that describe what is considered innappropriate content? (i.e. child sexual abuse materials)
If yes - please link to the relevant policy/guidelines/documentation.
If yes - does this project have policies and processes for detecting and moderating innappropriate/illegal content?
If yes - please describe the policies and processes for detecting, reporting and removing innapropriate/illegal content (Please include the average response time for assessment and/or action. Link to any policies or descriptions of how inappropriate content is handled):
9.c. Protection from harassment
Does this project facilitate interactions with or between users or contributors?
If yes - does the project take steps to address the safety and security of underage users?
If yes - please describe the steps this project takes to address risk or prevent access by underage users:
If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment?
If yes - please describe the steps taken to help users protect themselves.
Development & deployment countries
List of countries this project was developed in.
List of countries this project is actively deployed in.
- Sri Lanka