saascode
healthcare & clinical·run 003 · Apr 2026

Hearthstone

A multi-client monitoring workspace that normalizes consented sensor observations, explains baseline deviations and routes reviewable alerts to authorized care teams.

Genesis score6.41/10
Make Hearthstone real.0/500
500 more votes and Hearthstone is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Home-care agencies may receive motion, fall, sleep or vital-sign observations from different household devices while coordinating many clients. The supplied research confirms mature facility-focused monitoring and usable sensor infrastructure, but did not find a direct pure-software aggregator for independent home-care agencies in its reviewed set. One referenced capability remains unverified.

Hearthstone binds every device and data stream to a client, lawful authority, consent scope and observation time. It builds a client-specific baseline and proposes anomaly candidates with source evidence, missing data and confidence. An authorized care-team member reviews the candidate and follows an agency-approved escalation protocol.

Sensor output is not a diagnosis, fall confirmation, emergency determination, proof of adherence or measure of caregiver performance. A sent family notification does not prove receipt or appropriate response. Observation, anomaly candidate, clinical or operational review, outreach decision, delivery, acknowledgment, intervention and outcome remain separate.

The first release should cover one agency, one low-risk sensor class and a read-only workflow. It must fail visibly when devices are offline, exclude employee scoring, avoid hidden cross-agency pooling and direct urgent concerns to existing emergency procedures rather than pretending the dashboard is an emergency service.

Who pays — and why

Clinical operations or care-coordination leader at an independent home-care agency supervising many consented clients

What it unlocks
A device ledger separating client, household, device owner, sensor class, consent, data authority, connection state, calibration, observation time and gap
An anomaly record separating baseline window, observed deviation, model version, confidence, missing data, reviewer finding, correction and disposition
An escalation trail separating protocol, authorized recipient, notification, delivery, acknowledgment, outreach, intervention, clinical documentation and outcome
How Genesis scored it
6.41across seven criteria
tension 6temporal 6blindspot 5buyer 8leverage 8convergence 9why-not 5
9
Convergence

The record contains two cross-references and three inbound connections and received strong convergence scoring.

8
Buyer persona

Independent home-care agency care operations is a concrete buyer and multi-client workflow.

5
Why nobody did it

The gap is clearer than the barrier that kept it unbuilt.

Why it scored well

The supplied research confirms relevant sensor infrastructure, a funded facility-focused adjacent product and a reviewed-set gap for an independent-agency software aggregator.

What's holding it back

One capability remains unverified, clinical and emergency workflows require human operations, device heterogeneity is costly and no structural incumbent copying cost is established.

Signals detected3 sources crossed
SignalSupplied competitor research

SignalSupplied capability research

SignalSupplied market scan

Direction briefhearthstone.md
hearthstone.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.