ToC+-+UCR+Workgroup+Charter

include component="page" wikiName="siframework" page="TOC Header" **The version below of the Transition of Care UCR Workgroup Charter has been approved through the Consensus Process on 02/18/11.**

=Charter:=

1.0 Use Case and Requirements Workgroup Composition

 * **Initiative Coordinator:** || Arien Malec, ONC S&I Framework ||

**S&I Framework Support Members**
Ed Larsen || John Stinn || John Stinn || Andriy Selivonenko Joan DuHaime Chitra Ragu || Charles Ndunda Anjali Gupte Chitra Ragu || Chad Clay || Marc Bernard || Neal Richards ||
 * **S&I Team** || **Transition of Care** ||
 * Use Case || Amy Berk
 * Harmonization || Jillian Wanner
 * Implementation Specifications || Jillian Wanner
 * RI || Steve Cason
 * DP || Dave Colbert
 * Certification and Testing || Chris Brancato
 * Tools || Kevin Puscas ||
 * Architecture || Dragon Bashyam
 * FHA || Erik Pupo

**Committed Members**
This list will be updated on Tuesdays and Fridays. If you notice a change that needs to be made, please send your request to admin@siframework.org so that we can update it in all of our records.
 * **Name** || **Organization** ||
 * Steven Waldren || AAFP ||
 * David C. Kibbe || American Academy of Family Physicians ||
 * Anne Diamond || American College of Obstetricians and Gynecologists (ACOG) ||
 * James Scroggs || American College of Obstetricians and Gynecologists (ACOG) ||
 * Thomson Kuhn || American College of Physicians (ACP) ||
 * Greg Alexander || ANI ||
 * Seonho Kim || ApeniMED (formerly MEDNET) ||
 * Amber Broadwater || Avisena Inc. ||
 * Lin Wan || Axolotl Corp. ||
 * Paula Gwyn || CareTech Solutions ||
 * Gary Dickinson || CentriHealth ||
 * John Odden || Coto Partners, AIIM, CGC, C4UH ||
 * Chris Doucette || Deloitte ||
 * Randolph Sanks, MBA || Deloitte (Health and Life Sciences) ||
 * Susan E. Campbell, PhD, RN || Deloitte Consulting, LLC Federal Strategy & Operations ||
 * Tom Dawson || Dispersive Medical ||
 * Stephen Hufnagel || DoD Military Health System ||
 * Jim Hansen || Dossia Consortium ||
 * Kyle Meadors || Drummond Group Inc. ||
 * Vassil Peytchev || Epic ||
 * Larry Garber, MD || Fallon Clinic/SAFEHealth ||
 * John Williams || Garden State Health Systems Inc / Health-ISP.com ||
 * Steve Rushing || Georgia Institute of Technology ||
 * Greg Smith || Greg Smith and Associates (KHIN, KHIE) ||
 * Jaime Estrada || Health Information Network of Arizona ||
 * Simpson William || Healthland ||
 * Susan Nedza MD || HealthyCircles, LLC. ||
 * Louise V. Fryer, RN, MS, PMP || Highmark Blue Cross Blue Shield ||
 * Audrey Dickerson || HIMSS ||
 * Joyce Sensmeier || HIMSS ||
 * David Cheng || IBM ||
 * Aaron Stranahan || ICA ||
 * Mayuri Patel || ICA ||
 * Tim Dunnington || ICA ||
 * John Moehrke || IHE ITI ||
 * Keith Boone || IHE PCC Domain ||
 * Michael J. McCoy, MD || IHE PCC, ACOG, Catholic Health East ||
 * Scott Serich || IJIS Institute ||
 * John Donnelly || IntePro Solutions, IHE ||
 * Cyndalynn Tilley || Intermountain Healthcare ||
 * Larry Wolf || Kindred Healthcare ||
 * Jeff Bloemker || Lewis And Clark Information Exchange ||
 * Corey Spears || McKesson ||
 * Holly Miller, MD, MBA || MedAllies ||
 * Vasu Iyengar || MedAZ.net, LLC ||
 * Adrian Gropper || MedCommons ||
 * Mark Bamberg || MEDfx ||
 * Eric Heflin || Medicity ||
 * Luann Whittenburg || Medicomp System, Inc. ||
 * Fred Buhr || Metasteward LLC ||
 * Paul Edge || Microsoft ||
 * Larry Sampson || Minnesota Health Information Exchange (MNHIE) ||
 * Konda Mullapudi || Misys Open Source Solutions (MOSS) LLC. ||
 * Lynne Gilbertson || NCPDP ||
 * Teresa Strickland || NCPDP ||
 * Thomas Foley || NextEnt, LLC ||
 * Steven Saitsky || NextGen Healthcare ||
 * Russel B. Leftwich, MD || Office of eHealth Initiatives, State of Tennessee ||
 * Kimberly Tooles || Onyx Home Health Care, LLC. ||
 * Lola McCune || Onyx Home Health Care, LLC. ||
 * Brian Ahier || Oregon HIE Planning Team ||
 * Elizabeth Evans || PANDA and Associates, LLC ||
 * Perry D. Cohen, PhD || Parkinson Pipeline Project ||
 * Elaine A. Blechman || Prosocial Applications, Inc. ||
 * Teresa Mota || Quality Partners of Rhode Island ||
 * Freida Hall || Quest Diagnostics, Inc. ||
 * Ken McCaslin || Quest Diagnostics, Inc. ||
 * Bob DeAnna || Recursion Software ||
 * Will Ross || Redwood MedNet ||
 * Ernest Grove || Secure Hitech LLC ||
 * Lester Keeper Jr. || Secure Hitech LLC ||
 * Doug Pratt || Siemens ||
 * Lorre Pacheco || Sunquest Information Systems ||
 * Betty Levine || Telemedicine Advance Technology Research Center/Department of the Army ||
 * Ollie B. Gray || Telemedicine Advance Technology Research Center/Department of the Army ||
 * Virginia Lorenzi || The NewYorkPresbyterian Hospital ||
 * Tory Berger || TJB Consulting ||
 * Philip DePalo || Towson University ||
 * Yeong-Tae Song || Towson University ||
 * Holly Miller || VA ||
 * Patricia Greim || VA ||
 * You-Ying Whipple || VA ||
 * Terry Hearn || WellPoint ||

