Commission Implementing Decision (EU) 2021/2014

law://eu/dec/2021/2014@2026-11-13

Contents

THE EUROPEAN COMMISSION,Having regard to the Treaty on the Functioning of the European Union,Having regard to Regulation (EU) 2021/953 of the European Parliament and of the Council of 14 June 2021 on a framework for the issuance, verification and acceptance of interoperable COVID-19 vaccination, test and recovery certificates (EU Digital COVID Certificate) to facilitate free movement during the COVID-19 pandemic^note, and in particular Article 9(1) and (3) thereof,Whereas:

(1)Regulation (EU) 2021/953 sets out the EU Digital COVID Certificate the purpose of which is to serve as a proof that a person has received a COVID-19 vaccine, a negative test result or has recovered from infection for the purpose of facilitating the holders’ exercise of their right to free movement during the COVID-19 pandemic.

(2)In order for the EU Digital COVID Certificate to be operational throughout the Union, the Commission adopted Commission Implementing Decision (EU) 2021/1073^note, laying down technical specifications and rules to populate, securely issue and verify EU Digital COVID Certificates, ensure the protection of personal data, lay down the common structure of the unique certificate identifier and issue a valid, secure and interoperable barcode.

(3)Many Member States have already announced or have already started to administer COVID-19 vaccine doses additional to the standard primary vaccination series, that is, the vaccination series intended to provide sufficient protection at an initial stage, notably to persons who may not have responded adequately to the primary vaccination series, and are considering ‘booster’ doses for people who responded adequately to primary vaccination. In this context, the European Centre for Disease Prevention and Control published, on 1 September 2021, interim public health considerations for the provision of additional COVID-19 vaccine doses^note.

(4)On 4 October 2021, the European Medicines Agency’s Committee for Medicinal Products for Human Use concluded that an extra dose of the COVID-19 vaccines Comirnaty and Spikevax may be given to people with severely weakened immune systems, at least 28 days after their second dose^note. The Committee also evaluated data for Comirnaty showing a rise in antibody levels when a booster dose is given approximately 6 months after the second dose in people from 18 to 55 years old. On the basis of this data, the Committee concluded that booster doses for Comirnaty may be considered at least 6 months after the second dose for people aged 18 years and older. As stated by the European Medicines Agency, public health bodies at national level may issue official recommendations on the use of booster doses, taking into account emerging effectiveness data and the limited safety data. The product information of Comirnaty^note and Spikevax^note have been updated accordingly to include these recommendations.

(5)To avoid diverging, confusing or technically incompatible approaches among Member States, it is necessary to adopt uniform rules as to populating vaccination certificates referred to in point (a) of Article 3(1) of Regulation (EU) 2021/953 issued following the administration of such additional doses.

(6)According to Article 5 of Regulation (EU) 2021/953, a vaccination certificate is to be issued after the administration of each dose, it is to clearly indicate whether or not the vaccination course has been completed, and it is to contain the number of doses administered to the holder. Pursuant to the Annex to that Regulation, a vaccination certificate is to include, as data fields, the number in a series of doses as well as the overall number of doses in the series. Any rules as to how to populate vaccination certificates issued following the administration of additional doses, adopted by means of an implementing act, are to comply with the requirements established by Regulation (EU) 2021/953.

(7)Vaccine certificates issued for doses of the primary vaccination series should indicate full vaccination after the completion of the standard primary series even in cases where the later administration of additional doses is recommended. Vaccine certificates issued for additional doses administered after the standard primary vaccination series should indicate the number of doses administered to the holder, as provided for in point (b) of Article 5(2) of Regulation (EU) 2021/953, as well as the overall number of doses within the series, counting the primary vaccination doses as well as any additional doses.

(8)Particular attention should be paid to the situation of vulnerable groups who may receive additional doses as a matter of priority. If a Member State decides to administer additional doses only to specific sub-groups of the population, it could consider issuing vaccination certificates indicating the administration of such additional doses only upon request and not automatically, given that Article 5(1) of Regulation (EU) 2021/953 offers Member States the possibility to choose between these two options. As long as additional doses are administered only to a specific sub-group of the population, persons belonging to that sub-group should not be required to produce the certificate indicating the administration of an additional dose when exercising their right to free movement during the COVID-19 pandemic, and could instead make use of the certificate received following the completing of the primary vaccination series.

