Flamingo: built to make the imaging systems you already run work together
Your imaging systems were added over years, each for a good reason. Flamingo is built to sit above the PACS and archives you already run, so you can keep what works and replace what you've outgrown, one at a time. See it demonstrated at RSNA 2026.
Where Flamingo fits
You don't have to start over
Flamingo is built to work alongside the systems you already run, and its modules don't require a Mach7 archive.
No rip and replace required. You decide what changes, and when.
Flamingo isn't for sale yet. This page describes its first release as designed, and you can see it demonstrated at RSNA 2026.
What's new?
Designed for the first release: your team sets a turnaround target for each priority level, and each study shows how much time it has left.
What's underneath?
A modern core, built to run in containers, on PostgreSQL or SQL Server, and on Windows or Linux.
What about AI?
Your imaging, ready for AI. Mach7 integrates with third-party AI solutions, so their results are available within your imaging workflow.
How it fits together
Five modules, one foundation
Think of Foundation as the ground floor. Worklists, Flow and Storage are built on top of it, Sonar shows how it's all running, and they're designed to sit alongside the Mach7 products you may already have.
Flamingo modules
Operations
Sonar
A monitoring dashboard that shows IT teams how the imaging platform is performing and where attention is needed
Applications
Worklists
Turnaround targets, countdowns and early alerts
Archive access
Flow
Archive Browser: find a study, then act on it
Data and storage
Storage
Your servers, the cloud, or both
Platform
Foundation
Who your people are, what they're allowed to do, and how it's all set up
Runs on
PostgreSQL or SQL ServerWindows or LinuxOn premisesMicrosoft AzureAWSOracle Cloud Infrastructure
Connects to
eUnity
Enterprise diagnostic viewer
VNA
Vendor-neutral archive
Standard interfaces
DICOM · DICOMweb · HL7
Shown for context. Flamingo is built to work alongside these products.
The modules
What each module is built to do for you
Here's what's in the first release of Foundation, Storage, Worklists and Flow, as designed.
Foundation, Storage, Worklists and Flow are functional descriptions. Final product naming will be confirmed later.
Platform
Foundation
Everything around the images: your people, what they're allowed to do, and how the system is set up.
- Your database, your choice. It is built to run on SQL Server or PostgreSQL, on Windows or Linux.
- Your data center or the cloud. It is built to run on premises or in the cloud.
- Sign-in options. Your staff can sign in with Active Directory, or with single sign-on through Microsoft Entra.
- Read-only when you want it. Permission to view is separate from permission to make changes.
- Sign-ins and settings changes, on record. Sign-ins and configuration changes are recorded.
Why it matters: Flamingo is built to run on the databases, operating systems and sign-in services your IT team may already use.
Data and storage
Storage
Your images are stored in standard formats, so they stay yours.
- No proprietary format. Images are stored in standard formats, with no proprietary format of our own.
- Keep them where you choose. Keep them on your own servers, in Amazon S3 or AWS HealthImaging, in Oracle Cloud Infrastructure or Microsoft Azure storage, or in a mix.
- Room to grow. Add storage locations after deployment.
- Built for very large files. It is built to stream image files of 4 GB and up instead of holding them in memory.
- Less room on disk. A modern compression standard, High-Throughput JPEG 2000, helps images take up less room.
Why it matters: Your images aren't locked in a format of our own, so what happens to them next stays your choice.
Applications
Worklists
See which studies are coming due, early.
- Your priorities, your targets. Your team sets the priority levels and a turnaround target for each.
- A clock on each study. Each study shows how much time it has left.
- Early alerts. Studies getting close to their target are flagged early, without changing the priority you set.
- A detailed audit trail. Configuration changes, actions taken on each study, and study views are recorded.
Why it matters: Studies nearing their targets are flagged at a lead time your team chooses, so the pressure shows before a target passes.
Worklists orders studies by the priorities and rules your team sets. Mach7 does not analyze images or clinical content to rank studies.
Archive access
Flow
Find a study across the whole archive, then act on it right there.
- Search that goes deep. You can search the whole archive on more than 20 study fields.
- Open it your way. You can open a study in the viewer you prefer.
- Move it where it belongs. Copy or move it to other storage, or send it to another DICOM system.
- Check the study's details. View its DICOM header, the descriptive information stored inside each image file.
Why it matters: The Archive Browser is where you find a study and act on it.
Operations
Sonar
A monitoring dashboard that shows IT teams how the imaging platform is performing and where attention is needed.
Lighter to run
Lighter on your servers
40 to 50 percent
better web performance than our current VNA in our own testing. It handled more requests per second and responded faster.
About 100 MB
Flamingo's memory footprint in Linux containers. A Windows-based VNA server uses about 3 to 4 GB.
Mach7 internal testing comparing Flamingo with the current Mach7 VNA on identical hardware, using synthetic test data.
Related Resources
View all resources
Imaging Without Boundaries
A PACS alone does not solve enterprise imaging. Eight patterns most health systems will recognize, and what a connected imaging foundation adds beneath them.
Adopting an Enterprise Strategy: Considerations Beyond Radiology
Imaging is an enterprise decision. Six considerations beyond radiology for consolidating, securing and sharing imaging data across the enterprise.
Mach7 Enterprise Imaging Solution
The Mach7 Enterprise Imaging Solution guide: one vendor-neutral imaging layer for storage, access and zero-footprint viewing across the enterprise.
Frequently Asked Questions
-
What is Flamingo?
Flamingo is software built to sit above the PACS, archives and AI tools you already have and connect them. It's how Mach7 is moving enterprise imaging from archive to architecture: one index of record across your systems, and worklists that span them. That's different from IT data architecture, such as data warehouses.
-
How does Flamingo work with your existing PACS and VNA?
It's built to run alongside them. Keep the systems that work, connect them, and replace the ones you've outgrown when you're ready, one at a time. A new site can be added using infrastructure you already have, where it meets platform requirements.
-
What AI vendors does Flamingo support?
Mach7 integrates with third-party AI solutions, so their results are available within your imaging workflow.
-
Is Flamingo cloud-only or can it run on-prem?
It can run either way, or both. Flamingo is built to run on Windows or Linux, in containers, in your own data center or on Amazon Web Services, Microsoft Azure or Oracle Cloud Infrastructure, and your storage can mix your own servers with the cloud.
-
How does pricing work?
Flamingo uses flexible licensing that maps to how you actually work. Tell us about your environment and we'll shape a model that fits.
Ready to Unify Your Imaging Data?
Transform your imaging experience today with Mach7.
Request a Demo

