# DenQAI: seller transfer evidence request

File-specific companion · 2026-09-10

## Purpose

What aggregate evidence is needed to support each seller-to-buyer transfer bridge?

**Who:** Buyer’s clinical and financial diligence reviewers

**Records:** Provider/procedure/cohort aggregates; schedules; payer and staffing records; documented transition duties; reconciliation controls.

## Complete the file

1. Use bridge_or_gate to associate each request with the specific transfer assumption.
2. Request the stated aggregate record and period from source_system within privacy_boundary.
3. Verify reconciliation, reviewer_role, material_gap, and pause_reprice_or_walk_condition before marking the request resolved.

## Definitions

- **Transfer bridge:** Reconciliation showing which historical activity can support the buyer’s model.
- **Aggregate record:** Summary without the patient-level detail prohibited by the public workflow.
- **Reconciliation:** Check that summarized values agree with relevant source and control records.

## Fictional example

Fictional example: TR-PROVIDER-01 asks for clinical days and collections by coded provider; the buyer reconciles totals before assuming the seller’s workload can transfer.

## Review and next action

Request the evidence for the largest buyer-dependent collection or capacity assumption.

A fulfilled request is not proof of transferability. Contract, clinical, staffing, and payer assumptions require their own appropriate review.

[Related DenQAI guide](https://denqai.com/acquisition/clinical-transfer)

## AI coach prompt

Help me use DenQAI’s seller transfer evidence request. My question is: What aggregate evidence is needed to support each seller-to-buyer transfer bridge? Explain these terms in plain language: Transfer bridge, Aggregate record, Reconciliation. Ask one question at a time about the required records: Provider/procedure/cohort aggregates; schedules; payer and staffing records; documented transition duties; reconciliation controls. Walk through the supplied fictional example before asking me for inputs. Treat every missing value as unknown, not zero. Do not invent source records, contract terms, legal conclusions, or clinical facts. Use only permitted fictional or aggregate, non-identifying information. Follow this boundary: A fulfilled request is not proof of transferability. Contract, clinical, staffing, and payer assumptions require their own appropriate review. End with the missing evidence and this next step: Request the evidence for the largest buyer-dependent collection or capacity assumption.

## AI review prompt

Review my permitted fictional or aggregate draft of DenQAI’s seller transfer evidence request against the file instructions. Check each required field and period, units, evidence locator, assumptions, arithmetic where formulas are actually supplied, and unresolved contradictions. Check the sequence: Use bridge_or_gate to associate each request with the specific transfer assumption. Request the stated aggregate record and period from source_system within privacy_boundary. Verify reconciliation, reviewer_role, material_gap, and pause_reprice_or_walk_condition before marking the request resolved. Separate facts from assumptions and missing records. Do not supply unsupported numbers or make a professional decision for me. Apply this limitation: A fulfilled request is not proof of transferability. Contract, clinical, staffing, and payer assumptions require their own appropriate review. Return corrections, questions for the responsible reviewer, and the next action.