Fasten just filed 200+ information blocking complaints against health systems using MEDITECH

guidebook

Developers Need to Know: SQL Is Not Enough for FHIR Data

You have FHIR data arriving from a provider API, Postgres is already running and you know JSONB is genuinely fast. And in fact, it’s working f...

Jason Kulatunga • Jul 04, 2026

update

Fasten’s 𝐁𝐫𝐢𝐧𝐠 𝐘𝐨𝐮𝐫 𝐎𝐰𝐧 𝐈𝐝𝐞𝐧𝐭𝐢𝐭𝐲 capability is now live

Don’t make patients prove themselves twice. 

Jason Kulatunga • Jun 23, 2026

update

We need to have a Conversation about Consent - Part 1

There has been a lot of progress in TEFCA since our last update (discussing Patient Matching & RLS) a couple of months ago. Now the conver...

Jason Kulatunga • May 14, 2026

update

TEFCA Mode Is Here: One Line of Code, 60,000 Providers

Happy New Year from the Fasten team.

Jason Kulatunga • Jan 12, 2026

guidebook

TEFCA IAS - Deep Dive into Patient Matching & RLS Responses

It’s been just over eight months since our last technical deep dive into TEFCA Individual Access Services (IAS). In earlier posts, we looked b...

Jason Kulatunga • Nov 05, 2025

guidebook

Developers Need to Know: Which Payers Are Required to Provide API Access?

Our previous post, Who’s Actually Required to Provide Access to Clinical Data, covered the provider side of healthcare APIs. Now let’s complet...

Jason Kulatunga • Aug 19, 2025

legal

Fasten Health Pledges to CMS Interoperability Framework

Fasten Health started as an open-source privacy focused Personal Health Record app (PHR). One of the first of its kind.

Jason Kulatunga • Jul 31, 2025

carin

Patient Data, By Consent Only

Fasten Health is renewing our annual commitment to the CARIN Alliance Code of Conduct, reinforcing our stance that trust isn’t optional, it’s ...

Jason Kulatunga • Jul 29, 2025

guidebook

TEFCA IAS - What Does it Actually Mean for Patients

Note: This post is a follow-up to TEFCA IAS - A Story of Interoperability and Unrealized Potential, where we discussed the structural challeng...

Jason Kulatunga • Jun 17, 2025

guidebook

Developers Need to Know: Do Patient Access Apps Need to Sign a BAA with Providers/EHRs?

Developers building patient-directed apps often get asked by healthcare providers or EHR vendors to sign a Business Associate Agreement (BAA)....

Jason Kulatunga • May 23, 2025

guidebook

Developers Need to Know: Who’s Actually Required to Provide Access to Clinical Data?

If you’re building a patient-facing app that requires access to medical records, you’ve probably been given the runaround: told that you need ...

Jason Kulatunga • Apr 07, 2025

guidebook

Developers Need to Know: How to Report Information Blocking to ASTP

Application Programming Interfaces (APIs) are a way to allow different applications to communicate and exchange data programmatically (without...

Jason Kulatunga • Mar 11, 2025

guidebook

Developers Need to Know: What is the 5-Day / 10-Day Rule?

The 21st Century Cures Act requires Certified EHRs to approve Patient Access API requests within: 10 business days to verify an API user’s id...

Jason Kulatunga • Mar 11, 2025

guidebook

TEFCA IAS - A Story of Interoperability and Unrealized Potential

Over the last few months, I’ve had a number of patients and companies reach out to ask about Fasten and how we fit in with TEFCA Individual Ac...

Jason Kulatunga • Feb 21, 2025