# DenQAI: purchasing data use portability

File-specific companion · 2026-09-10

## Purpose

What data would a hypothetical purchasing service need, and can a member inspect, export, or delete it?

**Who:** Product or purchasing design lead and privacy/security reviewers

**Records:** Field inventory; intended uses; access roles; vendor list; retention, deletion, export, and incident design.

## Complete the file

1. Apply Minimum necessary intake to each proposed field and remove unrelated information.
2. Map Purpose and access plus Security and operations to accountable roles and actual systems.
3. Test the Member control and portability actions and record unmet Launch boundary items.

## Definitions

- **Data minimization:** Collecting only the fields required for the defined comparison.
- **Least privilege:** Giving each role only the access required for its task.
- **Portability:** Exporting permitted records in a usable documented format.

## Fictional example

Fictional example: A proposed annual package-count field is needed for comparison; a patient-name field has no purchasing purpose and is excluded.

## Review and next action

Close data-map and portability gaps before any new intake opens.

These are hypothetical rules, not an implemented privacy program, security certification, or data-processing agreement.

[Related DenQAI guide](https://denqai.com/independent/governance)

## AI coach prompt

Help me use DenQAI’s purchasing data use portability. My question is: What data would a hypothetical purchasing service need, and can a member inspect, export, or delete it? Explain these terms in plain language: Data minimization, Least privilege, Portability. Ask one question at a time about the required records: Field inventory; intended uses; access roles; vendor list; retention, deletion, export, and incident design. 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: These are hypothetical rules, not an implemented privacy program, security certification, or data-processing agreement. End with the missing evidence and this next step: Close data-map and portability gaps before any new intake opens.

## AI review prompt

Review my permitted fictional or aggregate draft of DenQAI’s purchasing data use portability 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: Apply Minimum necessary intake to each proposed field and remove unrelated information. Map Purpose and access plus Security and operations to accountable roles and actual systems. Test the Member control and portability actions and record unmet Launch boundary items. Separate facts from assumptions and missing records. Do not supply unsupported numbers or make a professional decision for me. Apply this limitation: These are hypothetical rules, not an implemented privacy program, security certification, or data-processing agreement. Return corrections, questions for the responsible reviewer, and the next action.