(9)At the same time, it is important that vaccination certificates issued to persons belonging to such groups following the administration of additional doses also correctly reflect the number of doses administered to them. Firstly, Regulation (EU) 2021/953 gives all persons a right to receive a vaccination certificate, indicating the number of doses administered to them, after the administration of each dose. Secondly, Member States may eventually limit the duration of acceptance, for the purposes of free movement, of vaccination certificates issued following the completion of the primary vaccination series, if scientific evidence becomes available that the protection afforded by the primary vaccination series wanes below a certain level after a certain period. Not giving vulnerable groups the opportunity to obtain vaccination certificates following the administration of an additional dose would require further administrative steps to obtain them when they become more important for their freedom of movement, and could thus result in obstacles thereto.

(10)In addition, the rules for populating the EU Digital COVID Certificate should be further clarified. Specific value sets applying the established coding rules should be made publicly available.

(11)To ensure the interoperability of the EU Digital COVID Certificate, a common coordinated data structure for the data to be included in certificates referred to in Article 3(1) of Regulation (EU) 2021/953 should be defined through the use of a JavaScript Object Notation (JSON) schema.

(12)Implementing Decision (EU) 2021/1073 should therefore be amended accordingly.

(13)The European Data Protection Supervisor was consulted in accordance with Article 42(1) of Regulation (EU) 2018/1725 of the European Parliament and of the Council^note and delivered formal comments on 18 October 2021^note.

(14)In the light of the need for rapid implementation of the amended technical specifications for the EU Digital COVID Certificate, this Decision should enter into force on the day of its publication in the Official Journal of the European Union.

(15)The measures provided for in this Decision are in accordance with the opinion of the Committee established by Article 14 of Regulation (EU) 2021/953,

HAS ADOPTED THIS DECISION:

Article 1 #

Implementing Decision (EU) 2021/1073 is amended as follows:

(1)Article 4 is replaced by the following:“Article 4The governance rules applicable to public key certificates in relation to the EU Digital COVID Certificate gateway supporting the interoperability aspects of the trust framework are set out in Annex IV.”;

(2)the following Articles 5 and 6 are added:“Article 5A common coordinated data structure for the data to be included in certificates referred to in Article 3(1) of Regulation (EU) 2021/953, using a JavaScript Object Notation (JSON) schema, is set out in Annex V to this Decision.Article 6This Decision shall enter into force on the day of its publication in the Official Journal of the European Union.”;

(3)Annex II is replaced by the text in Annex I to this Decision;

(4)Annex III is amended in accordance with Annex II to this Decision;

(5)the text in Annex III to this Decision is added as Annex V.

Article 2 #

This Decision shall enter into force on the day of its publication in the Official Journal of the European Union.

Annex I

‘’

Annex II

Section 3 of Annex III to Implementing Decision (EU) 2021/1073 is replaced by the following:

“3.General requirementsThe following overarching requirements shall be satisfied in relation to the UCI:

(1)Charset: only uppercase US-ASCII alpha numerical characters (‘A’ to ‘Z’, ‘0’ to ’9’) are allowed; with additional special characters for separation from RFC3986^note, namely {'/','#',':'};

(2)Maximum length: designers shall try to aim for a length of 27-30 characters^note;

(3)Version prefix: this refers to the version of the UCI schema. The version prefix is ‘01’ for this version of the document; the version prefix is composed of two digits;