2.0 Use Case and Requirements Workgroup Mission, Vision, and Objectives
//Mission//: The Mission of the Use Case and Requirements Workgroup is to define the necessary components and artifacts to develop Use Cases and their associated Functional Requirements. In developing these Use Cases the workgroup will define a valuable set of integrated functions and processes achieve harmonized interoperability for healthcare interoperability exchange for any warranted Initiative.

//Vision//: The Vision of the Use Case and Requirements Workgroup is to deliver guidance to the health information technology community on how to achieve healthcare delivery improvements. The Workgroup will develop Use Cases and Functional Requirements to support and unite stakeholders on common healthcare challenges. More specifically the Workgroup will work to produce a set of reusable tools and processes through the development of Use Case artifacts.

Specifically, the Transition of Care Initiative presents the following Challenge to be discussed and evaluated when developing an Initiative specific Use Case:

//Meaningful Use Stage 1 and foreseen Stage 2 require information to be exchanged in transition of care. Implementers are often confused on how to use the specifications to exchange the required data. The exchange of clinical summaries is hampered by ambiguous common definitions of what data elements must at a minimum be exchanged, how they must be encoded, and how those common semantic elements map to MU specified formats (C32/CCD and CCR). Finally, the lack of a robust toolset to aid in development and validation of conformant templated clinical documents is a major impediment to the widespread adoption of the standards.//

