110 likes | 233 Vues
This document provides a comprehensive overview of the Transitions of Care (ToC) Use Case, focusing on data exchange operations. It outlines the operational context, stakeholders involved, necessary information flows, and required data types for effective data exchange. The development process is explained, emphasizing the definition of business actors participating in the information exchange and their roles within scenarios. This overview is meant to enhance understanding of the process, requirements, and the functionalities necessary for successful data interoperability.
E N D
ToC Use Case Components Lightning Overview Presented to LCC WG December 1, 2011
Purpose of the Use Case The Use Case describes: • The operational context for the data exchange • The stakeholders with an interest in the Use Case • The information flows that must be supported by the data exchange • The types of data required in the data exchange
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.
Transitions of Care – Use Case Diagram http://wiki.siframework.org/file/view/SIFramework_ToC_UC_v%201.1.docx
Transitions of Care – Context Diagram Actors & Roles Context Diagram http://wiki.siframework.org/file/view/SIFramework_ToC_UC_v%201.1.docx
[1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references. [1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references. Review of Key Use Case SectionsFunctional Requirements
[1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references. [1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references. Review of Key Use Case SectionsData Sets