Understanding the data

Medicare-like research files usually separate who the person is, whether they were enrolled, condition indicators, and service/claim events. Medicare-Synth mirrors that shape in its fixtures and MVP worlds so analysis code can practice joins and definitions.

A minimal relationship picture

Beneficiary (one row per person in the extract)
    │
    ├── Enrollment (membership over time / year rules)
    ├── Chronic-condition indicators (e.g. diabetes, heart failure flags)
    └── Claims / encounters (zero, one, or many rows per person)
            └── optional claim lines / detail rows in richer fixtures
Idea Plain meaning
What one row represents The grain: person, enrollment spell, claim, or line
How records connect Shared identifiers (keys) linking persons to events
Administrative indicator A coded flag or algorithm result—not identical to a clinician’s chart diagnosis
Claim presence An event occurred in the synthetic extract—not proof of clinical necessity

Why counts differ

Where technical field definitions live

For table families, keys, and source-to-release flow, use the developer data model guide. For lineage statuses and what validation does (and does not) prove, see provenance and validation.