Capability statement

What we do, on one page.

Three strands, one commercial structure, and the practice platform in detail, for anyone deciding whether to talk to us.

Platform engineering

Fixed-fee builds for small operators holding sensitive records: portals, CRM, workflow automation. Authentication, row-level security, audit logging, billing, and migration of the data you already have, accepted milestone by milestone on a working system.

0pon Care

An operational core for appointment-driven practices, integrated with the system of record you already run rather than replacing it. Read-only first. Proving out in healthcare, built to travel. Detailed below.

Verified systems

Access control whose confidentiality properties are machine-checked in a theorem prover and enforced by the same predicate the proof reasons about. Built in the open on standard parts.

The longer version, with how engagements are priced, is on the Platform page.

0pon Care · Healthcare

The layer around your practice software.

Your practice-management system is the system of record and should stay that way. The work that decides whether the month was good happens around it: referrals arriving by fax and getting re-keyed, cases crawling from consult to surgery, payers paying something other than the contracted rate. 0pon Care is an operating layer for that work: modules that read from the systems you already run.

It is not a replacement for your practice-management system, your phones, or an AI receptionist; those stay. Integrations start read-only, through the practice system's API where one exists, or from claims and EOB exports where it does not. The first audit pass can run from claims and EOB data without patient identifiers. Your data is exportable on exit.

What 0pon Care covers, built out module by module. The referral hub and the audit engine are the parts you can see running today, in a synthetic practice; the rest is in build on the same layer.

Referral pipeline

Inbound referrals, whether fax, letter, portal, or phone note, collected onto a working board for staff review, nothing re-keyed.

AI intake

Referral letters, even rasterized fax scans, read into structured cases. Referrers resolved against your own directory; anything ambiguous flagged to a person.

Case journey

Each case tracked from consult through treatment to handback, with the referring office updated at the moments that matter.

Insights

Where referrals come from, where cases stall, and which referring offices are sending fewer patients over time.

Payment-variance audit

Adjudicated claims reconciled against your contracted fee schedules, not just the copy in your practice software. Underpayments, downgrades, and wrong-network payments ranked by dollar impact.

Recall, utilization, unscheduled work

The recurring operations of an appointment-driven practice, surfaced from the system of record instead of chased by hand.

Client portal

One owned, branded front door for patients and referrers, across locations.

Where you start

Nobody starts with all of it. PPO-heavy or multi-office practices start with the audit, and the first pass is free on your own numbers. Referral-driven specialty practices, endo, perio, oral surgery, start with the referral pipeline. Each next module builds onto the same layer.

Plainly: 0pon Care is early. What exists today is a working product, not a slide deck: a working referral hub and a working audit engine in a synthetic demo practice with no real patient data, ready to walk through by screenshare, and, separately, integration work for a first practice now in deployment with 0pon as integrator.

Engineering

Data, platforms, and modernization

Data engineering

Pipeline architecture
ETL and ELT workflows
Databricks, Spark, SQL
Analytics-ready delivery

Platform architecture

Microservices in Python
API development
Workflow orchestration
Kubernetes, Terraform, CI/CD

Systems integration and modernization

Legacy modernization, including mainframe-to-modern and proprietary job-control translation
Hospital application streaming, subcontract Phase 1 in progress: preparing the migration of clinical and back-office applications from Citrix to AWS WorkSpaces Applications
Headless, reproducible server builds and tech refreshes
Practice-management and clinical-system integration, read-only first

Privacy and security

Built in, then documented

Zero-knowledge proofs (STARKs)
End-to-end encrypted communications
DoDM 5200.45 security classification guide tooling
SIEM and vulnerability management
n0de: multi-level access control with Lean 4-checked confidentiality properties; an SBIR proposal building on it is under review

Assurance

What we claim, and what we don't

NIST SP 800-171: Self-assessment current in SPRS
CMMC 2.0: Level 2 self-assessment; conditional status through January 2027
DFARS 252.204-7019: Current self-assessment submitted in SPRS
CUI handling: FIPS-mode enclave
HIPAA: Health data only as a Business Associate under a signed BAA
SOC 2: No attestation of our own; inherited controls, documented on the Security page

The full posture is on the Security page.

How we work

Three phases.

Discovery

A short, gated first phase. We review your actual data and systems before migration and integration pricing is fixed.

Build

Fixed-fee, milestone-locked. Payments tie to demonstrated acceptance, not the calendar.

Run

A monthly retainer with a defined hours bucket carries the system after handover.

Recent work

Stated as far as it has gone

Client names appear only under signed agreements. The work is described plainly and generically; the decisions are real.

Clinical systems · In deployment

Paper to practice, one machine

A single-chair dental practice, previously paper-only, moving onto an open-source practice-management system with 0pon as the integrator. The whole system lives on one machine in the clinic; patient records never leave the room they are used in.

Modernization · Subcontract, Phase 1 in progress

Hospital application streaming

For a hospital client, under subcontract: Phase 1 discovery and preparation for a planned migration of four clinical and back-office applications from Citrix to AWS WorkSpaces Applications. Requirements, persona identification, an image strategy tested on the client's own image builder, storage and persistence design, UAT criteria, and risk tracking.

0pon Care · Working product

Referral hub and audit engine

A working referral hub and a working payment-variance audit engine, demonstrated in a synthetic practice with no real patient data. Practice-system API integration proven end to end in the demo environment; export-based ingestion for any system that can produce a claims file.

NAICS codes

541511

Custom Programming

541512

Systems Design

541513

Facilities Mgmt

541519

Computer Services

541330

Engineering

541611

Mgmt Consulting

541690

Tech Consulting

541715

R&D Engineering

518210

Data Hosting

517919

Telecom

561499

Business Support

541990

Professional Svcs

Fifteen minutes is usually enough.

Enough to know whether we can help. If we can, the first pass on an audit is on us.

Contact Form →202-978-4640