HN's June Thread Hid 6 RCM Startups. The Epic Talent Is Titled "Analyst."
Why LinkedIn Boolean searches miss Epic Bridges, Mirth, and Cloverleaf talent, and where healthcare RCM startup recruiters should actually look.
The June 2026 HN "Who is hiring" thread (item 48357725, posted June 2) surfaced something most sourcers missed because the thread explicitly banned recruiting firms: a cluster of six healthcare RCM startups all asking for the same hard requirement. Epic, Athena, ModMed, and eClinicalWorks integration via FHIR, HL7, or RPA. The job specs are tight, the salary bands are posted, and standard LinkedIn searches return roughly nothing.
That last part is not your Boolean. It is the market.
The HN signal is six RCM startups in one month
Scroll the June thread and the same shape repeats. One representative posting wants engineers who can build EHR integrations across "Epic, Athena, ModMed, eClinicalWorks via API (FHIR, HL7) or RPA/computer vision based integrations," with RCM experience as a MUST. The same posting wants fluency in "healthcare billing data (837, 835, 270/271), HL7 and FHIR data" and clearinghouses like Change Healthcare, Availity, and Waystar. Salary bands published in-thread: Platform Engineer $140 to $160K, Full-Stack $110 to $130K, IT Specialist $90 to $110K.
That is a Playwright plus healthcare hybrid skill, on top of an Epic-gated certification universe, on top of a clearinghouse vocabulary nobody outside RCM uses. The job spec returns zero results on the LinkedIn searches most founders run. Not because nobody can do it. Because the people who can do it do not call themselves engineers.
Why six startups, why now
VCs are funding RPA-over-EHR plays because FHIR coverage is still patchy. If you cannot get a clean FHIR endpoint at ModMed or eClinicalWorks, you screen-scrape. That requires people who have shipped against those EMRs in production at a hospital or a billing company, not people who have read the spec. The HN thread is the leading indicator. The funding rounds will hit Pitchbook in Q3.
The title problem: "Analyst," not "Engineer"
Here is the core mismatch. ZipRecruiter draws the line itself: "Hl7 Integration Epic focuses on implementing and configuring HL7 interfaces within the Epic EMR system, often requiring Epic-specific certifications. In contrast, Hl7 Interface Analysts primarily support HL7 messaging, troubleshooting, and maintaining interfaces across various healthcare systems."
In other words, the person who has actually built and maintained an Epic Bridges interface in production almost always carries the title "Interface Analyst" or "HL7 Integration Analyst." Not "Software Engineer." Not "Backend Engineer." Not "Integration Engineer." A LinkedIn Boolean for ("Epic" OR "FHIR") AND ("engineer" OR "developer") filters out the exact applied pool you want.
When we ran a structured query against the Refolk index for US-based Epic Bridges and interface analyst talent, the strongly-matched pool came back at roughly 59 profiles. Of the top 25 sampled, 16 carried "Interface Analyst" in their title. Almost none said "Engineer."
Where they actually sit
Top employers in that pool: ELLKAY, Kootenai Health, Kaiser Permanente, UPMC Enterprises, Provation Medical, Omnicell, McKesson, Optimum Healthcare IT, NYC Health + Hospitals, and Abbott. The Epic-certified consulting shops (Optimum Healthcare IT, BridgeView, MDI Solutions, CTG/Cegeka) are also concentrated here, because they are some of the few non-hospital employers Epic recognizes for cert sponsorship.
Geography matters too. The cluster sits in Franklin and Nashville TN, Houston, Baltimore, Madison WI, Minneapolis, and Orlando. If your sourcing template defaults to SF Bay Area and NYC metro, you will see an empty funnel and conclude the talent does not exist. It exists. It is in Franklin.
Epic gated the market on purpose
The reason the analyst pool is trapped inside hospitals is structural, not accidental. Epic certification is "tightly controlled and is usually only available to individuals who are employed by a healthcare organization that has a current contract with Epic. Independent certifications are generally not available to the public." Each cert "generally ranges between $500 to $10,000," and that bill is paid by the hospital, not the candidate.
Epic UserWeb, the central training and knowledge hub, requires "an email associated with an Epic organization" to access. A startup recruiter cannot create an account, cannot post in the forums, and cannot DM anyone there. The community where these people actually learn and trade tips is invisible to you by design.
Epic did not just build software. It built a candidate moat with employer sponsorship as the only gate.
That changes the sourcing motion. There is no organic indie pipeline for Epic-certified talent. There is only poaching from hospitals and from the certified consulting bench. Anyone telling you otherwise has not actually placed one of these candidates.
The Mirth license flip created a new sourcable pool
On March 19, 2025, NextGen Healthcare announced that Mirth Connect 4.6 would transition from a dual open-source/commercial license to a closed-source proprietary model. Version 4.5.2 was the last freely available open-source release. The community forked, twice: BridgeLink (from Innovar Healthcare) and Open Integration Engine.
This matters for hiring. Mirth is "widely used (in 40+ countries) and powers about one-third of US health data exchanges." Anyone who jumped to one of the forks in 2025 or 2026 is, by definition, (a) opinionated about open-source HL7, (b) willing to make career decisions based on licensing politics, and (c) findable on GitHub instead of LinkedIn. They are the most reachable Mirth talent that exists right now, and most of them have never been pitched by a recruiter because they do not show up in LinkedIn Recruiter.
This is exactly the kind of search where natural-language sourcing pays off. Instead of trying to express "GitHub activity in BridgeLink or Open Integration Engine forks, plus prior experience with FHIR endpoints at a US hospital, plus location flexibility" as a Boolean string, you describe it in English. That is why we built Refolk: you ask in plain English and get the right people across GitHub, LinkedIn, and the open web, including the half of this pool that LinkedIn alone cannot see.
The engine ecosystem is wider than Epic Bridges
Epic Bridges is the prestige interface engine because Epic dominates large IDNs, but the integration-engineer pool spans more. The names worth knowing on a resume:
- Epic Bridges (Epic's own engine, certification-gated)
- Infor Cloverleaf (the legacy enterprise standard, often paired with Bridges in shops running both)
- Rhapsody (Lyniate, Best in KLAS for Integration Engines 2024 through 2026)
- Mirth Connect (NextGen, now closed-source post-4.5.2)
- BridgeLink and Open Integration Engine (the 2025 forks)
- Corepoint
- Iguana (iNTERFACEWARE, where one customer reports processing over 20 million HL7 messages daily across 2,500-plus channels)
- Redox (the API-first managed integration layer)
- InterSystems IRIS for Health
A Detroit Metro contract posted in May 2026 paid $60/hr 1099 for dual-engine work in "both Cloverleaf and Epic Bridges." That dual-engine fluency is one of the cleanest signals on a resume. Hospitals migrating from Cloverleaf to Bridges (or running both during transition) train a small subset of analysts on both engines, and those people are the highest-leverage hires for any RCM startup needing to ingest from multiple hospital systems.
Money: contract rates are clearing $73/hr median
ZipRecruiter's data (pulled May 31, 2026) puts average yearly pay for "Epic Bridges HL7 Interface" roles at $73,848 in the US, with a $55K to $90K spread for full-time. But that headline number understates the market because the senior people work contract. A Madison-based Epic Bridges contract posted in May 2026 paid $60 to $65 per hour for a remote six-month engagement. The Detroit dual-engine role was $60/hr 1099.
For an RCM startup paying a $140K to $160K Platform Engineer band, you are competitive on cash with the hospital FTE market (which tops out around $127,500 for senior HL7 integration analysts per ZipRecruiter), but you are losing on certification sponsorship, benefits stability, and the gravitational pull of a familiar Epic shop. Your pitch needs to be the work itself: building integrations across four EMRs, shipping fast, and seeing your code in production at multiple hospital customers. That story lands. "Move to SF" does not.
Where to actually source
A sane sourcing plan for an RCM startup hiring Epic, FHIR, and HL7 talent looks like this:
- Drop "Engineer" from your title filter. Search "Interface Analyst," "Integration Analyst," "HL7 Analyst," and "Epic Bridges Analyst." This single change unlocks most of the pool.
- Target the hospital and consulting employers by name. ELLKAY, Kootenai Health, UPMC Enterprises, Optimum Healthcare IT, MDI Solutions, BridgeView, CTG/Cegeka. Search current and recent.
- Search for clearinghouse vocabulary. Anyone listing Change Healthcare, Availity, or Waystar on a resume has touched 837, 835, and 270/271 in production. That is the RCM tell.
- Cross-reference GitHub for the Mirth fork population. BridgeLink and Open Integration Engine contributor lists, plus active participants in the NextGen Healthcare Connect GitHub Discussions, are the cleanest open-source HL7 signal you can get.
- Search the right geographies. Franklin TN, Nashville, Houston, Baltimore, Madison WI, Minneapolis, Orlando. Not SF, not NYC.
A natural-language sourcing tool like Refolk collapses these five filters into one query. You describe the person ("hospital-employed Epic Bridges analyst with Cloverleaf cross-training, plus clearinghouse experience, open to remote contract") and the ranked shortlist comes back across GitHub, LinkedIn, and the open web. That is the entire reason a healthcare integration recruiter needs more than LinkedIn for this category: the title taxonomy and the gated communities mean the highest-signal candidates are everywhere except the platform you are searching.
The takeaway for RCM founders
Six RCM startups posting the same hard requirement in one HN thread is a market signal. The talent exists. It is concentrated in maybe a few hundred Epic-certified analysts at named hospitals and consulting shops, plus the Mirth fork community on GitHub, plus the Rhapsody and Cloverleaf user groups. If your epic interface analyst sourcing keeps coming back empty, the answer is not a better Boolean. The answer is searching the right titles in the right geographies and pulling in the GitHub signal LinkedIn does not have. Do that and the pool is reachable. Skip it and you will spend Q3 wondering why nobody applies.
FAQ
Why do experienced Epic Bridges people use the title "Analyst" instead of "Engineer"?
It is a hospital-IT cultural artifact, not a seniority signal. Hospitals classify interface work under IT operations rather than software engineering, and Epic's own certification and role taxonomy reinforces the "Analyst" label. The work itself (HL7 channel configuration, FHIR endpoint design, troubleshooting production interfaces) is engineering work, but the title rarely changes even when these people move to consulting shops. If you are hiring fhir hl7 developers, search "Analyst" first.
Can I get my recruiters access to Epic UserWeb to source candidates there?
No. Epic UserWeb access requires an email associated with an Epic customer organization, which means a hospital, health system, or contracted consulting shop. Startup recruiters cannot create accounts. You can hire people who have UserWeb access through their current employer, but you cannot reach them on the platform itself. DM via LinkedIn, GitHub for the open-source HL7 crowd, and warm intros via Epic alumni are the realistic channels.
Is it worth sponsoring Epic certification for a hire who does not have it yet?
Generally no, because Epic certifications are gated to employer-sponsored candidates and the sponsorship route for non-hospital companies is narrow and expensive ($500 to $10,000 per cert, and that assumes Epic approves the sponsoring relationship). For RCM startup engineering hiring, the better motion is poaching someone who is already certified, and pairing them with strong generalist engineers who handle the non-Epic surface area (FHIR, RPA, clearinghouse integration, billing pipelines).
What is the single highest-signal phrase to search for on a resume?
"Cloverleaf and Epic Bridges" together, or any combination of two interface engines plus one clearinghouse name (Change Healthcare, Availity, Waystar). Dual-engine fluency is rare and almost always indicates someone who has lived through a hospital migration, which means they have shipped real integrations under deadline pressure. Pair that with FHIR experience on a recent EMR (Athena, ModMed, eCW) and you have the exact profile the June HN thread was asking for.