Launching a new version of a trusted healthcare solution is never just about adding new features. For Haystack™ iS v2, it was about taking a step back and asking a simple question: how can patient privacy monitoring work better for the people who rely on it every day?
Over the past few years, we spent a lot of time listening to customers, watching how privacy teams actually use Haystack, and gathering feedback from hospitals of all sizes. That feedback led us to make a bigger decision. Instead of continuing to build on what already existed, we chose to start fresh and build Haystack iS v2 from the ground up.
What came out of that effort is not just an update, but a more modern platform shaped by product leadership, engineering innovation, and real-world implementation experience. The story of Haystack iS v2 is best told by the people who built it.
Product Vision: Built from the Customer Back
Demi Borden, Product Owner, Haystack iS
From the beginning, the driving force behind Haystack iS v2 was customer feedback. Privacy teams told us what slowed them down, where the system created friction, and what they needed to see faster. That input shaped everything from the interface to how insights are surfaced.
“We wanted a clean slate to do a lot of this work. There were a lot of features customers had requested, especially dashboards and the ability to drill into them. Having that opportunity to rebuild was really beneficial.”
Demi describes Haystack iS v2 as a product designed for how privacy teams actually operate today. Many teams have limited time, competing priorities, and varying levels of system engagement.
“Each of our customers personalizes what they prioritize. Being able to have a favorite view so that every time they log in, it’s exactly what they want to see, that’s huge.”
One of the most meaningful additions is built-in guidance that meets users where they are.
“There are customers who only get into the system once a month. Being able to watch a quick ‘how-to’ video right when they need it is really beneficial for teams that wear a lot of hats.”
The result is a platform that feels intuitive, flexible, and immediately useful whether you are part of a full privacy team or a single compliance leader managing multiple responsibilities.
Engineering the Future: Expanding What Haystack Can Do
Ryan Smith, Director of Development, Haystack iS
From a development standpoint, Haystack iS v2 was about unlocking more value from capabilities that already existed. In v1, AI-driven analytics and automation were available, but they were offered as optional components. As a result, not every customer was benefiting from the full breadth of what Haystack could do.
With v2, that changes.
AI and automation are now built directly into the core platform. Every customer, regardless of deployment or configuration, has access to the same intelligent tools that help reduce manual work, surface risk faster, and support more efficient investigations.
“AI and automation have always been an important part of Haystack. What’s different in v2 is that they’re now included rather than optional add-ons. Everyone gets the full benefit of those capabilities right out of the box.”
Ryan also explains why rebuilding from the ground up was necessary to support that kind of experience.
“v1 was built on fairly old technology. Moving to a modern platform was a necessary jump to stay current with the market.”
The process took time, but it removed limitations that had accumulated over years of growth.
“The end product showcases the effort we put into building something that’s not only equal to v1, but better in just about every form.”
With Haystack iS v2, the platform is no longer constrained by older technology or optional feature sets. It is designed to grow alongside evolving privacy needs, regulatory expectations, and future advancements in AI and automation.
Implementation Reality: Making Privacy More Reliable
Cody Plate, Manager of Professional Services
From the professional services perspective, some of the most important improvements in Haystack iS v2 happen behind the scenes.
In v1, import feeds had to match perfectly. If a hospital’s IT team made even a small change, such as adding an extra column to a file or adjusting the format slightly, it could cause the feed to fail because everything had to match one-to-one.
That created unnecessary disruption. Privacy teams might not even realize a minor IT change had happened, yet suddenly their feed would error out.
With v2, that rigidity is gone.
“It became more robust and less error-prone. Little technical issues that used to cause problems can now be ignored or handled automatically.”
The new import process is more flexible and resilient. Minor changes in file structure no longer break the system. The platform can recognize and handle small variations without shutting down or requiring immediate intervention.
“We’re not relying on the site to have everything exactly right anymore. That makes a big difference in the long run.”
For privacy teams, that means confidence. Their monitoring continues to run, even when IT environments evolve. And in healthcare, where systems change often, that reliability matters.
For Cody, one of the most rewarding parts of the journey is simply seeing the work come together.
“Seeing it release and seeing what you’ve built actually out there and complete, that’s what I’m most excited about.”
Ready for What’s Next
Haystack iS v2 represents more than a product update. It reflects years of listening, rebuilding, and aligning the platform with how privacy teams actually work.
It’s customer-informed. It’s built from the ground up. And now, with AI and automation included for everyone, it delivers the full value of modern patient privacy monitoring to every organization that uses it.
As Demi, Ryan, and Cody all echoed in different ways, there is a shared sense of pride in finally getting Haystack iS v2 into customers’ hands.
“It’s a breath of fresh air to see it in use and hear the reactions we get.”
Haystack™ iS v2 is now available, and we are excited to see how privacy teams use it to strengthen oversight, reduce manual effort, and move confidently into the next era of patient privacy.