Open-source medical record management, honestly reviewed. The pitch is compelling. The current reality is more complicated.

TL;DR

What it is: Open-source (GPL-3.0) self-hosted personal/family electronic medical record manager — a single private location for your scattered health data that never touches a third-party server [README][3].
Who it’s for: Privacy-conscious individuals and families frustrated by fragmented medical records across multiple providers, insurers, and labs — and specifically those who already have FHIR data exports to work with [README][2].
Cost savings: No direct SaaS equivalent to replace — most competing personal health record apps are free but cloud-based (Apple Health, Google Health). The value proposition here is privacy and control, not bill reduction.
Key strength: Genuinely the most coherent open-source PHR for families rather than clinics. Clean interface, condition-specific dashboards, FHIR standard support, Docker deployment [5][2].
Key weakness: Fasten OnPrem can no longer pull records directly from healthcare providers. The much-cited EHR integration with thousands of institutions migrated to the commercial “Fasten Connect” product. OnPrem today accepts only manual entry or FHIR Bundle file uploads [README]. This is the biggest gotcha in the project.

What is Fasten Health

Fasten Health is an open-source, self-hosted personal health record (PHR) manager built for individuals and families — not for clinics or hospitals. The founder, Jason Kulatunga, built it out of personal necessity: after a semi-serious medical issue, he realized his own health history was scattered across a decade’s worth of insurance providers, hospital networks, vision clinics, and labs with no single place to see it all [3][2].

The pitch is simple: one private dashboard for your entire family’s medical history. Lab results, conditions, encounters, medications — structured around the FHIR protocol (the healthcare industry’s data interchange standard) and stored on your own server [README][3].

Here’s where you need to read carefully before getting excited.

The project splits into two products. Fasten OnPrem is this open-source repository — community-maintained, GPL-3.0 licensed, free to self-host. Fasten Connect is the company’s commercial product: a fully managed enterprise API platform with direct integrations to 50,000+ healthcare institutions [README]. The EHR connection capability that generated most of the early enthusiasm — OAuth2/SMART-on-FHIR logins to hospitals, insurers, and labs — lives in Fasten Connect, not OnPrem.

The README now carries an explicit warning box: “Fasten Onprem is not able to import data from healthcare providers directly. You can only use this application to manually enter data, or upload FHIR Bundles that have been exported through other means.” [README]

That’s a substantial change from the 2023 Reddit announcement [2] that described 2,000 connected healthcare institutions and OAuth2 flows. The community edition has been narrowed. Keep that in mind for everything that follows.

At 2,667 GitHub stars and 163 forks with 30 contributors, this is a legitimate open-source project with real community traction — but it’s not a high-velocity project like Nextcloud or Home Assistant [README].

Why people choose it

The self-hosting community’s interest in Fasten traces back to a consistent frustration: medical data is fragmented by design. Patients accumulate records across every employer’s health plan, every specialist visit, every lab network. Nobody consolidates it. Cloud PHR services exist, but they’re operated by companies whose business model involves your health data in ways you can’t fully audit [3][5].

One TrueNAS community member summarized the appeal directly: a disabled user managing a large volume of medical records who specifically wanted a private, self-hosted solution rather than trusting any external service [1]. The medevel.com analysis frames the same motivation through the lens of a doctor who witnessed the power of a patient-held PHR: when a patient could show their full medication history, sleep data, and insulin dose logs from their own device, the diagnosis that had stumped the clinic became obvious within minutes [5].

The FHIR angle matters more than it sounds. FHIR (Fast Healthcare Interoperability Resources) is the protocol that most modern US healthcare providers are legally required to support for patient data export requests. If you can get a FHIR bundle export from your insurer or hospital — and in the US, under 21st Century Cures Act rules, you often can — Fasten can ingest it [README][2]. The friction is that “you can get a FHIR export” is aspirational for most patients; the process varies wildly by institution.

The family-first design is a genuine differentiator. OpenEMR, the most-cited open-source alternative, is built for clinical workflows — it assumes you’re a practice managing patient records, not a parent tracking three kids’ vaccination histories alongside an aging parent’s medication list [README][2]. Fasten assumes the opposite.

Features

Based on the README and reviewed sources:

Core record management:

Manual health record entry [README]
FHIR Bundle JSON file import [README][2]
Condition-specific dashboards with grouping of related encounters, labs, and practitioners [2]
Labs report with historical test data and comparison against reference ranges [2]
Medical History view — groups all records by condition [2]
Editor for grouping related conditions [2]
Multi-user support for household/family use (listed as “future” in README, present in earlier announcements) [README][2]

Technical:

Self-hosted, offline-capable [README]
Docker and Docker Compose deployment [README]
REST API [merged profile]
SSL/TLS support [merged profile]
AI integration capability [merged profile]
Go backend, Angular/TypeScript frontend [README]

On the roadmap (not yet shipped in community edition):

