S&I Framework
Use Case and Requirements Workgroup
Laboratory Results Interface Initiative
Meeting Summary
Date: 04/06/11
Name: Laboratory Results Interface Initiative (LRI) Use Case Diagram Sub-Workgroup Session 5
Agenda/Objectives:
Topic
Administrative Items
Review of Scenario 1 Alternative Flows
 Preliminary Results
 Corrected Results
 Physician Requested Rerun
Review of Sequence, Context and Use Case Diagrams (we
didn’t get to these agenda items)
Time Allotted
12:00 – 12:05 EDT
12:05 – 1:00 EDT
1:00 – 1:30 EDT
Attendees:
Glen Moy, Rob Allen, Mike Trebatoski, Bob Yencha, John Ritter, Kathy Walsh
Panelist Attendees:
 Merideth Vida
 Ed Larsen
 Jitin Asnaani
Action Items:
Action Item
Status / Next Steps
Lead
Revise Activity
Diagram
Comment on Revised
Activity Diagram
Revise Actors Table &
Post Suggestions to
Wiki
Comment on
suggested actors
change.
Complete
Support Leads
In Progress
All
Complete
Support Leads
In Progress
All
Contributor
s
Rob Allen
Due
Date
4/7/11
SWG
Members
SWG
Members
4/11/11
SWG
Members
4/11/11
Laboratory Results Interface Initiative (LRI) Use Case Diagram Sub-Workgroup Session 5, 04/06/11
4/7/11
1
Meeting Summary
S&I Framework
Use Case and Requirements Workgroup
Laboratory Results Interface Initiative
Review of Alternative Flows for Scenario 1
Key Discussion Points:
 The sub-workgroup’s charge is that the process of placing a Laboratory Order is out-of-scope.
That is, from the laboratory’s perspective, we (the lab) simply receive a request for us to perform
some kind of lab test on a specimen. We don’t care how the Lab Order was created.
 After receiving a request to perform a lab test, that request will be fulfilled by performing a lab
test.
 As previously discussed if there are issues when performing the test the lab might have to rerun
the test. This action (namely, to perform the test again) can arise from three different
“requestors”, namely:
o The lab – when we notice something that is troublesome and decide to re-perform the
test so as to correct the results (based on the original Order).
o The lab - when we notice something that is troublesome and decide to re-perform the
test so as to amend the results (based on the original Order)
o The “Order Placer” – when the physician who ordered the test notices something that is
troublesome and requests that the lab repeat the lab test (based on the original Order).
 Thus, it seems that there are four (legitimate, but distinct) modes for beginning a lab test:
o Perform,
o Correct,
o Amend, or
o Repeat
 If this is true, then each of these four modes needs to be captured in our flow diagram.
Consequently, each of these four modes needs to be characterized in terms of who initiates
each workflow.
 Challenges of using “Order Placer” as the sole moniker
o Does the Ordering Physician initiate all four workflows? No. The lab (itself) initiates some
of those workflows.
o Additionally, from the lab’s perspective, we (the lab) perform “tests”; we don’t perform
“orders”.
o As a result, if we attempt to use the moniker “Order Placer” to name the actor who
requests lab tests, then we misrepresent the fact that the lab can also play the role as a
legitimate actor who can request lab tests.

Resolution(s):
 Update the Activity diagram to include in meeting changes
o Change the description of the first step so that the baseflow is inclusive of all test types
o Incorporate amended/corrected results appropriately
 The sub-workgroup thinks it would be best (from the lab’s perspective) to name the actor who
can request lab tests as “Test Requestor” (instead of “Order Placer”).
Review of Use Case, Context & Sequence Diagram
Key Discussion Points:
 These items were not discussed.
Laboratory Results Interface Initiative (LRI) Use Case Diagram Sub-Workgroup Session 5, 04/06/11
2
Meeting Summary
S&I Framework
Use Case and Requirements Workgroup
Laboratory Results Interface Initiative
Schedule for Upcoming Sub-Workgroups:
Sub-Workgroup title: UC and Scenario SWG
Date/Time: 4/11 at 12:00 EDT
Sub-Workgroup title: UC and Scenario SWG
Date/Time: 4/13 at 2:00 EDT
Laboratory Results Interface Initiative (LRI) Use Case Diagram Sub-Workgroup Session 5, 04/06/11
3