ClinicOS StudioCoverage & system comparison
What each system covers, what we can demonstrate today, and what must still be validated before a production transition.
Replace PractiPlan. Connect to PixelData. ClinicOS proposes replacing PractiPlan for clinic operations and the patient experience. PixelData remains the PACS and imaging archive: we connect it to ClinicOS so authorised patients can access their released scans and reports. Replacing PixelData is not in scope. “Not verified” does not mean a vendor lacks a feature. A working fictional demo or mockup is not clinical production readiness.
System responsibilities & integration
| Capability | PractiPlan — vendor documentation | PixelData — retained imaging system | ClinicOS — current scope |
|---|---|---|---|
| Appointments & availability | Documented: online scheduling, flexible slots and multiple locations. | Not assessed as a scheduling product. | Connected fictional booking flow; richer weekly roster/evening/weekend planning in mockup. |
| Patient portal & required actions | Documented: appointments, questionnaires, notifications, documents and dossiers. | Vendor advertises imaging access; clinic-specific patient portal not verified. | Public patient demo; current native experience uses five isolated local scenarios. |
| Patient records & change history | Vendor describes consultation records; detailed audit/export coverage needs verification. | Imaging studies and PACS are its documented focus; full record workflow not assessed. | Fictional records, versioned internal notes, History and named change logs in protected CRM. |
| Reports & clinical release | Documents/dossiers documented; clinical release contract needs confirmation. | PACS/viewer capability documented; report permissions and API need vendor confirmation. | Scoped release/hide demo exists. Structured findings/recommendations are fictional local app/mockup content. |
| DICOM archive & viewer | PACS/DICOM integration not verified. | Documented PACS and browser viewer supporting DICOM modalities, including mobile browser use. | Local public JPEG Baseline cine sample works. No real PixelData/PACS connection; not a replacement PACS. |
| AI assistant & workflows | Comparable AI/workflow scope not verified in this review. | Comparable administrative AI/workflow scope not verified. | Server AI/knowledge and demo workflows exist. Current local app and design assistants use scripted responses. |
| App content & FAQ publishing | Comparable app-content CMS scope not verified. | Not assessed as a content CMS. | Protected content/knowledge draft and release flows exist; FAQ remains separate from app/chat. |
| Patient & influencer referrals | Comparable referral tracking not verified. | Not assessed as a referral platform. | Codes, attribution and €100 rewards are mockups/local demonstrations, with no tracking or payouts. |
| WhatsApp & social planner | Exact channel integrations/licences need confirmation. | Not assessed for these channels. | Proposed integrations only. Social planner is out of scope for the initial delivery. |
| Migration & production readiness | Export format, attachments, identifiers and access require vendor validation. | VPN/DICOM-node approach discussed with vendor; deployed interface and licences unverified. | Phased PractiPlan replacement is a proposal; PixelData is retained and integrated. Approximately 4,400 records require export inspection; production acceptance remains open. |
Coverage across our layers
| Layer | Covered / demonstrated | Current evidence level | Still required |
|---|---|---|---|
| Patient app | Native tabs, five JSON scenarios, appointments, preparation, documents, notifications, local scripted booking changes, DICOM sample. | Local executable demo | Real patient login, full clinical reports, live PACS, native push and secure report sharing. |
| CRM | Protected fictional records, notes/history/audit, booking and workflow review tasks. | Connected demo + richer mockups | Real patient operations, full role model, production migration and weekly roster backend. |
| CMS | App content, FAQ, templates and publishing. Referrals and influencer management demonstrated in designs. | Connected demo + mockups | Live referral attribution/payouts; native channel delivery. Social planner: out of scope. |
| Brain | Server-side AI configuration/knowledge and fictional workflow runtime; visual design and execution screens. | Connected demo + mockups | Broader workflow actions, production governance, drag-and-drop editor refinement. |
| Today | Fictional agenda, tasks and briefing; mockup adds per-clinic today/tomorrow and scripted Ask AI. | Connected demo + mockups | Role-specific live operations and integrated production data. |
| Access & integrations | Owner Google/Clerk gate in actual portal; public fictional selectors in demos. | Partial | Configurable staff roles, verified patient identity, PixelData/API contracts, messaging providers. |
Transition without losing context
1. Validate exports and access. Inspect the approximately 4,400 records, attachments, historical appointments and source identifiers.
2. Map and trial the migration. Patient → record → encounters → reports/documents/related studies. Validate matching and released access.
3. Connect to the existing PixelData system. Confirm the PixelData interface, network access, licence and supported study formats; keep PixelData as the source of imaging. No PixelData replacement or imaging archive migration is proposed.
4. Pilot before replacing PractiPlan. Agree acceptance, role/clinic scope, rollback and reconciliation before switching production operations.
Not every user sees everything. Staff roles and permissions govern visibility and management; patients see only their own released items. Internal notes and audit remain staff-only. The role matrix in the presentation is proposed, not an implemented security boundary in the mockup.
Sources & evidence
Vendor information checked on 22 October 2026. Vendor capabilities and the installed clinic configuration must be confirmed independently. ClinicOS coverage is based on the project’s source/verification documentation and local demo reports.
Prepared for product discussion. No prices, clinical guarantees or unverified integration commitments.