This is the base resource type for everything.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

The business identifier(s) for the immunization entry - This is an optional attribute, used for example to track an entry throughout its lifecycle, or across vaults.

The status of the immunization record entry - whether it is active, entered in error, etc.

Supporting reason for status information.....

The patient that has received the immunization.

The target of the immunization - the disease that the immunization action is protecting against. This should be a coded value.

The date and/or time when the immunization administration has been recorded

The patient-specific order or recommendation for the immunization, for example a prescription or a request for immunization for a patient by a physician, for example for optional vaccines.

The vaccination plan or protocol (not patient-specific) that this immunization is fulfilling. For example 'Basisvaccinatieschema'

The type of immunization action - for example first dose or reinforcement.

The professional that recorded the administration of the vaccine.

The date and time when the administration of the vaccine was recorded - typically used when the vaccine event is recorded a posteriori.

The professional that administered the medication.

The route of administration for the vaccine. This can be free text (not desired) or a code

The lot number

The expiration date of the product.

The location where the immunization administration was performed. This can be a text (e.g. 'at the physician's office' or a code e.g. '00078' meaning 'patient's home' or a resource (Location) if one exists e.g. 'Location/kind-en-gezin-092375' which could be defining 'Kind en Gezin Gent Koepoortkaai'

Additional notes for the immunization