The Scope of this Initiative is as its first priority support for Meaningful Use Stage 1 summary of care (Eligible Provider, Eligible Hospital, and Critical Access Hospital) requirements for transition of care and transition of care to consumer and as a second priority support for expected Stage 2 requirements.

The Main Goal of the Transition of Care Initiative is the achievement of Meaningful Use:

//Exchange key clinical information among providers of care and with patients and other authorized entities electronically based on level of system capability, i.e., human readable, unstructured text or full interoperable structured data//


 * //Enable Clinical Summary validation services to be available such that if an organization passes validation, they have a high degree of confidence that any other organization passing the same validation has a 99.9% opportunity to understand the same core clinical information whether as unstructured data or structured and encoded data.//
 * //Reduce template development time through new tools and process developed through the S&I Framework and public/private activities (such as Open Health Tools) by a factor of 1.5x. Reduce time to create a new unstructured and structured documents based on the HL7 CDA by 10% in 2011 and by 25% in 2013.//

Objectives of the Use Case and Requirements Workgroup are the following:
 * 1) Engage Stakeholders as Committed Members, Invited Experts, or Interested Parties in the creation of the Use Case(s) for the Transition of Care Initiative
 * 2) Publish a finalized Use Case or set of Use Cases that contain necessary content, supported by artifacts, to enable Harmonization and subsequent S&I Framework efforts to occur.
 * 3) Establish the Use Case or set of Use Cases and supporting artifacts in a reusable fashion to support future health information exchange initiatives.
 * 4) Create a finalized Use Case or set of Use Cases that demonstrate value and supports the proposed goals and success criteria for the Transition of Care Initiative. Specifically, success criteria for this Initiative are the following:
 * Number of providers using Transition of Care output
 * Number of organizations who have been certified to produce valid specifications (Software development/Tools organizations/Provider organizations)
 * Time reduction for creation of a new minimal unstructured summary and structured summary document
 * Cost reduction for creation of core elements within transitions of care
 * Improvement in ability to achieve MU criteria

3.0 Deliverables

 * **Deliverable Name** || **Draft Due Date** || **Final Due Date** ||
 * Transition of Care Initiative Use Case Timeline || 01/15/11 || 01/31/11 ||
 * Transition of Care Initiative Use Case Template Draft || 01/31/11 || 01/31/11 ||
 * Review Log of Comments/Feedback of the Transition of Care Initiative Use Case || 02/02/11 || 03/30/11 ||
 * Finalized Transition of Care Initiative Use Case || 03/28/11 || 03/31/11 ||

4.0 Key Interfaces
The Use Case and Requirements Workgroup will work as part of the Standards and Interoperability (S&I) Framework. The Workgroup serves as the primary interface with various Stakeholders of the healthcare technology community that have interest and expertise related to the specific Initiative. Specifically, the Stakeholders to be interfaced with for this Workgroup include the following:
 * Patients
 * Consumers
 * Care Coordinators
 * Clinicians
 * Laboratories
 * Pharmacies
 * Other Provider Organizations
 * Standards Organizations
 * Electronic Health Record/Personal Health Record Vendors
 * Physicians and Physician Organizations
 * Hospitals including Critical Access Hospitals
 * Health Information Exchanges and HIE Vendors
 * Payers
 * Beacon Communities
 * Regional Extension Centers (RECs)

The Workgroup will work to develop and evolve key Use Cases in alignment with the Initiatives, as selected by prioritization criteria, to illicit future recommendations. These efforts will form a foundation for healthcare interoperability in the US.

