EHR vendor roadmap transparency tracker for health IT buyers

A health system's IT director is trying to decide whether to push for a configuration fix, wait for a promised feature, or escalate to the vendor — and they have no reliable way to know what the vendor is actually working on or when. Users explicitly call out that 'the company as a whole is not transparent with what services they are working on or how they plan to implement them,' and that 'hard coding prevents ability to create efficiency and lack of clarity around rollout timelines' compounds the frustration because nobody knows if relief is coming.

This gap exists because EHR vendors have every incentive to be vague about roadmaps. Specificity creates accountability. If they commit to a feature date and miss it, clients escalate or use it in contract renegotiations. So vendors keep roadmap communications deliberately fuzzy — high-level themes, no dates, no scope. The buyer (health system leadership) often accepts this because they're not the ones living with the day-to-day pain. The users who are suffering don't have a channel to aggregate their frustration into something the vendor has to respond to.

What's missing is a structured way for health IT staff across organizations running the same EHR to pool what they know — vendor communications, release notes, support ticket responses, conference announcements — into a consolidated, timestamped picture of what each vendor has promised versus what has shipped. This isn't a rumor board; it's evidentiary, sourced from real documents that individual organizations already receive but never compare.

Health systems use this kind of intelligence during contract renewals, upgrade decisions, and when evaluating whether to invest in workarounds or wait for native fixes. The need recurs every budget cycle and every time a vendor announces a 'new initiative' with no timeline.

What to build

Build a collaborative tracker where health IT staff upload and tag vendor communications (release notes, roadmap PDFs, support responses), and the system normalizes them into a per-vendor, per-feature timeline showing what was promised, when, and what actually shipped — with community annotations from other health systems running the same EHR.

Where to start

Launch as a closed, invitation-only group for health IT directors running one specific EHR (Altera/Sunrise is a good candidate given the complaint volume) through an existing peer network like a HIMSS chapter or regional health system consortium, where trust already exists.

The hard part

Getting the first cohort of organizations to contribute documents requires trust and clear data governance — health IT teams are cautious about sharing anything that looks like internal vendor communications, so the first version needs a credible answer to 'can the vendor see this and retaliate against us?'

How it makes money

Annual subscription per organization; free read-only access for contributors to create the contribution incentive, paid access for full historical data and export.