Talk With Acuity.

You

Built around your patients. Your workflows. Your economics.

Acuity is not another seat-based software tool. It is a longitudinal clinical intelligence layer designed to operate across the population you are responsible for—then help your teams understand who needs help, why, and what to do next.

For provider organizations, ACOs, care-management groups, home/post-acute organizations and other teams accountable for longitudinal patient outcomes.
ACUITY.health
Population → Patient → Cue
Population Cue20
Who needs
help now?
AB
CD
EF
GH
JK
LM
NP
Patient 01Worsening
Patient 02Review
Patient 03Stable
Patient longitudinal state
Illustrative product rendition
Priority ↑
CHI73
Worst systemCV
Trend↓
WHY THIS PATIENT MOVED

Weight is above recent baseline, dyspnea is newly documented, and the cardiovascular system index is worsening.

Review latest RPM + symptomsClinicalCue
Medication reconciliation completeTrusted state
Outreach workflow readyAction
Product rendition for website display; interface details may evolve by deployment.
Reference deployment

AllHeart Home Health

Acuity is being deployed with AllHeart Home Health to support longitudinal patient management in a distributed home-health setting where clinical information often lives across multiple systems and locations.

5Rural Tennessee counties in the deployment footprint.
QHIN + RPMExternal longitudinal records and remote patient data can contribute to the patient state.
Mobile + PortalClinician-facing workflows extend from population operations to patient-level action.
LongitudinalDesigned for continuous patient management rather than a single encounter or episode.
Technical specification

What buyers need to know.

Acuity is designed as an interoperability-native clinical state and orchestration layer. This technical profile is concrete enough for initial buyer and technical diligence.

Clinical variables
~140 longitudinal inputs across symptoms, diagnoses, vital signs, laboratory values and related clinical evidence.
Body systems
16 clinical systems contribute to system-level indices and the composite Continuous Health Index.
Core data standards
FHIR, C-CDA and QHIN-connected exchange, with additional clinical, claims, RPM and patient-generated inputs incorporated according to deployment scope.
Clinical state model
Evidence → interpretation → reconciled state → clinician-authored state. Provenance and source boundaries are retained through the workflow.
Latency target
≤5 minutes from receipt of a supported event to state-refresh / Cue eligibility under normal operating conditions.Design target; upstream QHIN, source-system and network latency are excluded. Final SLA is deployment-specific.
Clinical reasoning
Deterministic CHI + bounded ClinicalCue orchestration, with visible evidence supporting state changes and clinician review.
Authorization + governance
CyberCue enforcement for identity, role, tenant, consent, data rights, provenance, signed status, permitted scope and destination.
Deployment options
Acuity-hosted clinical platform for mobile + portal workflows; API-first integration for customer systems; and Acuity Normalize for interoperability normalization as a narrower infrastructure deployment.
Interfaces
Provider mobile experience, nurse-manager / operations portal, patient-facing workflows and APIs. Surface area can be scoped by implementation.
Security posture
Server-side tenant isolation, least privilege, evidence provenance and auditable clinical state transitions are core architectural requirements.
Commercial clarity

PMPM—not seat-based SaaS.

Acuity aligns pricing to the population being managed. That gives provider organizations a cleaner way to model cost against attributed lives, care-program economics and future value-based arrangements.

Population-aligned

Pricing scales with attributed patients rather than forcing clinical organizations into per-user licensing.

Implementation scoped

Professional services depend on integrations, workflow configuration, migration and deployment complexity.

Expandable

Additional clinical, workflow and care-economics modules can be layered onto the baseline deployment.

Phase 1 platform starting point
$4.75per attributed patient / month
✓
Longitudinal interoperability and patient-state foundation
✓
CHI and core clinical prioritization workflows
✓
Population and patient Cue surfaces within deployment scope
✓
Professional services quoted separately for implementation, integrations and configuration
Starting commercial framework shown for buyer clarity. Final PMPM and professional-services pricing depend on population size, integration scope, modules, implementation requirements and contract terms.
Deployment paths

Start where you need Acuity most.

A buyer does not need to adopt every Acuity surface on day one. The architecture supports phased adoption around the organization's highest-value problem.

01 — Normalize

Begin with QHIN / C-CDA / FHIR normalization and provenance-preserving clinical data infrastructure.

02 — Clinical intelligence

Add longitudinal clinical state, CHI, ClinicalCue and population/patient prioritization.

03 — Action + economics

Extend into clinical authoring, RPM / care-management workflows, CareCapture and provider-led VBC strategy.

Your population

Bring your data, your clinicians and your economics into one longitudinal operating layer.

Start with interoperability, clinical intelligence, or a defined population workflow. Acuity can expand as the operating model expands.

Talk with Acuity