Public tools and internal workspaces our team ships and runs. Tap any tile to pop a Mac-style window — drag, minimize, zoom, close.
Every parser, viewer and code lookup a healthcare data engineer reaches for.
Prior authorization workspace built to cut days off approval times.
Bilingual EN/AR patient portal and provider workspace, tuned for the Kingdom.
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.