# DenQAI: owner case data dictionary

File-specific companion · 2026-09-10

## Purpose

What is each owner-case field allowed to contain, and how may it be used?

**Who:** Case-draft preparer, research data owner, and privacy reviewer

**Records:** Current protocol and schema; data dictionary; permitted coded example; public-release rules.

## Complete the file

1. Locate each field_name by record_type before preparing a case draft.
2. Follow definition, allowed_values_or_format, and source_rule without inventing missing information.
3. Review required_for_local_export, sensitivity, and public_release_default as separate conditions.

## Definitions

- **Allowed values or format:** Specified vocabulary or structure for a field.
- **Public release default:** Starting release treatment that still requires the stated review.
- **Source rule:** Permitted evidence or origin for the field’s value.

## Fictional example

Fictional example: case_id is CASE-27 rather than an owner’s initials or practice abbreviation; the field still receives the required re-identification review.

## Review and next action

Resolve an undefined or sensitive field before adding it to an analytic or public file.

The data dictionary is a schema reference, not approval to collect, publish, or enroll a case. Removing names alone does not establish de-identification.

[Related DenQAI guide](https://denqai.com/research/case-series)

## AI coach prompt

Help me use DenQAI’s owner case data dictionary. My question is: What is each owner-case field allowed to contain, and how may it be used? Explain these terms in plain language: Allowed values or format, Public release default, Source rule. Ask one question at a time about the required records: Current protocol and schema; data dictionary; permitted coded example; public-release rules. 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: The data dictionary is a schema reference, not approval to collect, publish, or enroll a case. Removing names alone does not establish de-identification. End with the missing evidence and this next step: Resolve an undefined or sensitive field before adding it to an analytic or public file.

## AI review prompt

Review my permitted fictional or aggregate draft of DenQAI’s owner case data dictionary 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: Locate each field_name by record_type before preparing a case draft. Follow definition, allowed_values_or_format, and source_rule without inventing missing information. Review required_for_local_export, sensitivity, and public_release_default as separate conditions. Separate facts from assumptions and missing records. Do not supply unsupported numbers or make a professional decision for me. Apply this limitation: The data dictionary is a schema reference, not approval to collect, publish, or enroll a case. Removing names alone does not establish de-identification. Return corrections, questions for the responsible reviewer, and the next action.