Skip to main content
Oralstack

Product updates

Product changes, with rollout state attached.

Last updated: 10 August 2026

Public notes for clinic-facing changes that affect the front desk, patient record, checkout, or rollout. Each entry separates what is visible today, what is verified in source, and what still needs clinic setup.

Book a clinic walkthroughReview capability status
Current public release

Standalone-first setup and an accountable clinic rollout.

The public product journey now starts with how the clinic will run Oralstack. It keeps optional connections, record ownership, security evidence, and setup work visible before a walkthrough or pilot proposal.

Public now
Starting paths
New clinic, paper or spreadsheets, existing system, or optional connection.
Clinic workflows
Reception, patient care, checkout, operations, insights, and access control.
Evidence boundary
Guided-pilot, clinic-setup, and source-reviewed labels remain explicit.
Review the four setup pathsSee all seven clinic workflows

Current release notes

Changes a clinic can evaluate now.

Website changes are labelled public. Application changes are labelled source reviewed when the public page cannot prove a live clinic deployment.

  1. Public nowPublic product guideStandalone clinic setup is now the default path.

    New clinics, paper or spreadsheet moves, existing-system transitions, and optional Plato connections now have separate setup paths before the front desk starts work.

    Evidence boundary

    This is a public product-scope change. Standalone clinic go-live still requires provisioning and a readiness review.

    Review the setup paths
  2. Public nowClinic rolloutClinic accountability now starts before the walkthrough.

    The About page now maps discovery, record-boundary review, training, and support into explicit clinic and Oralstack responsibilities.

    Evidence boundary

    The model describes a guided pilot. It does not promise a self-serve rollout, fixed implementation time, or named support coverage.

    See the accountability model
  3. Public nowTrust journeySecurity reviews now keep document context.

    Requests for agreements, processing terms, subprocessors, questionnaires, and deployment evidence now open the structured review form with the requested item retained.

    Evidence boundary

    The Security page is a dated evidence summary. It is not a certification claim or a live control-monitoring feed.

    Review the security evidence
  4. Public nowMobile product guideWorkflow navigation now preserves the selected area.

    On smaller screens, one clinic workflow stays expanded at a time, the active selector stays visible, and browser history restores the matching section.

    Evidence boundary

    The desktop catalogue remains expanded so teams can compare all seven workflow groups without changing views.

    Explore the workflow guide
  5. Source reviewedApplication performanceHeavy clinic workspaces now load on demand.

    Optional workspaces, checkout editing, and patient details load when staff open them, while appointment booking remains ready in the initial clinic view.

    Evidence boundary

    This is verified in current application source. It changes payload behaviour, not clinic rollout availability or a field-performance guarantee.

    Review the dated capability snapshot

Clinic setup

The current workflow boundary, in one place.

These seven groups reuse the same rollout labels as the main product guide. This is a release-scope summary, not a live uptime claim.

Guided pilot

4 workflow groups
  • Patient care
  • Clinic operations
  • Insights
  • Organization and security

Configured in clinic setup

3 workflow groups
  • Run the day
  • Checkout and money
  • Patient access
Review every workflow boundaryCheck the dated capability evidence
Historical prototype archive10 notes from March and April 2026. Closed by default so archived experiments do not read as current product availability.
  • Pilot

    Controlled rollout: DICOM and sensor-bridge evaluation.

    Historical rollout entry. It did not represent general availability. DICOM viewing, device ingest, measurements, and the X-ray bridge remain gated and are not marketed as live.

  • Fix

    Historical prototype: local-time reschedule handling.

    This entry recorded schedule UI prototype work. Current Plato-backed reschedules are staged proposals that staff apply in Plato and then resolve in Oralstack; native scheduling remains a controlled rollout.

  • Branch

    Historical prototype: imaging branch exploration.

    The archived branch explored a DICOM viewer and sensor-bridge seam. Current product marketing does not treat either capability as available while the independent rollout gates remain off.

  • Fix

    Historical prototype: schedule grid placement fix.

    This archived UI milestone corrected appointment placement in an earlier schedule prototype. The current live claim is limited to Plato-connected schedule reads, reviewed appointment create or cancel paths, and reception flow.

  • Feature

    Historical prototype: staff appointment flow.

    The prototype explored matched-patient search and name-only appointment creation. Current staff can create Plato-backed appointments, while native patient identity and public self-booking remain outside live claims.

  • Sweep

    Historical prototype: performance and correctness pass.

    Archived engineering milestone covering caching, render work, and dead-code removal in the earlier prototype. It is not a statement of current feature availability.

  • Architecture

    Historical prototype: tenant-context coverage.

    Archived architecture milestone from the earlier application. The current production boundary uses tenant-scoped access, Postgres row-level security, origin checks, encryption requirements, and chained audit evidence; the old test counts are historical only.

  • Feature

    Historical prototype: Postgres shadow introduced.

    This entry documents a retired transition architecture in which local JSON remained the source of truth. The current app uses tenant-scoped Postgres services; local JSON is not the current production architecture.

  • Compliance

    Historical prototype: Singpass integration scaffolding.

    This entry records the initial integration seam. The current intake product can offer Singpass MyInfo retrieval when approved clinic configuration is present, with the manual intake path retained.

  • Feature

    Historical prototype: recall candidate analysis.

    This entry records the first recall-risk exploration. The current app supports recall settings, campaigns, audiences, touch queues, and recall-risk reporting; automated WhatsApp or SMS dispatch is not a live claim.