{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Health Connect duplicate records",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/health-connect-duplicate-data",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Inventory sources and record identifiers per metric",
    "Separate synchronization identity from daily aggregation",
    "Test overlap partial coverage and corrected records"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "The same provider record arrives again",
      "expectedBehavior": "Update or ignore by stable identity",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "Two devices cover one interval",
      "expectedBehavior": "Apply the documented aggregation policy",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "One record is corrected later",
      "expectedBehavior": "Recompute affected derived values",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "Source preference is a product decision that may differ by metric and platform. Make the rule inspectable and testable rather than presenting one device as inherently correct for every user."
}