Alix Goss

Bob Dieterle

Tim Young

Rick Geimer

Patrick Murta

Alex Kontur

 

Use Cases

  • Tiger Team has been meeting for ~3 months
    • Meetings to date have primarily focused on developing a format/presentation approach for use cases
  • Originally had 20+ use cases to define independently
  • New approach is to group use cases by common theme. Each use case document will focus on a particular theme (e.g. provider to payer request for patient information), and include a set of scenarios that represent variations on the theme (e.g. coverage requirements discovery)
    • Use cases rely on core use case capabilities that may be shared across use cases. Core capabilities will be defined separately

 

Example Use Case [Patrick Murta]

  • Use cases are not necessarily defining functional system requirements, rather they define the capabilities needed to operate at scale
    • Da Vinci is more focused on functional use cases
  • Each use case document is based on the classic model and includes:
    • Intro & background – information about the P2 FHIR Task Force & which “approach” the use case represents (barrier use case, generic use case, or Da Vinci use case)
    • Items deemed in scope (typically the core capabilities the use case relies on)
    • Items deemed out of scope
    • Assumptions
    • Primary/secondary actors
    • Stakeholders/interests – indicates entities that may have an interest in the use case, includes both actors and entities that aren’t necessarily involved in the workflow
      • Question on whether or not to call out ONC as a stakeholder
    • Pre-conditions/post-conditions
    • Definition of the high-level use case theme
    • Definition of the variations on the general theme (i.e. the scenarios)
  • No labels