Prototype portal. Synthetic/de-identified demo only. No PHI. Not for live patient care. Validation in progress — governance required. Assistive outputs require clinician review; OrthoPath does not autonomously diagnose, order, or prescribe.
Last updated: 2026-06-15
`pendarlink.com` is a prototype / demonstration / presentation / collaboration portal for OrthoSphere — not a production clinical SaaS product. Public surfaces may describe or show synthetic or de-identified overview demos. Deeper controlled demo workspaces remain sign-in and access-gated. Clinical validation is not complete. Institutional pilots require governance approval.
OrthoSphere is an orthopaedic intelligence platform prototype that includes assistive clinical decision support (OrthoPath), evidence retrieval and citation (OrthoRAG), OncoRegistry (orthopaedic oncology case workspace prototype: guided intake, documents, timeline, and MDT-oriented views), and—when your tenant enables them—OrthoPilot (operational cockpit and drafting), OrthoSearch (research-assist and literature workspace), and OrthoMonitor (monitoring and follow-up visibility for controlled-demo cases). Only OrthoPath (through its CDS engine) emits clinical recommendation objects when you run modules or snapshots; those outputs require independent clinical review by a qualified clinician. OncoRegistry is built on the same advanced prototype case and protocol infrastructure but is positioned as data capture and workflow assistance—it does not autonomously recommend treatment. The platform does not autonomously diagnose, prescribe, order tests, or guide discharge. The clinician retains full professional and legal responsibility for all clinical decisions.
Do not enter patient identifiers or any Protected Health Information (PHI) into this tool. Not for live patient care.
This portal remains a prototype / demonstration / collaboration site. Any broader institutional use remains governed by validation, governance, and data-protection review — not offered as a public paid clinical product today.
All clinical logic was authored, reviewed, and validated by Dr. Pendar. Evidence anchors for each module are drawn from published guidelines and peer-reviewed literature cited in the per-module evidence manifests. No rule fires without a traceable evidence source.
This system has not undergone regulatory clearance (e.g. FDA 510(k), CE marking). It is provided as an assistive reference prototype only — not approved for patient care.
OrthoSphere is the umbrella orthopaedic intelligence platform prototype. It is not only CDS: it brings together deterministic CDS, evidence retrieval, OncoRegistry (oncology case workspace prototype), and tenant-gated OrthoPilot, OrthoSearch, and OrthoMonitor where those features are enabled, each with strict authority boundaries.
| Service | Role | Authority boundary | |--------|------|--------------------| | OrthoPath | Deterministic orthopaedic clinical decision support prototype (Core: single-encounter; advanced prototype: cases, timeline). | Only component that may emit recommendation objects (via CDS when you evaluate). All outputs require independent clinical review. | | OncoRegistry | Orthopaedic oncology workspace prototype: guided intake (History/Exam, Imaging, Pathology, Treatment, Follow-up), document upload with extraction review (accept/reject suggested fields), timeline and visits, decision snapshots, and MDT summary views. Shown as its own area in the app (e.g. OncoRegistry / oncology routes under a case). Requires controlled demo access (advanced prototype tier) and tenant access. | Data capture and workflow support—not a separate recommender. Treatment decisions remain with the clinician; any CDS runs use the same assistive-only rules as OrthoPath. | | OrthoRAG | Orthopaedic evidence retrieval and citation prototype. Explain-only; answers and citations from the knowledge base. | Must not emit recommendations or use clinical “decide” language. | | OrthoPilot | Operational cockpit prototype: dashboard, read-only oncology ops, tasks, draft centre, notifications, saved views on tasks and drafts; governance and agents (admin) as read-only visibility where present. Requires controlled demo access and tenant `pilot_enabled`. | Operational and draft support only; does not change oncology workflow state in OncoRegistry or emit CDS recommendations. | | OrthoSearch | Literature surveillance and workspace prototype: saved searches, collections, notes, case links where enabled. Requires tenant `orthosearch_enabled` (and related feature configuration). | Research-assist only; not a clinical recommendation engine. | | OrthoMonitor | Monitoring and follow-up visibility prototype for controlled-demo cases: dashboards, follow-up queue, per-case summaries, tasks, forms, saved views, export, admin analytics where configured. Requires controlled demo access and tenant `monitor_enabled`. | Visibility and documentation only; not a second CDS lane, not outbound alerts or orders. |
Core = single-encounter OrthoPath demonstration (module → structured input → recommendation + evidence). Advanced prototype tier (internally: Pro capability tier) = OrthoPath cases and timeline, OncoRegistry, OrthoRAG (Evidence Copilot) when enabled, OrthoPilot, OrthoSearch, and OrthoMonitor when those tenant features are on, decision snapshots, and replay. Public copy uses “controlled demo access” / “prototype workspace”; internal access architecture is unchanged.
On the OrthoPath page, each clinical module card may show an optional How to use this module box when the underlying protocol pack includes `user_instruction.md`. That file supplies three short, assistive lines—Goal, How to use, and Practical use—so you can see what the module is for, what to enter before you run it, and typical clinical settings. The box is orientation only: it does not replace the structured run form, evidence text, or independent clinical review. Packs add or refresh this content over time (including soft-tissue sarcoma pathways and other modules); see the Changelog for platform notes.
OrthoSphere is implemented as a monorepo with one deployable stack: API, CDS engine, Evidence service, and Web app. Core services:
Clinical rules are encoded in YAML protocol packs. Each rule’s `when` condition is expressed in CEL (Common Expression Language) or a CEL-compatible subset—non-Turing-complete, safe for embedding—and each pack ships with an evidence manifest linking every rule to its supporting literature.