Post on 01-Jan-2016
transcript
Meeting Etiquette
2
• Remember: If you are not speaking, please keep your phone on mute
• Do not put your phone on hold. If you need to take a call, hang up and dial in again when finished with your other call o Hold = Elevator Music = frustrated speakers and
participants• This meeting is being recorded
o Another reason to keep your phone on mute when not speaking
• Use the “Chat” feature for questions, comments and items you would like the moderator or other participants to know.o Send comments to All Panelists so they can be
addressed publically in the chat, or discussed in the meeting (as appropriate).
From S&I Framework to Participants:Hi everyone: remember to keep your phone on mute
All Panelists
Agenda
Topic Time Allotted
Welcome and AnnouncementsMeeting RemindersSDC and S&I Get Together @ HIMSSSDC RoadmapReminder: Vote on the Project Charter
5 minutes
SDC Use Case & Functional Requirements Kickoff S&I Use Case Development ProcessSDC Use Case Development TimelineInitiative Concept Diagram & Use Case ApproachUse Case Context DiagramUse Case AssumptionsUse Case Next Steps
50 minutes
Next Steps / Contact Information
3
Welcome and Announcements
• Structured Data Capture (SDC) Initiative holds weekly community meetings on Thursdays at 3:25 pm EST. – Due to the HIMSS conference, the meeting scheduled for
Thursday, March 4 is CANCELLED.– Next meeting is scheduled for March 14, 2013. – Please see the SDC Wiki Page for meeting information– http://wiki.siframework.org/Structured+Data+Capture+Initiative
4
Please check the meeting schedule weekly as the meeting link and call in numbers will change.
HIMSS Conference Meet & Greet(s)1. SDC Get Together
– Tuesday, March 5 @ 5:00 pm
– Accenture Booth Meeting Room (Booth #4331)
2. S&I Get Together
– Tuesday, March 5 @ 5:30 pm
– Wolfe’s (in the Warehouse Bar at the Marriott, 1 block down from the Convention Center)
ReminderVote on the SDC Project Charter
• Consensus voting OPENS on February 22, 2013.
• Consensus voting CLOSES on March 4, 2013.
Voting form is on the SDC Project Charter Pagehttp://wiki.siframework.org/Structured+Data+Capture+Charter+and+Members
For more information on the S&I Framework Consensus Process, seehttp://wiki.siframework.org/S%26I+Steering+and+Consensus+Process
IMPORTANTOnly Committed Members may vote on the Project Charter. Each Organization, no matter the number of Committed Members only receives 1 Vote. If there are multiple committed members from your organization please verify your collective vote with them.
Timelines for Consideration: MU Stage 3, SDO Ballot Cycles
Structured Data Capture (SDC) Initiative:S&I Phases
Dec ‘12 Apr ‘13Jan ‘13 Feb ‘13 Mar ‘13 May ‘13 Jun ‘13 Jul ‘13 Aug ‘13 Sept ‘13
Pilots & Testing
• Pilot site readiness• Implementation of solution• Test User Stories and Scenarios• Monitor Progress & Outcomes• Utilize Requirements Traceability
Matrix
Evaluation
• Evaluate outcomes against Success Metrics and Criteria
Use Case & Functional
Requirements
• Develop, review, and finalize the Use Case and Functional Requirements
Pre-Planning
• Call for Participation
• Conduct Environmental Scan
• Success Criteria
• Stakeholder Engagement
Standards & Harmonization
• Finalize Candidate Standards• Standards Gap Analysis• Technical & Standards Design• Develop Requirements
Traceability Matrix• Develop Implementation
Guide
Pre-Discovery
• Launch initiative• Review and
Finalize Charter• Review initial
Candidate Standards
7
Initiative Kick Off: 1/23/13
8
Structured Data Capture (SDC) Initiative:Notional Timeline & Initiative Work steams
Pilots & TestingUse Case & Functional Requirements
Pre-Discovery Standards & Harmonization
Timelines for Consideration: MU Stage 3, SDO Ballot Cycles
Dec ‘12 Apr ‘13Jan ‘13 Feb ‘13 May ‘13 Jun ‘13 Jul ‘13 Aug ‘13 Sept ‘13
Evaluation
Pre-Planning
Mar ‘13Initiative Kick Off: 1/23/13
Technical Work stream
Content Work stream
SDC All-Hands WG - TBD Lead
Use Case WG:API Functionality
Technical SWGTBD Lead
Common Formats SWGAHRQ Lead
PCOR Content SWGNLM Lead
Pilots WG
Standards & Harmonization WG
S&I FrameworkStructured Data Capture Initiative
Use Case & Functional Requirements Kickoff Meeting
2/28/13
9
Agenda
Topic Time Allotted
S&I Use Case Development Process 20 minutes
SDC Use Case Development Timeline 7 minutes
Initiative Concept Diagram & Use Case Approach 7 minutes
Use Case Context Diagram 7 minutes
Use Case Assumptions 7 minutes
Use Case Next Steps 3 minutes
10
Use Case Development in the S&I Framework
11
Federal
Responsibility Private SectorJoint Efforts
NwHINExchange
OperationsS&I PilotsS&I
Framework
ATCBs and Testing
Infrastructure
NWHIN Implementation & Pre-Certification
TestingStandards DevelopmentUse Cases Harmonization
S&I Framework
eHealth Exchange
Use Case Development Objectives
• Engage Stakeholders as Committed Members, Invited Experts, or Interested Parties in the creation of a Use Case
• Identify a Use Case and User Stories that address real-world problems
• Keep it simple
• Create a finalized Use Case that demonstrates value and supports the proposed goals and success criteria for the Initiative
• Publish a finalized Use Case that contains necessary content, supported by artifacts, to enable Harmonization and subsequent S&I Framework efforts to occur
• Establish the Use Case and supporting artifacts in a reusable fashion to support future health information interchange Initiatives
12
•1.0 Preface and Introduction**
•2.0 Initiative Overview– 2.1 Initiative Challenge Statement**
•3.0 Use Case Scope– 3.1 Background**– 3.2 In Scope– 3.2 Out of Scope– 3.3 Stakeholders**
•4.0 Value Statement**
•5.0 Use Case Assumptions
•6.0 Pre-Conditions
•7.0 Post Conditions
•8.0 Actors and Roles
•9.0 Use Case Diagram
Use Case OutlineTailored for each Initiative
• 10.0 Scenario: Generic Provider Workflow– 10.1 User Story 1, 2, x, …– 10.2 Activity Diagram
o 10.2.1 Base Flowo 10.2.2 Alternate Flow
– 10.3 Functional Requirementso 10.3.1 Information Interchange Requirementso 10.3.2 System Requirements
– 10.4 Sequence Diagram
• 11.0 Dataset Requirements
• 12.0 Risks, Issues and Obstacles
• Appendices
– Related Use Cases– Previous Work Efforts– References
13
** Leverage content from Charter
Review of Key Use Case SectionsDefining the Actors
• This section of the Use Case outlines the business actors that are participants in the information exchange requirements for each scenario. A business actor is a person or organization that directly participates in a scenario. Thus, as a person or organization, the actor can (and should) be a stakeholder.
• The business actor must use a system to perform the functions and to participate in the information interchange. The system or system actor has roles (send, receive, publish, subscribe or in some cases display) and actions which involve exchanging content. Please see the table below for an example of these designations.
• NOTE: A Business Actor may be a Stakeholder and also can have more than one role.
Actor System Role
PCP EHR System Sender
Specialist EHR System Receiver
Patient PHR System Receiver
Example
15
Review of Key Use Case SectionsUse Case Diagrams
• The Use Case and Context Diagrams conceptually represents the Business Actors interacting with the Use Case and the User Stories
– These diagrams characterize the types of interactions that an actor has with a specific system
– The section can include a Use Case Diagram and, if applicable, a Context Diagram (examples are shown below)
• The Use Case diagram shows the association and interaction between the business actors and the Use Case
– It provides an overview of the actors (users or external systems), Use Cases, and the interactions between them
• The context diagram uses inputs and outputs to provide a pictorial representation of the environment, both internal and external, where the exchange takes place
• As the UML associated with the diagrams proceeds through the different S&I Framework functions (i.e., Harmonization, Reference Implementation), it is defined at a more granular level closer to the coding (implementation).
• Example of Use Case Diagram
16
Transitions of Care – Use Case Diagram
http://wiki.siframework.org/file/view/SIFramework_ToC_UC_v%201.1.docx
17
Transitions of Care – Context Diagram
Actors & Roles
Context Diagram
Actor System RoleProvider (Person) Electronic Health Record (EHR) System Sender/Receiver or Source/Destination HISP Health Information Service Provider The “wire” across which the health information
is sent from the sender to the receiverPatient Personal Health Record (PHR) System Sender/Receiver or Source/DestinationProvider Organization Electronic Health Record (EHR) System Sender/Receiver or Source/Destination Caregivers Personal Health Record (PHR) System Sender/Receiver or Source/Destination
Transition Of CareProvider_1
Send Clinical Summary, Consultation Request Summary Discharge Summary
and/or Discharge Instruction
Patient Receives Clinical Summary, Consultation Request
Summary, Discharge Summary and/or Discharge
Instructions
Provider_2
Receive Clinical Summary, Consultation
Request Summary Discharge Summary and/
or Discharge InstructionsSend Clinical Summary and Consult
Summary
Receive Clinical Summary and Consultation Summary
Updates Provider EHRs (Out of Scope)
http://wiki.siframework.org/file/view/SIFramework_ToC_UC_v%201.1.docx 18
Review of Key Use Case SectionsScenarios
• The scenario is a comprehensive description of the actors, interactions, activities, and requirements associated with the information exchange
• It is a prototypical sequence of interactions in a business collaboration or the application context
• Scenarios pertain to supporting the health information exchange and, describing key flows, and are supplemented by User Stories
19
Review of Key Use Case SectionsUser Story
• User Stories summarize the interaction between the actors of the Use Case, and specify what information is exchanged from a contextual perspective
• Furthermore, the User Stories describe the real world application as an example of the Scenario
• These interactions are further described in subsequent sections. Historically, user stories have been utilized to provide clinical context.
20
Review of Key Use Case SectionsActivity Diagram
• An Activity Diagram is a special form of a state transition diagram in which all or most of the states are activity states or action states
– An action state represents the fulfillment of associated responsibilities in response to the communication received from the previous step
– Most transitions are triggered by completion of activities in the source states
• The Activity Diagram illustrates the Use Case flows graphically, and represents the flow of events and information between the actors
– It also displays the main events/actions that are required for the data exchange and the role of each system in supporting the change
• Example of Activity Diagram
21
Review of Key Use Case SectionsSequence Diagram
• A Sequence Diagram is primarily used to show the interactions between objects in the sequential order that they occur
– This representation can make it easy to communicate how the exchange works by displaying how the different components interact
– The primary use of the diagram is in the transition from requirements expressed as use cases to the next and more formal level of refinement
• Note: Horizontal lines are used to identify the specific activity between the systems
• Example of ToC Sequence Diagram on next slide
23
Review of Key Use Case SectionsFunctional Requirements
• Functional Requirements identify the capabilities a system in a role must have in order to enable interoperable exchange of the healthcare data of interest
– They provide a detailed breakdown of the requirements in terms of the intended functional behaviors of the application
• The Functional Requirements include:– Information Interchange Requirements– System Requirements– Dataset Requirements
• Detailed descriptions of requirement types on next slides
25
• The Information Interchange Requirements define the system’s name and role. They also specify the actions associated with the actual transport of content from the sending system to the receiving system
• System Requirements include the requirements internal to the system necessary to participate successfully in the transaction. System requirements may also detail a required workflow that is essential to the Use Case
• Dataset Requirements– Include the data elements and data element sets that will be available within the message
or document. Each data element included is necessary for some aspect of the Use Case; however, the requirements do not specify exactly how they may be used together. All data element sets may contain multiple data elements unless otherwise stated.
– The identification of data elements forms the foundation for harmonization activities. The data elements identified in the Use Case set constraints on the contents of documents and messages.
– NOTE: This content of this section will vary per Initiative as the references are contingent upon the specific list of Functional Requirements that is developed by the Workgroup. The Use Case Simplification Workgroup is tasked with creating a structure for this section that will eventually be applied to all Use Cases. Data element sets are defined for reuse within the Use Case Simplification Workgroup
26
Review of Key Use Case SectionsFunctional Requirements
Previous and Ongoing S&I Use Cases
28
Use Case Title StatusTransitions of Care CompleteLab Results Interface CompleteProvider Directory - Certificate Discovery CompleteProvider Directory - Electronic Service Information Discovery CompleteQuery Health CompleteData Segmentation for Privacy CompleteesMD - PPA Provider Registration (UC 1) CompleteesMD - Secure sending and Structure of eMDR (UC 2) CompleteesMD - Author of Record Level 1 CompleteLab Orders Interface CompleteLab Orders Interface - eDOS CompleteHealth eDecisions CDS Artifact Sharing UC 1 CompleteHealth eDecisions CDS Guidance Service UC 2 In progressStructured Data Capture In progressLongitudinal Coordination of Care CompletePublic Health Reporting CompleteAutomate Blue Button Initiative In progressPrescription Drug Monitoring Program In progressesMD – Author of Record Level 2 In progress
Agenda
Topic Time Allotted
S&I Use Case Development Process 20 minutes
SDC Use Case Development Timeline 7 minutes
Initiative Concept Diagram & Use Case Approach 7 minutes
Use Case Context Diagram 7 minutes
Use Case Assumptions 7 minutes
Use Case Next Steps 3 minutes
29
Week TargetDate All Hands WG Meeting Tasks Homework
due Tuesday COB
1 2/28 Use Case Kick-Off & UC Process OverviewIntroduce: Context Diagram, Assumptions
Review: Charter content, Context Diagram, Assumptions
- 3/7 Cancelled for HIMSS
2 3/14 User Stories, Pre/Post Conditions
Finalize: Context Diagram, Assumptions
Draft: User StoriesReview: Actors & Roles, Pre/Post Conditions
3 3/21 User Stories, Actors & Roles Review: User StoriesFinalize: Actors/Roles, Pre/Post Conditions Review: User Stories
4 3/28 Base Flow, Activity Diagram Finalize: User Stories Review: Base Flow, Activity Diagram
5 4/4 Functional Requirements Finalize: Base Flow, Activity Diagram Review: Functional Requirements
6 4/11 Functional Requirements,Sequence Diagram
Review: Functional Requirements, Sequence Diagram
Review: Functional Requirements, Sequence Diagram
7 4/18 Data Requirements Finalize: Functional Requirements, Sequence Diagram
Review: Data Requirements, Risks, Issues, & Obstacles
8 4/25 Data Requirements, Risks, Issues, & Obstacles
Review: Data Requirements, Risks, Issues, & Obstacles
Review: Data Requirements, Risks, Issues, & Obstacles
9 5/2 Finalize: Data Requirements, Risks, Issues, & Obstacles None
10 5/9 Full Review End-to-End Review (5/10-5/20)
11 5/16 End-to-End Review (5/10-5/20) End-to-End Review due 5/20
12 5/23 Consensus (5/24-5/29) Cast consensus vote
FINAL CONSENSUS
Structured Data Capture InitiativeProposed Use Case & Functional Requirements Development Timeline
30
1 2/28 Use Case Kick-Off & UC Process OverviewIntroduce: Context Diagram, Assumptions
Review: Charter content, Context Diagram, Assumptions
Agenda
Topic Time Allotted
S&I Use Case Development Process 20 minutes
SDC Use Case Development Timeline 7 minutes
Initiative Concept Diagram & Use Case Approach 7 minutes
Use Case Context Diagram 7 minutes
Use Case Assumptions 7 minutes
Use Case Next Steps 3 minutes
31
SDC Use Case Approach• The full diagram below highlights an overall picture of the full SDC workflow • The SDC Use Case itself will only focus on generic functionality outlined below and the
exchanges in scope for standardization
33
Use CaseScope
Agenda
Topic Time Allotted
S&I Use Case Development Process 20 minutes
SDC Use Case Development Timeline 7 minutes
Initiative Concept Diagram & Use Case Approach 7 minutes
Use Case Context Diagram 7 minutes
Use Case Assumptions 7 minutes
Use Case Next Steps 3 minutes
34
Agenda
Topic Time Allotted
S&I Use Case Development Process 20 minutes
SDC Use Case Development Timeline 7 minutes
Initiative Concept Diagram & Use Case Approach 7 minutes
Use Case Context Diagram 7 minutes
Use Case Assumptions 7 minutes
Use Case Next Steps 3 minutes
36
Agenda
Topic Time Allotted
S&I Use Case Development Process 20 minutes
SDC Use Case Development Timeline 7 minutes
Initiative Concept Diagram & Use Case Approach 7 minutes
Use Case Context Diagram 7 minutes
Use Case Assumptions 7 minutes
Use Case Next Steps 3 minutes
38
Next Steps for SDC Use Case...!• Next week is cancelled for HIMSS –
SDC Initiative Meet and Greet on Tuesday 3/5/13 Accenture Booth Meeting Room (Booth #4331) from 5:00 – 5:30 pm
S&I Framework Wide Meet & Greet Tuesday 3/5/13 Wolfe's in the Warehouse Bar at the Marriott a block down from the
Convention Center starting at 5:30
• Review content & submit comments by Tuesday 3/12 COB Context Diagram Assumptions Wiki link: http://wiki.siframework.org/Structured+Data+Capture+Use+Case
• Attend our next session on Thursday 3/14 to discuss... Pre & Post Conditions User Stories
39
Week TargetDate All Hands WG Meeting Tasks Homework
due Tuesday COB
1 2/28 Use Case Kick-Off & UC Process OverviewIntroduce: Assumptions, Pre/Post Conditions
Review: Charter content, Context Diagram, Assumptions
- 3/7 Cancelled for HIMSS
2 3/14 User Stories, Pre/Post Conditions
Finalize: Context Diagram, Assumptions
Draft: User StoriesReview: Actors & Roles, Pre/Post Conditions
3 3/21 User Stories, Actors & Roles Review: User StoriesFinalize: Actors/Roles, Pre/Post Conditions Review: User Stories
4 3/28 Base Flow, Activity Diagram Finalize: User Stories Review: Base Flow, Activity Diagram
5 4/4 Functional Requirements Finalize: Base Flow, Activity Diagram Review: Functional Requirements
6 4/11 Functional Requirements,Sequence Diagram
Review: Functional Requirements, Sequence Diagram
Review: Functional Requirements, Sequence Diagram
7 4/18 Data Requirements Finalize: Functional Requirements, Sequence Diagram
Review: Data Requirements, Risks, Issues, & Obstacles
8 4/25 Data Requirements, Risks, Issues, & Obstacles
Review: Data Requirements, Risks, Issues, & Obstacles
Review: Data Requirements, Risks, Issues, & Obstacles
9 5/2 Finalize: Data Requirements, Risks, Issues, & Obstacles None
10 5/9 Full Review End-to-End Review (5/10-5/20)
11 5/16 End-to-End Review (5/10-5/20) End-to-End Review due 5/20
12 5/23 Consensus (5/24-5/29) Cast consensus vote
FINAL CONSENSUS
Structured Data Capture InitiativeProposed Use Case & Functional Requirements Development Timeline
40
Next Steps
• HOMEWORK: Committed Members VOTE on the Project Charter: – http://wiki.siframework.org/Structured+Data+Capture+Charter+a
nd+Members
• Next Work Group Meeting• March 7, 2013 Meeting is CANCELLED• Next Meeting is Thursday, March 14, 2013 from 3:30pm - 4:30pm
Eastern – http://wiki.siframework.org/Structured+Data+Capture+Initiative
• Reminder: All SDC Announcements, Meeting Schedules, Agendas, Minutes, Reference Materials, Use Case, Project Charter and general information will be posted on the SDC Wiki page– http://wiki.siframework.org/Structured+Data+Capture+Initiative
Contact Information
• For questions, please contact your support leads– Initiative Coordinator: Evelyn Gallego (evelyn.gallego@siframework.org)– Project Manager: Jenny Brush (jenny.brush@esacinc.com)– PM Support: Zachary May (zachary.may@esacinc.com)– Use Case/Requirements Lead: Jennifer Sisto (jennifer.t.sisto@accenturefederal.com)– Standards Development Lead: Caryn Just (caryn.k.just@accenturefederal.com)