The member taps a card. The record follows.
My EHR Data gives members control of their clinical and claims records, and delivers those records to the insurance plan and the provider inside the systems they already use, with the member's consent.
The member taps their card
At the ER, a clinic, a pharmacy, a doctor outside the network, or a provider in another state. The tap is the request. No app, no login.
My EHR Data checks consent and routes the request
The request goes to the beneficiary's own record store, kept separate for each insurance plan and built on FHIR, the data standard CMS requires. The beneficiary's consent decides what can be returned and to whom. Nothing moves without it.
My EHR Data returns the record
Clinical and claims records go to the insurance plan, the treating provider and the member at the same time. The visit itself is recorded, so the insurance plan sees it as it happens.
My EHR Data gives insurance plans, providers and beneficiaries access to records the member owns. It routes each request and returns clinical and claims records together, inside the systems already in use.
The card is the credential.
It works like the insurance card the beneficiary already carries. The tap is what is new.
Sample card. Final card content is set with the card issuer.
What the card carries
- Member identityEnough to identify the member to the insurance plan and to the doctor, hospital or pharmacy.
- Insurance planThe insurance plan the beneficiary belongs to.
- PaymentTap to pay co-pays, deductibles and HSA/FSA amounts at the visit.
- The tapThe contactless request for the member's record.
What the tap returns
- Coverage checkConfirmed at the time of the visit, at no extra cost to the provider.
- Clinical historyFrom every provider and EHR system, shown inside the provider's own record viewer.
- Claims historyThe full history, including care the member paid for themselves and care outside the network.
- Only what the beneficiary allowsSensitive categories the beneficiary has restricted stay withheld.
Standards insurance plans and providers already run on.
Patient and provider workflows do not change. The member taps a card; the provider stays in their EHR; the insurance plan keeps its coverage-check, claims and hospital-alert (ADT) systems. My EHR Data connects to them and does not replace them.
No proprietary connector. My EHR Data uses the standards that insurance plans and providers are already required to support.
HL7 FHIR R4
The data standard for every record My EHR Data holds and returns. It is the same standard CMS requires for Patient Access APIs.
SMART on FHIR
The standard that shows the record inside the provider's EHR, so the clinician sees it where they already work.
ADT notifications
Hospital admission, discharge and transfer alerts (ADT) feed the same record store, so the insurance plan hears about an admission when it happens.
Coverage check and payment
The tap does what the insurance plan's current coverage check and point-of-sale processing do, within the systems already in place.
Four things that stay true.
Patient-centered
My EHR Data acts on behalf of members, with their consent.
Clinical + claims
Clinical and claims records are kept together in one record store.
Built to connect
Built on FHIR, so it connects to systems insurance plans and providers already have.
Consent-driven
Nothing moves without the beneficiary's permission.
Start with one plan, one population, one region.
A paid pilot shows an insurance plan what My EHR Data can see for its beneficiaries before the plan commits to more.