5.0 Key Activities, Timing, and Milestones
The following activities and milestones per the Use Case and Requirements Workgroup are fundamental in producing the final Use Case Deliverable. It is to be noted that the Use Case and Requirements Workgroup’s main focus is on Discovery activities; however, the Workgroup will remain engaged throughout the entirety of the S&I Framework. Requirements Workgroup || * Formation of Use Case and Requirements Workgroup || * Completion of Project Charter || Transition of Care Initiative || * Review of Existing Use Cases Wiki for Feedback || * Compile and Publish Transition of Care Use Case to Wiki for Stakeholder/COI Feedback/Comment || * Receipt of Stakeholder/COI Harmonization Team || * Transition of Finalized Transition of Care Use Case and Requirements to Harmonization Team || * Transition final Use Case and Requirements to Harmonization Function of S&I Framework ||
 * **Focus Area** || **Major Activities** || **Milestones** ||
 * Call for Participation || * Broadcast of Call for Stakeholders || * Confirmation of Stakeholder Participants ||
 * Transition of Care Kick-Off || * Introduction of S&I Framework
 * Introduction of Use Case
 * Complete Roles & Responsibilities
 * Introduce Agenda of Workgroup Sessions || * Complete Roles and Responsibilities
 * Confirmation of Workgroup Attendees
 * Confirmation of Topics to be discussed at Workgroups per Transition of Care Use Case ||
 * Establish Use Case and
 * Conduct Research Related to
 * Share Findings with Participants || * Incorporation of Gaps into Use Case Documentation ||
 * Document Business Processes || * Draft Content
 * Present to Stakeholders for Feedback
 * Resolve Feedback by Casting of Votes
 * Update Use Case with Feedback || * Confirmation of Business Processes ||
 * Document Use Case Diagrams || * Draft Content
 * Present to Stakeholders for Feedback
 * Resolve Feedback by Casting of Votes
 * Update Use Case with Feedback || * Confirmation of Use Case Diagrams ||
 * Document BusinessScenarios || * Draft Content
 * Present to Stakeholders for Feedback
 * Resolve Feedback by Casting of Votes
 * Update Use Case with Feedback || * Confirmation of Activity Diagrams
 * Confirmation of Sequence Diagrams
 * Confirmation of Business Scenarios ||
 * Document Functional Requirements || * Draft Content
 * Present to Stakeholders for Feedback
 * Resolve Feedback by Casting of Votes (2 Workgroup Sessions)
 * Update Transition of Care Use Case with Feedback || * Confirmation of Functional Requirements ||
 * Publish Use Case to the
 * Feedback/Comment ||
 * Finalize Use Case with Initiative Coordinator || * Finalize Content of Transition of Care Use Case || * Update Transition of Care Use Case with Feedback/Updates ||
 * Publish Final Use Case to Wiki || * Publish Final Transition of Care Use Case to Wiki || * Transition of Care Use Case Published on the Wiki ||
 * Transition of Use Case to
 * Use Case Workgroup Sessions || * Discussion of Transition of Care Use Case
 * Documentation of Transition of Care Use Case
 * Capturing of Feedback/Comments || * Documentation of Transition of Care Use Case
 * Updates to Transition of Care Use Case ||
 * Communications || * Updates/Feedback to Transition of Care Use Cases || * Documentation of Review Log of Transition of Care Use Case Feedback/Comments ||

