Generated Narrative: StructureDefinition CertDIVOC Name Flags Card. Type Description & Constraints <a href="StructureDefinition-CertDIVOC-definitions.html#CertDIVOC" title="Data elements for the DIVOC Core Data Set.#xA;#xA;The official DIVOC documentation appears to be at <https://divoc.digit.org>. However, this does not include a full list of elements included in DIVOC certificates.#xA;#xA;There is a JSON-LD context referenced in DIVOC certificate examples (`https://cowin.gov.in/credentials/vaccination/v1`), which would provide some element-level information, but this URL does not resolve. There is a copy of this JSON-LD context at <https://github.com/egovernments/DIVOC/blob/main/vaccination-context/vaccination-context.js>.#xA;#xA;It was not possible to find any online documentation regarding DIVOC proof of testing. Information on this was provided by the DIVOC team via email.#xA;#xA;Some element descriptions in this logical model provide details that are not in publicly available DIVOC documentation.">CertDIVOC 0..* Base This is an abstract type. Certificate - DIVOC Verifiable Credential Logical Model #xD; context 1..* string Context (JSON-LD) - should actually be `@context` but this name isn't supported by FHIR. #xD; type 1..* string Type #xD; issuer 1..1 string Issuer identifier #xD; issuanceDate 1..1 dateTime issuanceDate #xD; nonTransferable 0..1 boolean Non Trasnferability #xD; credentialSubject 1..1 BackboneElement CredentialSubject #xD; type 1..* string type #xD; uhid 0..1 string another id #xD; refId 0..1 string reference id #xD; name 0..1 string A name associated with the patient #xD; gender 0..1 string Gender (`Male` or `Female`; unknown if there are other options) #xD; sex 0..1 string Sex (not used in examples; presumably `Male` or `Female`; unknown if there are other options) #xD; age 0..1 string Age #xD; dob 0..1 date The date of birth for the individual (V2 only) #xD; nationality 0..1 string Nationality #xD; address 0..1 BackboneElement Address #xD; streetAddress 0..1 string Line 1 of the address #xD; streetAddress2 0..1 string Line 2 of the address #xD; district 0..1 string District name (aka county) #xD; city 0..1 string Name of city, town etc. #xD; addressRegion 0..1 string Sub-unit of country (abbreviations ok) #xD; addressCountry 0..1 string Country (e.g. may be ISO 3166 2 or 3 letter code) #xD; postalCode 0..1 string Postal code for area #xD; evidence 0..* BackboneElement Evidence #xD; feedbackUrl 0..1 string URL for feedback #xD; infoUrl 0..1 string URL for more information on this record #xD; certificateId 0..1 string Certificate Unique Identifier #xD; type 1..* string type #xD; batch 0..1 string Vaccine lot number #xD; vaccine 0..1 string Vaccine description. Might include vaccine type and brand #xD; manufacturer 0..1 string Name of the Vaccine/Test Manufacturer #xD; date 0..1 dateTime Date of immunization #xD; effectiveStart 0..1 date Effective immunization start date #xD; effectiveUntil 0..1 date Effective immunization end date #xD; dose 0..1 positiveInt Dose Number #xD; totalDoses 0..1 positiveInt Total doses for this vaccine protocol regimen #xD; verifier 0..1 BackboneElement Verifier #xD; name 0..1 string Name of the practitioner #xD; facility 0..1 BackboneElement Facility #xD; name 0..1 string Name of the facility/entity #xD; address 0..1 Address Address of the facility #xD; streetAddress 0..1 string Line 1 of the address #xD; streetAddress2 0..1 string Line 2 of the address #xD; district 0..1 string District name (aka county) #xD; city 0..1 string Name of city, town etc. #xD; addressRegion 0..1 string Sub-unit of country (abbreviations ok) #xD; addressCountry 0..1 string Country (e.g. may be ISO 3166 2 or 3 letter code) Binding: Iso3166-1-3 (preferred) #xD; postalCode 0..1 string Postal code for area #xD; icd11Code 0..1 string ICD-11 code of this vaccine type (no binding information in spec) Binding: WHO Vaccine List (COVID-19) (preferred) #xD; prophylaxis 0..1 string Descriptive details of the vaccine type #xD; testName 0..1 string Lab test results: Test name #xD; testType 0..1 string Lab test results: Type of test, either `RT-PCR` or `Rapid Antigen Test (RAT)` Binding: Lab Test - Type - DIVOC (required) #xD; sampleOrigin 0..1 string Lab test results: Type of sample that was taken (e.g., `nasal swab` Binding: Lab Test - Sample Origin - DIVOC (required) #xD; disease 0..1 string Lab test results: Disease or agent targeted Binding: Lab Test - Pathogen - DIVOC (required) #xD; sampleCollectionTimestamp 0..1 dateTime Lab test results: Sample collection date and time; complete date, with time and time zone, following ISO 8601 #xD; resultTimestamp 0..1 dateTime Lab test results: Results date and time; complete date, with time and time zone, following ISO 8601 #xD; result 0..1 string Lab test results: result of test Binding: Lab Test - Qualitative Result - DIVOC (required) #xD; proof 1..* BackboneElement Proof #xD; type 0..1 string Type of proof #xD; created 0..1 dateTime Signature date and time #xD; verificationMethod 1..1 string Resolvable issuer identifier #xD; proofPurpose 0..1 string Purpose of the signature #xD; jws 1..1 string Signature #xD; Documentation for this format
Certificate - DIVOC Verifiable Credential Logical Model
Data elements for the DIVOC Core Data Set. The official DIVOC documentation appears to be at <https://divoc.digit.org>. However, this does not include a full list of elements included in DIVOC certificates. There is a JSON-LD context referenced in DIVOC certificate examples (`https://cowin.gov.in/credentials/vaccination/v1`), which would provide some element-level information, but this URL does not resolve. There is a copy of this JSON-LD context at <https://github.com/egovernments/DIVOC/blob/main/vaccination-context/vaccination-context.js>. It was not possible to find any online documentation regarding DIVOC proof of testing. Information on this was provided by the DIVOC team via email. Some element descriptions in this logical model provide details that are not in publicly available DIVOC documentation.
Context (JSON-LD) - should actually be `@context` but this name isn't supported by FHIR.
Date and time when a credential becomes valid
indicates that a verifiable credential must only be encapsulated into a verifiable presentation whose proof was issued by the credentialSubject
Contains claims about one or more objects (Patients)
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
Gender (`Male` or `Female`; unknown if there are other options)
Sex (not used in examples; presumably `Male` or `Female`; unknown if there are other options)
The date of birth for the individual (V2 only)
Country (e.g. may be ISO 3166 2 or 3 letter code)
Type of evidence record. Generally `Vaccination` or `TestDetails`
Vaccine description. Might include vaccine type and brand
Total doses for this vaccine protocol regimen
Practitioner that oversaw the application
Facility where the immunization took place
home | work | temp | old | billing - purpose of this address
Applications can assume that an address is current unless it explicitly says that it is temporary or old.
Allows an appropriate address to be chosen from a list of many.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the [Location](http://hl7.org/fhir/R4/location.html#) resource).
The type of an address (physical / postal).
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
XAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6
Street name, number, direction & P.O. Box etc.
This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.
The order in which lines should appear in an address label
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes).
Country (e.g. can be ISO 3166 2 or 3 letter code)
Country - a nation as commonly understood or generally accepted.
ISO 3166 3 letter codes can be used in place of a human readable country name.
Allows addresses to be placed in historical context.
ICD-11 code of this vaccine type (no binding information in spec)
The specification for DIVOC does not provide any information beyond that this is an ICD-11 code, so correspondingly there is no required binding to a specific ValueSet in this logical model.
Lab test results: Type of test, either `RT-PCR` or `Rapid Antigen Test (RAT)`
Lab test results: Type of sample that was taken (e.g., `nasal swab`
Lab test results: Disease or agent targeted
Lab test results: Sample collection date and time; complete date, with time and time zone, following ISO 8601
Lab test results: Results date and time; complete date, with time and time zone, following ISO 8601
One or more cryptographic proofs that can be used to detect tampering and verify the authorship of a credential or presentation
Clearly expresses the purpose for the proof and ensures this information is protected by the signature