Med Pipers is a healthcare integration studio building the plumbing behind clinical software — HL7, FHIR, X12, CCDA, and the custom work in between. From a single ADT feed to a QHIN-connected enterprise, we ship integrations that stay up.
Every product below began as a real gap on a real engagement. We still write the first line of each one.
The core routing + transform engine. HL7 ↔ FHIR ↔ X12, mapping DSL, replay, PHI de-identification, monitoring.
Automated prior-authorization workflows. X12 278, Da Vinci PAS, payer-specific portals — handled.
Patient-facing healthcare marketplace for Saudi Arabia. Bookings, teleconsults, pharmacy, billing — all in one.
Direct-to-consumer platform for health brands. E-commerce, subscriptions, and the backend that keeps shipments on time.
Patient-journey platform for plastic surgery practices. Consults, imaging, consents, follow-ups — in one record.
Secure credential and secrets store for engineering teams. SSO, audit log, rotation, and share-with-expiry.
Lightweight project + task tracker for consulting engagements. Built for how we actually work.
If it exchanges patient data in the United States, we've probably integrated with it. Here's the short list.
Every piece of patient data that moves through our integration engine passes through seven stages — each auditable, replayable, and independently scalable.
Accept data from any source — batch, stream, push or pull — over FTP, SFTP, MLLP, REST, SOAP, webhook, Kafka, S3.
Land raw payload encrypted at rest. Replay any message, any time. Dead-letter queue for failed deliveries.
Turn bytes into structured records — HL7 v2/v3, CCDA, FHIR, X12, NCPDP, DICOM, JSON/XML — natively.
Detect PHI, apply consent, strip or tokenize. Safe Harbor de-ID or Expert Determination — your call.
Map to one clean semantic layer. ICD-10/11, SNOMED CT, LOINC, CPT, HCPCS, RxNorm, NDC, CVX, MVX.
Reshape to whatever the destination needs. In: Python, JS, SQL, XPath, Mapping DSL. Out: any format.
Deliver to any endpoint — with retries, ACKs, delivery receipts, and end-to-end lineage.
A snapshot of what we read, write, and translate between. If something's missing, we've probably seen it anyway.
| Standard | What it carries |
|---|---|
| HL7 v2.x | Workhorse of clinical messaging — ADT, ORM, ORU, SIU, MDM, DFT, VXU, and the rest. |
| HL7 v3 / CCDA | Structured clinical documents: discharge summaries, continuity of care, referral notes. |
| FHIR R4 | Modern RESTful healthcare API. Patient, Encounter, Observation, MedicationRequest, Bulk Data. |
| SMART on FHIR | OAuth 2.0 + FHIR launch framework for apps running inside the EHR. |
| X12 EDI | Payer transactions — 270/271 eligibility, 837 claims, 835 remittance, 278 prior auth, 276/277 status. |
| NCPDP SCRIPT | Pharmacy messaging — NewRx, RxRenewal, RxChange, CancelRx, RxHistory. |
| DICOM | Imaging — WADO-RS, QIDO-RS, STOW-RS, DICOM SR for structured reports. |
| Direct Secure Messaging | HIPAA-compliant encrypted messaging between providers via HISPs. |
| IHE Profiles | XDS.b, XCA, XCPD, PIX, PDQ — the plumbing of HIEs and TEFCA. |
| Coding systems | ICD-9 / 10 / 11, SNOMED CT, LOINC, CPT, HCPCS, RxNorm, NDC, CVX, MVX. |
| Quality & reporting | HEDIS, CQL / QDM, QRDA Cat I / III, eCQMs, NAACCR cancer reporting. |
Every engagement follows the same path. You always know where you are, what's next, and what it'll cost.
Free 30-minute call. We map your source systems, destination systems, data volumes, and compliance posture.
Within one business day: scope, timeline, fixed price, and a message-flow diagram. You pick what to do and what to skip.
Weekly check-ins, transparent progress, test fixtures from your real data (de-identified). No surprise invoices.
Launch is day one, not the finish line. Monitoring, on-call, and change management included on retainer.
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 above began as a real gap on a real engagement. I still write the first line of each one.
Tell us the source, the destination, and the format. We'll come back within one business day with questions, a plan, or a time to jump on a call — whichever makes sense.