Page History

The use cases outlined below are intended to provide additional context and frame the needs that candidate standards must meet. The use cases here are summarized and excerpted from a discussion document of the Canada Health Infoway Immunization Interoperability Working Group[1].

For a detailed use case list and required business rules please visit the Business Requirements space:

These use cases do not make any assumptions about the setting in which care is being delivered (e.g. primary care physician’s office, mobile immunization clinic, hospital, etc.) or the means by which providers record the information (e.g. desktop EMR software, mobile device, tablet, etc.).  It is preferred that .  Although some references to software applications are specific, the preferred candidate standards should, where possible, help to support and enable the delivery of care in any setting, and the viewing or recording of immunization data on any devicedifferent hardware devices.

UC-1

Patient or Delegate Retrieves Immunization History (

Yellow Card)

A provider reviews a patient’s immunization history for a purpose other than determining which vaccines a patient requires, examples:

• • History is required for proof of immunizations (i.e. to print a ‘Yellow Card’) or to determine immunity for differential diagnosis
  • Some applications may require that only a subset of vaccination history be returned/displayed (e.g. masking as a result of consent directives)

A patient views their own immunization history via a personal health record application

UC-2 View Immunization History (With Forecast)

A provider reviews a patient’s immunization history with a view to determining which vaccines the patient currently requires

• Once again, some applications may require that only a subset of vaccination history be returned/displayed  (e.g. masking as a result of consent directives)

A patient views their own immunization history via a personal health record application, and wishes to know which vaccines they currently require

UC-3 Administer Immunization and Record Event

A provider administers an immunization to a patient and records the immunization

• The record will likely include information regarding the provider who administered the immunization and the location
• Some applications may require the ability to record informed consent

A patient records and immunization that was administered to them in a personal health record application

UC-4 Record Immunization History

A provider records one or more past immunization events as part of a history taking

• The record will likely include information regarding the provider who administered the immunization and the location

user, typically a parent with a school age child, retrieves a patient's immunization history form the Immunization Connect Ontario (ICON) online or mobile application.

• User enters a patient's Ontario Immunization ID and PIN to request proof of immunization (Yellow Card) from ICON. 
• ICON (and related services):
  • authenticates request, 
  • queries panorama to retrieve patient immunization history, and
  • displays yellow card to user to print or download.

UC-2 Patient or Delegate Records Immunization History

A user, typically a parent with a school age child, enters a patient's immunization history into the Immunization Connect Ontario (ICON) online or mobile application.

• User enters information into ICON:
  • Identifying information about self (submitter),
  • Identifying information about patient, and
  • Information about one or more immunizations.
• ICON (and related services):
  • authenticates request, 
  • stores information for validation by Public Health.
• Health care provider or Public Health reviews and validates information in ICON and submits information to Panorama.  (Alternate flow on UC-4?)

UC-3 Health Care Provider Retrieves Immunization History

A health care provider retrieves a patient's immunization history using a clinical viewer, EMR or mobile application.

• User logs in to application, looks up patient and requests immunization history. 
• Application (and related services):
  • authenticates user using ONEID
  • queries panorama to retrieve patient immunization history, and
  • displays immunization history.

UC-4 Health Care Provider Records Immunization Event(s)

A health care provider enters information about a new immunization event using a clinical viewer, EMR or mobile application.

• User logs in to application, looks up patient and enters information about one or more immunization events. 
• Application (and related services):
  • authenticates user using ONEID, and
  • stores information about immunization event in Panorama.

UC-5 Update Existing Immunization Record

A A health care provider updates or changes an existing record of an immunization

A patient updates or changes an existing record of an immunization using a personal health record application

The information captured would be very similar to Administer Immunization and Record Event or Record Immunization History

a patient's immunization history using a clinical viewer, EMR or mobile application.

• User logs in to application, looks up patient and immunization history, updates information about an immunization event. 
• Application (and related services):
  • authenticates user using ONEID, and
  • stores information about the updated immunization event in Panorama.

UC-6 View Immunization History (With Forecast)

Extends reports in UC-1 and UC-3 to include information about the patient's outstanding and upcoming immunizations.