Retroact Connect

Who this is for

Vendors of pharmacy management, dispensing and clinical software. Pharmacies themselves are addressed at the foot of this page.

No agreement with Praxio is required to build this, and no notice of starting is expected.

What the users get

A pharmacist working in the vendor software clicks 1 button and lands on that patient’s anticoagulation record, already signed in under their own name. No second sign-in, no retyping a health insurance number, no second window to keep in step with the first.

What is built

1. The vendor server signs a short-lived token with its own private key.
2. Retroact is opened with it, from wherever the button lives.
3. Retroact verifies the signature, confirms the pharmacy enabled the vendor, finds the patient and signs the pharmacist in.

The token is valid for minutes and can be used once. That is the whole client side.

import { createConnectClient } from '@retroact/connect'

const retroact = createConnectClient({
  clientId: 'pms-acme',
  privateKey: process.env.RETROACT_PRIVATE_KEY
})

// On your "Open in Retroact" button:
const url = retroact.createLaunchUrl({
  org: pharmacy.storeNumber,
  practitioner: { email: pharmacist.email },
  patient: {
    healthInsuranceNumber: patient.healthCardNumber,
    birthDate: patient.dateOfBirth
  }
})

With the helper supplied on request. Optional — the token is a standard RS256 JWT, so any language that can sign one needs no library at all.

What it costs

• About a day, including testing.
• No fee, no revenue share, no certification to pass.
• No contract to sign before building starts.
• No dependency to adopt: the helper is optional and has none of its own.

What the commitment is

• A version. The launch contract is versioned, and a breaking change means a new version served alongside the old one, not a flag day.
• Nothing exclusive. Build ours, build others, build none — there is no clause here because there is no agreement.
• No support burden from Praxio. Praxio answers to the pharmacy for Retroact, and to the vendor for the protocol.
• It can be stopped. Removing the button is the whole rollback, and nothing in the vendor product depends on Praxio afterwards.

What Retroact does not do

• It does not dispense, bill, or hold a prescription record. It is not trying to become the system the customer already bought.
• It never writes into the vendor software. The connection runs one way.
• Nothing is shared until the pharmacy switches the integration on itself, from its own settings.
• Praxio holds the public key only, so it cannot sign anything on the vendor’s behalf, and no pharmacy that has not enabled the vendor can be reached.

Reading data back

A read-only FHIR R4 endpoint returns what a pharmacy recorded, so it can appear in the vendor’s own chart rather than only in Retroact.

• Patient
• INR results, coded with LOINC 6301-6
• Recorded doses

Doses are published as a record of what was taken, never as an order. Retroact documents the dosing a pharmacist decided under their own written protocol; it does not recommend one, and the data received must not be presented as though it had.

Starting

Send a public key and the origins launches will come from. A client id and a test environment are returned. Everything to read first is already public:

• Discovery document — /.well-known/retroact-connect
• Public keys — /.well-known/jwks.json
• Authorization server metadata — /.well-known/oauth-authorization-server