(4)Country prefix: the country code is specified by ISO 3166-1. Longer codes (e.g. 3 characters and up (for example, ‘UNHCR’) are reserved for future use;

(5)Code suffix / Checksum:

5.1Member States may use a checksum when it is likely that transmission, (human) transcription or other corruptions may occur (that is to say when used in print).

5.2The checksum shall not be relied upon for validating the certificate and is not technically part of the identifier but is used to verify the integrity of the code. This checksum shall be the ISO-7812-1 (LUHN-10)^note summary of the entire UCI in digital/wire transport format. The checksum is separated from the rest of the UCI by a '#' character.

Backwards-compatibility shall be ensured: Member States that over time change the structure of their identifiers (within the main version, currently set at v1) shall ensure that any two identifiers that are identical represent the same vaccination certificate/assertion. Or, in other words, Member States cannot recycle identifiers.

III

‘’

Annex V

Javascript object notation (json) schema

1. Introduction

This Annex establishes the technical data structure for EU Digital COVID Certificates (EUDCC), represented as a JSON schema. The document provides specific instructions related to the individual data fields.

2. JSON Schema location and versions

The authoritative official JSON schema for EUDCC is made available at https://github.com/ehn-dcc-development/ehn-dcc-schema. Other locations are not authoritative, but may be used for preparing upcoming revisions.

By default, the current version as set out in this Annex and supported by all countries currently in production is shown under the indicated URL.

Upcoming next version, to be supported by a defined date by all countries, is shown under the indicated URL through version tagging, described more specifically in the Readme file.

3. Common structures and general requirements

An EU Digital COVID Certificate shall not be issued if not all data fields can be correctly populated in accordance with this specification due to missing information. This shall not be understood as affecting the obligation of Member States to issue EU Digital COVID Certificates.

Information in all fields may be provided using the full set of UNICODE 13.0 characters encoded using UTF-8, unless specifically restricted to value sets or narrower sets of characters.

The common structure shall be as follows:

"JSON": {

"ver": <version information>,

"nam": {

<person name information>

"dob": <date of birth>,

"v" or "t" or "r": [

{<vaccination dose or test or recovery information, one entry>}

]

}

Detailed information on individual groups and fields is provided in next sections.

3.1. Version

Version information shall be provided. Versioning is following Semantic Versioning (semver: https://semver.org). In production, it shall be one of the officially released (current or one of the older officially released) versions. See Section JSON Schema location for more details.

Field id	Field name	Instructions
ver	Schema version	Shall match the identifier of the schema version used for producing the EUDCC.Example:"ver": "1.3.0"

3.2. Person name and date of birth

Person name is the official full name of the person, matching the name stated on travel documents. The identifier of the structure is nam. Exactly 1 (one) person name shall be provided.

Field id	Field name	Instructions
nam/fn	Surname(s)	Surname(s) of the holder.Exactly 1 (one) non-empty field shall be provided, with all surnames included in it. In case of multiple surnames, these shall be separated by a space. Combination names including hyphens or similar characters must however stay the same.Examples:"fn": "Musterfrau-Gößinger""fn": "Musterfrau-Gößinger Müller"
nam/fnt	Standardised surname(s)	Surname(s) of the holder transliterated using the same convention as the one used in the holder’s machine readable travel documents (such as the rules defined in ICAO Doc 9303 Part 3).Exactly 1 (one) non-empty field shall be provided, only including characters A-Z and <. Maximum length: 80 characters (as per ICAO 9303 specification).Examples:"fnt": "MUSTERFRAU<GOESSINGER""fnt": "MUSTERFRAU<GOESSINGER<MUELLER"
nam/gn	Forename(s)	Forename(s), such as given name(s), of the holder.If the holder has no forenames, the field shall be skipped.In all other cases, exactly 1 (one) non-empty field shall be provided, with all forenames included in it. In case of multiple forenames, these shall be separated by a space.Example:"gn": "Isolde Erika"
nam/gnt	Standardised forename(s)	Forename(s) of the holder transliterated using the same convention as the one used in the holder’s machine readable travel documents (such as the rules defined in ICAO Doc 9303 Part 3).If the holder has no forenames, the field shall be skipped.In all other cases, exactly 1 (one) non-empty field shall be provided, only including characters A-Z and <. Maximum length: 80 characters.Example:"gnt": "ISOLDE<ERIKA"
dob	Date of birth	Date of birth of the DCC holder.Complete or partial date without time restricted to the range from 1900-01-01 to 2099-12-31.Exactly 1 (one) non-empty field shall be provided if the complete or partial date of birth is known. If the date of birth is not known even partially, the field shall be set to an empty string "". This should match the information as provided on travel documents.One of the following ISO 8601 formats shall be used if information on date of birth is available. Other options are not supported.YYYY-MM-DDYYYY-MMYYYY(The verifier app may show missing parts of the date of birth using the XX convention as the one used in machine-readable travel documents, e.g. 1990-XX-XX.)Examples:"dob": "1979-04-14""dob": "1901-08""dob": "1939""dob": ""

3.3. Groups for certificate type specific information

The JSON Schema supports three groups of entries encompassing certificate type specific information. Each EUDCC shall contain exactly 1 (one) group. Empty groups are not allowed.

Group identifier	Group name	Entries
v	Vaccination group	If present, shall contain exactly 1 (one) entry describing exactly 1 (one) vaccination dose (one dose).
t	Test group	If present, shall contain exactly 1 (one) entry describing exactly 1 (one) test result.
r	Recovery group	If present, shall contain exactly 1 (one) entry describing 1 (one) recovery statement.

4. Certificate type specific information

4.1. Vaccination certificate

Vaccination group, if present, shall contain exactly 1 (one) entry describing exactly one vaccination event (one dose). All elements of the vaccination group are mandatory, empty values are not supported.

Field id	Field name	Instructions
v/tg	Disease or agent targeted: COVID-19 (SARS-CoV or one of its variants)	A coded value from the value setdisease-agent-targeted.json.This value set has a single entry 840539006, which is the code for COVID-19 from SNOMED CT (GPS).Exactly 1 (one) non-empty field shall be provided.Example:"tg": "840539006"
v/vp	COVID-19 vaccine or prophylaxis	Type of the vaccine or prophylaxis used.A coded value from the value setvaccine-prophylaxis.json.The value set is distributed from the EUDCC Gateway.Exactly 1 (one) non-empty field shall be provided.Example:"vp": "1119349007"(a SARS-CoV-2 mRNA vaccine)
v/mp	COVID-19 vaccine product	Medicinal product used for this specific dose of vaccination. A coded value from the value setvaccine-medicinal-product.json.The value set is distributed from the EUDCC Gateway.Exactly 1 (one) non-empty field shall be provided. Example:"mp": "EU/1/20/1528" (Comirnaty)
v/ma	COVID-19 vaccine marketing authorisation holder or manufacturer	Marketing authorisation holder or manufacturer, if no marketing authorization holder is present. A coded value from the value setvaccine-mah-manf.json.The value set is distributed from the EUDCC Gateway.Exactly 1 (one) non-empty field shall be provided. Example:"ma": "ORG-100030215"(Biontech Manufacturing GmbH)
v/dn	Number in a series of doses	Sequence number (positive integer) of the dose given during this vaccination event. 1 for the first dose, 2 for the second dose etc. More specific rules are provided in Section 5 of Annex II.Exactly 1 (one) non-empty field shall be provided.Examples:"dn": "1"(first dose)"dn": "2"(second dose)"dn": "3"(third dose)
v/sd	The overall number of doses in the series	Overall number of doses (positive integer) in the vaccination series. More specific rules are provided in Section 5 of Annex II.Exactly 1 (one) non-empty field shall be provided.Examples:"sd": "1" (in case of a 1-dose primary vaccination course)"sd": "2" (in case of a 2-dose primary vaccination series or for an additional dose following a 1-dose primary vaccination course)"sd": "3" (e.g. in case of additional doses following a 2-dose primary vaccination series)
v/dt	Date of vaccination	The date when the described dose was received, in the format YYYY-MM-DD (full date without time). Other formats are not supported.Exactly 1 (one) non-empty field shall be provided. Example:"dt": "2021-03-28"
v/co	Member State or third country in which the vaccine was administered	Country expressed as a 2-letter ISO3166 code (RECOMMENDED) or a reference to an international organisation responsible for the vaccination event (such as UNHCR or WHO). A coded value from the value set country-2-codes.json.The value set is distributed from the EUDCC Gateway.Exactly 1 (one) field shall be provided.Example:"co": "CZ""co": "UNHCR"
v/is	Certificate issuer	Name of the organisation that issued the certificate. Identifiers are allowed as part of the name, but not recommended to be used individually without the name as a text. Max 80 UTF-8 characters.Exactly 1 (one) non-empty field shall be provided. Example:"is": "Ministry of Health of the Czech Republic""is": "Vaccination Centre South District 3"
v/ci	Unique certificate identifier	Unique certificate identifier (UVCI) as specified in the https://ec.europa.eu/health/sites/default/files/ehealth/docs/vaccination-proof_interoperability-guidelines_en.pdfThe inclusion of the checksum is optional. The prefix "URN:UVCI:" may be added.Exactly 1 (one) non-empty field shall be provided.Examples:"ci": "URN:UVCI:01:NL:187/37512422923""ci": "URN:UVCI:01:AT:10807843F94AEE0EE5093FBC254BD813#B"

4.2. Test certificate

Test group, if present, shall contain exactly 1 (one) entry describing exactly one test result.

Field id	Field name	Instructions
t/tg	Disease or agent targeted: COVID-19 (SARS-CoV or one of its variants)	A coded value from the value set disease-agent-targeted.json.This value set has a single entry 840539006, which is the code for COVID-19 from SNOMED CT (GPS).Exactly 1 (one) non-empty field shall be provided.Example:"tg": "840539006"
t/tt	The type of test	The type of the test used, based on the material targeted by the test. A coded value from the value set test-type.json (based on LOINC). Values outside of the value set are not allowed.Exactly 1 (one) non-empty field shall be provided.Example:"tt": "LP6464-4"(Nucleic acid amplification with probe detection)"tt": "LP217198-3"(Rapid immunoassay)
t/nm	Test name (nucleic acid amplification tests only)	The name of the nucleic acid amplification test (NAAT) used. The name should include the name of the test manufacturer and the commercial name of the test, separated by a comma.For NAAT: the field is optional.For RAT: the field shall not be used, as the name of the test is supplied indirectly through the test device identifier (t/ma).When supplied, the field shall not be empty.Example:"nm": "ELITechGroup, SARS-CoV-2 ELITe MGB® Kit"
t/ma	Test device identifier (rapid antigen tests only)	Rapid antigen test (RAT) device identifier from the JRC database. Value set (HSC common list):All Rapid antigen tests in HSC common list (human readable).https://covid-19-diagnostics.jrc.ec.europa.eu/devices/hsc-common-recognition-rat (machine-readable, values of the field id_device included on the list form the value set).In EU/EEA countries, issuers shall only issue certificates for tests belonging to the currently valid value set. The value set shall be updated every 24 hours.Values outside of the value set may be used in certificates issued by third countries, however the identifiers shall still be from the JRC database. The use of other identifiers such as those provided directly by test manufacturers is not permitted.Verifiers shall detect values not belonging to the up to date value set and display certificates bearing these as invalid. If an identifier is removed from the value set, certificates including it may be accepted for a maximum of 72 hours after the date of removal.The value set is distributed from the EUDCC Gateway.For RAT: exactly 1 (one) non-empty field shall be provided.For NAAT: the field shall not be used, even if the NAA test identifier is available in the JRC database.Example:"ma": "344"(SD BIOSENSOR Inc, STANDARD F COVID-19 Ag FIA)
t/sc	Date and time of the test sample collection	The date and time when the test sample was collected. The time shall include information on the time zone. The value shall not denote the time when the test result was produced.Exactly 1 (one) non-empty field shall be provided.One of the following ISO 8601 formats shall be used. Other options are not supported.YYYY-MM-DDThh:mm:ssZYYYY-MM-DDThh:mm:ss[+-]hhYYYY-MM-DDThh:mm:ss[+-]hhmmYYYY-MM-DDThh:mm:ss[+-]hh:mmExamples:"sc": "2021-08-20T10:03:12Z" (UTC time)"sc": "2021-08-20T12:03:12+02" (CEST time)"sc": "2021-08-20T12:03:12+0200" (CEST time)"sc": "2021-08-20T12:03:12+02:00" (CEST time)
t/tr	Result of the test	The result of the test. A coded value from the value set test-result.json (based on SNOMED CT, GPS).Exactly 1 (one) non-empty field shall be provided.Example:"tr": "260415000" (Not detected)
t/tc	Testing centre or facility	Name of the actor that conducted the test. Identifiers are allowed as part of the name, but not recommended to be used individually without the name as a text. Max 80 UTF-8 characters. Any extra characters should be truncated. The name is not designed for automated verification.For NAAT tests: exactly 1 (one) non-empty field shall be provided.For RAT tests: the field is optional. If provided, shall not be empty.Example:"tc": "Test centre west region 245"
t/co	Member State or third country in which the test was carried out	Country expressed as a 2-letter ISO3166 code (RECOMMENDED) or a reference to an international organisation responsible for carrying out the test (such as UNHCR or WHO). This shall be a coded value from the value set country-2-codes.json.The value set is distributed from the EUDCC Gateway.Exactly 1 (one) field shall be provided.Examples:"co": "CZ""co": "UNHCR"
t/is	Certificate issuer	Name of the organisation that issued the certificate. Identifiers are allowed as part of the name, but not recommended to be used individually without the name as a text. Max 80 UTF-8 characters.Exactly 1 (one) non-empty field shall be provided.Examples:"is": "Ministry of Health of the Czech Republic""is": "North-West region health authority"
t/ci	Unique certificate identifier	Unique certificate identifier (UVCI) as specified in the vaccination-proof_interoperability-guidelines_en.pdf (europa.eu)The inclusion of the checksum is optional. The prefix "URN:UVCI:" may be added.Exactly 1 (one) non-empty field shall be provided.Examples:"ci": "URN:UVCI:01:NL:187/37512422923""ci": "URN:UVCI:01:AT:10807843F94AEE0EE5093FBC254BD813#B"

4.3. Recovery certificate

Recovery group, if present, shall contain exactly 1 (one) entry describing exactly one recovery statement. All elements of the recovery group are mandatory, empty values are not supported.

Field id	Field name	Instructions
r/tg	Disease or agent from which the holder has recovered: COVID-19 (SARS-CoV-2 or one of its variants)	A coded value from the value setdisease-agent-targeted.json.This value set has a single entry 840539006, which is the code for COVID-19 from SNOMED CT (GPS).Exactly 1 (one) non-empty field shall be provided.Example:"tg": "840539006"
r/fr	Date of the holder’s first positive NAAT test result	The date when a sample for the NAAT test producing a positive result was collected, in the format YYYY-MM-DD (complete date without time). Other formats are not supported.Exactly 1 (one) non-empty field shall be provided.Example:"fr": "2021-05-18"
r/co	Member State or third country in which test was carried out	Country expressed as a 2-letter ISO3166 code (RECOMMENDED) or a reference to an international organisation responsible for carrying out the test (such as UNHCR or WHO). This shall be a coded value from the value setcountry-2-codes.json.The value set is distributed from the EUDCC Gateway.Exactly 1 (one) field shall be provided.Examples:"co": "CZ""co": "UNHCR"
r/is	Certificate issuer	Name of the organisation that issued the certificate. Identifiers are allowed as part of the name, but not recommended to be used individually without the name as a text. Max 80 UTF-8 characters.Exactly 1 (one) non-empty field shall be provided. Example:"is": "Ministry of Health of the Czech Republic""is": "Central University Hospital"
r/df	Certificate valid from	The first date on which the certificate is considered to be valid. The date shall not be earlier than the date calculated as r/fr + 11 days.The date shall be provided in the format YYYY-MM-DD (complete date without time). Other formats are not supported.Exactly 1 (one) non-empty field shall be provided.Example:"df": "2021-05-29"
r/du	Certificate valid until	The last date on which the certificate is considered to be valid, assigned by the certificate issuer. The date shall not be after the date calculated as r/fr + 180 days.The date shall be provided in the format YYYY-MM-DD (complete date without time). Other formats are not supported.Exactly 1 (one) non-empty field shall be provided.Example:"du": "2021-11-14"
r/ci	Unique certificate identifier	Unique certificate identifier (UVCI) as specified in the vaccination-proof_interoperability-guidelines_en.pdf (europa.eu)The inclusion of the checksum is optional. The prefix "URN:UVCI:" may be added.Exactly 1 (one) non-empty field shall be provided.Examples:"ci": "URN:UVCI:01:NL:187/37512422923""ci": "URN:UVCI:01:AT:10807843F94AEE0EE5093FBC254BD813#B"

Commission Implementing Decision (EU) 2021/2014

Commission Implementing Decision (EU) 2021/2014

Article 1 #

Article 2 #

Annex I

Annex II

III

Annex V

Javascript object notation (json) schema

1. Introduction

2. JSON Schema location and versions

3. Common structures and general requirements

3.1. Version

3.2. Person name and date of birth

3.3. Groups for certificate type specific information

4. Certificate type specific information

4.1. Vaccination certificate

4.2. Test certificate

4.3. Recovery certificate

Key facts

Connections

History · 2 versions

Article 1 #

Article 2 #

Annex I

Annex II

III

Annex V

Javascript object notation (json) schema

1. Introduction

2. JSON Schema location and versions

3. Common structures and general requirements

3.1. Version

3.2. Person name and date of birth

3.3. Groups for certificate type specific information

4. Certificate type specific information

4.1. Vaccination certificate

4.2. Test certificate

4.3. Recovery certificate