Generated Narrative: StructureDefinition DDCCCoreDataSetVS Name Flags Card. Type Description & Constraints DDCCCoreDataSet 0..* DDCCCoreDataSet This is an abstract type. Child types: DDCCCoreDataSetVSCoC, DDCCCoreDataSetVSPoV Elements defined in Ancestors:name, birthDate, identifier, certificate DDCC Core Data Set Logical Model for Vaccination Status #xD; certificate #xD; issuer 1..1 Reference(DDCC Organization) Certificate issuer #xD; vaccination Σ<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 ( who-ddcc-data-1 )">C 1..1 BackboneElement Vaccination Event Constraints: who-ddcc-data-1 #xD; vaccine Σ 1..1 Coding Vaccine or prophylaxis Binding: WHO Vaccine List (COVID-19) (preferred) #xD; brand Σ 1..1 Coding Vaccine brand #xD; manufacturer Σ 0..1 Coding Vaccine manufacturer #xD; maholder Σ 0..1 Coding Vaccine market authorization holder #xD; lot Σ 1..1 string Vaccine lot number #xD; date Σ 1..1 dateTime Date of vaccination #xD; validFrom 0..1 date Vaccination valid from #xD; dose Σ 1..1 positiveInt Dose number #xD; totalDoses 0..1 positiveInt Total doses #xD; country Σ 1..1 Coding Country of vaccination Binding: Iso3166-1-3 (preferred) #xD; centre 0..1 string Administering centre #xD; signature 0..1 Signature Signature of health worker #xD; <a href="StructureDefinition-DDCCCoreDataSetVS-definitions.html#DDCCCoreDataSet.vaccination.practitioner" title="OPTIONAL for DIGITAL and PAPER vaccination certificates. The unique identifier for the health worker as determined by the member state. There can be more than one unique identifier used. (e.g. system generated ID, health profession number, cryptographic signature, or any other form of health worker unique identifier). This can be used in lieu of a paper-based signature.">practitioner 0..1 Identifier Health worker identifier #xD; disease 0..1 Coding Disease or agent targeted Binding: WHO Disease or Agent Targeted (COVID-19) (preferred) #xD; nextDose 0..1 date Due date of next dose #xD; Documentation for this format
DDCC Core Data Set Logical Model for Vaccination Status
Data elements for the DDCC Core Data Set for Vaccination Status.
WHO Digital Documentation of COVID Certificates
The person's date of birth (DOB) if known. If unknown, use given DOB for administrative purposes
Unique identifier for the person, according to the policies applicable to each country. There can be more than one unique identifier used to link records. (e.g. national ID, health ID, immunization information system ID, medical record ID).
Metadata associated with the certificate
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
Key ID used to verify the signature of the certificate
If present, start SHALL have a lower value than end
start.hasValue().not() or end.hasValue().not() or (start <= end)
not(exists(f:start/@value)) or not(exists(f:end/@value)) or (xs:dateTime(f:start/@value) <= xs:dateTime(f:end/@value))
If the low element is missing, the meaning is that the low boundary is not known.
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
Manufacturer or Market Authorization Holder SHALL be present
manufacturer.exists() or maholder.exists()
Generic description of the vaccine or vaccine sub-type. e.g. COVID-19 mRNA vaccine, HPV vaccine.
The brand or trade name used to refer to the vaccine received.
Name of the manufacturer of the vaccine received. e.g. Serum institute of India, AstraZeneca. If vaccine manufacturer is unknown, market authorization holder is REQUIRED.
Name of the market authorization holder of the vaccine received. If market authorization holder is unknown, vaccine manufacturer is REQUIRED.
Lot number or batch number of vaccination.
Date upon which provided vaccination is considered valid.
Total expected doses as defined by Member State care plan and immunization programme policies.
The country in which the individual has been vaccinated.
The name or identifier of the vaccination facility responsible for providing the vaccination.
REQUIRED for PAPER vaccination certificates ONLY. The health worker who provided the vaccination or the supervising clinician's hand-written signature.
OPTIONAL for DIGITAL and PAPER vaccination certificates. The unique identifier for the health worker as determined by the member state. There can be more than one unique identifier used. (e.g. system generated ID, health profession number, cryptographic signature, or any other form of health worker unique identifier). This can be used in lieu of a paper-based signature.
Name of disease vaccinated against (such as COVID-19).
Date on which the next vaccination should be administered, if a next dose is REQUIRED.