Use cases

The goal of MortalityMinder (MM) is to enable healthcare researchers, providers, payers, and policy makers to gain actionable insights into how, where, and why midlife mortality rates are rising in the United States (US).

MortalityMinder provides a compelling and engaging tool to investigate the social and economic determinants of mortality. MM:

• Documents the disturbing rise in midlife Deaths of Despair due to suicide, overdose, and self-harm and other national/regional increases in midlife mortality rates due to All Causes, Cancer, and Cardiovascular Disease.

• Highlights potential social determinants through statistical analysis of factors associated with disparities in regional trends in midlife mortality rates.

• Provides county-level confirmation of trends and hypothesized causes.

• Yields insights that can be used to create region-specific interventions and best practices to meet unmet healthcare needs.

• Enables rigorous analysis of potential determinants of health by local, state, and national healthcare organizations to support development of programs, policies, and procedures to improve longevity.

The Overview Video demonstrates some use cases.

Use Case Structure From Use Cases vs User Stories in Agile Development* A use case is a description of a set of interactions between a system and and one or more actors (where ‘actor’ can be people, or other systems: for example, both online shoppers and PayPal can be actors). They are usually created as documents, and generally include this kind of information:

• Use case title
• Rationale/description/goal
• Actor/user
• Preconditions (the things that must have already happened in the system)
• Standard path or main success scenario (what will usually happen, described as a series of steps)
• Alternate paths or extensions (variations on the above/edge cases)
• Post conditions (what the system will have done by the end of the steps).

Community-Contributed Use Cases

We welcome your suggestions for possible use cases!