← Atlas Journey · Docs

Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.

Disability income, dental and long-term care claim research

Access date for all web sources: 2026-10-07. Primary sources only. This is research for fictional Atlas journeys, not real coverage terms or advice. Stages and screen grouping below are proposed Atlas design. Source forms establish field/evidence patterns; they do not establish Atlas eligibility, duration, limits, deadlines or payment amounts.

Read local README, CONTEXT, fictional-product-rules, domain/process/tracker instructions and accepted ADRs 0003/0004. A read-only attempt to retrieve the canonical GitHub map failed because api.github.com was unavailable. The parent should reconcile this research with its map context before publishing. No repository, code or Git changes were made.

Disability income

Evidence anchors:

Proposed wizard and handoffs:

StageField groups / ownershipAnswer-triggered branch
Coverage and claimantSeeded policy, insured identity, contact, employer relationship, work location; customerGroup coverage identifies employer contribution. Individual coverage would need a separately approved variant; initial Atlas fixtures remain employer funded.
Work interruptionLast worked date, claimed absence interval, current work status, expected/actual return; customerWorking part time opens earnings period/hours contribution D3. Related leave is linked as a separate case.
Cause and treatmentIllness/injury/pregnancy selection, onset, incident, treating-provider references; customerInjury opens date/location/description; employment-related opens workers-compensation status; pregnancy opens expected/actual delivery and complications D1. Hospitalization opens stay dates D5.
Income and occupationOther income type, amount/frequency, application/award status; occupation/duties; customer and employerApplied but not awarded requests receipt; awarded requests decision evidence D5. Employer confirms earnings, schedule and work demands D1. No automatic offset calculation.
Evidence and attestationsMedical authorization, requested statement/document slots, claimant acknowledgement; customerReviewer requests provider-specific evidence. Clinical restrictions and prognosis remain insurer-visible. Contribution received is distinct from reviewer acceptance D2.
Review and decisionReadable answers, contributor checklist, outstanding evidence; insurer reviewerMissing evidence opens a same-case correction task. Approve produces seeded benefit decision; decline produces reason; approved payout uses separate account/reference and simulated payment status.

Continuing claim forms should ask what changed, the requested extension period, updated treatment/evidence, other-income changes and resumed-work details. Employer payroll confirmation must not let a manager view diagnoses or medical files. A limited-work proposal can lead to two independent outcomes: insurer benefit review and employer RTW review. An employer saying work can be modified does not approve benefits or certify medical fitness.

Atlas-specific proposal: a denial review request captures disputed decision, explanation and new evidence, linked to the original case and assigned to a different synthetic reviewer. Appeal support is a proposed scope extension; current accepted Atlas rules only establish approve/request-information/decline. Keep legal deadlines out of prototype logic unless separately specified.

Dental

Evidence anchors:

Proposed wizard:

StageField groupsBranch / handoff
Policy and patientSeeded policy/subscriber, dependent selection, patient relationship/contactDifferent patient opens dependent confirmation. Student status only appears when the seeded policy scenario requests it N2.
Provider and servicesTreating provider, billing entity if different, service line date/type/tooth/surface/amountRepeatable lines for a treatment episode N1. Provider simulation supplies clinical/procedure facts; customer confirms submitted information.
Procedure detailTreatment-family discriminatorCrown/prosthetic replacement asks prior placement; orthodontics asks appliance date, treatment months and plan fee; accident asks date and type N1.
Other coverageOther plan/carrier/subscriber relationshipSecondary-payer scenario requests primary EOB and amount; unknown payer order goes to reviewer, not browser inference N2.
Supporting documentsProcedure-dependent evidence slotsPeriodontal treatment requests charting and relevant images; prosthetics request extraction/prior-placement detail; orthodontics requests plan N3.
Confirm and submitItemized claimed total, attachments, customer declaration, provider contribution statusReviewer asks for a specific missing item or correction. Approval updates seeded benefit use once; no separate dental payout journey.

Correction proposal: preserve original service-line IDs and submission snapshot; show which line/document needs attention; replacing an unreadable image marks the old version superseded. An excess amount can be corrected or declined under accepted fictional rules. A proposed appeal form collects decision reference, disputed service lines, explanation and evidence N4. Keep appeal review separate from editing an unsubmitted draft.

Predetermination exists in the real form N1, but Atlas's accepted dental journey is a claim. Do not silently add a quote/predetermination workflow. Avoid embedding the full copyrighted CDT catalog or reproducing ADA form layout; use synthetic service categories and provider-supplied synthetic codes if needed.

Long-term care

Evidence anchors:

Proposed wizard:

StageField groupsTriggered subflow
Identity and authoritySeeded policy, insured contact, person completing requestRepresentative opens relationship and synthetic authority-document evidence; permission to receive information and authority to act are distinct L1/L4.
Care needRequested period, current location, daily assistance needs, cognitive-support indicationAnswers tailor assessment questions and evidence request; no automatic diagnosis or eligibility finding L2.
Care setting/providerHome agency, independent caregiver, facility or adult day care; provider identity, start dateEach opens matching provider-review/confinement contribution L4. Family relationship prompts manual policy review L5.
Assessment preparationPractitioner contact, visit availability, support person, requested recordsSynthetic assessor contribution then coordinator/reviewer decision L2. External licensed actors can remain simulated documents unless new portal roles are approved.
Eligibility and care planReviewer-confirmed insured/provider/service eligibility, seeded plan referenceEligible-but-not-payable remains visible until seeded waiting-period and invoice conditions are satisfied L3.
Expense periodService dates, amounts, provider invoice, care notesIndependent caregiver opens daily hours/rate/tasks and dual certification L5. Facility opens confinement verification L6.
Decision and paymentEvidence checklist, requested seeded benefit, account referenceReviewer accepts or requests correction; simulated payout occurs only after benefit decision. Account setup does not approve care.

Recurring update proposal: ask whether care setting/provider/need changed. A move opens provider review; hospitalization or nights away opens date detail and expense reconciliation; recovery opens closure review L7. Do not mutate the old invoice or release another payment when its result is unknown. Missing care notes return an information task attached to that expense period L6.

An LTC appeal form is an Atlas proposal, not established by these Genworth pages. Capture disputed eligibility/provider/service decision and supporting reassessment; route to synthetic reviewer. No universal ADL count, cognitive test score, waiting period, family-care exclusion, daily cap or appeal deadline is inferred.

Shared implementation implications for later synthesis

Contentful authors stage definitions, field groups, repeaters, labels, conditional visibility and declarative constraints in immutable bilingual releases. Answer changes recompute visibility and evidence checklists; hidden stale values cannot satisfy a new branch. Define whether inactive answers are retained separately or cleared in the spec.

Camunda owns contributor tasks, information requests, reviewer decisions and workflow progression. A screen next button, completed checklist or CMS branch cannot authorize benefit/payment decisions. BFF enforces pinned declarative form constraints and record/task permissions through Fastify/TypeBox boundary contracts; React receives authorized SDUI through tRPC. Simulated business owners store claim answers, contributor evidence references, decisions and benefit use. Preserve correction lineage, stable identifiers and idempotent financial effects.

These are research-backed proposals awaiting synthesis with accepted scope. Third-party contribution portals, independent appeals, recurring claim periods and new journey variants require explicit specification treatment before issue publication. Existing manager medical/privacy boundaries and dental no-payout scope are already accepted constraints.