Technology.

Access.

State 02

The access state.

Where evidence becomes infrastructure. We understand the science behind the tools we build, which is the part most software teams are missing.

The access state, where evidence becomes infrastructure.

RJC Technology, the access state

01 / What we build

A model that lives in a spreadsheet reaches the people who already believe you. A model that opens in a meeting reaches the people who decide.

02 / The build

01 Model digitisation

Validated Excel cost-effectiveness and budget impact models ported to applications a payer can use in the room.

02 e-GVDs

The global value dossier as a navigable application, every claim linked to its source, one update propagating everywhere.

03 Interactive payer tools

Budget impact calculators and value communication tools built for a meeting, not for a download folder.

04 HEOR data platforms

Where the evidence base, the extractions and the model inputs live in one place instead of across forty spreadsheets.

05 Full-stack health applications

When the tool is the product rather than the sales aid.

A development shop can build the calculator. It cannot catch the half-cycle correction you left out.

03 / Why the science matters

What a generalist team cannot notice is that the discount rate is applied to the wrong arm, or that a Markov trace stops summing to one after year eight. Those are the errors that survive user acceptance testing and then surface in front of a payer.

We work the other way round: the health economics comes first and the interface serves it. A digitised model is verified against the validated source across the full scenario set before anyone looks at a screen.

04 / Common questions

What is an e-GVD?

An electronic global value dossier is the value dossier delivered as a navigable, permission-controlled application instead of a several-hundred-page document. Country teams pull the sections and figures they need, every claim stays linked to its source, and one update propagates everywhere instead of forking into fifteen local versions.

Can you digitise an existing Excel cost-effectiveness model?

Yes. The usual route keeps the validated Excel model as the reference implementation, ports the engine, then verifies the port reproduces the original results exactly across the full scenario set before anyone sees an interface. The Excel file remains the thing that was validated.

Who owns the code you write?

You do. We hand over the repository and the deployment. Nothing important stays locked inside our systems, which is the same principle as the rest of how we work.

Evidence a payer can open.

Onboard within 48 hours.

Book a call