6.0 Use Case and Requirements Workgroup Member Knowledge and Skills Coverage
This list will be updated on Tuesdays and Fridays. If you notice a change that needs to be made, please send your request to admin@siframework.org so that we can update it in all of our records.
 * **Name** || **Organization** || **Role** ||
 * Arien Malec || ONC S&I Framework || Initiative Coordinator ||
 * Amy Berk || ONC S&I Framework || Support Lead ||
 * Ed Larsen || ONC S&I Framework || Support Lead ||
 * Steven Waldren || AAFP || Committed Member ||
 * David C. Kibbe || American Academy of Family Physicians || Committed Member ||
 * Anne Diamond || American College of Obstetricians and Gynecologists (ACOG) || Committed Member ||
 * James Scroggs || American College of Obstetricians and Gynecologists (ACOG) || Committed Member ||
 * Thomson Kuhn || American College of Physicians (ACP) || Committed Member ||
 * Greg Alexander || ANI || Committed Member ||
 * Seonho Kim || ApeniMED (formerly MEDNET) || Committed Member ||
 * Amber Broadwater || Avisena Inc. || Committed Member ||
 * Lin Wan || Axolotl Corp. || Committed Member ||
 * Paula Gwyn || CareTech Solutions || Committed Member ||
 * Gary Dickinson || CentriHealth || Committed Member ||
 * John Odden || Coto Partners, AIIM, CGC, C4UH || Committed Member ||
 * Chris Doucette || Deloitte || Committed Member ||
 * Randolph Sanks, MBA || Deloitte (Health and Life Sciences) || Committed Member ||
 * Susan E. Campbell, PhD, RN || Deloitte Consulting, LLC Federal Strategy & Operations || Committed Member ||
 * Tom Dawson || Dispersive Medical || Committed Member ||
 * Stephen Hufnagel || DoD Military Health System || Committed Member ||
 * Jim Hansen || Dossia Consortium || Committed Member ||
 * Kyle Meadors || Drummond Group Inc. || Committed Member ||
 * Vassil Peytchev || Epic || Committed Member ||
 * Larry Garber, MD || Fallon Clinic/SAFEHealth || Committed Member ||
 * John Williams || Garden State Health Systems Inc / Health-ISP.com || Committed Member ||
 * Steve Rushing || Georgia Institute of Technology || Committed Member ||
 * Greg Smith || Greg Smith and Associates (KHIN, KHIE) || Committed Member ||
 * Jaime Estrada || Health Information Network of Arizona || Committed Member ||
 * Simpson William || Healthland || Committed Member ||
 * Susan Nedza MD || HealthyCircles, LLC. || Committed Member ||
 * Louise V. Fryer, RN, MS, PMP || Highmark Blue Cross Blue Shield || Committed Member ||
 * Audrey Dickerson || HIMSS || Committed Member ||
 * Joyce Sensmeier || HIMSS || Committed Member ||
 * David Cheng || IBM || Committed Member ||
 * Aaron Stranahan || ICA || Committed Member ||
 * Mayuri Patel || ICA || Committed Member ||
 * Tim Dunnington || ICA || Committed Member ||
 * John Moehrke || IHE ITI || Committed Member ||
 * Keith Boone || IHE PCC Domain || Committed Member ||
 * Michael J. McCoy, MD || IHE PCC, ACOG, Catholic Health East || Committed Member ||
 * Scott Serich || IJIS Institute || Committed Member ||
 * John Donnelly || IntePro Solutions, IHE || Committed Member ||
 * Cyndalynn Tilley || Intermountain Healthcare || Committed Member ||
 * Greg Smith || KHIE (consultant team), KHIN || Committed Member ||
 * Larry Wolf || Kindred Healthcare || Committed Member ||
 * Jeff Bloemker || Lewis And Clark Information Exchange || Committed Member ||
 * Corey Spears || McKesson || Committed Member ||
 * Holly Miller, MD, MBA || MedAllies || Committed Member ||
 * Vasu Iyengar || MedAZ.net, LLC || Committed Member ||
 * Adrian Gropper || MedCommons || Committed Member ||
 * Mark Bamberg || MEDfx || Committed Member ||
 * Eric Heflin || Medicity || Committed Member ||
 * Luann Whittenburg || Medicomp System, Inc. || Committed Member ||
 * Fred Buhr || Metasteward LLC || Committed Member ||
 * Paul Edge || Microsoft || Committed Member ||
 * Larry Sampson || Minnesota Health Information Exchange (MNHIE) || Committed Member ||
 * Konda Mullapudi || Misys Open Source Solutions (MOSS) LLC. || Committed Member ||
 * Lynne Gilbertson || NCPDP || Committed Member ||
 * Teresa Strickland || NCPDP || Committed Member ||
 * Thomas Foley || NextEnt, LLC || Committed Member ||
 * Steven Saitsky || NextGen Healthcare || Committed Member ||
 * Russel B. Leftwich, MD || Office of eHealth Initiatives, State of Tennessee || Committed Member ||
 * Kimberly Tooles || Onyx Home Health Care, LLC. ||  ||
 * Lola McCune || Onyx Home Health Care, LLC. ||  ||
 * Brian Ahier || Oregon HIE Planning Team || Committed Member ||
 * Elizabeth Evans || PANDA and Associates, LLC || Committed Member ||
 * Perry D. Cohen, PhD || Parkinson Pipeline Project || Committed Mmber ||
 * Elaine A. Blechman || Prosocial Applications, Inc. || Committed Member ||
 * Teresa Mota || Quality Partners of Rhode Island || Committed Member ||
 * Freida Hall || Quest Diagnostics, Inc. || Committed Member ||
 * Ken McCaslin || Quest Diagnostics, Inc. || Committed Member ||
 * Bob DeAnna || Recursion Software || Committed Member ||
 * Will Ross || Redwood MedNet || Committed Member ||
 * Ernest Grove || Secure Hitech LLC || Committed Member ||
 * Lester Keeper Jr. || Secure Hitech LLC || Committed Member ||
 * Doug Pratt || Siemens || Committed Member ||
 * Lorre Pacheco || Sunquest Information Systems || Committed Member ||
 * Betty Levine || Telemedicine Advance Technology Research Center/Department of the Army || Committed Member ||
 * Ollie B. Gray || Telemedicine Advance Technology Research Center/Department of the Army || Committed Member ||
 * Virginia Lorenzi || The NewYorkPresbyterian Hospital || Committed Member ||
 * Tory Berger || TJB Consulting || Committed Member ||
 * Philip DePalo || Towson University || Committed Member ||
 * Yeong-Tae Song || Towson University || Committed Member ||
 * Holly Miller || VA || Committed Member ||
 * Patricia Greim || VA || Committed Member ||
 * You-Ying Whipple || VA || Committed Member ||
 * Terry Hearn || WellPoint || Committed Member ||

