8 February, 2016
Use Case Diagram Documentation
Page: 1
PHER Immunization DAM Use Case View-- Release 11
This document illustrates the use cases and actors associated with immunizations. It is
built from story boards submitted by PHER members and from existing Version 2 and
Version 3 HL7 artefacts. Input was gathered from the American Immunization Registry
Association. The story boards are available in the PHER wiki.
System View Use Case Release 11 - (Use Case diagram)
This diagram illustrates the relationships between major systems and activities. Each package contains diagrams
which include the actors and use cases required to support the goals of the parent package.
8 February, 2016
Use Case Diagram Documentation
Figure: 1
System View Use Case Release 11 Elements:
Page: 2
8 February, 2016
Use Case Diagram Documentation
Page: 3
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A02: Patient
A patient is a person receiving health care. In our models, this is generally related to immunization.
A04: Provider
A provider is a person providing health care, that is a clinician.
A10: Distributor
This actor distributes vaccine from manufacturer to end users.
A12: Electronic Health Record System
An electronic health record system is an information system which contains patient's medical records.
A13: Health Information Exchange
This actor acts as a hub to facilitate access to consolidated health records from multiple sources.
A17: PHR system
This is the Personal Health Record system. It houses a health record owned and maintained by the person
it is about.
A18: Government Payor
Vaccine is often paid for with public funds. This actor is involved in both paying and assurance of correct
usage of vaccines.
Clinical Care
This package contains use cases related to clinical care and immunization.
Clinical Decision Support
This package contains use cases related to immunization CDS. It does not contain use cases related to
schedule development.
Manage Adverse Event Reporting
8 February, 2016
Use Case Diagram Documentation
This package contains use cases to reporting of adverse events.
Manage Immunization History
This package contains use cases related to recording, updating and retrieving immunization history.
Manage Patient identity
This package contains use cases related to managing patient identify and demographics.
Manage Reports
This package contains use case related to a wide variety of reports.
Manage schedule
This package contains use case related to creating and maintaining immunization schedule rules.
Manage Vaccine Inventory
This package contains use cases supporting Vaccine inventory management.
Clinical Care - (Use Case diagram)
This diagram shows the clinical care activities related to immunization.
Page: 4
8 February, 2016
Use Case Diagram Documentation
Page: 5
uc Clinical Care
UC11.20.0 Ev aluate
patient
A02: Patient
UC11.18.0 Administer
Vaccine
A04: Prov ider
UC11.19.0 Record
clinical care
Figure: 2
Clinical Care Elements:
A02: Patient
A patient is a person receiving health care. In our models, this is generally related to immunization.
A04: Provider
A provider is a person providing health care, that is a clinician.
UC11.18.0 Administer Vaccine
The goal of this use case is to administer vaccine to a patient.
UC11.19.0 Record clinical care
The goal of this use case is to record clinical care, usually in EHR. We do not go into great depth here as
that is part of another Domain Analysis Model.
UC11.20.0 Evaluate patient
8 February, 2016
Use Case Diagram Documentation
Page: 6
The goal of this use case is to evaluate a patient's condition in order to determine if immunization is
appropriate. We will not elaborate as this belongs in another Domain Analysis model.
Clinical Decision Support - (Use Case diagram)
This diagram shows the use cases and actors participating in Clinical Decisions Support.
uc Clinical Decision Support
UC11.10.0 Request
CDS
A01: Immunization
Information System
A14: Ev aluation/forecast
prov ider
UC11.11.0 Return
CDS
Figure: 3
Clinical Decision Support Elements:
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A14: Evaluation/forecast provider
This actor evaluates a patient's immunization history and other factors and produces a forecast of next
doses due. It also returns the evaluation of the history.
UC11.10.0 Request CDS
8 February, 2016
Use Case Diagram Documentation
Page: 7
The goal of this use case is to request clinical decision support (evaluation and forecast) for a given patient.
We assume that the pertinent immunization history is supplied to support this request.
UC11.11.0 Return CDS
The goal of this use case is to return an evaluated immunization history and forecast of next doses due. We
assume that an immunization history is available for the patient in question.
Manage Adverse Event Reporting - (Use Case diagram)
This diagram shows the use cases and actors participating in Adverse Event Reporting.
uc Manage Adv erse Ev ent Reporting
UC11.22.0 Receiv e
Adv erse Ev ent
A19: Adv erse
Ev ent Reporting
System
A09: Public Health
A13: Health
Information
Exchange
A12: Electronic
Health Record
System
UC11.21.0 Record
Adv erse Ev ent
A02: Patient
A04: Prov ider
Figure: 4
A01: Immunization
Information
System
8 February, 2016
Use Case Diagram Documentation
Page: 8
Manage Adverse Event Reporting Elements:
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A02: Patient
A patient is a person receiving health care. In our models, this is generally related to immunization.
A04: Provider
A provider is a person providing health care, that is a clinician.
A09: Public Health
Public Health (also known as population health) fulfills a number of roles related to immunization. It is
concerned about promoting the health of the population.
A12: Electronic Health Record System
An electronic health record system is an information system which contains patient's medical records.
A13: Health Information Exchange
This actor acts as a hub to facilitate access to consolidated health records from multiple sources.
A19: Adverse Event Reporting System
This actor represents the system intended to capture and track adverse events. It is typically a national
effort.
UC11.21.0 Record Adverse Event
The goal of this is use case is to record. This can be either via direct interface or by electronic transmission.
UC11.22.0 Receive Adverse Event
The goal of this use case is to receive adverse event information.
Manage Immunization History Use Case - (Use Case diagram)
8 February, 2016
Use Case Diagram Documentation
Page: 9
This diagram shows the use cases and actors participating in management of Immunization Histories.
uc Manage Immunization History Use Case
UC11.1.0 Record
Immunization History
UC11.2.0 Request
Immunization History
A17: PHR system
A01: Immunization
Information System
UC11.3.0 Receiv e
Immunization History
A12: Electronic Health
Record System
UC11.4.0 Return
immunization history
Figure: 5
Manage Immunization History Use Case Elements:
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A12: Electronic Health Record System
An electronic health record system is an information system which contains patient's medical records.
A17: PHR system
8 February, 2016
Use Case Diagram Documentation
Page: 10
This is the Personal Health Record system. It houses a health record owned and maintained by the person
it is about.
UC11.1.0 Record Immunization History
The goal of this use case is to record immunization history in information system. An immunization history
includes all immunizations, patient demographics and patient conditions. It may include functionality from
record demographics use case.
UC11.2.0 Request Immunization History
The goal of this use case is to request a complete immunization history from an information system, based
on specified parameters. These could be demographic information or patient identifiers known or obtained
from MPI.
UC11.3.0 Receive Immunization History
The goal of this use case is to receive an immunization history from another system. It could be unsolicited
or in response to a query.
UC11.4.0 Return immunization history
The goal of this use case is to return an immunization history in response to a request for immunization
history.
Manage Patient identity - (Use Case diagram)
This diagram shows the use cases and actors participating in Patient Identity managment.
8 February, 2016
Use Case Diagram Documentation
Page: 11
uc Manage Patient identity
UC11.13.0
Deduplicate patients
UC11.5.0 request
identifiers
UC11.6.0 register
identifiers
A01: Immunization
Information System
A03: Patient Registry
UC11.9.0 Request
patient demographics
UC11.8.0 Record patient
demographics
Figure: 6
Manage Patient identity Elements:
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A03: Patient Registry
8 February, 2016
Use Case Diagram Documentation
Page: 12
A patient registry is an information system with the goal of maintaining demographic information about a
patient. Included in this function is tracking identifiers from different sources.
UC11.13.0 Deduplicate patients
The goal of this use case is to assure an unduplicated registry of persons (patients). This may be part of an
MPI or other information system, including IIS.
UC11.5.0 request identifiers
The goal of this use case is to get identifiers for a patient based on specified parameters.
UC11.6.0 register identifiers
The goal of this use case is to register patient identifiers with an identity resolution system/service.
UC11.8.0 Record patient demographics
The goal of this use case is to record patient demographic information in an information system.
UC11.9.0 Request patient demographics
The goal of this use case is to request demographic information on a patient based on selected parameters.
Manage Vaccine Inventory - (Use Case diagram)
This diagram shows the use cases and actors participating in vaccine inventory management.
8 February, 2016
Use Case Diagram Documentation
Page: 13
uc Manage Vaccine Inv entory
UC11.17.0 Manage
Vaccine inv entory
A01: Immunization
Information System
A10: Distributor
UC11.15.0 Distribute
v accine
A12: Electronic Health
Record System
A16: Relabeller
UC11.14.0
Manufacture v accine
A08: Manufacturer
Figure: 7
Manage Vaccine Inventory Elements:
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A08: Manufacturer
A manufacturer makes products, vaccines in our case.
A10: Distributor
8 February, 2016
Use Case Diagram Documentation
Page: 14
This actor distributes vaccine from manufacturer to end users.
A12: Electronic Health Record System
An electronic health record system is an information system which contains patient's medical records.
A16: Relabeller
A relabeller repackages vaccines and sells them under their label.
UC11.14.0 Manufacture vaccine
The goal of this use case is to make vaccine.
UC11.15.0 Distribute vaccine
The goal of this use case is to distribute vaccine to provider organizations.It includes activiies such as
relabelling.
UC11.17.0 Manage Vaccine inventory
The goal of this use case is to manage inventory of vaccine. This includes ordering, accepting,
decrementing (use or waste) and transferring vaccine inventory.
Manage schedule - (Use Case diagram)
This diagram shows the use cases and actors participating in management of rules and supporting data required by
Clinical Decisions Support.
8 February, 2016
Use Case Diagram Documentation
Page: 15
uc Manage schedule
add BP flow
diagram under
manage schedule
diagram.
UC11.23.0 dev elop
series rules
A20: Designated
SME group
UC11.24.0 publish
rules
A09: Public Health
UC11.25.0 integrate
rules
A21: CDS support SME
A14: Ev aluation/forecast
prov ider
A01: Immunization
Information System
Figure: 8
Manage schedule Elements:
A01: Immunization Information System
According to the CDC IISSB: Immunization Information Systems are confidential, population-based,
computerized information systems that attempt to collect vaccination data about all children within a
geographic area.
A09: Public Health
Public Health (also known as population health) fulfills a number of roles related to immunization. It is
concerned about promoting the health of the population.
A14: Evaluation/forecast provider
8 February, 2016
Use Case Diagram Documentation
Page: 16
This actor evaluates a patient's immunization history and other factors and produces a forecast of next
doses due. It also returns the evaluation of the history.
A20: Designated SME group
This is the group of clinical SME responsible for rule development. An example in the US would be the
ACIP.
A21: CDS support SME
This is a SME who integrates series rules into CDS engine.
UC11.23.0 develop series rules
The goal of this use case is to develop the rules used by CDS to evaluate immunization histories and
forecast next dose.
UC11.24.0 publish rules
The goal of this use case is publish the series rules developed to guide immunization practices.
UC11.25.0 integrate rules
The goals of this use case are to integrate the series rules as published.
add BP flow diagram under manage schedule diagram.
add BP flow diagram under manage schedule diagram. Embedded Elements