Immunization Content

From IHE Wiki
Jump to navigation Jump to search

The Immunization Content Profile describes the content and format of documents for exchange of immunization data.


The Immunization Content Profile provides a standard document to exchange immunization data among multiple systems belonging to a single or multiple organizations. Common data formats are providing to exchange immunization data only as well as exchanging immunization data along with medical summary data to provide information to care givers that is relevant to the overall care of a patient related to immunizations. The systems between which data is shared often include Electronic Health Record systems (EHRs), Health Information Exchanges (HIEs), and Personal Health Records (PHRs).

PCC IC diagram.png


<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>

  • Participation in an Immunization Information System (IIS) automates workflows of clinicians, saving time and reducing potential for data entry errors.
  • Provides a "yellow card" for parents and guardians of minors, reducing friction associated with acquiring child immunization records for purposes such as school enrollment.
  • Availability of immunization data in a patient's Personal Health Record (PHR) account, providing opportunities for the patient to better manage their own healthcare.
  • Integration with an immunization forecasting service that accepts the IC document as a payload to facilitate automated immunization recommendations.


<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>

<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>

<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>

Systems Affected

<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>

Actors & Transactions:

PCC Share Content Diagram.png



Profile Status: Final Text


<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

Underlying Standards:

  • HL7 CDAR2

See Also

Related Profiles

  • Cross-Enterprise Document Sharing (XDS)
  • Cross-Enterprise Reliable Document Interchange (XDR)
  • Cross-Enterprise Document Media Interchange (XDM)
  • Request for Clinical Guidance (RCG)
  • Notification of Availability (NAV)
  • Document Digital Signature (DSG)

Reference Articles

This page is based on the Profile Overview Template