You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 26, 2023. It is now read-only.
* Replaced ASCII art with SVG (and its draw.io source, and backup PNG).
* OCD w.r.t. whitespace, including putting each sentence on 1 line.
* Various textual things.
Copy file name to clipboardexpand all lines: issuing/readme.md
+45-27
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,18 @@
1
1
# DCC Issuance Guide
2
2
3
-
The EU DCC encodes a sequence of test and vaccination events into a single record. Depending on the sequence a DCC can be issued for:
3
+
The EU DCC encodes a certificate that's issued for:
4
+
5
+
* Vaccination - or more precisely: a status summarizing a combination of multiple vaccinations, and possibly a recovery
6
+
* Recovery - after positive test, and confirmation by a health authority
7
+
* Test result - after negative test at an officially-registered testing facility
4
8
5
-
* Vaccination
6
-
* Recovery (after positive test)
7
-
* Test (after negative test)
8
9
9
10
## General structure
10
11
11
-
The DCC is encoded as a JSON. It includes a section linking the identity of the holder to the DCC, and a section which includes a medical statement made about the holder - for example their vaccination status.
12
+
The DCC is encoded as JSON.
13
+
This includes a section linking the identity of the holder to the DCC, and a section which includes a medical statement made about the holder - for example their vaccination status.
12
14
13
-
This is schema 1.3.0:
15
+
An example of a DCC is:
14
16
15
17
{
16
18
"ver": "1.3.0",
@@ -41,7 +43,8 @@ The version number is stored in `ver` and it represents the version of the schem
41
43
42
44
"ver": "1.3.0"
43
45
44
-
The holder's name is stored in the element `nam`, `fn` contains the family name and `gn` contains the given name of the holder encoded in any UTF-8 alphabet character. The fields `fnt` and `gnt` contain the family name and given name respectively transliterated according to the [ICAO 9303 MRTD transliteration rules](https://www.icao.int/publications/Documents/9303_p3_cons_en.pdf).
46
+
The holder's name is stored in the element `nam`, `fn` contains the family name and `gn` contains the given name of the holder encoded in any UTF-8 alphabet character.
47
+
The fields `fnt` and `gnt` contain the family name and given name respectively transliterated according to the [ICAO 9303 MRTD transliteration rules](https://www.icao.int/publications/Documents/9303_p3_cons_en.pdf).
45
48
46
49
"nam": {
47
50
"fn": "Smith-Jones",
@@ -50,13 +53,17 @@ The holder's name is stored in the element `nam`, `fn` contains the family name
50
53
"gnt": "CHARLES<EDWARD"
51
54
}
52
55
53
-
The holder's date of birth is included in the `dob` element. It is date formatted according to ISO-8601 UTC and may contain either: `YYYY`, `YYYY-MM` or `YYYY-MM-DD`. This date must match the date the holder's identity document.
56
+
The holder's date of birth is included in the `dob` element.
57
+
It is date-formatted according to ISO-8601 UTC and may contain either: `YYYY`, `YYYY-MM` or `YYYY-MM-DD`.
58
+
This date must match the date the holder's identity document.
54
59
55
60
"dob": "1964-01-01"
56
61
57
-
In case the identity document contains `YYYY-XX-XX`, `YYYY-00-00` or other such partial dates, then only the known portion of the date should be encoded,
62
+
In case the identity document contains `YYYY-XX-XX`, `YYYY-00-00` or other such partial dates, then only the known portion of the date should be encoded.
58
63
59
-
The medical data is stored in an array containing a single element. The name of the array differs depending on the type of medical data. For vaccinations the array is `v`, for test it is `t` and for recovery it is `r`.
64
+
The medical data is stored in an array containing a single element.
65
+
The name of the array differs depending on the type of medical data.
66
+
For vaccinations, the array is `v`, for test it is `t`, and for recovery it is `r`.
60
67
61
68
There are a number elements that are shared by all of the medical data types:
62
69
@@ -69,6 +76,7 @@ There are a number elements that are shared by all of the medical data types:
69
76
70
77
The full certificate identifier specification can be found [here](https://ec.europa.eu/health/sites/default/files/ehealth/docs/vaccination-proof_interoperability-guidelines_en.pdf) and the official technical specifications for the EU-DCC schema is published [here](https://ec.europa.eu/health/sites/default/files/ehealth/docs/covid-certificate_json_specification_en.pdf).
71
78
79
+
72
80
## Test (PCR)
73
81
74
82
The test data is stored under the `t` element.
@@ -91,17 +99,18 @@ The fields which are unique to PCR tests are:
|`tt`| Test type | Value from the RAT TT valuset found on the gateway |
137
+
|`tt`| Test type | Value from the RAT TT valueset found on the Gateway|
129
138
|`ma`| Test device ID | RAT device id from the JRC DB, HSC common list valueset |
130
139
|`sc`| Sample date | ISO-8601 date/time formats (see below) |
131
-
|`tr`| Test result | Value from the PCR TT valuset found on the gateway |
140
+
|`tr`| Test result | Value from the PCR TT valueset found on the Gateway|
132
141
|`tc`| Test center | Actor who did the test, max 80 UTF-8 characters |
133
142
134
143
Extra information over the test device id:
135
144
136
-
In EU/EEA countries, issuers MUST only issue certificates for tests belonging to the currently valid value set. The value set MUST be updated every 24 hours.
145
+
In EU/EEA countries, issuers MUST only issue certificates for tests belonging to the currently valid value set.
146
+
The value set MUST be updated every 24 hours.
147
+
148
+
Values outside of the value set MAY be used in certificates issued by third countries, however the identifiers MUST still be from the JRC database.
149
+
The use of other identifiers such as those provided directly by test manufacturers is not permitted.
137
150
138
-
Values outside of the value set MAY be used in certificates issued by third countries, however the identifiers MUST still be from the JRC database. The use of other identifiers such as those provided directly by test manufacturers is not permitted.
139
151
140
152
## Recovery
141
153
@@ -161,10 +173,12 @@ The fields which are unique to recovery are:
161
173
|`df`| Date Valid From | ISO-8601, `YYYY-MM-DD`, > 11 days afer `fr`|
162
174
|`du`| Date Valid To | ISO-8601, `YYYY-MM-DD`, <= 180 days afer `fr`|
163
175
164
-
The recovery certificate can be issued for a person who has recovered from COVID-19, as proven by a positief NAAT/PCR test. To quote the legislation:
176
+
The recovery certificate can be issued for a person who has recovered from COVID-19, as proven by a positief NAAT/PCR test.
177
+
To quote the legislation:
165
178
166
179
"A certificate confirming that, following a positive result of a NAAT test carried out by health professionals or by skilled testing personnel the holder has recovered from a SARS-CoV-2 infection (certificate of recovery)."
167
180
181
+
168
182
## Vaccination
169
183
170
184
The vaccination data is stored under the `v` element.
@@ -188,14 +202,15 @@ The fields which are unique to a vaccination are:
|`vp`| Vaccination/prophylaxis | Value from the v/p valuset found on the gateway |
192
-
|`mp`| Medical product | Value from the v/p valuset found on the gateway |
193
-
|`ma`| Manufactorer/MAH | Value from the v/p valuset found on the gateway |
205
+
|`vp`| Vaccination/prophylaxis | Value from the v/p valueset found on the Gateway|
206
+
|`mp`| Medical product | Value from the v/p valueset found on the Gateway|
207
+
|`ma`| Manufactorer/MAH | Value from the v/p valueset found on the Gateway|
194
208
|`dn`| Dose number | Number of doses holder has received |
195
-
|`sd`| Total series | Number of doses in the full series, always >= `dn`|
209
+
|`sd`| Total series | Number of doses in the full series, always >= `dn`|
196
210
|`dt`| Date of event | ISO-8601 UTC, `YYYY-MM-DD`|
197
211
198
-
For vaccinations the record contains the details of the last vaccination event along with a sequence counter. The sequence counter identifies the vaccination count over the number of doses required for the vaccination.
212
+
For vaccinations the record contains the details of the last vaccination event along with a sequence counter.
213
+
The sequence counter identifies the vaccination count over the number of doses required for the vaccination.
199
214
200
215
For example, the sequence of Pfizer 1/2 will be encoded like this:
201
216
@@ -229,7 +244,7 @@ And the sequence Pfizer 2/2 is encoded like this:
229
244
230
245
In the cases that a person has received more than the standard sequence of doses, then the actual number of doses given will be provided, and `dn` will be equal to `sd`.
231
246
232
-
## Vaccine Boosters
247
+
###Vaccine Boosters
233
248
234
249
Booster vaccinations MUST be encoded as an additional dose in the sequence. For Pfizer this results in a sequence of 3/3, which is encoded like this:
235
250
@@ -248,13 +263,16 @@ Booster vaccinations MUST be encoded as an additional dose in the sequence. For
248
263
249
264
### Wait times
250
265
251
-
There is an issue regards wait time after last dose. Many countries consider a person "fully vaccinated" only 14 days after their last vaccination. For people who have received a booster dose, this will mean that there is a wait time before their booster DCC is accepted.
266
+
There is an issue regards wait time after last dose.
267
+
Many countries consider a person "fully vaccinated" only 14 days after their last vaccination.
268
+
For people who have received a booster dose, this will mean that there is a wait time before their booster DCC is accepted.
252
269
253
-
There are ? ways to handle this situation:
270
+
There are several ways to handle this situation:
254
271
255
272
* Issue multiple DCC, then the original complete vaccination can be used during the wait time.
256
273
* Educate citizens so that they know about the wait time.
0 commit comments