Synthetic sandbox. Real SMART authorization, synthetic patient data, simulated payer & review.

Prior Authorization — SMART launch

Launch with SMART on FHIR to establish an authorized patient context, then run a configuration-driven prior-authorization workflow: the payer's rules select the requirement and questionnaire, you complete and submit the documentation, and you follow its status and history.

Launch with SMART
What happens:
  1. You pick a synthetic patient at the SMART Health IT sandbox and authorize access.
  2. Redix retrieves the authorized patient (server-side) and starts a workflow session bound to it.
  3. You select a payer & procedure; the configuration decides what documentation is required.
  4. You submit to the Redix demo reviewer queue and see its status and history. Reviewer actions (requesting more information, recording a decision) are shown in guided walkthroughs with Redix; they are not performed automatically for public visitors.

The payer decision is simulated. Nothing is sent to a live payer or to QNXT. Do not enter real PHI.

What this shows: a real SMART on FHIR user launch against a public test EHR (not SMART Backend Services), and Redix’s configuration-driven workflow API (not Da Vinci PAS transport).