PreRelay™

One prescription.One authorization.One chain of custody.

Demo-ready prior-auth coordination on synthetic data: one Case ID, one custody trail, and simulated payer statuses — integration-ready for provider, pharmacy, payer, FHIR, and clearinghouse configuration.

Demo environment — synthetic patient data. Simulated payer responses only. Integration-ready; payer connectivity requires customer or partner configuration.

Platform

Integration and coordination — not another system of record

PreRelay™ is the coordination layer between EHR, pharmacy, PBM, and payer systems. It does not replace those systems. It creates one authoritative prior-authorization case, one evidence package, and one chain of custody that every party can trust.

PreRelay currently demonstrates the complete prior-authorization workflow using synthetic patient and case data. The integration layer is designed to connect with provider, pharmacy, payer, PBM, FHIR, and clearinghouse systems. Production connectivity will be configured and validated with each participating organization.

The problem

Fragmented systems create competing truths

Providers, pharmacies, PBMs, and payers maintain separate records of the same authorization — and nobody can point to the authoritative case when a patient needs medication.

Today

  • Doctor says the PA was submitted
  • Insurance says it was never received
  • Pharmacy keeps getting rejections
  • Duplicate PA requests pile up
  • Dose history is split across parties
  • No one owns the next action

With PreRelay™

  • One Case ID for the authorization
  • One authoritative state machine
  • One evidence package with provenance
  • One audit history of every handoff
  • One medication continuity timeline
  • Explicit responsibility when blocked

Workflow

How It Works

Eight deterministic steps from prescription intake to ready to dispense — AI may assist with extraction and drafting; it never approves, denies, or attests.

  1. 01

    Prescription intake

    New Rx signals enter through the integration layer (mock adapters in the demo environment).

  2. 02

    Coverage & PA detection

    Coverage checks surface when prior authorization is required before dispense.

  3. 03

    Dose-escalation awareness

    Medication continuity detects escalation (e.g. 7.5 mg → 10 mg) and gathers lower-dose history.

  4. 04

    One Case ID

    A single authoritative PA case is created — duplicate requests attach to the same record.

  5. 05

    Evidence packaging

    Required clinical and continuity evidence is versioned with provenance.

  6. 06

    Clear responsibility

    The case is blocked with an explicit waiting-on party and required action — not a vague “pending.”

  7. 07

    Attest & simulate submit

    Providers attest continuity; submission uses simulated payer responses in the demo (not a live network call).

  8. 08

    Approve → ready to dispense

    Simulated payer decision, pharmacy adjudication, and dispense close on the same chain of custody.

Medication continuity

Dose escalation, fully visible

Demo scenario: TEST PATIENT 001 on Mounjaro — verified 2.5 / 5 / 7.5 mg dispensed, new 10 mg Rx requiring prior authorization and continuity evidence.

Medication
Mounjaro
Patient: TEST PATIENT 001
2.5
2.5 mg
DISPENSED

Verified dispensed

5
5 mg
DISPENSED

Verified dispensed

7.5
7.5 mg
DISPENSED

Verified dispensed

10
10 mg
REQUESTED

New Rx — PA required

Chain of custody

Sample case PA-2026-000009824

Every handoff attaches to one Case ID — from prescription received through provider attestation request.

  1. 09:04Prescription received
    Demo Specialty Pharmacy
  2. 09:05Coverage checked
    Demo PBM
  3. 09:05Prior authorization required
    System
  4. 09:06PA-2026-000009824 created
    PreRelay™
  5. 09:08Clinical requirements identified
    Requirements engine
  6. 09:13Previous dosage evidence retrieved
    Continuity engine
  7. 09:25Provider documentation requested
    Responsibility engine
  8. —Awaiting provider attestation
    Demo Endocrinology Clinic

Responsibility

Never just “pending”

Ambiguous status hides ownership. PreRelay™ surfaces who must act, why the case is blocked, and what action is required.

Bad

Prior Authorization Pending

No owner. No reason. No next step. Every party assumes someone else is working it.

Good

STATUS: BLOCKED

Waiting on:
Provider
Reason:
Previous dosage documentation required
Required action:
Complete medication-continuity attestation

Who it serves

Built for every party in the PA chain

Providers

See what is blocked, what evidence is missing, and attest dosage continuity against a verified medication timeline.

Learn more

Pharmacies

Know whether an authorization already exists before opening another. Track adjudication and ready-to-dispense on the same case.

Learn more

Payers

Receive complete, versioned evidence packages with provenance — including prior dose history for escalation therapies.

Learn more

Architecture

Integration-ready — not live by default

Today’s demo uses mock adapters, an NCPDP stub, and simulated payer responses. Live EHR, pharmacy, and payer connectivity requires customer or partner configuration and validation — we do not claim those connections are operational until they are.

  • Mock adapters (EHR / pharmacy / payer)Demo
  • NCPDP SCRIPT connector stubDemo
  • RAG policy decision supportDemo
  • EHR / FHIR · live payer · pharmacy networksIntegration-ready

Security

Trustworthy by design

Designed with HIPAA-aligned security requirements in mind. Multi-tenant isolation, auditability, and least-privilege access are first-class product constraints — not afterthoughts. Architecture targets Microsoft Azure Container Apps hosting.

This release does not claim HIPAA Certified or HIPAA Compliant status. Controls are defined for future attestation and compliance programs.

Company

About PreRelay™

PreRelay™ is a healthcare coordination platform from Full Digital Consulting Systems (FDCS). It is not a replacement for EHR, pharmacy management, PBM, or payer systems — it is the integration, workflow, attestation, and coordination layer between them.

Request a demo

Prefer a guided walkthrough? We demonstrate the full prior-authorization workflow on synthetic patient data — Case ID, custody, attestation, simulated payer responses, RAG policy retrieval, and the future API/FHIR architecture. Live payer or EHR connectivity is configured per organization.

Demo environment — synthetic patient data. Free trial creates your own organization in the operator portal.