01Local start only
The patient would start Bonsai on the device. A remote system cannot start a session or raise the clinician’s limits.
Clear limits
What recorded activity cannot tell you.
An event does not prove consumption, a missed dose, or a health outcome. Patient feedback is a report, not verified clinical evidence.
Demo controls
Patient start
The patient starts within the clinician’s limits.
Blocks
Remote start · role-only clinical access
Separate records
Plans, activity, and patient feedback remain distinct.
Safety reports
Flagged side-effect reports await clinician review.
Where actions happen
Who controls each part?
The clinician sets the plan in the Care Portal. In the demo, the patient starts in the app. The linked care team can review records after upload—not before.
Device and software roles
Cloud platform
- Plan setup
- Record storage
- LOCAL START ONLY
Patient app
- Product and plan view
- Record upload
- DEVICE-LOCAL
Bonsai concept
- Proposed plan limits
- Proposed event recording
Read by topic
Controls and limits in the demo.
Operating boundaries, access rules, and evidence limits answer different questions. None establishes validated hardware safety.
02Who can see care records
Care access requires an active patient relationship. Support and administrator roles alone do not grant it.
03Consent and an audit trail
The demo records which consent was accepted, along with plan changes, record access, and review.
04Research and privacy
Researchers see de-identified study views, not identifiable care records. The public inquiry form is not a place for health details.
05Fictional examples
The demo uses fictional records and simulated sessions, not working Bonsai hardware.
06What this site does not claim
A session record does not measure chemical intake or prove benefit. This site does not establish safety outcomes, regulatory approval, certification, or commercial availability.