Patients & families
Plain-language projections of the approved plan
The interface is loading. No clinical action is performed by this state.
Pilot-stage product · synthetic demonstration
Synorthopic manages the whole lifecycle of an orthopedic episode — every implant, restriction, and document — across the systems it already lives in.
Loading illustration…
Synorthopic runs bounded orthopedic workflows on one deterministic engine: specialized software agents draft summaries, candidate codes, packets, and letters from supplied sources, deterministic checks verify each draft against those sources, and an accountable human approves every consequential step.
The public demonstration requires an explicit fictional clinician approval and marks every downstream output not delivered; it sends no EHR task, message, order, payer action, or patient contact.
Platform loop
Data sources
Agent layer · agents propose
Deterministic core · the engine verifies
Human review · your team decides
Projections · marked not delivered
Built around the whole team
Plain-language projections of the approved plan
Referral summaries and missing-item checklists
Review the disagreement, not the whole chart
Follow-up queues and one named plan version
Readiness gaps surfaced before the date
Criteria matrices and appeal outlines to review
Quote-backed candidates with typed acknowledgement
Restriction projections beside their sources
Device identity and reconciliation workflows
Provenance, audit, and reviewer surfaces
Program, operations, and scorecard views
The Synorthopic agent layer
Every agent in the layer is a bounded service with the same contract: it receives an immutable source payload, returns a structured proposal, and cannot send, order, schedule, bill, or write outside the workflow; deterministic verification and human review stand between each proposal and any downstream state.
Referral summaries, missing-item checklists, and a human routing queue.
Restriction, evidence, and hardware sources compared field by field.
Quote-backed facts pulled from notes; every value keeps its exact source.
Readiness gaps, checklists, and case packets prepared for human review.
Imaging may help a reviewer orient to an episode, but this product does not infer hardware presence, removal need, urgency, or lifecycle closure from pixels.
Operative-note pipeline with documentation gaps and candidate codes.
Criteria matrices, packets, and scorecards; nothing is submitted.
Evidence gaps, exception queues, and proposed next steps for a human.
Core platform services
The core services under every workflow are deterministic: immutable source records with digests, exact-quote evidence checks, versioned rules and policies, durable commands with per-stage human review, and an external outbox that stays suppressed in this release.
Longitudinal episode model: anatomy, laterality, devices, restrictions, chronology.
Immutable sources, digests, exact quotes, and reviewer decisions.
Versioned procedure, policy, and coding criteria with evidence thresholds.
Durable commands, queues, retries, and a complete audit trail.
Deep orthopedic vocabularies, device ontology, and coding packs.
Local registries, scorecards, and program-level reporting.
Tenant boundaries, policy gates, audit logging, and disabled external writes.
Orthopedic specialty pathway packs
One spine-shaped operative workflow runs end to end on deterministic rules; trauma registers a second, narrower tier whose case schema checks its own shape and verifies quote provenance while derivation stays structurally refused; the remaining five orthopedic specialties ship as registered knowledge packs whose candidates are quote-backed keyword detections, and every candidate on every specialty requires coder adjudication.
The listed orthopedic use cases are fictional workflow-evaluation examples, not treatment protocols, validated clinical use, or evidence that a customer process is safe or complete.
Working proof, not promises
In the operative-note demonstration, an immutable fictional note is extracted into quote-backed facts and candidate codes, the result is judged against each pack's own expect-and-forbid fixtures, and every human-required candidate needs an explicit typed acknowledgement before the worksheet can close.
Synorthopic finds conflicting or incomplete postoperative orthopedic instructions, shows an authorized clinician the exact evidence needed to resolve them, and derives care-team, post-acute, and patient-facing outputs from one approved plan version.
The fictional demo loads an immutable episode and a bounded set of versioned postoperative source documents without merging their text into a new source.
Deterministic extraction compares controlled orthopedic restriction fields and keeps agreement, terminology variance, conflict, and missing information explicit.
Conflicting fields remain unresolved until the fictional authorized reviewer chooses an evidence-linked option and prepares the exact selection set for approval.
Implant & device ledger
Implemented boundary: DI-only AccessGUDID lookup and customer-catalog contracts; registry data cannot prove implantation or lifecycle state.
Integration posture
Implemented contracts, sandbox verification, customer verification, and production authorization are separate evidence stages.
Public demo dataThe restriction demo accepts no case text or patient input from the visitor and loads only server-allowlisted fictional episodes.
Customer dataCustomer-data processing is not authorized by the public release and requires a separately configured customer runtime, approved data boundary, operating evidence, and explicit authorization.
Design goals, stated honestly
Most platform diagrams end in an outcomes box. Ours does too — so here is the current evidence status of every one of them, from the same registry that governs the rest of this page.
Time saved in a customer workflow: Not measured in a customer workflow
No preregistered time-motion comparison against a locked baseline exists yet.
Clinical outcome effect: Not established
No comparative clinical trial with a patient-important endpoint has been run yet.
Validated demand: Not established
No retained deployments, renewals, or verified customer references are recorded.
Novelty of the workflow: Hypothesis only
Public landscape research has not been converted into a verified novelty opinion.
Waitlist and bounded pilots
Recommended evaluation sequence: scope one restriction handoff, validate the fictional workflow, map approved read-only sources, and authorize any delivery boundary separately.
Outreach and correspondence drafts; nothing is sent to anyone.
Restriction reconciliation and follow-up queues across the episode.
UDI parsing, device reconciliation, and safety review workflows.
Scorecards, drift summaries, and subgroup reviews prepared for humans; no autonomous learning.
This release blocks autonomous clinical orders, removal or retention disposition, final code confirmation, payer submission, and patient contact.
One approved plan deterministically produces care-team, post-acute, and plain-language patient outputs, all visibly marked not delivered in the public demo.