7.0 Operating Procedures and Conditions of the Use Case and Requirements Workgroup
In the short term, the Use Case and Requirements Workgroup will leverage the ONC announcement to seek external stakeholders with specific interest and subject matter expertise to participate in the Use Case and Requirements Workgroup, facilitated by the Use Case team and under the guidance of the Initiative Coordinator. Stakeholders will be asked to participate to greater or lesser extent based on their interests, contribution and commitments to the project by selecting to be an Initiative Committed Member, Invited Expert or an Interested Party. Once there is confirmation of Stakeholders, a Use Case and Requirements Kick-off will occur, which will provide the agenda and the expectations of the workgroup. Once established, this combined Use Case and Requirements Workgroup will draft, review, and update the Use Cases. Workgroup Meetings will occur on a weekly basis by conference call with face to face meetings to occur at the very end of the Discovery Phase. The process for which to document comments and feedback is one that promotes transparency and collaboration.

The S&I Framework Functions have chosen to use a table format to gather feedback from Committed Members, Invited Experts and Other Interested Parties. This table will also serve to capture the actions taken by the Workgroup Leads and/or Initiative Coordinators in relation to the comment and/or points for feedback. There is space throughout the table for Stakeholders to leave feedback, and then trace their own comments through each action taken by Workgroup Leads and the Initiative Coordinator. Ultimately, each stakeholder will be able to see how he or she was able to impact the final product. Every suggestion will be accounted for, promoting teamwork and a positive environment for those who have dedicated their time to participating in the separate Initiatives.

Once realized, the final Use Case draft will be posted to the Wiki for public comment, which is another opportunity to engage additional stakeholders. Public comments will be evaluated and dispositioned by the Use Case and Requirements Workgroup with guidance from the Initiative Coordinator and ultimately ONC.

