Ciyex has reached a significant milestone. The core EHR platform is stable, FHIR-native, and serving real clinical workloads. The patient portal gives patients direct access to their health data. The telehealth module brings care to communities that distance or mobility would otherwise exclude. But there is much more to build. This roadmap outlines the major initiatives planned for 2027, each driven by the same principle that guides everything we do: healthcare technology should serve patients first, and it should be accessible to everyone.

Healthcare software has unique deployment requirements. It must be highly available because clinics cannot afford downtime during patient visits. It must be secure because it handles protected health information. It must be auditable because regulators need to verify what is running and when it changed. Kubernetes, combined with GitOps practices, provides the foundation for meeting all of these requirements. This guide walks through how Ciyex is deployed in production using Kubernetes, Helm, ArgoCD, and supporting infrastructure.

For decades, the patient experience with healthcare technology has been defined by what patients cannot do. They cannot see their own lab results until the doctor calls. They cannot read the notes from their last visit. They cannot schedule an appointment without sitting on hold. They cannot send a simple question to their care team without making a phone call during business hours. The Ciyex Patient Portal changes this by giving patients direct, standards-based access to their health information and care services.

Contributing to healthcare software is one of the most meaningful things a developer can do. Every bug fix, every performance improvement, every accessibility enhancement directly impacts patient care. This guide walks you through setting up a Ciyex development environment, understanding the project structure, and making your first contribution.

A mother in rural Guatemala walks two hours to a clinic where her child's vaccination records are kept in a paper ledger. A community health center in Mississippi cannot afford to upgrade from a discontinued EHR system, so staff manually re-enter data into spreadsheets. A public hospital in Kenya uses three different systems that cannot share patient information, forcing doctors to rely on patients to remember their own medication lists. These are not edge cases. They represent the reality of healthcare technology for most of the world's population.

Open source software does not solve every problem in healthcare. But it removes one of the most persistent barriers: the cost and control of the technology itself.

For the 60 million Americans living in rural areas, seeing a specialist can mean a four-hour drive each way. For elderly patients with mobility limitations, for parents juggling work and childcare, for immunocompromised patients who should avoid waiting rooms, the barrier to care is often not clinical but logistical. Telehealth removes that barrier. Ciyex integrates telehealth directly into the clinical workflow, powered by Jitsi, so that virtual visits are as natural and well-documented as in-person encounters.

Interoperability, the ability of different healthcare systems to exchange and use data, has been the central challenge of health IT for decades. HL7 v2 messages, CDA documents, and proprietary formats have created a landscape where patient data is trapped in silos. FHIR (Fast Healthcare Interoperability Resources) is the standard that finally makes seamless data exchange practical. Ciyex is built on FHIR from the ground up, not as an afterthought or an integration layer, but as the core data model.

In healthcare software, a security breach is not an inconvenience. It is a violation of patient trust, a potential HIPAA violation carrying fines up to $1.5 million per incident category, and a risk to patient safety. Ciyex treats security as the foundational layer upon which every feature is built. This post details the specific mechanisms we use to protect protected health information (PHI) at every layer of the system.

Building a healthcare platform that handles protected health information (PHI), scales across thousands of concurrent users, and remains maintainable by an open source community requires deliberate technology choices. Every component in the Ciyex stack was selected for stability, security, and long-term viability. Here is a detailed look at what powers the platform and why we chose each piece.

Healthcare software has failed the people who need it most. Not the large hospital systems with seven-figure IT budgets, but the 30 million Americans who receive care at community health centers, rural clinics, and safety-net practices that cannot afford modern electronic health records. Globally, the picture is far worse. Billions of people receive care documented on paper, in spreadsheets, or in fragmented systems that cannot share data with one another.

Ciyex was built to change that.