The Portal-Less Promise of TEFCA Is Getting (One Step) Closer
Fasten now supports Epic ID and MyChart Central for TEFCA Individual Access Services (IAS).
200+ health systems never responded to our requests to let patients pull their own records into Fasten. We just filed information blocking com...
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...
Don’t make patients prove themselves twice.
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...
Happy New Year from the Fasten team.
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...
Our previous post, Who’s Actually Required to Provide Access to Clinical Data, covered the provider side of healthcare APIs. Now let’s complet...
Fasten Health started as an open-source privacy focused Personal Health Record app (PHR). One of the first of its kind.
Fasten Health is renewing our annual commitment to the CARIN Alliance Code of Conduct, reinforcing our stance that trust isn’t optional, it’s ...
Note: This post is a follow-up to TEFCA IAS - A Story of Interoperability and Unrealized Potential, where we discussed the structural challeng...
Developers building patient-directed apps often get asked by healthcare providers or EHR vendors to sign a Business Associate Agreement (BAA)....
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 ...
Application Programming Interfaces (APIs) are a way to allow different applications to communicate and exchange data programmatically (without...
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...
No posts match that search.