The following types of Stakeholders are invited to participate as part of the Use Case and Requirements Workgroup:

A Committed Member is an organization or individual who has a particular interest in solving the Challenge Statement and reaching the Initiative Goal and commits to actively achieve the Use Case Deliverables. The nature of the commitment will vary depending on the Use Case Deliverables, but must be meaningful and relevant. A meaningful commitment will not be fulfilled by merely attending required meetings but instead will require significant contributions outside of meetings.

**Committed Member**
The commitment will be documented in a public Statement of Commitment within the timeline of the Call for Participation. The Initiative Coordinator will be responsible for verifying that the Statement of Commitment is meaningful and relevant to the Use Case Deliverables. Should the Initiative Coordinator believe the Statement of Commitment is not meaningful or relevant; the Initiative Coordinator will inform the prospective member of the issue with the Statement of Commitment to provide an opportunity to address the issue. Should the prospective member feel the Statement of Commitment does meet the tests of relevance and meaningfulness; the member will have the right to a single written appeal to the S&I Steering Team. After the Call for Participation timeline, Statements of Commitment from prospective members may only be approved by the S&I Steering Team. Organizational Initiative Group members may assign multiple employees to participate in the Use Case and Requirements Workgroups, but will only have one vote in Consensus decisions. Organizations that provide S&I Staff may not be Use Case and Requirements Workgroup members. When an individual represents an organization, the individual’s vote represents the organization’s vote. Lastly, organizations and individuals should not create "pseudo-organizations" to gain multiple votes in the Use Case Workgroup Consensus Process.

**Invited Experts**
Invited Experts are individuals who do not individually meet the requirements of the Use Case and Requirements Workgroup and whose organization is not a Committed Member. These Experts are invited by the Initiative Coordinator to participate in discussions.

**Other Interested Parties**
Any interested party is invited to participate in discussions and can provide comments and feedback by joining the Wiki. However, only Committed Members have voting rights in the Use Case and Requirements Workgroup Consensus Process.

Success of the Use Case and Requirements Workgroup is dependent on Stakeholders’ vested commitment, interest and expertise.

8.0 Use Case and Functional Requirements Workgroup Ground Rules

 * 1) Stakeholder participation in person or by phone; not by proxy
 * 2) Engage in Workgroup meetings in a professional manner, do not interrupt other Workgroup members when they are speaking
 * 3) Encourage Participation; bring forth subject matter expertise and knowledge relevant to the Initiative
 * 4) Actively Listen
 * 5) Present a United Front by Consensus
 * 6) Issues will be resolved in a timely manner within workgroups or offline and resolution of these issues are priority within the workgroups themselves
 * 7) Workgroup Minutes will be posted to the Wiki 48 hrs after each Workgroup

9.0 Use Case and Requirements Workgroup Code of Conduct

 * 1) Stakeholder participation in person; not by proxy
 * 2) Engage in Workgroup meetings in a professional manner; do not interrupt other Workgroup members when they are speaking.
 * 3) Encourage Participation; bring forth subject matter expertise and knowledge relevant to the Initiative
 * 4) Listen
 * 5) Vote by balloting
 * 6) Present a united front
 * 7) Reach Consensus

Related/Existing Use Cases
The following Use Cases are Related/Existing Use Cases that are relevant and have been leveraged for the Transition of Care Initiative.

**AHIC**

 * Consultations and Transfers of Care
 * Consumer Empowerment; Consumer Access to Clinical Information
 * Common Data Transport
 * Clinical Notes Detail
 * Personalized Healthcare

**NHIN Direct Project**

 * Primary care provider refers patient to specialist including summary care record
 * Direct Primary care provider refers patient to hospital including summary care record
 * Direct Specialist sends summary care information back to referring provider
 * Direct Hospital sends discharge information to referring provider

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"