> ## Documentation Index
> Fetch the complete documentation index at: https://docs.haau3.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> The CMS Health Tech Ecosystem and where the haau3 caregiver app's Kill the Clipboard work fits.

The **CMS Health Tech Ecosystem** is helping push healthcare toward a more connected,
patient-directed future. Rather than focusing only on compliance, the broader goal is to make
it easier for people, caregivers, providers, payers, and developers to use interoperable
technology to access, share, and act on health information in more practical ways.

The haau3 caregiver app participates through the **Kill the Clipboard** use case. It lets a
patient or caregiver present verified, structured health data at the point of care instead of
re-entering it on paper forms.

## Official CMS resources

<CardGroup cols={2}>
  <Card title="CMS Ecosystem Overview" icon="link" href="https://www.cms.gov/priorities/health-technology-ecosystem/overview">
    The official description of the Health Technology Ecosystem initiative.
  </Card>

  <Card title="CMS Ecosystem Categories" icon="layer-group" href="https://www.cms.gov/health-technology-ecosystem/categories">
    The categories of organizations and solutions participating in it.
  </Card>
</CardGroup>

## What the ecosystem emphasizes

<CardGroup cols={3}>
  <Card title="Patient-directed access" icon="user">
    More useful ways for people and caregivers to access and use health information through
    modern apps, services, and data-sharing workflows.
  </Card>

  <Card title="Standards-based interoperability" icon="diagram-project">
    Secure, standards-based exchange so apps, EHRs, providers, and networks connect using
    shared approaches instead of one-off integrations.
  </Card>

  <Card title="Real-world utility" icon="bolt">
    Tools that create immediate value for users rather than abstract interoperability for its
    own sake.
  </Card>
</CardGroup>

## Categories of work

CMS organizes the ecosystem into categories that show the types of solutions and participants
that can contribute to a more connected digital health environment. These help developers
understand where their work fits and what kind of user-facing value CMS is encouraging.

<CardGroup cols={2}>
  <Card title="Patient-facing apps" icon="mobile-screen">
    Applications that help people and caregivers access, understand, and use health
    information, including navigation, data sharing, chronic-condition support, and
    administrative simplification.
  </Card>

  <Card title="Providers and health systems" icon="hospital">
    Organizations that consume, exchange, and act on interoperable data to improve care
    coordination and reduce operational friction.
  </Card>

  <Card title="EHRs, payers, and data networks" icon="network-wired">
    Infrastructure participants that make data available and create the connectivity layer
    needed for trusted exchange across systems.
  </Card>

  <Card title="Friends of the ecosystem" icon="handshake">
    Organizations that accelerate adoption, implementation, trust, and reach, even if they are
    not the primary system of record.
  </Card>
</CardGroup>

## Next

<Card title="Kill the Clipboard" icon="arrow-right" href="/app/kill-the-clipboard/kill-the-clipboard">
  The patient-facing app use case the haau3 app implements.
</Card>