Skip to main content

​
Overview

The Immunization resource describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. At its minimum, Immunization contains vaccine code, date, reference to the patient and status of the immunization, but may also contain data about the administered vaccine including the manufacturer, lot number and expiration date. If an immunization was not given, this would be represented as:
  • Immunization.status = “not-done”
Each Immunization has next elements:
  • a status
  • a vaccine code that identifies the kind of vaccine administered
  • a date the vaccine was administered
  • a patient
Each Immunization must support:
  • a statusReason if the vaccine wasn’t given
Profile specific implementation guidance:
  • Use the status code: not-done to represent that an immunization was not given.
  • NDC codes as a translational data element: Based upon the 2015 Edition Certification Requirements, CVX vaccine codes are required and the NDC vaccine codes SHOULD be supported as translations to them. A NDC to CVX ConceptMap is provided and is based upon the CDC’s CVX crosswalk table. A translation is illustrated in the example below.
This resource conforms to USCDI v3 profile for Immunization - refer to StructureDefinition US Core Immunization. Immunization response will be provided in JSON (refers to Capability Statement) format as per FHIR standard R4 version.

​
Must support elements, mandatory and optional search parameters

Immunization must support these elements:
  • status
  • statusReason
  • vaccineCode
  • patient
  • occurrence[x]
  • primarySource
The following search parameters and search parameter combinations SHALL be supported: The syntax used to describe the interactions is described here. SHALL support searching for all immunizations for a patient using the patient search parameter: GET [base url]/Immunization?patient={Type/}[id] The following search parameters and search parameter combinations SHOULD be supported: SHOULD support searching using the combination of the patient and date search parameters:
  • including support for these date comparators: gt,lt,ge,le
  • including optional support for AND search on date (e.g.date=[date]&date=[date]]&…) GET [base url]/Immunization?patient={Type/}[id]&date=[date]
SHOULD support searching using the combination of the patient and status search parameters: GET [base url]/Immunization?patient={Type/}[id]&status={system|}[code] The response to any search operation is always a list of resources in a Bundle or an Operation Outcome.

​
Immunization By Patient Id

Search for immunizations by patient id. METHOD GET
PARAMS [base url] - FHIR base url [id] - Id for the Patient HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Immunization By Id

Get Immunization by ID. METHOD GET
or
PARAMS [base url] - FHIR base url {id} - Id of Immunization resource HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Immunization By patient and date search parameters

Get Immunization by combination of the patient and date search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient [date] - immunization date HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Immunization by patient and status search parameters

Get Immunization by combination of the patient and status search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient {system|} - terminology system used to define immunization status code [code] - status of immunization HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE: