NEW: The pharmacist's guide to the Rural Health Transformation Program β€” Read the brief β†’
Home/ Platform/ Integrations
Integrations

Works with the systems your pharmacy already runs.

MedMe is the clinical and billing layer β€” not a rip-and-replace. We meet your Rx system, your clearinghouse, your wholesalers, and your payers where they are. Real-time, bidirectional, HIPAA-compliant, and tuned for the way US pharmacy actually operates.

Connecting your stack
38 production integrations across Rx systems, clearinghouses, wholesalers, and payers.
38
Production integrations live across the platform
Real-time
Bidirectional sync where the partner system supports it
< 30 min
Median time to wire up a new pharmacy's Rx system
SOC 2
Type II audited Β· all integrations BAA-protected
Rx dispensing systems

Connected to the dispensing system that runs your store.

Patient demographics, allergies, active medications, dispensing history, and prescriber relationships flow into MedMe automatically. Your pharmacists never re-key β€” and the chart is always current.

Rx system Direction Sync cadence What's synced
PioneerRx↔ BidirectionalReal-time webhookDemographics, Rx history, allergies, refills, fill events
BestRx↔ BidirectionalHourly batchDemographics, Rx history, allergies, fill events
McKesson Pharmacy Manager→ ReadReal-time webhookDemographics, Rx history, allergies
Liberty Software↔ BidirectionalReal-time webhookDemographics, Rx history, allergies, refills, fill events
RxConnect→ ReadHourly batchDemographics, Rx history (writeback Q3 2026)
QS/1β†’ ReadDaily batchDemographics, Rx history, allergies
PrimeRx→ ReadHourly batchDemographics, Rx history, allergies
Computer-Rx→ ReadDaily batchDemographics, Rx history
Clearinghouses

Whichever clearinghouse you use, MedMe routes through it.

Eligibility (270/271), claims (837P), remittance (835), and claim status (276/277) β€” all wired into the major US clearinghouses. Bring your existing contract or use a partner clearinghouse we set up during onboarding.

Clearinghouse Eligibility (270/271) Claims (837P) Remittance (835) Status (276/277)
Change Healthcareβœ“βœ“βœ“βœ“
Availityβœ“βœ“βœ“βœ“
Office Allyβœ“βœ“βœ“βœ“
Waystarβœ“βœ“βœ“β—‹ Q3 2026
Trizetto Provider Solutionsβœ“βœ“βœ“βœ“
Wholesalers and payers

Tied into the rest of the supply chain β€” and the people who pay you.

Wholesalers

Wholesaler What's connected
AmerisourceBergen (Cencora)Catalog, contract pricing, ordering EDI
McKessonCatalog, contract pricing, ordering EDI
Cardinal HealthCatalog, contract pricing, ordering EDI
Smith DrugCatalog, ordering EDI
AndaCatalog, ordering EDI

Direct payer connections

Payer Coverage
Medicare Part BAll MAC jurisdictions
BCBS (regional plans)34 BCBS plans across US
UnitedHealthcareMedicare Advantage + commercial
HumanaMedicare Advantage + commercial
Aetna (CVS Health)Medicare Advantage + commercial
CignaCommercial + select Medicare
Medicaid (state plans)Configured per pharmacy state

Don't see your payer? MedMe routes through clearinghouses for any payer with a standard 270/271 EDI envelope β€” which covers virtually every US plan.

Developer API

Build whatever else you need.

Beyond the prebuilt integrations, MedMe ships a REST + webhook API for everything: patients, encounters, claims, remittances, immunizations, care plans, eligibility checks. Use it to feed your data warehouse, build a custom patient portal, or wire up a payer your team has a special relationship with.

  • OAuth 2.0 with scoped per-tenant tokens
  • Webhook-first event streaming (encounter.completed, claim.paid, claim.denied, etc.)
  • FHIR R4 endpoints for clinical data exchange
  • SDK packages for Node, Python, Ruby, Go
  • Sandbox environment with seed data on signup
POST /v1/encounters
{
  "patient_id": "pat_8f2c01",
  "service": "ccm",
  "start_at": "2026-05-08T14:32:00Z",
  "end_at":   "2026-05-08T14:54:00Z",
  "pharmacist_npi": "1234567890",
  "diagnoses": ["E11.9", "I10"],
  "code": "99490",
  "minutes": 22,
  "place_of_service": "01",
  "modifiers": []
}
β†’ 201 Created
{
  "encounter_id": "enc_2a91f4",
  "claim_id":     "clm_b81e22",
  "status":       "submitted",
  "estimated_paid_at": "2026-05-22"
}

Full API reference at developers.medmehealth.com

Security

Every integration BAA-protected, every byte encrypted, every action audited.

SOC 2
Type II audited annually Β· most recent audit Q1 2026
AICPA-licensed firm
HIPAA
BAA executed with every integration partner before go-live
Standard contract clause
TLS 1.3
All in-transit traffic; AES-256 encryption at rest
AWS KMS-backed
Audit log
Every API call, every webhook, every sync β€” immutable, exportable
7-year retention

Read the full security overview Β· HIPAA documentation Β· live status

Don't see your stack?

Tell us what you run. We'll tell you what's wired up.

20-minute call. We'll map your Rx system, your clearinghouse, and your top payers β€” and walk through exactly what onboarding looks like for your setup.