Three healthcare platforms, two data-engineering tools, and a shelf of utilities we build for ourselves and our operators. Tap any tile for the full feature list in a draggable Mac-style window.
US EHR with an integrated revenue-cycle suite and a patient portal — one system, one login for the whole practice.
A US-first EHR with a full revenue-cycle suite built in. Staff workbench and patient portal live on the same clinical core — no bolt-on billing module, no second vendor.
Clinical & scheduling
Revenue cycle
Patient portal — dashboard, timeline, care-team messaging, pre-visit check-in, pharmacy / labs / imaging marketplaces, patient-share payments (card, ACH, Apple Pay, HSA/FSA), family switching.
Bilingual, RTL-first healthcare platform for the Kingdom — clinical core, patient portal and NPHIES-style RCM in one build.
An Arabic-first, RTL-native healthcare platform for Saudi Arabia — with the same clinical core as HealthVerse USA, but tuned to KSA identity, currency, coding and payment rails.
Two front doors
Patient portal features
Revenue cycle (NPHIES-style) — charge capture with ICD-10-AM coding, claims workbench with configurable scrubber, submission over a simulated NPHIES rail, payer adjudication, denials, appeals, remittance batches with auto-posting, statements with A/R aging.
Multi-region — one REGION env flag toggles KSA (SAR, 15% VAT, Nafath, mada) or Qatar (QAR, zero-VAT healthcare, QID, NAS) — same build.
Chairside dental practice suite — interactive odontogram, CDT/SBS coding, treatment planning and bilingual patient journey.
A chairside-first dental practice management suite. Same HealthVerse clinical core, re-skinned around the way dentists actually chart, code and plan treatment.
Clinical charting
Coding & treatment planning
Front-desk & patient journey — dashboard, patient journey view, visit workspace, bilingual English / Arabic UI with proper RTL layout.
| HealthVerse USA | HealthVerse KSA | Healthverse Dental | |
|---|---|---|---|
| Primary use | US EHR + billing | KSA / Qatar EHR + patient portal | Dental practice management |
| Languages | English | English · العربية (RTL) | English · العربية (RTL) |
| Coding | ICD-10-CM · CPT · HCPCS | ICD-10-AM · SBS · ACHI | CDT · SBS · ICD-10 |
| Claims rail | X12 837 / 835 / 270 / 271 | NPHIES · MOPH eClaims | CDT / SBS via HV core |
| Patient portal | Yes — full portal + marketplaces | Yes — Arabic-first + marketplaces | Patient journey view |
| Revenue cycle | Full RCM workbench | NPHIES-style RCM | Charges & fees (bills via HV) |
| Specialty focus | General & multi-specialty | General & multi-specialty | Perio · Endo · Prosth · Oral Surg |
| Learn more | Read → | Read → | Read → |
Every parser, viewer and code lookup a healthcare data engineer reaches for — plus scheduled jobs.
Scheduled integration jobs plus a full toolkit for every healthcare data engineer — the app you keep open in a second tab all day.
Prior-authorization automation platform — from eligibility to decision to appeal.
An end-to-end prior-authorization automation platform. Designed to cut days off approval times and give front-office staff one screen for every payer request.
Keyboard-first SFTP, FTPS, WebDAV and S3 client for macOS & Windows.
Operations, inventory and orders workspace for a plastics manufacturer.
Self-hosted secrets vault for BAAs, credentials and integration keys.
Lightweight web app for tracking personal notes and expenses.
Every vendor, standard, ACO, clearinghouse, registry and network we've moved data across in production — scanning live below. Most engagements touch four or more of these; several touch a dozen. If it's not here, ask — the answer is usually still yes.
Every engagement starts with a discovery week and ends with monitored, operable pipelines ? not a handover doc and a shrug.
We walk your systems end-to-end: source, transform, destination. Sample messages, credentials, edge cases. Deliverable is a written map.
HL7 vs FHIR vs EDI. Push vs pull. Existing engine vs custom service. We choose the boring, resilient option unless the case is exceptional.
Iterative delivery in staging, with parsed sample messages you can inspect using our Integration Engine tools before we cut over.
Monitored feeds, alert routing, PHI-safe logs, on-call for critical interfaces. Optional runbooks handed to your team.
Healthcare data has different rules. Our defaults reflect that — logging, storage, access, and support are all designed around HIPAA, not bolted on later.
PHI never leaves controlled environments. Logs are scrubbed. Access is scoped. Data at rest is encrypted, always.
Business Associate Agreements with every client and every sub-processor we touch ? including Zyp for developer file transfer.
We deploy into your AWS / Azure / GCP / on-prem ? or a dedicated tenant we operate. Never a shared multi-tenant PHI store.
Ten-plus years shipping healthcare integrations across EMRs, HIEs, labs, payers, and public-health registries. Med Pipers started as the way I wanted this work to be done ? engineered by people who actually read HL7 message specs and X12 companion guides for fun.
Every product listed above ? Integration Engine, PriorIQ, HealthVerse KSA, Zyp ? began as a real gap on a real engagement. I still write the first line of every one.