Skip to content

v1.0.0 — Foundational Release

Choose a tag to compare

@dorofino dorofino released this 21 May 20:36

Note: This is a retroactive tag and release. The v1.0.0 schema was originally published on 2025-11-30 and accreted through December 2025 as the examples and supporting docs landed. This tag marks the final state of main immediately before v1.1.0 work began (commit 14fe5ba, 2025-12-06).

What v1.0.0 includes

  • Canonical JSON Schemaschema/v1.0.0/benefit-plan.schema.json (JSON Schema Draft 2020-12).
  • Top-level model: plan_id, plan_name, carrier, plan_type, effective_date, expiry_date, network_tiers[], accumulators (4 in-network slots), benefits[], source_references[], schema_version.
  • Benefit model: benefit_id, category, service_name, place_of_service[], network_cost_shares[] (with ordered cost_shares[] array — copay/coinsurance/deductible with sequence, amount, rate, basis, applies_to_deductible, applies_to_moop), limits[], conditions[], moop_applicability, coding_hints.
  • Example normalized plans for 7 carriers: Aetna, Blue Cross, Cigna, GatorCare, Humana, SCAN, UnitedHealthcare.
  • Modules placeholder — extension framework for pharmacy, behavioral health, dental/vision.
  • Documentation site at benefitplanstandard.org.

Canonical URL

https://benefitplanstandard.org/schema/v1.0.0/benefit-plan.schema.json

This URL is preserved going forward — v1.1.0 lives at a separate path and v1.0.0 documents continue to validate against v1.1.0 unchanged (backward-compatible).

Known gaps (addressed in v1.1.0)

  • Accumulators only modeled in-network; out-of-network deductibles and OOP maxes required adopter extensions.
  • No plan_year, coverage_period, or top-level market field.
  • No benefit_type discriminator on benefits — module support required schema redesign.
  • The examples/scan_example.json example placed notes inside cost_shares[] items, which would fail additionalProperties: false.

See v1.1.0 for the backward-compatible additions that close these gaps.