Skip to main content

Clear access.
Accountable clinic work.

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.

Access has a context
Clinic and facility
Person and responsibility
Purpose and scope
The task

Illustrative access model. Evidence is required before live use.

Keep responsibility
close to the action.

The person, patient, source, and current state belong with the work being performed.

  1. Illustrative visit record

    Context before action

    01

    Clinic and facility

    02

    Patient and practitioner

    03

    Role for the work

    Context stays with the record
    Resolve context before loading work.
    01

    Clinic context

    Resolve clinic, facility, practitioner, patient, and role context before loading the work.

  2. Illustrative access scope

    Access with a purpose

    PERSON / PURPOSEResponsible person
    Scope
    Defined scope
    Boundary
    Sensitive information
    Review
    Reason and review
    Permissions are one part of the decision.
    02

    Purposeful access

    Keep sensitive access tied to a reason, a defined scope, and review.

  3. Illustrative sequence

    Source to clinical record

    1. 01Source retained
    2. 02Draft for review
    3. 03Clinician signs
    Drafts and signed records remain distinct.
    03

    Source and review

    Preserve the source of information and distinguish drafts from signed clinical records.

  4. Illustrative comparison

    Read the system state

    Local save

    Work preserved on device

    Provider outcome

    Confirmation may be pending

    Keep conflicts explicit
    A local save does not confirm an outcome.
    04

    Visible system state

    Keep local saves, provider outcomes, and conflicts clear enough to act on.

Illustrative workflow principles. A local save does not confirm a provider outcome.

Start with the right
clinic and patient context.

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 review
Illustrative access scope

The right visit context

PERSON / PURPOSEPractitioner and patient
Scope
Clinic and facility
Boundary
Task permissions
Review
Resolve before loading work
Identity, facility, and purpose define the work.
  1. 01Confirm clinic and facility context
  2. 02Resolve the person and their responsibility
  3. 03Apply the scope needed for the task

Sensitive access
needs a clear purpose.

Role permissions are one part of the decision. Additional access needs its own reason, scope, and review.

Illustrative access scope

An agreed relationship

PERSON / PURPOSEChosen caregiver
Scope
Agreed shared information
Boundary
Purpose-limited access
Review
Confirm the relationship
Sharing does not grant unrestricted access.

Caregiver access

Keep relationships and sharing explicit, with access limited to the agreed purpose.

Illustrative review

Exceptional access

Scope
Reason for access
Evidence
Defined sensitive scope
Next action
Review the exception
Review required
Reason and scope stay attached to access.

Exceptional access

Review the reason and scope for break-glass access to sensitive information.

Illustrative access scope

Support for a specific task

PERSON / PURPOSESupport request
Scope
Required information
Boundary
Access limited to purpose
Review
Review support access
Support access has its own scope.

Support access

Define what support needs to access and how that access is reviewed.

Source informationClinical reviewSigned record

The responsible practitioner reviews and signs.

Keep the source
with the clinical record.

Distinguish imported information, delegated observations, and generated drafts from reviewed clinical content. Clinical review and signing remain with the responsible practitioner.

Explore clinical review

Name the state
before the next action.

Saved 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 synchronization
  1. 01Show where the work is saved
  2. 02Keep provider outcomes explicit
  3. 03Preserve conflicts for deliberate review

Review the requirements
around your workflow.

Use these pages to frame the discussion about data, accessible use, and external connections.

Questions about
trust and readiness.

Confirm evidence for the specific workflow and environment you intend to use.

Does this page certify Bractis as secure or compliant?

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.

Can we use Bractis for live patient work today?

Bractis is preparing for launch. Availability, onboarding, privacy, security, and clinical-safety requirements must be reviewed before live use.

Does a staff role grant unrestricted access?

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.

Does a saved record mean an external action completed?

No. Local save, synchronization, and provider confirmation are distinct. Unknown external outcomes need review or reconciliation before they are treated as complete.

How can we discuss our security requirements?

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.

Bring your requirements
to the conversation.

Tell us which workflows, access boundaries, and evidence your evaluation needs.

Talk to Bractis