WHO SMART Trust
1.1.5 - CI Build
WHO SMART Trust, published by WHO. This guide is not an authorized publication; it is the continuous build for version 1.1.5 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/WorldHealthOrganization/smart-trust/ and changes regularly. See the Directory of published versions
A designated public health authority from a WHO Member State, with decision-making authority regarding participation in the GDHCN, should be the representative.
A senior official with decision-making powers, involved in strategic decisions but not daily operations.
An individual responsible for addressing technical inquiries and issues during the project's lifecycle.
Manages legal aspects, including regulatory compliance and contractual matters related to GDHCN participation.
Participation in the GDHCN is currently free, supported by existing WHO funding.
The tool aims to manage vaccine codes effectively, addressing the complexities of medical terminology coding.
Yes, continuing in the UAT environment is possible and does not hinder future transition to the production environment.
Through platforms like GitHub, enabling community contributions to enhance technical specifications and documentation.
By incorporating EU DCC specifications like APIs for key access, business rules, and value sets, ensuring compatibility.
Future developments will be guided by WHO, focusing on compatibility with existing systems and ensuring security and backward compatibility.
This includes moving APIs and sets into GDHCN specifications, with WHO ensuring a smooth integration.
It involves verifying technical connections and compatibility with existing systems, especially regarding TLS certificates.
With detailed definitions for key materials, ensuring clarity and visibility in the key exchange process, closely resembling EU DCC definitions.
The focus is on addressing security incidents, with no changes to the repository unless necessary for security reasons.
The policy is under review, with discussions on alternatives to the three-month renewal policy, including longer expiry times or self-signed certificates.
The possibility of WHO using self-signed certificates with extended expiry times is under discussion.
Proposals for alternatives, like extended expiry times, are being considered to alleviate concerns with short renewal policies.
Trusting the CA rather than the certificate itself may provide a solution to frequent renewals.