Plan names, benefit levels, and premiums shown throughout are placeholders. DDAZ has advised that plan designs and rate tables are not yet developed, so nothing here should be read as a proposed plan or price. Every plan, tier, and rate in this prototype is configuration a DDAZ administrator sets — the screens for doing that are in the admin console.
EyeMed's member experience, claims, and ID card issuance stay with EyeMed. Where the journey reaches that boundary, the prototype shows the handoff and stops. Member names, identifiers, and payment details are fictional.
Member screens are built to the WCAG 2.2 AA baseline we propose: 18px minimum body text, 44px targets, one decision per screen, plain language, and forgiving validation. Use the text-size control inside the member journey to see it hold up.
Operations
Eligibility review
Clean matches against the ASRS roster pass straight through. These are the near matches — held for a person rather than rejected by the system. Attestations awaiting the next roster appear here too.
No record is edited in place. Confirming writes a new eligibility decision with its actor, timestamp, basis, and correlation identifier — which is what makes a retroactive question answerable a year later.
Billing & dunning
Where every delinquent account stands, what notice it last received, and when the next thing happens. Retry timing follows the failure reason — an insufficient-funds return and an expired card are not the same problem.
Enrollment feed · ANSI X12 834
A daily change file with a weekly full audit file, delivered to DDAZ with checksums, sequence numbers, and gap detection — so a missed file is noticed by the system rather than by a member without coverage. DDAZ manages the downstream exchange with EyeMed.
Plans & rates
DDAZ owns the plan catalog and the rate tables. Plans, tiers, effective dates, and enrollment rules are configuration — no release, no developer. Publishing a rate creates a new version and never overwrites the last one.
You created this version, so you cannot approve it. Segregation of duties on rate changes and financial adjustments is enforced by the platform, not by a procedure someone has to remember. It can be staged now and it activates on its effective date.
Versioned with effective dates. A rule change for next plan year is configuration, not a release — and the engine explains a blocked change to the member in words rather than a code.
Assisted enrollment
Creed builds the capability; DDAZ operates the channel. A representative works the same record the member was working, with the same eligibility, rating, and billing logic — there is no parallel process to reconcile later.
ASRS can work in this portal or receive the same aggregate figures as a scheduled file. Both draw on the same sponsor-scoped view, so the numbers cannot disagree.