Months of work, live for four hours, seen by whoever happened to walk past. The video is step one. The real move: every panel opens into its own branch, so each delegate enters at their question, through the 90 days after congress when the real reading happens.
A delegate scans the code and enters at the panel they came for, in their own time. Tap a panel on the poster and see what opens behind it.
Why the study exists, told for the delegate who is new to this space. The one who already knows skips straight past it, and loses nothing.
You just did what a delegate does with the QR code. Their panel first, their depth, their moment, on the flight home or three weeks later. The poster stops being four hours in a hall and becomes the 90 days after it.
The physician who wanted to stop and read was three sessions behind schedule. A video waits for them. It travels in the follow-up email, plays on the flight home, and answers the question they did not have time to ask.
The same poster reel reaches two delegates after the session. Tap one and watch their route change. The quick tour and the methods read never cross paths, and it is all one MLR review.

60+ studies, side by side: why your best science never reaches the physicians it was written for, and what the evidence says actually works instead.
Get the free report →Turning the poster into a video is step one. These are the layers that turn the scan into a relationship.
The lead after the scanThe board reached one hallway. Smart Pathways decides what happens after the scan: the trialist lands on the endpoint, the clinician lands on patient fit, the skeptic lands on methods. Every route recombines the same approved modules from your poster, so no delegate sits through another delegate’s part, and one MLR review covers every journey. Your follow-up stops being one PDF sent to every badge.
See PubVisual Smart Pathways →
A poster ends at the board. With smart nuggets inside the story, the delegate who reaches the endpoint can request the full paper, ask your team a question, or book time with an MSL, right where their interest peaked, weeks after the hall closed.
See PubVisual Engage →
The poster travels further when a respected expert explains it. PubVisual KOL builds their recorded commentary into the story itself, one tap from the data, so the delegate hears the findings from a peer, not a panel of small print.
See PubVisual KOL →Nothing on the poster changes on its way to video. Every scene maps to the data you presented, so it is built for MLR from the first frame and ready the moment the session ends.
“The poster came home in a tube. The video was still being watched a month later.”
Send the poster or the abstract. We will show you what opens behind each panel and the route your delegates would take. On the house. No promises. Presenting soon? Perfect, we can be ready when the session is.
No. A looping MP4 is the old answer. Here every panel opens into its own branch: the delegate enters at their question, goes as deep as they want, and can take an approved next step through a smart nugget. The video is the way in; the exploration is the product.
Yes. Bring us the poster once it clears review, and it can be ready for the session itself, so the video and the board go up together and the follow-up is set from day one.
No. Every scene maps to the data you presented. We change the format, not the findings, which is what keeps it built for MLR.
As a link the physician can open on their own time, in the follow-up email, on a congress portal, or from a rep. They explore it themselves, wherever they are.
We will not tie it to a fixed date. You approve the core the normal way, at script, storyboard, and final animation. From there, that same approved core carries every version, so new cuts and languages do not restart the scientific review. The overall pace tracks your own review, which we plan around with you from day one.
Yes. Because every scene traces to data you already presented and approved, the video is structured for MLR from the first frame and fits your existing Veeva workflow.