Let beneficiaries sign in with their Medicare.gov account and share approved coverage and claims data with your application.
Patient-authorized Medicare Blue Button 2.0 record access
Supported record categories
- Basic details
- Claims & coverage
Medicare Blue Button 2.0 uses OAuth 2.0 and FHIR so beneficiaries can authorize access without giving their credentials to your product. FinchNode packages that connection into a hosted flow and one normalized API.
Best fit: Patient-facing products that need beneficiary-authorized Medicare coverage and claims data.
The connection journey
- 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 availability depends on the beneficiary’s Medicare.gov account and the coverage and claims CMS makes available for them.
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, self-serve production access to real, patient-authorized records. Free ($0/month) includes one production application, a synthetic sandbox included with every account, hosted consent and patient controls, scheduled sync, and signed webhooks. Pro ($99/month) includes up to 5 production applications, email support, and everything in Free. Usage-based pricing is not in effect. Owners enable production when application settings are complete; FinchNode can suspend access. Live reads require production credentials and patient authorization and consent; availability varies by organization and scopes.
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?
For Medicare Blue Button 2.0, request supported categories such as Basic details, Claims & coverage. 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.