An open-source, self-hosted personal/family electronic medical record manager for private health data aggregation.
Fasten is an open-source, self-hosted personal health record (PHR) manager that allows individuals and families to securely aggregate and view their medical history from multiple healthcare providers. It solves the problem of fragmented medical records by providing a private, centralized dashboard where sensitive health data remains under the user's full control.
Individuals and families seeking a private, self-hosted solution to manage their electronic medical records across various healthcare providers, insurance companies, and labs.
Developers choose Fasten for its strong emphasis on privacy and data ownership, offering a self-hosted alternative to commercial health platforms. Its family-centric design and support for the FHIR protocol make it uniquely suited for personal health management without relying on third-party services.
Fasten is an open-source, self-hosted, personal/family electronic medical record manager
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Fasten is fully self-hosted, ensuring sensitive medical data never leaves user control, as emphasized in its privacy-first philosophy.
Built for households with configurable user roles, unlike clinic-oriented EMR systems such as OpenEMR, making it ideal for family health management.
Utilizes the healthcare industry's semi-standard FHIR protocol, allowing compatibility with medical data exports and future integrations.
Includes HTTPS with self-signed TLS certificates by default, providing secure data transmission without relying on third-party services.
The open-source version cannot import data automatically from healthcare providers; users must manually enter data or upload FHIR Bundles, which is inconvenient for ongoing updates.
Requires manual import of self-signed CA certificates across different operating systems and browsers, adding technical overhead and potential for errors.
Multi-user support is explicitly noted as a work in progress, so current implementations may lack robust access control and permissions.