Use+Case+Simplification+-+Charter



**Use Case Simplification __DRAFT__ Charter:** **Updated 11/10/2011 after UC Simplification WG Session


 * **Challenge** || To identify a core set of constructs broadly applicable to and re-usable in subsequent specification of Use Cases. ||
 * **Scope Statement** || Scope is the common (core) set of requirements, actors, actions, data elements (names, definitions, representations, base standard source) and data element sets across all Use Case Scenarios, across the S&I Framework (and potentially beyond). Ensure workgroup output is consistent with, enables and supports Meaningful Use. ||
 * **Value Statement** || Common constructs:


 * 1) Ensure uniformity across Use Case specifications
 * 2) Affirm that standards-based messages, documents, data elements, vocabularies and protocols (functions/processes/services) offer a path to consistent and interoperable implementation.
 * 3) Make specifications available in a repository (with appropriate tooling) to allow rapid use case prototyping.
 * 4)  Provide specifications on which users can take action to promote a common understanding and application of health information concepts that are exchanged or stored.  ||
 * **Target Outcomes** || # Repository of common (core) constructs: requirements, actors, actions, data elements (names, definitions, representations, base standard source), data element sets.
 * 1) Repository Management Tools: to add, update, query/browse.
 * 2) Use Case Development Tools: to adapt or build out new Use Cases from core constructs. ||
 * **Timeline** || For duration of S&I Framework. ||
 * **Expected Deliverables** || As identified in Target Outcomes ||
 * **Standards, Stakeholders** || # Applicable standards to meet requirements.
 * 1) Stakeholders represented in Use Case Scenarios. ||
 * **Potential Risks** || # Use case “silo” syndrome.
 * 1) Disjunction between conceptual and implementable outcomes.
 * 2) Too narrow focus on exchange: point-to-point vs. end-to-end.
 * 3) Insufficient focus on understanding content from the sender and receivers views. ||