Serhii Kholin
Serhii Kholin is the CEO of Onix Systems, the parent company of Onix Health. He has helped grow the company into a 370+ engineer organization with a dedicated healthcare practice serving US digital health startups, hospitals, and MedTech companies.

What Serhii works on
He writes on healthcare delivery strategy: build-versus-buy decisions, the real total cost of ownership behind off-the-shelf platforms, and how to scope custom software so it ships.
- Healthcare software strategy
- Build vs buy decisions
- Total cost of ownership
- Engagement scoping and delivery
Articles by Serhii
- EHR integration for startups: a HIPAA-ready path to your first EHR
A startup's first EHR integration should be one EHR, the one your first paying customer runs, read-only on standard FHIR APIs, with BAAs and a risk analysis in place before any PHI flows. - White-Label Patient Portal vs Custom Build: How to Decide
A white-label patient portal gets you to market under your brand fast. A custom build gives you the roadmap and the data model. How to compare the two on full cost, what stays your responsibility either way, and what to ask a vendor before you sign. - Hospital at Home Software: What the Program Needs to Run
A hospital-at-home program delivers inpatient care in the patient's home, so its software has to cover screening, daily evaluations, two in-person visits a day, instant audio contact and a 30-minute response. Each CMS requirement maps to a software module, and the CMS study of the program shows which data to capture. - Caregiver Coordination Apps: Building for Family and Carer Networks
A caregiver coordination app gives the patient, family, friends and paid carers one place for tasks, a calendar and messages, with the patient deciding who sees what. The roles, the sharing rules from HIPAA, the Medicare programs that pay for caregiver support, and the build decisions behind them. - CRM for Health Plans: Building a Member Engagement System
A health plan's CRM is organized around the member for as long as they stay with the plan. What the member record should show, which communications run on federal deadlines, when a member message counts as HIPAA marketing, and how Star Ratings and the CMS interoperability rule change what service teams need to see. - Salesforce Health Cloud Alternatives: Five Options and What Each One Gives Up
If Health Cloud costs more than your team uses, there are five realistic paths: a standard Salesforce cloud, Microsoft Dynamics 365, HubSpot with Sensitive Data turned on, a custom CRM, or a hybrid. What each option trades away, and what to check before you move. - HIPAA Risk Analysis for Startups: How to Run Your First One
Covered entities and business associates must assess the risks to the electronic PHI they hold, and a startup that handles PHI for a provider or plan is usually a business associate. NIST's method gives you a step-by-step way to run the first analysis, and the rule sets what to write down and when to redo it. - BAA Questions to Ask a Vendor Before You Sign
HIPAA fixes the required terms of a business associate agreement and leaves several practical points open: which services are covered, how fast you hear about a breach, who the subcontractors are and what happens to the data at the end. Twelve questions to ask, with the regulation behind each one. - AI in Patient Portals: Safe Uses for Patients and Where to Draw the Line
AI in a patient portal is safest when it helps patients find, navigate and understand what their care team already gave them, and riskiest when it interprets symptoms or results on its own. Here is how FDA, Anthropic's usage policy and NIST frame the line, and the safeguards a portal should build in. - Multi-state telehealth: the licensing routing problem (and what to build)
A telehealth visit generally happens where the patient is, so the clinician usually needs a license or registration in the patient's state. Here is how licensure compacts, state telehealth registrations and DEA rules work, and the routing logic a platform needs. - CDS Hooks: shipping clinical decision support clinicians actually use
CDS Hooks is the HL7 standard for showing decision support inside the EHR at the moment it matters. The standard gets your card on screen; whether clinicians act on it depends on when it fires, what it says and how you measure it. - Building a clinical validation harness for ML in healthcare
Clinical validation means proving, on data the model never saw, that it works for the patients and sites it will serve, overall and by subgroup, and that it keeps working after launch. Here is what FDA and NIST expect and how to turn that into a repeatable harness. - IEC 62304 in practice: what it actually requires (and what people get wrong)
IEC 62304 sets the life cycle processes for medical device software, scaled by software safety class A, B or C. Here is what the standard asks for, how FDA uses it in premarket submissions, and where teams misread it. - Surviving Epic integration after App Orchard: open.epic, Vendor Services and Showroom
Epic no longer runs App Orchard. Connecting an app to Epic now involves free open.epic APIs, the optional Vendor Services program, Connection Hub listings on Showroom, and an approval from each health system, which is what decides your go-live. - Ambient voice documentation: pipelines that don't leak PHI
Ambient clinical documentation records a visit, transcribes it and drafts the note. Every stage handles PHI. Here is how HIPAA, business associate agreements and recording-consent laws apply, and where a voice-to-note pipeline tends to leak. - FDA's “Cybersecurity in Medical Devices” premarket guidance: what changed from 2023 to 2026 for SaMD teams
FDA's premarket cybersecurity guidance was finalized in September 2023, revised in June 2025 and again in February 2026. Here is what it asks for: threat models, SBOMs, four architecture views, penetration testing and section 524B plans for cyber devices.