Flexpa
Talk to us

Guides

  • Overview
  • Quickstart
  • Patient accessNew
  • Test mode
  • Searching Coverage
  • Viewing medications
  • Explanation of Benefits

SDK

  • Link
  • API

FHIR Resources New

  • CareTeam
  • Condition
  • Coverage
  • Encounter
  • ExplanationOfBenefit
  • MedicationRequest
  • Observation
  • Procedure

Reference

  • Endpoints

About

  • ChangelogNew
  • FAQ
  • Join us
  • Brand
  • Privacy policy
  • Terms of service

Explanation of Benefits

An Explanation of Benefits (EOB) is a statement from a health insurance plan describing what costs will be covered for medical care received (e.g., a medical procedure or a prescription) by a covered person. EOBs are typically created when providers such as hospitals, medical clinics or pharmacies submit a claim on behalf of a covered person to their health insurance plan.

We will use Flexpa Link and Flexpa API together to retrieve EOBs. A history of EOBs can aid in workflows such as recommending the best health insurance plans during enrolment periods.

Getting started

EOBs are directly represented in patient access APIs as a FHIR Resource. We can make HTTP requests to Flexpa API to search for and find EOBs belonging to a particular patient. Patients authorize your app to access their EOBs via Flexpa Link. At the end of the Flexpa Link flow you'll have:

  • An access token that is required for all requests to Flexpa API
  • A patient id, that is required to query FHIR resources directly related to the patient

Searching for a patient's EOB

Flexpa API can be used to search for EOBs after a patient has authorized access via Flexpa Link. Searches on Flexpa API follow the RESTful style of the FHIR specification by submitting a GET HTTP request to the base URL of the resource. To search for EOBs belonging to a particular patient, you can use an API wildcard parameter: $PATIENT_ID. We'll swap this out for the real Patient ID before we send the request to the right FHIR API.

You can retrieve the patient id by either:

  • Using the $PATIENT_ID wildcard parameter and inspecting the response
    • Example: GET /ExplanationOfBenefitPatient?patient=$PATIENT_ID
  • Introspecting the access token
ACCESS_TOKEN=... # replace with the access token you obtained at the end of the Flexpa Link flow

curl "https://api.flexpa.com/fhir/ExplanationOfBenefit?patient=$PATIENT_ID" \
  -H "Authorization: $ACCESS_TOKEN"

Response type

The return type of querying the EOB endpoint is a searchset bundle. Technically, a searchset bundle may contain different types of resources (e.g., EOBs, Patients, etc) in the entry field. When iterating through entry it is best practice to inspect each resourceType field to ensure you are dealing with the expected resource.

Sample response

Notable fields

An EOB response contains many fields. You can get an exhaustive list and explanation of each field here. Some notable fields:

  • entry - A collection of EOBs (see response type on best practice of checking resourceType)
  • meta.lastUpdated - An ISO8601 string representing the last time the bundle was modified
  • entry[i].resource.type.code[j].code - A claim type string, can have a value of "institutional", "oral", "pharmacy", "professional" or "vision"
  • entry[i].resource.provider - The provider (practitioner or organization) which is responsible for the claim
  • entry[i].resource.prescription (optional) - The prescription to support the dispensing of pharmacy, device or vision products
  • entry[i].resource.total[] - Categorized monetary totals for the adjunction
    • Includes dollar amount the insurer paid
    • Includes dollar amount the patient paid out-of-pocket

Next steps

Flexpa Link

Flexpa Link is a client-side component to help your users link health plan data sources
Build with Flexpa Link →

API Reference

Use Flexpa API as a unified API to access Explanation of Benefits and more
Build with Flexpa API →
TwitterGitHubDiscord

© 2022 Flexpa. All rights reserved.

On this page
  • Getting started
  • Searching for a patient's EOB
  • Response type
  • Sample response
  • Notable fields
  • Next steps