0.1.0-test - CI Build

OpenHIE DDCC - Local Development build (v0.1.0-test). See the Directory of published versions


This is the OpenHIE Implementation Guide for WHO's Digital Documentation of Covid Certificates (DDCC) IG
This documentation and set of artefacts are still undergoing development. This content is only for demonstrative purposes.


This publication contains the full set of specifications for an OpenHIE compliant implementation of WHO's Digital Documentation of Covid Certificates (DDCC) IG
The WHO DDCC Implementation Guide contains a standards-compliant specifications for the DDCC:VS technical specifications and guidance document. This Implementation Guide explicitly encodes computer-interoperable logic, including data models, terminologies, and logic expressions, in a computable language to support implementation of continuity of care and proof of vaccination use cases by Member States.
The OpenHIE DDCC Implementation Guide builds off the WHO DDCC Implementation Guide while leveraging the OpenHIE Architecture Specification. Highlights of the differences between the Implementation Guides include:
  • The Certificate Repository actor is required in the OpenHIE DDCC IG
  • The Certificate Repository and Certificate Registry actors are grouped in the OpenHIE DDCC IG
  • The OpenHIE Share Health Record is used to fufill the Certificate Repository actor role in the OpenHIE DDCC IG
  • The DDCC Generator Service is a service within the Interoperability Layer within the OpenHIE architecture
With these requirements, OpenHIE DDCC implementors are able to utilize other components of the OpenHIE Architecture to provide auxilary services related to DDCC implementations which may include:
  • Use of a Terminology Service to handle mappings of terminologies from jurisidiction defined code systems to those requried by the WHO DDCC using the IHE SVCM profile
  • Use of a Product Catalog to handle codings, market authorization and other metadata associated to the vaccines available with the implementation jurisidiction
  • Use of a Client Registry record linkage/deduplication services to better ensure continuity of care using PMRIR
  • Use of a Health Worker Registry to ensure that appropriately authorized and credentialed health workers are vaccinating clients using IHE mCSD
  • Use of a Facility Regsitry to ensure consistent codings of health facility and health devlivery organizations using IHE mCSD
The top menu allows quick navigation to the different sections, and a Table of Contents is provided with the entire content of this Implementation Guide. (Be aware that some pages have multiple tabs).

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide includes examples making use of terminologies such as LOINC, SNOMED CT and others which have more restrictive licensing requirements. Implementers should make themselves familiar with licensing and any other constraints of terminologies, questionnaires, and other components used as part of their implementation process. In some cases, licensing requirements may limit the systems that data captured using certain questionnaires may be shared with.


The specification herewith documented is a demo working specification, and may not be used for any implementation purposes. This draft is provided without warranty of completeness or consistency, and the official publication supersedes this draft. No liability can be inferred from the use or misuse of this specification, or its consequences.