TheFhirStorm

Notes on healthcare integrations

Practice management systems, EHRs, payer portals and the X12 transactions between them, written for engineers.

Claims data

Writing back to a practice management system without duplicates

Idempotency keys, duplicate detection, systems with no update endpoint, and how to confirm a write landed in a practice management system.

Claims data

What a practice management system sends in an 837P

The 837P loops a practice management system fills, the fields that cause rejections, and how to read the 999 and 277CA that come back.

Vendor APIs

What the Tebra API exposes, and what it does not

Tebra's SOAP API: how access works, which patient, appointment, encounter and charge operations exist, the rate limits, and the gaps.

Vendor APIs

SMART Backend Services against eClinicalWorks FHIR R4

How a server-side app gets an eClinicalWorks FHIR R4 token with a signed RS384 JWT, and what that token can read.

Integration ops

Integrating with payer portals: logins, MFA, sessions and change

How Availity, UnitedHealthcare, Aetna and state Medicaid portals handle logins, second factors and sessions, and which data lives only in the portal.

Claims data

Parsing an 835 remit: CLP, CAS, PLB and payment matching

How to parse an 835 remittance advice, read CAS adjustments and PLB segments, and match payments back to claims in the practice management system.

Vendor APIs

Office Ally integration when the PM has no public API

What practices and vendors do when a practice management system such as Office Ally Practice Mate publishes no general API, and the tradeoffs.

Vendor APIs

NextGen Healthcare API notes: Enterprise and Office

NextGen Enterprise and NextGen Office FHIR R4 endpoints, partner programs, fees and rate limits as stated on NextGen's public API pages.

Integration ops

What the information blocking rule requires of EHR APIs

What 45 CFR Part 171 and the Cures Act require of certified health IT vendors for APIs, with the Infeasibility and Manner exceptions explained.

Vendor APIs

The healow scheduling API for eClinicalWorks practices

How to find open slots and book a visit through healow for an eClinicalWorks practice, and what the public documentation leaves out.

Claims data

FHIR R4 vs vendor APIs for revenue cycle data

What US Core FHIR gives a billing startup, what the vendor's own APIs add, and why most teams end up reading both.

Claims data

Three ways to check eligibility: 270/271, portal, EHR

What a 270/271, a payer portal and the EHR's built-in check each return, where the results differ, and how to store them.

Integration ops

EHR sandboxes: what vendors publish and what they lack

Which EHR and PM vendors publish a sandbox, what a sandbox leaves out, and how to test an integration before the first customer connects.

Vendor APIs

eClinicalWorks FHIR R4 in practice: where the API departs from the spec

What an engineer meets when integrating with the eClinicalWorks FHIR R4 API, why the behavior differs from the documentation, and an open source client that encodes what we learned.

Integration ops

Detecting and surviving breaking changes in vendor APIs

How to catch an EHR vendor change in minutes with schema checks, canary accounts and per-connector alerts, and roll a fix without downtime.

Integration ops

Handling customer EHR and portal credentials safely

A design for collecting, storing, re-authenticating and logging customer EHR and payer portal credentials without your product seeing the password.

Claims data

Claim status with X12 276/277 and what the 277 leaves out

How the 276/277 claim status transaction works, what the category and status codes mean, and what to do when the answer is thin.

Integration ops

Build or buy EHR and PM integrations: a decision guide

What each EHR connector contains, the maintenance vendors impose, the partner fees vendors publish, and when a startup should build its own.

Vendor APIs

athenahealth API notes: Preview, practice access and claims

What the athenahealth developer docs say about the Preview sandbox, practice-level enablement, Marketplace contracting and the Claim API.

Vendor APIs

AdvancedMD API notes: access, data, writes and gaps

How AdvancedMD grants API access, what its Connect and FHIR APIs expose, where writes are allowed, and what the public pages do not say.