How the Home Health Hub ecosystem connects everyone
The AegisOne Home Health Hub isn’t just a device — it’s a connected ecosystem that links families at home, telehealth clinicians, health systems, payers, and employer or program sponsors through a single intelligence layer. This page explains how the pieces fit together and what data actually flows where.
Ecosystem Components
Five interconnected layers work together to deliver at-home diagnostics, clinical verification, provider integration, and insurance-ready reporting.
The Hub lives on the countertop and is the family’s “first stop” when someone doesn’t feel well or needs a routine check. It standardizes what “I tested at home” means.
- 10-inch touchscreen with calm, step-by-step guidance
- Single-use cartridges and strips for common diagnostics
- Vitals capture (BP, temperature, oxygen saturation, heart rate)
- Plain-language explanations and on-screen summaries
The AegisOne Intelligence Layer transforms raw Hub readings into structured, routeable events that clinicians, providers, and payers can actually use.
- Preliminary scoring, safety checks, and rule-based triage
- Mapping to standard clinical concepts and codes
- Longitudinal tracking across tests, vitals, and time
- Routing logic that knows which clinician, program, or system to notify
No matter how smart the device is, final clinical decisions sit with humans. Clinicians review Hub events and decide what happens next.
- Human-in-the-loop review of test events and vitals
- Telehealth encounters tied directly to Hub sessions
- Care plans, prescriptions, and referrals documented against Hub data
- Ability to override, comment on, or supplement Hub interpretations
The Intelligence Layer hands off structured events to provider systems so Hub activity becomes part of the patient’s official medical story.
- FHIR/HL7-aligned observations, diagnostic reports, and notes
- Attachment of Hub-driven encounters to existing patient records
- Support for follow-up visits, referrals, and care pathways
- Audit-friendly logs that show what happened at home and when
Payers, employers, and program sponsors see Hub activity as structured, explainable data tied to utilization, outcomes, and value-based models.
- Test events mapped to CPT / ICD and payer-specific requirements
- Utilization and adherence reporting for chronic and episodic care
- Support for condition-specific, employer, or plan-level programs
- Clear separation between demo/test content and production use
End-to-End Signal Flow
From a family member tapping the Hub to a documented, insurer-ready outcome — in one continuous flow.
The user selects who they’re testing (e.g., Alex, Mia, Jordan) and what they’re worried about: flu/COVID, sore throat, UTI, glucose check, pregnancy, or simply “I don’t feel well.”
- Profile selection for each family member
- Simple symptom questions in plain language
- Hub recommends a specific test/vitals combination
The device shows exactly what to do — swab, strip, fingerstick, or vitals — and provides feedback like “that looked perfect, I’m reading your sample now.”
- On-screen animations and timing cues
- Confirmation when the cartridge or strip is correctly inserted
- Vitals captured in the same, unified session
The Hub and Intelligence Layer convert readings and answers into a structured event with metadata: who, what, when, which test, which vitals, which symptoms.
- Preliminary interpretations and risk flags
- Standardized fields ready for EHR and payer ingestion
- Routing rules decide which clinician or program should see it
Clinicians review the event, finalize interpretation, and decide on next steps. Provider systems and payers receive a clean record of what happened at home.
- Telehealth encounters linked directly to Hub session data
- Notes, prescriptions, and follow-up plans stored in the EHR
- Claim-ready record produced for payers and program sponsors
Who Sees What in the Ecosystem
Different stakeholders see different slices of the same underlying Hub signal — with rights, roles, and context appropriate to their job.
Patients and families see a friendly view: “what you did, what we saw, what this might mean, and what to do next,” not raw lab codes.
- Plain-language summaries and traffic-light style risk cues
- History of Hub sessions by family member
- Work/school note concepts (in the demo) clearly labeled as non-clinical previews
Clinicians see standardized data they can actually chart and reason about: tests run, vitals, symptom answers, trends, and a clear audit trail.
- Timestamped events aligned to the clinical record
- Access to raw readings and Hub interpretations
- Ability to correct, comment, and override device suggestions
Payers and sponsors see population-level metrics and claims-ready records, not raw device screens from someone’s kitchen.
- Aggregated program views (e.g., respiratory season utilization)
- Evidence of guideline-consistent use and follow-up
- Signals for value-based care and contract performance
Architecture & Extensibility
A hardware-anchored platform that is intentionally left open for acquirers and partners to plug in their own tests, networks, and programs.
The Hub handles user interaction, basic validations, and the first layer of interpretation — keeping latency low and experience smooth even if connectivity blips.
- UX, sample timing, and basic quality checks handled on-device
- Local safeguards to avoid obviously invalid readings
- Graceful handling of offline/low-connectivity scenarios
The Intelligence Layer is where patterns, routing decisions, and longitudinal analytics live, designed to plug into an acquirer’s broader data and AI stack.
- Rules and models tuned to partner clinical protocols
- Program- and condition-specific routing configurations
- Exportable data structures for enterprise analytics environments
AegisOne exposes results and controls via dedicated portals and standards-based APIs — a foundation that a strategic acquirer can harden and extend.
- Client Portal for providers and partner programs
- Insurance Portal for payers and plan sponsors
- RESTful and standards-aligned APIs for deep integration