Generated Narrative: StructureDefinition HCertDCC Name Flags Card. Type Description & Constraints <a href="StructureDefinition-HCertDCC-definitions.html#HCertDCC" title="Data elements for the EU Digital COVID Certificate Core Data Set. Based on the official specification for COVID-19-related payloads <https://health.ec.europa.eu/system/files/2021-06/covid-certificate_json_specification_en_0.pdf> as of 2023-01-31, and Implementing Decision (EU) 2021/1073, Annex 1 <https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32021D1073&from=EN#d1e34-35-1>.">HCertDCC 0..* Base This is an abstract type. Payload for Certificate - EU DCC CBOR Web Token Logical Model #xD; 1 1..1 BackboneElement EU Digital COVID Certificate v1 #xD; ver 1..1 string Schema version #xD; nam 1..1 BackboneElement Person name #xD; fn 0..1 string Surname/family name (separate multiple with spaces) #xD; fnt 1..1 string Standardised surname #xD; gn 0..1 string Forename/given name. Skip if no given name. Separate with spaces. #xD; gnt 0..1 string Standardised forename, same approach as fnt. Skip if no given name. #xD; dob 0..1 date Date of birth in YYYY-MM-DD format. Skip if missing. Fill unknown months or days with 'XX'. #xD; v <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( OnlyOneAllowed )">C 0..* BackboneElement Vaccination Group (see element details) Constraints: OnlyOneAllowed #xD; tg 1..1 string Disease or agent targeted (SNOMED CT GPS code for COVID-19 or variant; see element details) #xD; <a href="StructureDefinition-HCertDCC-definitions.html#HCertDCC.1.v.vp" title="Preferred Code System: SNOMED CT or ATC Classification. Examples of codes that should be used from the preferred code systems are the SNOMED CT code 1119305005 (SARS-CoV-2 antigen vaccine), 1119349007 (SARS-CoV-2 mRNA vaccine) or J07BX03 (covid-19 vaccines). The value set should be extended when new vaccine types are developed and put into use.">vp 1..1 string Vaccine or prophylaxis (e.g., 'SARS-CoV-2 mRNA vaccine'; SNOMED or ATC; see element details) #xD; <a href="StructureDefinition-HCertDCC-definitions.html#HCertDCC.1.v.mp" title="Preferred Code Systems (in the order of preference):#xA;#xA;- Union Register of medicinal products for vaccines with EU-wide authorisation (authorisation numbers) - for example, `EU/1/20/1528` (Comirnaty)#xA;- A global vaccine register such as one that could be established by the World Health Organisation#xA;- Name of the vaccine medicinal product in other cases. If the name includes whitespaces, these should be replaced by a hyphen (-). For example, `Sputnik-V` (standing for Sputnik V).">mp 1..1 string Vaccine product (e.g., 'EU/1/20/1528 (Comirnaty)'; see element details) Binding: Vaccine - COVID-19 - EU Union Register of Medicinial Products (preferred) #xD; <a href="StructureDefinition-HCertDCC-definitions.html#HCertDCC.1.v.ma" title="Preferred Code System:#xA;#xA;- Organisation code from EMA (SPOR system for ISO IDMP)#xA;- A global vaccine marketing authorisation holder or manufacturer register, such as one that could be established by the World Health Organisation#xA;- Name of the organisation in other cases.#xA;#xA;If the name includes whitespaces, these should be replaced by a hyphen (-).If marketing authorisation holder is not available, this will be the manufacturer.">ma 1..1 string Vaccine marketing authorisation holder or manufacturer (e.g., 'ORG-100030215' (Biontech Manufacturing GmbH)) #xD; dn 1..1 positiveInt Number in a series of doses #xD; sd 1..1 positiveInt The overall number of doses in the series #xD; dt 1..1 date Date of vaccination, YYYY-MM-DD format #xD; co 1..1 string Country where vaccine was administered (two letter ISo-3166) Binding: Iso3166-1-2 (preferred) #xD; is 1..1 string Certificate issuer (organization name) #xD; ci 1..1 string Unique certificate identifier (UVCI) #xD; t <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( OnlyOneAllowed )">C 0..* BackboneElement Test Group Constraints: OnlyOneAllowed #xD; tg 1..1 string Disease or agent targeted (SNOMED CT GPS code for COVID-19 or variant; see element details) Binding: Lab Test - Pathogen - COVID-19 - SNOMED CT (preferred) #xD; tt 1..1 string Type of test (LOINC code; see element details) Binding: Lab Test - Type - Generic - LOINC (preferred) #xD; nm 0..1 string Name of the nucleic acid amplification test (NAAT) used #xD; ma 0..1 string Rapid antigen test (RAT) device identifier from the JRC database #xD; sc 1..1 dateTime Date and time when test sample was collected in ISO 8601 format #xD; <a href="StructureDefinition-HCertDCC-definitions.html#HCertDCC.1.t.tr" title="The codes selected shall allow distinguishing between positive and negative test results (detected or not detected). Additional values (like undetermined) may be added if the use cases do require this.#xA;#xA;Examples of codes that should be used from the preferred code system are `260415000` (Not detected) and `260373001` (Detected).">tr 1..1 string Result of the test (preferred: SNOMED CT GPS code) Binding: Lab Test - Qualitative Result - SNOMED CT (preferred) #xD; tc 0..1 string Testing centre or facility #xD; co 1..1 string Country of test (two letter ISo-3166) Binding: Iso3166-1-2 (preferred) #xD; is 1..1 string Certificate issuer #xD; ci 1..1 string Unique Certificate Identifier (UVCI) #xD; r <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( OnlyOneAllowed )">C 0..* BackboneElement Recovery Group Constraints: OnlyOneAllowed #xD; tg 1..1 string Disease or agent targeted (SNOMED CT GPS code for COVID-19 or variant) #xD; fr 1..1 date 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). #xD; co 1..1 string Country of test (two letter ISo-3166) Binding: Iso3166-1-2 (preferred) #xD; is 0..1 string Certificate issuer #xD; df 1..1 date The first date on which the certificate is considered to be valid, in YYYY-MM-DD format (complete date without time). #xD; du 1..1 date The last date on which the certificate is considered to be valid, assigned by the certificate issuer, in YYYY-MM-DD format (complete date without time). #xD; ci 1..1 string Unique certificate identifier (UVCI) #xD; Documentation for this format
Payload for Certificate - EU DCC CBOR Web Token Logical Model
Data elements for the EU Digital COVID Certificate Core Data Set. Based on the official specification for COVID-19-related payloads <https://health.ec.europa.eu/system/files/2021-06/covid-certificate_json_specification_en_0.pdf> as of 2023-01-31, and Implementing Decision (EU) 2021/1073, Annex 1 <https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32021D1073&from=EN#d1e34-35-1>.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Surname/family name (separate multiple with spaces)
Example from spec: "Musterfrau-Gößinger Müller"
"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 MUST be provided, only including characters A-Z and <. Maximum length: 80 characters (as per ICAO 9303 specification)."
Forename/given name. Skip if no given name. Separate with spaces.
Standardised forename, same approach as fnt. Skip if no given name.
Date of birth in YYYY-MM-DD format. Skip if missing. Fill unknown months or days with 'XX'.
According to the spec, "Vaccination group, if present, MUST contain exactly 1 (one) entry describing exactly one vaccination event. All elements of the vaccination group are mandatory, empty values are not supported." It appears this means the maximum cardinality of the `v` element is 1, and all sub-elements have minimum cardinality of 1.
Only one allowed (cardinality of 0..* is necessary because this element is an array in the EU DCC JSON).
Disease or agent targeted (SNOMED CT GPS code for COVID-19 or variant; see element details)
The selected codes shall refer to COVID-19 or, if more detailed information on the genetic variant of SARS-CoV-2 is needed, to these variants if such detailed information is needed due to epidemiological reasons. Example of a code that should be used is the SNOMED CT code `840539006` (COVID-19).
Vaccine or prophylaxis (e.g., 'SARS-CoV-2 mRNA vaccine'; SNOMED or ATC; see element details)
Preferred Code System: SNOMED CT or ATC Classification. Examples of codes that should be used from the preferred code systems are the SNOMED CT code 1119305005 (SARS-CoV-2 antigen vaccine), 1119349007 (SARS-CoV-2 mRNA vaccine) or J07BX03 (covid-19 vaccines). The value set should be extended when new vaccine types are developed and put into use.
Vaccine product (e.g., 'EU/1/20/1528 (Comirnaty)'; see element details)
Preferred Code Systems (in the order of preference): - Union Register of medicinal products for vaccines with EU-wide authorisation (authorisation numbers) - for example, `EU/1/20/1528` (Comirnaty) - A global vaccine register such as one that could be established by the World Health Organisation - Name of the vaccine medicinal product in other cases. If the name includes whitespaces, these should be replaced by a hyphen (-). For example, `Sputnik-V` (standing for Sputnik V).
Vaccine marketing authorisation holder or manufacturer (e.g., 'ORG-100030215' (Biontech Manufacturing GmbH))
Preferred Code System: - Organisation code from EMA (SPOR system for ISO IDMP) - A global vaccine marketing authorisation holder or manufacturer register, such as one that could be established by the World Health Organisation - Name of the organisation in other cases. If the name includes whitespaces, these should be replaced by a hyphen (-).If marketing authorisation holder is not available, this will be the manufacturer.
The overall number of doses in the series
Country where vaccine was administered (two letter ISo-3166)
"Test group, if present, MUST contain exactly 1 (one) entry describing exactly one test result."
Type of test (LOINC code; see element details)
The codes in this value set shall refer to the method of the test and shall be selected at least to separate the NAAT tests from RAT tests as expressed in Regulation (EU) 2021/953. An example of a code that should be used from the preferred code system is LP217198-3 (Rapid immunoassay).
Name of the nucleic acid amplification test (NAAT) used
From the spec: "The name should include the name of the test manufacturer and the commercial name of the test, separated by a comma." Omit element for RAT test. MUST not be empty.
Rapid antigen test (RAT) device identifier from the JRC database
Date and time when test sample was collected in ISO 8601 format
Result of the test (preferred: SNOMED CT GPS code)
The codes selected shall allow distinguishing between positive and negative test results (detected or not detected). Additional values (like undetermined) may be added if the use cases do require this. Examples of codes that should be used from the preferred code system are `260415000` (Not detected) and `260373001` (Detected).
Required for NAAT tests. Optional for RAT tests. MUST not be empty (omit instead).
"Recovery group, if present, MUST contain exactly 1 (one) entry describing exactly one recovery statement."
Disease or agent targeted (SNOMED CT GPS code for COVID-19 or variant)
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).
The first date on which the certificate is considered to be valid, in YYYY-MM-DD format (complete date without time).
The last date on which the certificate is considered to be valid, assigned by the certificate issuer, in YYYY-MM-DD format (complete date without time).