Vaccination and condition-specific recommendations via NIH/WHO clinical guidelines (HEDIS/CQL) [README]
ChatGPT-style offline query interface for your own health data [README]
Smart device and wearable integration [README]
Automated EHR pulls from providers (commercial Fasten Connect only) [README]

The gap between “current” and “future” in the README is notable. Several features that appear in third-party reviews as present capabilities — including direct EHR connections — have shifted to either the commercial product or future roadmap items. The honest characterization of Fasten OnPrem today is: a well-designed FHIR data viewer and manual health record manager, not yet the autonomous health data aggregator it’s positioned as [README][2].

Pricing: SaaS vs self-hosted math

This category doesn’t map cleanly onto the usual “escape your SaaS bill” framing, because most personal health record apps are free.

Fasten OnPrem:

Software: $0 (GPL-3.0)
VPS to run it: $5–10/month on Hetzner, DigitalOcean, or similar
Your time to set up and maintain

Fasten Connect (commercial):

Enterprise pricing, contact sales. Not disclosed publicly [fastenhealth.com].

Competing options (for comparison):

Apple Health / Health Records: Free, iOS-only, integrates with some US healthcare providers directly
Google Health: Limited, free, no self-hosting
CommonHealth: Free Android app, supports FHIR imports
Epic MyChart: Free for patients, requires your provider to use Epic

The savings argument doesn’t apply the way it does for Zapier or Notion alternatives. You’re not escaping a $100/month bill — you’re trading cloud convenience and potential data mining for local control. For most users, the question is less “how much does this save” and more “how much do I value not having my medical history on someone else’s servers.”

For a family that has used the same insurer and hospital network for years and can obtain FHIR exports, the setup cost is a one-time investment: a $5/month VPS, an afternoon of configuration, and you have a permanent private health archive. There’s no ongoing per-record fee, no subscription expiring, and no company that can pivot away from consumer PHR and delete your account.

Deployment reality check

The install path is Docker Compose, which is about as straightforward as self-hosted tools get [README]. The TrueNAS community forum thread [1] is instructive: even a non-expert user evaluating their options settled on “VM running Docker” as the most stable path, with TrueNAS App Catalog as a simpler but less stable alternative. The recommendation from the community was to keep data backed up separately regardless of deployment method — sensible advice for any health data store.

What you need:

A Linux VPS or home server with Docker and docker-compose
A domain name and reverse proxy (Caddy or nginx) for HTTPS
1–2GB RAM minimum; more if you’re managing large FHIR bundles
Basic comfort with the command line

What can go sideways:

Getting FHIR exports from your actual healthcare providers is harder than the original pitch made it sound. US regulations require providers to offer FHIR exports, but in practice, finding and requesting them involves navigating individual patient portals, which vary in quality [README note][4].
The fork between OnPrem and Connect isn’t fully explained in third-party reviews. Several reviews written in 2022–2023 [2][5] describe capabilities that now require a commercial license or are simply gone from the community edition.
GPL-3.0 license means you can’t embed this in a proprietary product without open-sourcing your own code — different from MIT-licensed tools [README].
With only 30 contributors and 1,078 commits as of the snapshot date, this isn’t a high-bus-factor project. If the maintainer deprioritizes OnPrem in favor of Fasten Connect, the community edition could stagnate.

Realistic time to a working instance: 30–90 minutes for a technical user following the Docker Compose path. Getting useful data into it is the harder problem — exporting FHIR bundles from your real providers varies from trivially easy to essentially impossible depending on which institutions you use.

Pros and Cons

Pros

Privacy-first by design. Your health records stay on your hardware. No third-party analytics, no data sale, no account that gets hacked or acquired [README][3][5].
FHIR-native. Built around the actual standard that healthcare providers use. If you can get FHIR exports, Fasten can handle them cleanly [README][2].
Family-oriented design. Most open-source medical tools are clinic software repurposed for personal use. Fasten was designed from day one for household-level record aggregation, multiple family members, condition tracking [README][2].
Condition dashboards. The Medical History view — all encounters, labs, and practitioners grouped by condition — is genuinely useful for anyone managing a complex health history [2].
Docker deployment. The install path is simple and well-documented [README][1].
Active enough community. Discord server, GitHub Issues, 30+ contributors, 26 releases as of data snapshot [README].

Cons

The EHR integration is gone from the free version. This is the most important con. The automated “connect to your hospital/insurer/lab” feature that defined the project’s early pitch is now a commercial product (Fasten Connect). OnPrem requires manual entry or FHIR file uploads [README]. Many reviews [2][5] pre-date this split and describe capabilities that don’t exist in OnPrem today.
Modest community size. 2,667 stars and 30 contributors is small for infrastructure you’re trusting with sensitive health data. Compare to Nextcloud (28,000 stars) or Home Assistant (75,000 stars). Community-maintained means community-dependent [README].
GPL-3.0, not MIT. Can’t embed in proprietary products. If you’re building something commercial on top of this, you need a lawyer [README]. (Note: medevel.com incorrectly states MIT license [5] — the actual license is GPL-3.0.)
Several roadmap items are still future. Multi-user, wearables, AI query interface — prominently featured in the vision, not yet in the product [README].
Getting real data in is the hard part. The product is only as useful as your ability to obtain FHIR exports from your actual providers. This friction isn’t Fasten’s fault, but it’s the practical blocker for most users [4][README].
Thin ecosystem. No plugin marketplace, no integrations beyond what’s built in, no community-contributed connectors (unlike Home Assistant or n8n) [README].

