An agreed relationship
- Scope
- Agreed shared information
- Boundary
- Purpose-limited access
- Review
- Confirm the relationship
Caregiver access
Keep relationships and sharing explicit, with access limited to the agreed purpose.
Understand how Bractis approaches clinic separation, sensitive access, record history, and system state. Review the scope and evidence required for the work you intend to run.
Preparing for launch. This page describes the design approach, not a certification.
Illustrative access model. Evidence is required before live use.
The person, patient, source, and current state belong with the work being performed.
Clinic and facility
Patient and practitioner
Role for the work
Resolve clinic, facility, practitioner, patient, and role context before loading the work.
Keep sensitive access tied to a reason, a defined scope, and review.
Preserve the source of information and distinguish drafts from signed clinical records.
Work preserved on device
Confirmation may be pending
Keep local saves, provider outcomes, and conflicts clear enough to act on.
Illustrative workflow principles. A local save does not confirm a provider outcome.
Clinic, facility, practitioner, patient, and role context must be resolved before work is loaded. Tenant separation and high-risk workflows require supporting evidence before they can be relied on in live use.
Plan an evidence reviewRole permissions are one part of the decision. Additional access needs its own reason, scope, and review.
Keep relationships and sharing explicit, with access limited to the agreed purpose.
Review the reason and scope for break-glass access to sensitive information.
Define what support needs to access and how that access is reviewed.
The responsible practitioner reviews and signs.
Distinguish imported information, delegated observations, and generated drafts from reviewed clinical content. Clinical review and signing remain with the responsible practitioner.
Explore clinical reviewSaved locally, queued, synchronized, failed, signed, and conflict review carry different meanings. Unknown provider outcomes require confirmation or reconciliation before repeating consequential work.
Explore recovery and synchronizationUse these pages to frame the discussion about data, accessible use, and external connections.
Confirm evidence for the specific workflow and environment you intend to use.
No. This page describes the design approach. Security and compliance claims require evidence for a defined scope. Discuss current evidence, gaps, and live-use requirements with Bractis.
Bractis is preparing for launch. Availability, onboarding, privacy, security, and clinical-safety requirements must be reviewed before live use.
No. Access also depends on clinic, facility, purpose, and the sensitivity of the information. Caregiver, exceptional, and support access require their own scope and review.
No. Local save, synchronization, and provider confirmation are distinct. Unknown external outcomes need review or reconciliation before they are treated as complete.
Use the contact form to describe your organisation and evaluation needs. Do not include patient records, credentials, or sensitive clinical information in a public inquiry.
Tell us which workflows, access boundaries, and evidence your evaluation needs.
Talk to Bractis