Valerii Checha
Valerii Checha leads the healthcare business unit at Onix Health. He works with US digital health startups, hospitals, and MedTech companies to scope engagements and align software investment with business outcomes — deciding, early and honestly, what to build, what to buy, and what to rescue.

What Valerii works on
He writes on the business side of healthcare software: build-versus-buy economics, total cost of ownership, and turning compliance and engineering constraints into a plan that ships.
- Healthcare software strategy
- Build vs buy and TCO
- Engagement scoping
- Digital health go-to-market
Articles by Valerii
- TEFCA: What It Means for Health Apps and the Teams Building Them
TEFCA is the national network-of-networks for health data, and apps can reach it only through a QHIN. What product teams need to know about roles, exchange purposes, Individual Access Services identity rules and FHIR. - Epic Showroom vs Connection Hub vs Toolbox: Which Epic Listing Fits Your App?
Showroom is Epic's marketplace site. Connection Hub and Toolbox are two different designations inside it, with different requirements, costs and support, and the right one depends on how far along your Epic integration is. - EHR With a Patient Portal vs a Separate Portal: Which Do You Need?
Most certified EHRs come with a patient portal, and for many practices it is enough. A separate portal earns its cost when patients span several EHRs, when the workflows go beyond the chart, or when the organization is not a provider. Here is how to tell which case you are in. - Patient Portal Features: What a Portal Must Do and What It Should
A patient portal feature list in three tiers: what regulations and certification require, what patients actually use according to federal survey data, and the staff-side features that decide whether the portal saves work or creates it. - Patient Portal Proxy Access for Caregivers: How to Design It
Proxy access lets a parent, spouse or adult child use a patient portal on someone else's behalf, with their own login. What HIPAA says about who may act for a patient, and how to turn that into proxy types, permissions, verification and revocation. - Home Health EMR Systems: What the Record Has to Hold
A home health EMR is shaped by Medicare's home health rules more than by clinic workflows. The system has to support assessment and OASIS deadlines, plan of care and order rules, clinical record requirements, PDGM payment periods and EVV. - Electronic Visit Verification Requirements: What a Home Care App Must Capture
Federal law requires electronic visit verification for Medicaid personal care and home health visits, and leaves the system design to each state. A home care app has to capture six data elements, cover the right services, and follow what CMS says about GPS and privacy. - RPM CPT Codes and Medicare Billing Rules: What Your Software Must Track
Medicare pays for remote patient monitoring through codes for setup, device supply and treatment management, each with its own rules. The codes CMS names, the conditions behind every claim, what changes in 2027, and the checks a billing engine should run before a claim goes out. - RTM vs RPM: Which Remote Monitoring Program Fits Your Patients?
Remote physiologic monitoring and remote therapeutic monitoring look alike on a claim, but they measure different things, suit different care teams and cannot be billed together. How to pick one per patient, and what the software has to record for each. - Chronic Care Management Software: The CCM Workflow and Billing Rules It Must Follow
Medicare's chronic care management program runs on a monthly cycle of consent, care plans, round-the-clock access and counted minutes. What CMS requires at each step, where advanced primary care management fits, and the checks CCM software should run before the month closes. - Health Insurance CRM Requirements: What the System Must Hold
Besides leads and deals, a health insurance CRM for Medicare Advantage sales has to hold contact permissions, Scope of Appointment records, agent licensing and training, call recordings and required documents, alongside the member data itself. Each requirement on this field-by-field list comes with the rule behind it. - Medicare CRM for AEP and OEP: Running an Agency Through Enrollment Season
Most of a Medicare agency's year happens in a few months: Annual Enrollment from October 15 to December 7, then the Medicare Advantage Open Enrollment Period from January 1 to March 31. How a CRM should handle the calendar, the lead surge, Scope of Appointment timing, recordings and the retention work that follows. - Broker Portal for Health Insurance: What Agents, Brokers and the Plan Need From It
A broker portal gives a health plan's appointed agents and brokers one place for licensing status, quotes, applications, their book of business and commissions. What it should hold, which CMS rules shape it for Medicare Advantage and Marketplace sales, and how to limit each broker to their own members. - Information Blocking Rules for Developers: What Your Software Must Not Do
Information blocking is any practice likely to interfere with access to, exchange of or use of electronic health information, unless the law requires it or an exception applies. Here is who the rules cover, the API practices regulators have called out and how to build software that supports the exceptions. - Build vs buy: when a custom EHR beats Epic or Cerner (and when it doesn't)
Most healthcare organizations don't need a custom EHR; they need a few custom workflows on top of one. Here's a decision framework for when to buy, when to extend a bought EHR, and when building your own is worth the long-term commitment. - Custom CRM vs Salesforce vs HubSpot for Health Insurance: An Honest TCO Comparison
Salesforce Health Cloud, HubSpot Enterprise and a custom CRM, priced from the vendors' own pages and modeled over five years. How to compute the total cost for your seat count, and what changes once PHI is in the CRM. - Why Mid-Size Health Insurers Overpay for Salesforce, and How to Check Your Own Bill
Per-seat pricing grows with headcount whether or not the value grows with it. Where a health insurer's Salesforce bill usually leaks, how to find each leak with data you already have, and what to change at renewal. - How a California Health Insurer Moved Off Per-Seat CRM Fees: A Custom CRM Case Study
A California health insurer replaced monthly third-party CRM fees with a one-time build: a custom, HIPAA-compliant CRM on its own private server, delivered January to June 2023 by 5 specialists. The case covers what was built and how PHI is protected, with a way to estimate the same move for your team. - FHIR for non-engineers: a 10-minute primer for product managers
If you're the PM on a healthcare project, you don't need to write FHIR code, but you do need to know what your engineers mean by resources, profiles, scopes and US Core, and what FHIR will not do for you. - When to Rescue and When to Rebuild a Healthcare Software Project: A Decision Framework
A struggling healthcare product can be fixed in place, rebuilt from scratch, or replaced piece by piece while it runs. Five areas to inspect, a simple way to score them, and the HIPAA checks that apply whichever way you go.