The use cases outlined below are intended to provide additional context and frame the needs that the candidate standards must meet. The use cases here are summarized and excerpted from a discussion document of the HL7 v3 pan-Canadian Messaging Standards Implementation Guide (Volume 10 – Immunization).

The use cases identify different activities related to immunization events and access to an immunization record:

Table of Contents

UC-1 Record an Immunization Event

The purpose of this use case is to describe the activities involved in recording an immunization event.

Trigger: Immunization has been administered

  • A healthcare provider administers a vaccine to a patient.
  • The healthcare provider records the vaccination event in the local EMR System
  • The EMR sends a request to add the immunization event details to the repository.
  • The event is recorded in the repository and the message is acknowledged.

(The above flow represents a successful transaction, alternate flows exist.)

UC-2 Query an Immunization Repository

The purpose of this use case is to describe the activities involved in retrieving immunization records for a patient from a repository.

Trigger: Immunization information for a patient needs to be retrieved from an immunization repository.

  • A user of an EMR (or other client system) requests detailed information about a patient's immunization history, potentially filtered by:
    • time-range of the immunization, 
    • time-range the immunization was last updated, and/or
    •  type of immunization.
  • The EMR sends the query to the repository.
  • The repository returns the requested list of past immunization events.

(The above flow represents a successful transaction, alternate flows exist.)

UC-3 Update an Immunization Record

The purpose of this use case is to describe the activities involved in updating an immunization event.

Trigger: A healthcare provider needs to add additional information related to an immunization event to a record.

  • Healthcare provider wishes to update information related to a vaccination event:
    • additional information in the textual comment,
    • add/change the vaccine dose number, and/or
    • mark the immunization course as complete.
  • The healthcare provider records the vaccination event in the local EMR System
  • The EMR sends a request to update the immunization event details in the repository.
  • The update is recorded in the repository and the message is acknowledged.

(The above flow represents a successful transaction, alternate flows exist.)

UC-4 Retract an Immunization Record

The purpose of this use case is to describe the activities involved in retracting an erroneous immunization event.

Trigger: A healthcare provider identifies an erroneous immunization record.

  • Healthcare provider wishes to remove an erroneous immunization event from the patient's record.
  • The erroneous information is removed (or flagged as removed) in the local EMR system.
  • The EMR sends a request to remove the immunization event from the repository.
  • The record is removed (or flagged as removed) in the repository and the message is acknowledged.

(The above flow represents a successful transaction, alternate flows exist.)

  • No labels