Edifecs makes healthcare speak the same language

The first thing to understand about Edifecs is that a computer can receive a healthcare claim perfectly and still have no useful idea what to do with it. The message arrived. The meaning did not. Somewhere between a hospital, an insurer and the systems inside each organization, somebody has to make the handoff work.

Edifecs built its business in that gap. Today it belongs to Cotiviti, which completed the acquisition in March 2025. At the time the deal was announced, Edifecs said its payer and health-system customers served nearly 300 million people in the United States. That describes the reach of its customers, rather than people logging into an Edifecs app.

01 The pipeline that vanished

There is a sheep story. Founder Gurpreet “Sunny” Singh told interviewer Sramana Mitra that an early Edifecs office occupied a converted motel, with sheep behind it. Open windows supplied ventilation and an unexpected soundtrack. He also recalled financing the young company with roughly 18 to 20 credit cards. This was enterprise software with decidedly household economics.

Founded in 1996, Edifecs initially worked on electronic data interchange, or EDI. Its SpecBuilder tool helped people document and test the information one business sent another. A purchase order and a medical claim posed a related engineering question: what does each field mean, and will the recipient accept it?

The early threat came from the business around the software. In Singh’s account, an important customer’s funding dried up, expected sales failed to materialize, and debt accumulated. The company missed payments to vendors, its landlord and employees. A pipeline that looked reassuring on paper could not pay a salary.

In 2001, the company entered healthcare as HIPAA transaction requirements created demand for its skills. Singh later described learning the industry one customer at a time. By around 2006, the work expanded from tools for defining transactions into products processing them. The company found a market where its existing expertise answered a pressing operational problem.

“We had to innovate with our backs on the wall.”Sunny Singh, speaking to Sramana Mitra, 2015

02 A translator with a day job

The modern product family makes more sense when viewed as a sequence of jobs. SpecBuilder defines and tests transaction rules. XEngine validates messages. XEngine Server supports the workflows that move them. Smart Trading combines these kinds of capabilities into a modular data-exchange suite, with transaction management for watching what happens along the way.

EDI Gateway handles established transaction formats. FHIR Gateway connects newer API-based exchange with older standards such as EDI and HL7. Consent Management handles members’ data-sharing preferences. Prior Authorization takes information arriving through channels including fax, portals and electronic transactions, then standardizes and routes it. The fax survives even inside a conversation about modern APIs.

This places Edifecs between the organizations producing information and the administrative systems acting on it. Its specialization is the combination of healthcare standards, transaction processing and operational workflows. A buyer comparing it with 1upHealth, Onyx Technology or Smile Digital Health should compare the particular exchange job, since the portfolios differ.

03 The price of a clean handoff

The economics are enterprise economics: software licenses and SaaS, supported by maintenance and professional services. A Michigan public contract offers a concrete historical example. A quote dated December 2021 listed a discounted eight-month temporary on-premise package at $250,875, including XEngine Server components and SpecBuilder. Implementation and other professional services were excluded. That is a defined historical purchase, not a current price guide.

Customers also buy the work of making systems cooperate. In September 2024, Edifecs and HealthEdge announced native integration between Edifecs’ EDI Gateway and HealthRules Payer. Their stated aim was to reduce bespoke integration, testing and maintenance. The attraction is easy to understand: every custom connection creates something a team must keep working.

Support deserves equal attention. KLAS’s 2025 interoperability report said Edifecs clients included it in their future plans but wanted more consistent support. In 2026, Edifecs won Best in KLAS for CMS Payer Interoperability. Those are dated signals, not proof that every concern disappeared. Buyers still need named responsibilities, escalation paths and a realistic implementation plan.

For a buyer, that suggests a practical way to evaluate the software: choose an awkward transaction and follow it all the way through. Who supplies the data? Which rule catches an error? Where does a rejected message go? Who can explain the result? A polished demonstration of an ideal message answers only part of the question. The operational value depends on what happens when a field is missing, a partner changes its specification, or an exception needs a human decision. That is where a healthcare integration purchase becomes a test of the organization buying it, too.

04 Follow the claim, then the money

TA Associates and Francisco Partners announced a growth investment in 2020, with financial terms undisclosed. Cotiviti’s acquisition followed five years later. The strategic logic connects the two companies’ work: Edifecs moves and prepares healthcare data; Cotiviti applies analytics to areas including payment accuracy, quality and risk adjustment.

Edifecs also works on the machinery of value-based payment. Population Payment Management handles contracts, populations, payment streams and settlements. Its September 2025 update introduced AI agents, including a conversational analyst called Virtual Jonathan. The pitch is that teams can question contract and performance data without building every answer in SQL. It is a product capability announcement, rather than independent evidence of savings.

The useful lesson is specific: start with a recurring handoff, learn the recipient’s rules, and prevent errors before they become somebody else’s queue. That approach needs willing trading partners, workable data and people responsible for exceptions. Better translation cannot settle a disputed contract or create missing clinical information. Edifecs’s opportunity lives in the considerable amount of work that remains once those conditions are met.