
What the SR 2026 Delay Actually Means for Your ISO 20022 Roadmap
Swift’s SR 2026 delay changes the ISO 20022 roadmap. Learn what banks need to do now on structured addresses, compliance, data quality and migration.
From the fringes to the mainstream, Medical Affairs is evolving. No longer confined as an afterthought and for the post-launch activities for regulatory and compliance requirements, Medical Affairs is increasingly sitting at the heart of pharmaceutical strategy.
At the recently concluded Reuters Pharma 2025, a lot of leaders were seen asking, “What’s next?”; The shift is not optional. It is structural.
As detailed in our whitepaper, this evolution is driven by both external market pressures and internal expectations. Medical Affairs is now expected to deliver insights that shape pipeline strategy, ensure regulatory alignment, and provide the scientific credibility that sales and marketing teams increasingly lack access to.
Let’s unpack the structural changes pushing Medical Affairs into the spotlight—and why your organization must keep up.
The term “Medical Affairs” may have originated in the 1960s, but its role today is far more pivotal. For many pharma organizations, it’s evolving into a core business function—no longer just a scientific communications team.
Key drivers of this change, as outlined in our whitepaper, include:
With clinical and commercial teams increasingly reliant on insights from the field, Medical Affairs is becoming the internal compass for both product strategy and external engagement.
The whitepaper outlines how Medical Affairs today encompasses a range of critical functions:
This is not a passive support function—it’s a network of scientific activity that underpins both pre-launch and post-launch success. Medical Affairs teams are managing educational programs, feeding insights into trial design, helping ensure payer alignment, and tracking product performance across markets.
According to the whitepaper, there is a significant realignment of power within pharma organizations. Previously siloed, Medical Affairs teams are now:
As a result, the function is earning not just a seat at the table, but a leadership voice—particularly in go/no-go decisions, label expansion discussions, and lifecycle management.
The question for pharma leaders isn’t “should we strengthen our Medical Affairs team?”
It’s:
“Have we equipped Medical Affairs to lead, not just support, our strategy?”
Because the teams that are still viewing Medical Affairs as reactive or compliance-oriented will miss the bigger opportunity—to embed them as a source of foresight, not just insight.
That means enabling them with:
From being relegated to post-launch support, Medical Affairs is now expected to influence every stage of the product lifecycle—from early clinical development to formulary access, from real-world insights to physician education. It’s a role shift that isn’t just semantic—it’s structural.
But is your organization structurally prepared?
Our whitepaper, “How Medical Affairs is Driving Pharmaceutical Companies’ Decision Making & AI/ML’s Role in Enhancing the Medical Affairs’ Contribution,” is designed to provide leadership teams with a clear, accessible, and actionable roadmap.
✅ Detailed breakdown of MA functions
✅ Strategic alignment with AI/ML tools
✅ Functional challenges & future-proofing tips
✅ Designed for internal business cases

Swift’s SR 2026 delay changes the ISO 20022 roadmap. Learn what banks need to do now on structured addresses, compliance, data quality and migration.

Code generation got fast. Getting an autonomous workflow into a bank’s production control environment did not. In Banking & Financial Services (BFS), the blocker is rarely the model; it’s trust. A risk officer will not sign off on a system that cannot say why it flagged something, that does its arithmetic inside a language model, or that leaves no audit trail an examiner can open. That is exactly the gap most agentic pilots die in.
Over the last two quarters, we built a portfolio of ten BFS agentic offerings on Alti AIOS™, Altimetrik’s AI Operating System, and deployed them on two stacks: Google Cloud with Gemini and AWS with OpenAI. This piece is the architecture and design principle behind them.

Most organizations can tell you what CVEs they found last quarter. Few can tell you which packages will become a problem next month or which AI skills are running in production without a certified identity. This piece is about closing that gap.
USA (Southfield) - HQ
2000 Town Center, Suite 170
Southfield, MI 48075
+1 248-281-2500