HL7 v2.x FHIR R4 CCDA X12 837 / 835 / 270 / 271 / 276 / 278 NCPDP SCRIPT DICOM SMART on FHIR OAuth 2.0 Direct Secure Messaging IHE Profiles HL7 v2.x FHIR R4 CCDA X12 837 / 835 / 270 / 271 / 276 / 278 NCPDP SCRIPT DICOM SMART on FHIR OAuth 2.0 Direct Secure Messaging IHE Profiles
Products

The lineup.

Public tools and internal workspaces our team ships and runs. Tap any tile to pop a Mac-style window — drag, minimize, zoom, close.

Integration Engine

Every parser, viewer and code lookup a healthcare data engineer reaches for.

Live integration.medpipers.com
PriorIQ

Prior authorization workspace built to cut days off approval times.

Live prioriq.medpipers.com
HealthVerse KSA

Bilingual EN/AR patient portal and provider workspace, tuned for the Kingdom.

Live healthverse.medpipers.com
Zyp

Keyboard-first SFTP, FTPS, WebDAV and S3 client for macOS & Windows.

v1.1.1 getzyp.com
Dura Plastic

Operations, inventory and orders workspace for a plastics manufacturer.

Workshop duraplastic.medpipers.com
MK Vault

Self-hosted secrets vault for BAAs, credentials and integration keys.

Internal vault.medpipers.com
Organizer

Lightweight web app for tracking personal notes and expenses.

Workshop organizer.medpipers.com
Interoperability

Systems we already speak.

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.

medpipers — systems.live
LIVE 0 systems  ·  0 categories
EMR / EHR
How we work

Four phases. No surprises.

Every engagement starts with a discovery week and ends with monitored, operable pipelines ? not a handover doc and a shrug.

01 ? Discover

Map the flow.

We walk your systems end-to-end: source, transform, destination. Sample messages, credentials, edge cases. Deliverable is a written map.

02 ? Design

Pick the pipe.

HL7 vs FHIR vs EDI. Push vs pull. Existing engine vs custom service. We choose the boring, resilient option unless the case is exceptional.

03 ? Build

Ship it.

Iterative delivery in staging, with parsed sample messages you can inspect using our Integration Engine tools before we cut over.

04 ? Operate

Watch it breathe.

Monitored feeds, alert routing, PHI-safe logs, on-call for critical interfaces. Optional runbooks handed to your team.

Trust

Built for PHI from day one.

Healthcare data has different rules. Our defaults reflect that — logging, storage, access, and support are all designed around HIPAA, not bolted on later.

HIPAA-first defaults

PHI never leaves controlled environments. Logs are scrubbed. Access is scoped. Data at rest is encrypted, always.

Signed BAAs

Business Associate Agreements with every client and every sub-processor we touch ? including Zyp for developer file transfer.

Runs on your infrastructure

We deploy into your AWS / Azure / GCP / on-prem ? or a dedicated tenant we operate. Never a shared multi-tenant PHI store.

Khawer Younas ? Founder of Med Pipers
Meet the founder

Khawer Younas

Founder

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.