Public Health Tiger Team User Story Template
1. Actors
List the business actors that are participants in the information exchange requirements. A business actor is a
person or organization that directly participates in a user story. The business actor must use a system to
perform the functions and to participate in the information exchange. The system or system actor has roles
(send, receive, publish, subscribe or in some cases display) and actions will involve exchanging context.
Actor
PCP
Public Health Professional
System
EHR System
Public Health IT System
Role
Sender
Receiver
2. Related Use Cases and User Stories
List relevant S&I Use Cases and/or User Stories that apply to this User Story.
Related Use
Case
Structured
Data Capture
Use Case 1.0
Related User
Story
Reportable
Condition User
Story
Description
A Provider has identified a patient with a reportable condition. Using an existing
EHR system, the Provider requests the reportable condition form electronically
from the jurisdictional public health organization or entity. In the background, the
EHR system sends information already collected about the patient to a forms
manager. At the time of the request the EHR indicates what archive option, if
any, should be used. The archive maintains the data as read only so they are an
indisputable and auditable record of the reporting. The archive may be
maintained by the EHR or by an independent service in behalf of the provider.
The archive option specifies information necessary to connect to the archive and
may include any combination of the following: the information that was sent with
the request; the form template; the form data returned after being autopopulated; and/or the form data as they were submitted
3. User Story
User Stories summarize the interaction between the actors of the Use Case, and specify what information is
exchanged from a contextual perspective. The User Story should provide clinical context of the exchange and
highlight the applicable domain and/or reportable condition. This User Story should reflect the future vision
for electronic interoperable exchange (to-be) rather than an existing (as-is) un-interoperable process.
A Provider has identified a patient with a reportable condition. Using an EHR system, the Provider requests
the reportable condition form electronically from the jurisdictional public health organization. The
jurisdictional public health organization receives the request, understands the request, and sends the
requested form to the Provider’s EHR system. The Provider successfully receives the form and completes the
required information on the form. The Provider saves the form and sends the completed form to the
jurisdictional public health system and/or registry.
4. Base Flow
The Base Flow presents the step-by-step process of the information exchange depicted in the user story. It
indicates the actor who performs the action and the description of the event/action).
Suggested Format: Table
Step
#
Actor
Role
Event/Description
Step
#
1
2
Actor
Provider
3
Public Health
Professional
(PHP)
PHP
4
Provider
5
Provider
6
PHP
Role
Event/Description
Request
Sender
Request
Receiver
Provider EHR System Requests Reportable Condition Form
Results Sender
PHP Sends Reportable Condition Form to Provider through PHP
System
Provider Receives Reportable Condition Form through EHR System
and completes it
Provider Sends completed Reportable Condition Form to PHP through
EHR System
PHP Receives Reportable Condition Form through PHP System
Results
Receiver
Results
Sender
Results
Receiver
PHP Receives Request for Reportable Conditions Form through Public
Health System