SAS and Posit Partner on Governed AI for Clinical Research
SAS and Posit PBC have partnered to connect SAS Viya and SAS Clinical Acceleration with Posit's open-source development tools, starting with clinical development. The deal lets programmers write SAS and R code in one environment while Viya runs the SAS work under audited permissions.
Clinical research runs on two cultures that don't share tools: regulated SAS shops and open-source R teams. This partnership doesn't merge the cultures. It builds one audited room where both can work, and that's the part regulators will actually test.
SAS and Posit PBC announced a partnership on Monday, November 16, that integrates SAS Viya and SAS Clinical Acceleration with Posit's development tools, giving life sciences organizations a way to run SAS and open-source work inside one governed environment. The initial focus is clinical development, the most heavily regulated corner of the industry.
The integration covers four Posit products: Posit Workbench, Positron, Posit Connect and Posit Package Manager. Posit, formerly known as RStudio, builds the open-source tools that R and Python programmers use to write and share analyses. SAS Clinical Acceleration, built on the Viya platform, is the system drug companies use to manage clinical trial data and the analyses that go to regulators.
The mechanics matter more than the announcement language. A programmer can write SAS and R code inside Positron, Posit's development environment, while Viya executes the SAS code under that programmer's own permissions. SAS contributes the analytics engine, the access controls and the audit trail. Posit supplies the workspace where mixed-language teams already live. Neither side is asking the other side's users to move.
That's a real concession from both directions. Clinical research has run for decades on a split: SAS as the regulated system of record, R as the open-source tool statisticians reach for when SAS can't do what they need. Work that crosses the split usually crosses it by hand, with exports, re-checks and documentation gaps that auditors find later. A shared, permissioned execution path is an attempt to close those gaps at the tool level instead of the paperwork level.
The timing is deliberate. Both companies are showing the integration at PHUSE EU Connect in Glasgow, running November 15 to 18, where the clinical data standards community gathers. Eric Pite, Posit's senior vice president of product and strategy, said the two companies are still working with joint customers to decide which clinical workflows to support next, which means the launch scope is the integration itself, not a finished product line.
What to watch is adoption at the regulated end. Pharma's validation teams, not its programmers, decide whether a combined SAS and open-source environment can produce submission-grade work. If the audit trail holds up under that scrutiny, the partnership removes one of the oldest friction points in clinical data work. If it doesn't, it's a nicer front door on the same split shop.
There's also a labor fact under the tooling. Clinical programming teams increasingly hire people who learned R first and SAS second, or never learned SAS at all, while the regulatory record still runs through SAS-based systems. Sponsors have been bridging that gap with one-off conversions for years. An environment where both languages execute under one set of permissions lets a mixed team stay mixed, instead of forcing every analysis through a single-language bottleneck.
Neither company disclosed financial terms, and the announcement doesn't promise dates for the follow-on workflows Pite described. The integration as announced is the deliverable: Viya and Clinical Acceleration on one side, Workbench, Positron, Connect and Package Manager on the other, meeting in the clinical development workflow first.
Sources
The conversation.
Loading comments…
A little more perspective.
Reading is free. Verified members can comment and reply for $2 a month.