Specialists
Specialist console for consent-scoped review
Specialists see assigned patients, active consent scopes, appointment requests, case-card summaries, and report drafts in one console; absent consent keeps the evidence hidden.
Separate Clinic tenantConsent scope before evidenceSpecialist-owned review
Consent decides what clinic roles can review.
Clinics is not a renamed company dashboard. Owners and specialists can invite patients, record consent scopes, review appointment requests and read structured, non-diagnostic reports. Sofia continuity stays patient-facing; clinical interpretation and next steps stay with qualified professionals and local services.
Consent-first clinic workspace
Four surfaces, each tied to a consent scope.
The public clinic layer is for owner setup, specialist review, patient portal, appointment requests, and reports. Every patient-context surface names who can see it and which consent scope allows it.
Patients
Patient portal with visible controls
Patients continue with Sofia, request appointments, review profile fields, and change consent scopes before clinic staff can use patient context.
Appointments
Requests remain human-confirmed
Appointment requests show patient intent, preferred time, and status. A specialist confirms the slot; Synphoria does not auto-book unavailable time.
Reports
Reports show source, uncertainty, and limit
Clinic reports organize permitted indicators, source IDs, and uncertainty for specialist review. They are support material, not a clinical conclusion or care-plan direction.
Reports
Reports show source, uncertainty, and limit
Clinic reports organize permitted indicators, source IDs, and uncertainty for specialist review. They are support material, not a clinical conclusion or care-plan direction.
Evidence review only, not diagnosis. Synphoria organizes consented context and non-diagnostic indicators; qualified professionals keep clinical interpretation and next steps.
Appointments
Requests remain human-confirmed
Appointment requests show patient intent, preferred time, and status. A specialist confirms the slot; Synphoria does not auto-book unavailable time.
Review
What can be used, and by whom.
Specialists review non-diagnostic indicators, appointment requests, and report drafts; owners see operational status, not raw conversations.
The professional stays accountable.
Reports, patient state, and owner views are support material. Final interpretation, clinical reasoning, and next steps stay with the qualified professional.
Clinic privacy boundary
Consent decides what each clinic role can see.
Patient portal, specialist console, owner overview, and server-side Sofia guidance stay separated. A scope has to name the patient, role, surface, and allowed context before patient evidence appears.
Non-clinical boundary: evidence review only, not diagnosis. Raw companion conversations and server-side guidance are not patient portal fields.
Clinic is not Company
Clinic tenant data stays separate from Company Wellness. Patient context is not converted into aggregate employer signals or B2B reports.
Consent gates every patient surface
Patient summaries, appointment context, and report drafts render only for roles included in the active consent scope.
Guidance does not become transcript
Server-side specialist guidance can constrain Sofia's session path, but it is not quoted into the patient transcript or exposed as hidden instruction text.
Owners see operational readiness
Clinic owners can see workload, consent status, appointment flow, and report readiness; raw Sofia/Mark conversations stay out of routine owner views.
Patient agency is visible.
Consent scopes are visible. Patients can review and change them without asking the clinic to manually unwind access.
Sofia supports continuity; she is not a clinician.
Sofia can carry permitted context inside the patient experience while specialist guidance remains server-side and non-quoted. She supports evidence review, not diagnosis; clinical interpretation and next steps stay with the qualified professional.
The professional stays accountable.
Reports, patient state, and owner views are support material. Final interpretation, clinical reasoning, and next steps stay with the qualified professional.
Clinic vertical
Build the clinic workspace as its own structure, not a renamed company dashboard.
Synphoria Clinics is designed for consent-scoped patient context, specialist workflows, structured reports, and privacy-filtered owner operations. Clinical interpretation and next steps stay with qualified professionals and local services.
Category map
Explore the connected system
Clinic Continuity Platform
The patient-facing Sofia continuity layer with private companion boundaries.
Privacy, safeguarding, and non-automated decision boundaries.
The separate aggregate company domain that clinic data must not be folded into.
Read-only product specimen for understanding the broader Synphoria system.