Generated Narrative: StructureDefinition CertICAO Name Flags Card. Type Description & Constraints <a href="StructureDefinition-CertICAO-definitions.html#CertICAO" title="Data elements for the ICAO Visible Digital Seal Core Data Set. Based on <https://www.icao.int/vdsnc-spec> as of 2023-02-02.">CertICAO 0..* Base This is an abstract type. Certificate - ICAO Visible Digital Seal Logical Model #xD; data 1..1 BackboneElement Data #xD; hdr 1..1 BackboneElement Header #xD; t 1..1 string Type (either `icao.test` for proof of testing, or `icao.vacc` for proof of vaccination) #xD; v 1..1 integer Version #xD; is 1..1 string IssuingCountry (ISO-3166 three letter code; see element details) Binding: Iso3166-1-3 (required) #xD; msg 1..1 BackboneElement Message #xD; pid 1..1 BackboneElement PersonalInformation (more info in element description) #xD; n 1..1 string Name (Name of the holder (as specified in Doc 9303-3) MUST be used.) #xD; dob 0..1 date Date of Birth (The DOB of the test subject. The [RFC 3339] full date format YYYY-MM- DD MUST be used.) #xD; <a href="StructureDefinition-CertICAO-definitions.html#CertICAO.data.msg.pid.dt" title="The ID Document Type of the identity document MUST be used. Only these values MUST be used:#xA;#xA;- `P` – Passport (Doc 9303-4)#xA;- `A` – ID Card (Doc 9303-5)#xA;- `C` – ID Card (Doc 9303-5)#xA;- `I` – ID Card Doc 9303-5)#xA;- `AC` - Crew Member Certificate (Doc 9303-5)#xA;- `V` – Visa (Doc 9303-7)#xA;- `D` – Driving License (ISO 18013-1)">dt 0..1 string ID Document Type of the identity document (see element details) #xD; dn 1..1 string ID Document Number of the identity document #xD; i 0..1 string Travel Document Number #xD; ai 0..1 string Other Document Number #xD; sex 0..1 string Sex of the test subject (as specified in Doc 9303-4 Section 4.1.1.1 – Visual Inspection Zone) #xD; utci 0..1 string UTCI (Unique Test Certificate Identifier; used for `icao.test` only, not used of `icao.vacc`) #xD; sp 0..1 BackboneElement ServiceProvider (Required for `icao.test` only, not used of `icao.vacc`) #xD; spn 1..1 string Name of testing facility or service provider #xD; ctr 1..1 string Country of test (spec does not indicate code system, but presumably this is ISO-3166 like the other country codes in the certificate) #xD; cd 1..1 BackboneElement ContactDetails #xD; p 1..1 string PhoneNumber #xD; e 1..1 string Email #xD; a 1..1 string Address #xD; dat 0..1 BackboneElement DateTimeTestReport (Required for `icao.test` only, not used of `icao.vacc`) #xD; sc 1..1 dateTime SpecimenCollection (RFC3339) #xD; ri 1..1 dateTime ReportIssuance (RFC3339) #xD; tr 0..1 BackboneElement TestResult (Required for `icao.test` only, not used of `icao.vacc`) #xD; tc 1..1 string TestConducted Binding: Lab Test - Type - ICAO (required) #xD; r 1..1 string Results Binding: Lab Test - Qualitative Result - ICAO (required) #xD; m 0..1 string Sampling method Binding: Lab Test - Sample Origin - ICAO (required) #xD; opt 0..1 string Optional data issued at the discretion of the issuing authority #xD; uvci 0..1 string Unique Vaccination Certificate Identifier (Required for `icao.vacc` only, not used of `icao.test`) #xD; ve 0..* BackboneElement VaccinationEvent (Required for `icao.vacc` only, not used of `icao.test`) #xD; des 1..1 string Vaccine or Prophylaxis (ICD-11 MMS code descending from http://id.who.int/icd/entity/164949870) Binding: WHO Vaccine List (COVID-19) (required) #xD; nam 1..1 string Vaccine Brand (medical product name) #xD; dis 0..1 string Disease or agent targeted (ICD-11 code) #xD; vd 1..* BackboneElement VaccinationDetails #xD; dvc 1..1 date Date of vaccination (see element details) #xD; seq 1..1 positiveInt Dose number (vaccine dose number, integer between 1 and 99) #xD; ctr 1..1 string Country of vaccination (ISO-3166 three letter code; see element details) Binding: Iso3166-1-3 (required) #xD; adm 1..1 string Administering centre (The name or identifier of the vaccination facility) #xD; lot 1..1 string Vaccine batch number #xD; dvn 0..1 date Due date of next dose (see element details) #xD; sig 0..1 BackboneElement Signature #xD; alg 1..1 string SignatureAlgo #xD; cer 1..1 string Certificate (X.509 signer certificate in base64url [RFC 4648]) #xD; sigvl 1..1 string SignatureValue (Signature value signed over the Data in base64url [RFC 4648]) #xD; Documentation for this format
Certificate - ICAO Visible Digital Seal Logical Model
Data elements for the ICAO Visible Digital Seal Core Data Set. Based on <https://www.icao.int/vdsnc-spec> as of 2023-02-02.
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
Type (either `icao.test` for proof of testing, or `icao.vacc` for proof of vaccination)
IssuingCountry (ISO-3166 three letter code; see element details)
The three letter code is according to Doc 9303-3, which defines this as ISO-3166 country codes.
PersonalInformation (more info in element description)
`pid.n`, `pid.dob`, `pid.dt`, and `pid.dn` are required for the `icao.test` type. `pid.n` and either `pid.i` or `pid.dob` are required for the `icao.vacc` type. Cardinalities in the logical model for these elements are set to `0..1` to accommodate the different schemas for the two different credential types.
Name (Name of the holder (as specified in Doc 9303-3) MUST be used.)
Date of Birth (The DOB of the test subject. The [RFC 3339] full date format YYYY-MM- DD MUST be used.)
ID Document Type of the identity document (see element details)
The ID Document Type of the identity document MUST be used. Only these values MUST be used: - `P` – Passport (Doc 9303-4) - `A` – ID Card (Doc 9303-5) - `C` – ID Card (Doc 9303-5) - `I` – ID Card Doc 9303-5) - `AC` - Crew Member Certificate (Doc 9303-5) - `V` – Visa (Doc 9303-7) - `D` – Driving License (ISO 18013-1)
ID Document Number of the identity document
Sex of the test subject (as specified in Doc 9303-4 Section 4.1.1.1 – Visual Inspection Zone)
UTCI (Unique Test Certificate Identifier; used for `icao.test` only, not used of `icao.vacc`)
ServiceProvider (Required for `icao.test` only, not used of `icao.vacc`)
Name of testing facility or service provider
Country of test (spec does not indicate code system, but presumably this is ISO-3166 like the other country codes in the certificate)
DateTimeTestReport (Required for `icao.test` only, not used of `icao.vacc`)
TestResult (Required for `icao.test` only, not used of `icao.vacc`)
Optional data issued at the discretion of the issuing authority
Unique Vaccination Certificate Identifier (Required for `icao.vacc` only, not used of `icao.test`)
VaccinationEvent (Required for `icao.vacc` only, not used of `icao.test`)
Vaccine or Prophylaxis (ICD-11 MMS code descending from http://id.who.int/icd/entity/164949870)
Date of vaccination (see element details)
Date on which the vaccine was administered. The ISO8601 full date format YYYY-MM-DD MUST be used.
Dose number (vaccine dose number, integer between 1 and 99)
Country of vaccination (ISO-3166 three letter code; see element details)
The country in which the individual has been vaccinated. A three letter code identifying the issuing state or organization. The three letter code is according to Doc 9303-3, which defines this as ISO-3166 country codes.
Administering centre (The name or identifier of the vaccination facility)
Due date of next dose (see element details)
Date on which the next 10 vaccination should be administered. The ISO8601 full date format YYYY-MM-DD MUST be used.
Certificate (X.509 signer certificate in base64url [RFC 4648])
SignatureValue (Signature value signed over the Data in base64url [RFC 4648])