Who should use this / who shouldn’t

Use Fasten Health if:

You have a complex medical history spread across multiple providers, insurers, and labs, and you want one private place to see it all.
You or a family member manages a chronic condition and wants structured condition-specific tracking rather than a folder of PDFs.
You can obtain FHIR exports from your healthcare providers (US patients under major insurers or hospital networks using Epic/Cerner often can).
You’re comfortable with Docker deployment, or you have someone who can set it up once.
Privacy is a genuine priority — you don’t want a company analyzing patterns in your health data.

Think carefully before committing if:

You were drawn by the “connect to 2,000 healthcare institutions” pitch. That requires Fasten Connect (commercial), not OnPrem.
Your providers don’t offer FHIR exports. The tool becomes a manual journal, which may or may not be worth the setup effort.
You’re not technical and don’t have technical support. This isn’t a point-and-click SaaS product.

Skip it if:

You need direct EHR connections without the commercial product — Apple Health Records on iOS or CommonHealth on Android may serve you better.
You’re a clinic or practice managing patient records — look at OpenEMR instead.
You want a guarantee of long-term maintenance — the community size doesn’t provide it, and the commercial product has diverged significantly from the OnPrem version.

Alternatives worth considering

Apple Health / Health Records — iOS-only, free, integrates directly with many US healthcare providers via FHIR. No self-hosting, but the provider integration actually works. The default choice for iPhone users who don’t need self-hosted privacy.
CommonHealth — Android alternative to Apple Health. Free, FHIR-capable, no self-hosting.
OpenEMR — The most mature open-source medical records system. Built for clinics, not individuals. Far more complex and powerful, but wrong tool for a family trying to aggregate their own records.
Metriport — Developer/API-focused healthcare interoperability platform. Not a consumer PHR tool, but worth knowing if you’re building something that needs to connect to EHRs [4].
Medisafe — Medication management, not a full PHR. Free, well-designed, but narrow scope.
Manual FHIR archive — If your providers support FHIR exports, you can store and query them yourself without any additional software. Less elegant, but zero dependencies.

The honest shortlist for a privacy-focused individual who wants self-hosted PHR is short: Fasten Health is essentially the only viable option in this category. That’s less a ringing endorsement and more a description of how underdeveloped the self-hosted personal health record space is.

Bottom line

Fasten Health is the right idea at an uneven stage of execution. The core problem it addresses — fragmented, insurer-held, provider-locked medical records that patients can’t easily consolidate — is real and genuinely underserved. The design philosophy (families, not clinics; FHIR-native; private by default) is correct. The Docker-based deployment is accessible. The condition dashboards, when populated, are genuinely useful.

The gap between the original vision and the current OnPrem reality is the part you need to understand before deploying it. The autonomous EHR connection feature — the piece that made early reviews exciting — moved to the commercial product. What you get free and self-hosted today is a well-designed FHIR viewer and manual health record manager. That’s still valuable for the right user, but it’s not the seamless aggregation engine the 2022 launch described.

If you have a complex health history, can get FHIR exports from your providers, and value keeping that data off cloud services — Fasten Health is worth the afternoon it takes to deploy. If you need the provider connections to work automatically, you either need to investigate Fasten Connect’s pricing or wait for the community edition to close the gap.

Sources

TrueNAS Community Forums — “Running Fasten Self-hosted - wait for Eel or use a VM?” (Aug 2024). https://forums.truenas.com/t/running-fasten-self-hosted-wait-for-eel-or-use-a-vm/11749
r/selfhosted (Jason Kulatunga / analogj) — “Fasten Health - Open Source Self-hosted Personal Health Record” (2023). https://www.reddit.com/r/selfhosted/comments/10ky6tb/fasten_health_open_source_selfhosted_personal/
Fasten Health Blog (Jason Kulatunga) — “An Open-Source Personal Health Record | Fasten Health Blog” (Sep 22, 2022). https://blog.fastenhealth.com/introducing-fasten-health
Metriport Blog (Beth Plumptre) — “Patient Tools and Apps to Access Health Records” (May 31, 2023). https://www.metriport.com/blog/patient-tools-and-apps-to-access-health-records
MEDevel.com (Hazem Abbas) — “Fasten: A Free Self-hosted Personal Health Records App for Families and Individuals”. https://medevel.com/fasten/

Primary sources:

GitHub repository and README: https://github.com/fastenhealth/fasten-onprem (2,667 stars, GPL-3.0 license, 30 contributors)
Fasten Connect (commercial product): https://www.fastenhealth.com/