Polypharmacy reasoned about — inside RxCanvas, on top of the real check.
Clinical · Full PHI · Every specialtyShips inside RxCanvas rather than as an app of its own: it is the AI layer above the deterministic drug-interaction table, and it has no users, no permission of its own and no register the prescribing screen does not already hold. The whole medication list is reasoned about — duplications, cascades and dose problems a pair-by-pair table cannot see — grounded on the interaction rows the hospital’s own licensed dataset produced and on nothing else, with the gateway refusing the call outright if that grounding is absent. What comes back is prose a prescriber reads beside those rows, not a finding: the deterministic list is what the screen shows first and what it still shows when AI is off, unconfigured or over budget — and it says which of the two it is showing.
It does not replace the deterministic check and it cannot run without it: the check’s own rows are the grounding, and a high-risk gateway call with no grounding is refused. It does not decide anything — the output is a proposal a named person accepts, which is what the high risk tier means, and the deterministic findings are shown whether it answers or not. It is not a tile — it opens on the prescribing screen.
Every app page carries this section. A listing with only benefits is an advertisement.InteractIQ reads medication lists, the deterministic interaction findings and writes a reviewed proposal a prescriber accepts or ignores. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
It does not replace the deterministic check and it cannot run without it: the check’s own rows are the grounding, and a high-risk gateway call with no grounding is refused. It does not decide anything — the output is a proposal a named person accepts, which is what the high risk tier means, and the deterministic findings are shown whether it answers or not. It is not a tile — it opens on the prescribing screen.
Every record stays; only the workflow leaves.
InteractIQ is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.