The DDCC specifications published by WHO relies on the FHIR standard, and on IHE FHIR-based Profiles such as
- SVCM: Sharing Valuesets, Codes, and Maps
- mCSD: Mobile Care Services Discovery
- PMIR: Patient Master Identity Registry
- MHD: Mobile access to Health Documents
- DDCC: Digital Documentation of COVID-19 Certificates
In this context, the SUT Operators who develop the client side of those specifications want to verify the compliance of their system under test in regards to the specifications, in particular, whether the HTTP Header and Body of the HTTP requests are conform.
The SUT Operator might choose to
- extract the message from his logs and validate it using Gazelle validation services (GUI or API)
- validate a message captured by Gazelle Proxy
Offer a validation tool for the HTTP requests produced by the SUT in the context of the DDCC specifications.
SUT Operator will be able to see if their implementattion are conformed with DDCC specification
More and more HTTP-based profiles are being developed by our customers, thus, being able to validate the full HTTP payload, including the HTTP header is necessary to improve the coverage of the specifications by test tools.
DDCC implementation guide: https://worldhealthorganization.github.io/ddcc/
SVCM implementation guide: https://profiles.ihe.net/ITI/SVCM/index.html
MHD implementation guide: https://profiles.ihe.net/ITI/MHD/index.html
mCSD implementation guide: https://profiles.ihe.net/ITI/mCSD/index.html
PMIR implementation guide: https://profiles.ihe.net/ITI/PMIR/index.html