Help centre

How to use Clinicom without guessing

Step-by-step guides for the Riverside demo, live interpreter, practice dashboard, roles, AI sidecar, and trust honesty. Use search or the left menu. For short questions, open Ask Clinicom from the Help button.

01 · Start

Get started in five minutes

  1. Open the live sample encounter

    Go to /app?story=adaeze. This loads the Adaeze Okonkwo Riverside scenario (Yoruba to English) with safety and cultural notes.

  2. Send or record a turn

    In Composer, keep direction as Patient to clinician, languages yo → en, type a patient turn or use Record, then Send. Review safety flags before continuing.

  3. Open the practice dashboard

    Sign in at /dashboard/ with the manager demo account. Check Overview activity, Sessions, Patients, and Settings sidecar status.

  4. Optional: request a practice demo

    Subscription pricing is not published yet. Use Request a demo for a guided walkthrough, or keep exploring the seeded Riverside demo yourself.

Note: Clinicom assists communication. Clinicians own clinical decisions, authorship, and safety acknowledgements.

02 · Demo

Riverside demo sign-in

Seeded demo practice: Riverside Family Practice.

RoleEmailPasswordUse for
Practice manager [email protected] demo-manager-2026 Team, patients, settings
Read-only auditor [email protected] demo-auditor-2026 Audit and compliance review

03 · Map

Surfaces and URLs

SurfaceURLPurpose
Marketing/Product story and demos
Interpreter PWA/appLive clinical encounter
Practice dashboard/dashboard/Team, sessions, patients, billing
Docs and guides/docsThis help centre
Organisations/organisationsROI, PCN, pharmacy paths
Status / privacy/status, /privacyTrust surfaces
Embed/embed/Embeddable shell
API reference (Swagger)/api/docsInteractive OpenAPI for developers
API/api/*Auth, interpret, patients, billing

Default local port is 8600.

04 · Interpreter

Live interpreter guide

Encounter chrome

  • Live badge and case title summarise the current session.
  • Metrics show message count, safety flags, and confidence.
  • Context opens patient/clinical/tools drawers.
  • Handoff builds a clinician-owned clinical summary.
  • Sample reseeds the demo encounter; New clears history for a fresh session.

Conversation record

  • Patient and clinician turns appear as timeline cards.
  • Safety flags and cultural notes interrupt for review.
  • Deep AI assists (cultural adapt, teach-back score, safety triage assist) appear on turns when the sidecar advertises them.
  • Use Edit / Accept when authorship review is required.
  • Open Source lines for original AI or translated variants; source labels stay honest (keprix-gemini, stub, and so on).

Deep AI card

  • The live shell shows a Deep AI capability card on boot via GET /api/capabilities.
  • Contract version should read 2.0 when the Keprix or Carina sidecar is healthy.
  • Teach-back scoring lives under Context → Tools; it is an assist for clinician judgement, not a grade that replaces review.

Composer

  1. Set Direction (patient→clinician or clinician→patient).
  2. Choose From and To languages.
  3. Type the turn or tap Record, then Send.
  4. Toggle Easy Read when you need plain-language patient support.

Safety: Acknowledge flagged content in the safety dialog. Clinicom never dials emergency services for you.

05 · Dashboard

Practice dashboard guide

  • Overview: team activity, next actions, usage signals, plus the Deep AI brief card (session depth, safety flags, teach-back average, honesty metrics).
  • Sessions: searchable encounter records and summaries.
  • Patients: consent, history, GDPR export/erase (managers).
  • Analytics / Feedback: language volume and product feedback. Deep briefs also load from GET /api/analytics/deep-brief.
  • Team: invites and role management.
  • Billing: org billing surface for later subscription cutover (Stripe when configured). Public prices are not on the marketing site yet.
  • Settings: sidecar profile, contract version, latency, capability tool list, Google SSO indicators.
  • Trust / Clinical safety: honesty chips and evidence surfaces when enabled.

Onboarding checklist appears until setup is complete (Riverside hides the completed tour by design).

06 · Access

Roles and permissions

Capability clinician readonly_admin practice_manager
Live interpretYesNoYes
View patientsYesYesYes
Export / erase patientNoNoYes
AnalyticsNoYesYes
Audit logNoYesYes
Invite usersNoNoYes
Billing / settingsNoNoYes

superadmin is support/break-glass. Linked patients need consent before record/send. Anonymous turns without a linked patient do not require consent.

07 · Patients

Patients, consent, export, erase

  1. Open Dashboard → Patients.
  2. Create or select a patient; set preferred language and notes.
  3. Record consent (verbal, written, or implied) before linked recording/sending.
  4. Managers can export a JSON pack or erase a patient. Erase redacts linked message and event text and removes the patient record.

08 · AI

AI and sidecar (contract v2)

Interpretation is the AI core of Clinicom. Sidecars advertise capabilities with GET /clinicom/capabilities (mirrored in the app as GET /api/capabilities). Contract version 2.0 is the shared target across Clinicom, Keprix, and Carina packs.

Live encounter tools

  • transcribe, translate, simplify, speak

Deep AI tools (v2)

  • clinicom_cultural_adapt: culture-aware phrasing notes for the turn.
  • clinicom_teachback_score: scores how well a patient restates the plan (assist only).
  • clinicom_safety_triage_assist: urgency and triage cues for clinician acknowledgement.

Deep assists run through the interpreter pipeline and can feed the overview Deep AI brief. Tool status may be live or explicitly stub; Clinicom keeps those labels visible.

Profiles

  • keprix (preferred production path): Keprix Clinicom pack; ML service and/or Gemini when configured.
  • carina: optional host for the same v2 contract.
  • local-clone: continuity/dev only.

Check Dashboard → Settings for profile, contract version, tool list, and latency. Ask Clinicom (Help widget) answers from FAQ and docs; it is not the interpreter AI and does not call deep clinical tools.

Clinicom is its own product. Using a Carina sidecar does not make Clinicom a Carina product.

Honesty: Source labels such as keprix-gemini, keprix, or stub matter. Do not treat stub or fallback paths as live clinical AI. Deep assists support clinician judgement; they do not diagnose or prescribe.

09 · Evaluate

Evaluate Clinicom

  • Public subscription amounts are not decided yet. Primary nav and homepage focus on value and demos, not a buy funnel.
  • Explore value now with the Riverside seeded demo and the live interpreter sample.
  • Request a practice walkthrough from Organisations → Request information.
  • Illustrative ROI planning remains available at /organisations#roi for conversation prep, not as a price quote.
  • Internal placeholder only: /pricing (noindex stub; not linked from primary nav). Fill amounts when you decide them.

10 · Trust

Trust and claim honesty

  • BSL: starter/curated phrases, not certified simultaneous interpreting.
  • FHIR: sandbox / structured handoff ready, not default live NHS writeback.
  • NHS CIS: sandbox/readiness scaffold.
  • DTAC / DCB0129: draft evidence packs; external audit pending.

More: /status, /privacy, dashboard Trust surfaces.

11 · FAQ

Frequently asked questions

Loaded from the same grounded FAQ used by Ask Clinicom.

Loading FAQ…

12 · Chat

Ask Clinicom

Use the Help button (bottom right) for short grounded questions: demo login, roles, sidecar, security/trust honesty. Greetings work. Medical advice and unknown topics are refused.

Ask Clinicom does not replace these guides. Prefer this page for step-by-step work.