Let Medicare beneficiaries authorize access to supported claims and coverage data, then read the approved information through FinchNode’s API.
Patient-authorized Medicare Blue Button 2.0 record access
FinchNode provides a hosted connection and consent experience around CMS Blue Button 2.0, keeps sandbox and production access separate, and delivers supported Medicare data through the same application model as EHR sources.
Best fit: Patient-facing products that need beneficiary-authorized Medicare coverage and claims data.
How the connection works
- Your backend creates a FinchNode Connect session.
- The patient selects their organization and authorizes through Medicare.gov.
- FinchNode syncs available records and records the patient’s sharing decision.
- Your backend reads approved data through the FinchNode API.
Production availability
Live access requires CMS production approval and is limited to the information, history, and scopes that CMS Blue Button makes available for the beneficiary.
FinchNode’s current integration is patient-directed and read-only. Actual data depends on the source, organization, approved scopes, patient record, and consent.
View all EHR integrations or learn about the EHR integration API.
Frequently asked questions
Is there a free EHR API for real patient data in production?
Yes. With a FinchNode account, developers get free production-grade access to real, patient-authorized health records through one unified EHR API. The $0/month plan includes 100 connected patient-months, 100,000 production API calls per month, one production application, and an unlimited synthetic sandbox. Production access requires a FinchNode account, production credentials, a supported live source, and patient authorization and consent. Availability depends on the EHR, organization, application approvals, scopes, and records returned.
How does FinchNode connect to Medicare Blue Button 2.0?
Your application creates a FinchNode Connect session. The patient selects their organization, authorizes access on the Medicare.gov experience, and approves the record categories your application may read. FinchNode then exposes supported, consent-filtered data through one API.
Do patients give FinchNode their Medicare Blue Button 2.0 password?
No. The patient signs in on the source authorization page. Their hospital, payer, or EHR username and password do not pass through FinchNode or your application.
What data can my app read from Medicare Blue Button 2.0?
FinchNode can normalize supported demographics, medications, conditions, allergies, vital signs, laboratory results, immunizations, and source-specific coverage or claims data. Actual availability depends on the source, organization, granted scopes, and patient consent.
Is the Medicare Blue Button 2.0 connection read-only?
Yes. FinchNode’s current patient-directed integration is read-only. It does not provide EHR write-back, scheduling, provider-side bulk access, or a general-purpose HL7 interface.