Metriport
FHIR-native healthcare data API that pulls complete U.S. patient records from HIEs, ADTs, pharmacies, labs, and EHRs into one query.
For U.S. health tech teams tired of stitching together Redox-style point integrations and closed HIE aggregators, Metriport is the version you can actually audit — MIT-licensed, FHIR-native, and fast enough (p80 under 15 seconds to first structured record) to sit inside a live clinical workflow. The clinical layer — summaries, suspected conditions, HEDIS gaps — is what separates it from a pure pipe, and the $26M raise says the roadmap is funded. The tradeoff is scope: U.S. networks only, and
Verified 4h ago · liveness 70/100 · cite: rightaichoice.com/tools/metriport
- U.S. health tech startups that need HIE connectivity live in days, not quarters
- Digital health platforms wanting to embed records into existing EHR workflows via iframe
- Value-based care teams working on RAF accuracy, HEDIS care gap closure, and readmission prevention
- CMS ACCESS participants that need documented HIE connectivity and FHIR reporting
- Non-U.S. healthcare organizations — coverage is limited to U.S. networks
- Buyers who need native mobile or desktop applications
- Care organizations that only want raw records and no clinical interpretation layer
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Metriport if you need international patient data, a free self-serve tier, or native mobile and desktop apps — its coverage is U.S.-only, pricing requires a sales call, and production access needs a covered entity, an NPI, and a Treatment purpose of use.
There is no published price list, so you cannot budget from the website — every quote requires a sales conversation and likely a scoped volume commitment.
Pricing is custom-quote only, so Metriport competes on value rather than sticker price against Particle Health and Redox, which are also sales-led. There is no free tier to self-serve on. That structure fits funded startups and enterprise health systems that can absorb a procurement cycle; it does not fit solo developers or pre-revenue teams wanting to test on real data without a contract. Evaluate against your expected patient-query volume before committing.
In short
Metriport — FHIR-native healthcare data API that pulls complete U.S. patient records from HIEs, ADTs, pharmacies, labs, and EHRs into one query. Best for U.S. health tech startups that need HIE connectivity live in days, not quarters, Digital health platforms wanting to embed records into existing EHR workflows via iframe, Value-based care teams working on RAF accuracy, HEDIS care gap closure, and readmission prevention. Contact Sales pricing.
What's new in Metriport
Checked todayAcross the latest 8 updates: 1 community discussion and 7 news mentions.
Metriport raises $26 million to give clinicians insight into any patient question at the point of care
Metriport raised $26M to turn scattered patient records into structured data delivered to clinicians at the point of care.
Open Source: Healthcare's Structural Data Advantage
Metriport argues open-source patient-matching logic gives interoperability platforms a verifiable trust advantage over vendor claims.
FHIR R4 Spec Guide: Resources & Standards (July 2026)
Metriport published a guide to FHIR R4 resources and standards for health data exchange.
What Is an ADT Feed in Healthcare? (July 2026)
Metriport explains HL7 v2 admission, discharge and transfer notifications, CMS requirements and how ADT data drives care coordination.
EHR Interoperability Standards: HL7, FHIR, and What They Mean for Health Data Exchange
Metriport breaks down HL7 and FHIR interoperability standards and their implications for health data exchange.
The CMS ACCESS Interoperability Checklist
Metriport published a deadline-by-deadline CMS ACCESS compliance checklist covering program start through full HIE connectivity.
The HIE Connectivity Gap That Could Cost ACCESS Participants
Metriport details HIE connectivity, FHIR reporting and care coordination requirements for CMS ACCESS Model participants.
How Cercanos Care Solved HIE Connectivity for CMS ACCESS
Cercanos Care used Metriport to meet CMS ACCESS HIE connectivity requirements and streamline clinical record retrieval.
What people actually say about Metriport — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
17 mentions across 4 sources (Reddit, Product Hunt, GitHub, Lemmy) · researched Jul 30, 2026.
Average across the 4 sources that answered — each source counts once, not each post.
- +Single FHIR endpoint to 300M+ patient records from U.S. HIEs.
- +Open-source MIT license allows self-hosting and code audit.
- +SOC 2 Type II and HIPAA compliant with end-to-end encryption.
- +Supports FHIR R4, C-CDA, and PDF formats for broad EHR compatibility.
- +No-code provider dashboard for streamlined record access.
- −No self-serve pricing; custom quotes only may deter small buyers.
- −Support responsiveness questioned in Reddit posts about premium features.
- −Most community feedback is from 2021-2022 about a different product.
- −GitHub has 71 open issues suggesting potential instability.
- −Learning curve for FHIR API may be steep for non-developers.
- • No self-serve pricing; may require sales call for quote.
- • Possible overage fees or volume-based pricing not disclosed.
Viability Score
How well maintained and how widely used is Metriport? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- FHIR-native REST API with a single consolidated patient query endpoint
- One integration to 750k+ U.S. providers across HIE, ADT, pharmacy, lab, and EHR sources
- 340M+ individuals accessible across U.S. networks
- p80 time to first structured record under 15 seconds
- 4.2B network requests processed per month at 99.999% platform uptime
- Extraction, normalization, deduplication, and enrichment into one record per patient
- Output in FHIR R4, HL7 v2, C-CDA, and PDF with OCR
- Asynchronous per-source webhooks (network-query.hie, network-query.pharmacy, network-query.lab)
- AI-generated medical record summaries
- Suspected condition detection (e.g. F33.1 major depressive disorder, E11.9 type 2 diabetes)
- HEDIS care gap identification (DSF-E depression screening, CCS cervical cancer screening)
- Real-time ADT discharge notifications with associated records
- Referrals, clinical data exchange, and electronic case reports to public health agencies
- Data warehouse with unified schema for analytics
- No-code provider dashboard at dash.metriport.com
About Metriport
Metriport is a healthcare data infrastructure platform built around one FHIR-native API for U.S. patient records. Instead of maintaining a dozen point-to-point connections to HIE networks, ADT feeds, pharmacies, labs, and EHRs, you make a single request to the consolidated patient query endpoint and get back a reconciled longitudinal record — conditions, medications, labs, encounters, documents — as FHIR R4, with HL7 v2, C-CDA, PDF/OCR, and a unified data warehouse schema feeding the same pipeline. The raw data comes in messy. Metriport extracts, normalizes, deduplicates, and enriches it so you end up with one record per patient rather than a folder of documents from competing sources. Scale figures matter here: 750k+ connected providers, 340M+ accessible individuals, 4.2B network requests processed per month, and a p80 time to first structured record under 15 seconds. Webhooks fire per source, so HIE, pharmacy, and lab results land asynchronously as each network responds rather than through polling. On top of the record layer sits clinical intelligence for care teams and the AI agents they're starting to run: AI-generated record summaries, suspected conditions like F33.1 and E11.9, and HEDIS care gap flags such as DSF-E depression screening and CCS cervical cancer screening. The same platform handles outbound messaging — provider referrals, clinical data exchange, and electronic case reports to public health agencies. Delivery is flexible by design. Teams can consume the REST API, sync an analytics-ready warehouse, work inside dash.metriport.com, or embed pre-built components via iframe into EHRs including athenaOne, Elation, Canvas, and Healthie. The codebase is open source on GitHub, and the platform carries SOC 2 Type II, HITRUST r2, and HIPAA BAA coverage with AES-256 encryption and end-to-end audit logging. Metriport raised $26M in August 2026 to push this record intelligence to the point of care. It's aimed at U.S. health tech startups, digital health
Behind the Verdict
The choice between Metriport and the incumbents usually comes down to one question: do you need to see inside the box? Closed aggregators like Particle Health and Redox will sell you connectivity, and for some teams that's fine. Metriport's pitch is different — the patient-matching and interoperability logic is open source on GitHub, so you can verify how records get linked instead of taking a vendor's word for it. We'd reach for this when accuracy claims need to survive diligence, whether that's a payer audit, a hospital security review, or your own engineering team's skepticism. Where it earns its keep is the delivery breadth. A seed-stage digital health startup can hit the REST API and ship in days. An enterprise system can sync the warehouse and leave records in the EHR via iframe embeds for athenaOne, Elation, Canvas, or Healthie. Same underlying record, three consumption patterns. That's a rarer combination than it sounds. The CMS angle is worth flagging. Metriport has spent the last few months publishing heavily on CMS ACCESS compliance — HIE connectivity requirements, FHIR reporting, care coordination deadlines — and Cercanos Care is on record using the platform to meet those requirements. If you're an ACCESS participant staring at an HIE connectivity gap, that's a documented path rather than a hypothetical one. Real-world caveats. Coverage stops at the U.S. border, full stop. Self-hosting exists because the code is open, but in practice it needs vendor engagement — don't budget for a weekend solo deployment of production HIE connectivity. Per-source webhooks are the right model for asynchronous network data, but they do mean your ingestion layer has to handle partial records gracefully; a condition set arriving before the matching labs is normal, not a
Researching Metriport? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Metriport actually fits — and what changes day-one when you adopt it.
You need a full patient history to power your app's intake flow. You create a facility, add the patient with rich demographics (nicknames, old addresses, prior names) to improve match rates, then fire one POST to /medical/v1/patient/{id}/consolidated/query. Webhooks call back as HIE, pharmacy, and lab data lands.
Outcome: A consolidated FHIR R4 bundle with conditions, medications, labs, and encounters — typically with first structured data in under 15 seconds at p80 — plus C-CDA and PDF when you need the source documents.
You want to close HEDIS gaps and catch patients before a 30-day readmission. You subscribe to ADT feeds and let Metriport flag suspected conditions and care gaps (DSF-E, CCS) alongside AI record summaries.
Outcome: Your care team gets discharge and lab alerts with complete records attached, plus a prioritized list of open care gaps read off the whole record rather than a referral face sheet.
A patient arrives with a thin referral packet. You run a full-history network query and read the AI summary on top of the reconciled record.
Outcome: Conditions the family didn't mention and that weren't on the face sheet surface in the review — the kind of find that changes the care decision.
Use Cases
- Pull a complete longitudinal patient history in one FHIR API call instead of chasing records from individual providers
- Generate AI record summaries so clinicians can read a full history before a visit
- Set up real-time alerts on hospital discharges, new lab results, or pharmacy pickups
- Embed patient data directly into existing EHR workflows with athenaOne, Elation, or Canvas apps
- Detect suspected conditions and HEDIS care gaps for value-based care and RAF accuracy work
- Send referrals and share records with other providers or submit electronic case reports to public health agencies
- Hydrate patient intake forms with deduplicated historical data
- Build analytics dashboards from the unified data warehouse
Models Under the Hood
as of 2026-09-26
Limitations
- Metriport aggregates data from U.S.
- Health Information Exchanges, so its coverage is U.S.-only and does not extend to international records.
- Pricing is not published; you have to go through a sales conversation, and there is no self-serve free tier.
- Production access requires a covered entity, an NPI, and a Treatment purpose of use — the sandbox requires none of these, so there is a real gating step between evaluation and going live.
- Delivery is via API, data warehouse, dashboard, or embedded EHR apps; there are no native mobile or desktop applications.
- Self-hosting is possible given the MIT license, but the seed data indicates it realistically needs vendor support.
- The open-source codebase does not eliminate lock-in entirely — network connectivity and coverage still depend on Metriport's agreements.
as of 2026-09-14
Verification history
We have re-verified Metriport 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
Where the pricing makes sense
The company stage and team size where Metriport's pricing actually pencils out — and where peers do it cheaper.
Pricing is custom-quote only, so Metriport competes on value rather than sticker price against Particle Health and Redox, which are also sales-led. There is no free tier to self-serve on. That structure fits funded startups and enterprise health systems that can absorb a procurement cycle; it does not fit solo developers or pre-revenue teams wanting to test on real data without a contract. Evaluate against your expected patient-query volume before committing.
Setup time & first value
How long it actually takes to get something useful out of Metriport — broken out by persona, not the marketing-page minute.
For developers: the sandbox runs the whole surface on seeded test patients the moment you have a key, so first value is effectively same-day. Customer reports put evaluation-to-deployment at a few days (Tono Health), with Color Health going from dashboard pilot to full API production in two weeks. For enterprise buyers, add time for the sales cycle and production gating — a covered entity, an
Switching to or from Metriport
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From direct HIE point-to-point integrations: replace each connection with one x-api-key against the Metriport API and keep the same downstream FHIR shape
- →From a folder-of-documents record vendor: switch to the consolidated FHIR query, which returns reconciled resources instead of a document pile
- →From polling-based data retrieval: move to Metriport's async webhooks (network-query.hie, network-query.lab) so sources call you back as they finish
- ↗To a self-hosted build: export using the MIT-licensed codebase on GitHub and run the extraction and normalization stack yourself
- ↗To another aggregator such as Particle Health or Redox: your downstream consumers already receive FHIR R4, so map the consolidated bundle rather than re-parsing C-CDA
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Metriport”, and we withheld 6: 6 could not be judged, because “Metriport” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Metriport.
Official links
Tools that pair well with Metriport
Common stack mates teams adopt alongside Metriport, with the specific reason each pairing earns its keep.
Hubble
AI-native medical record retrieval: one patient authorization pulls records from EHRs, payers, and the long tail.
Flatiron Health
Oncology real-world evidence platform turning patient data into AI-assisted cancer research insights.
Innovaccer
Agentic cloud platform that puts healthcare data and AI agents to work across clinical and administrative workflows.
Featured Head-to-Head Comparisons
Metriport vs Codametrix
CodaMetrix and Metriport serve fundamentally different needs. CodaMetrix is a specialized AI coding automation platform for large health systems, delivering 5:1 ROI, 70% reduction in manual coding, and deep EHR integration. Metriport is an open-source API for accessing 300M+ patient records via U.S. HIEs, ideal for startups needing fast interoperability. Choose CodaMetrix if you're a health system aiming to cut coding costs and denials; choose Metriport if you need real-time patient data access to build or enhance digital health applications.
Metriport vs Isomorphic Labs
Metriport and Isomorphic Labs serve completely different healthcare verticals: Metriport offers an open-source FHIR API for accessing patient medical records via US HIEs, ideal for health tech startups needing fast EHR integration. Isomorphic Labs provides AI-driven drug discovery through exclusive pharma partnerships (Novartis, Johnson & Johnson). Choose Metriport if you need real-time patient data integration; choose Isomorphic Labs only if you are a large pharma partner seeking advanced molecular design.
Metriport vs Rapidsos
RapidSOS and Metriport serve very different verticals: emergency response vs. healthcare data. Choose RapidSOS if your primary need is AI-enhanced 911 dispatch and real-time emergency intelligence for public safety or enterprise. Choose Metriport for fast, open-source FHIR API access to U.S. patient medical records. They are not direct competitors.
Alternatives to Metriport
View all
Hubble
AI-native medical record retrieval: one patient authorization pulls records from EHRs, payers, and the long tail.
Flatiron Health
Oncology real-world evidence platform turning patient data into AI-assisted cancer research insights.
Innovaccer
Agentic cloud platform that puts healthcare data and AI agents to work across clinical and administrative workflows.
Frequently Asked Questions
Categories
Used Metriport? Help shape our editorial sentiment research.