Skip to content
WhenWillIDie

Behind the crystal ball

Why WhenWillIDie only requests demographics

Understand the narrow record scope behind WhenWillIDie’s age-based entertainment calculation and what it deliberately does not analyze.

Start with the input the calculation actually uses

The implemented estimate needs a birth date to derive completed adult age. It does not use medications, diagnoses, lab results, allergies or encounter history. Requesting those categories would not improve this particular calculation because the function has no model that consumes them.

Enforce the category boundary in the server

The application’s allowed scope is demographics. The server rejects categories outside that site’s allowlist rather than trusting a browser to request anything it chooses. The authorization flow still asks the visitor to review the actual registered application and sharing purpose.

Reject inputs that cannot support the experience

The calculation rejects missing, invalid or future birth dates and completed ages outside 18 through 100. It does not substitute a guessed birthday. The interface also requires the visitor to acknowledge the entertainment limitation and explicitly reveal the date.

Keep the prediction claim out of the product

A future operator can redesign the experience without implying that a narrow demographics import becomes a medical prognosis. The current code has no individual mortality model or clinical validation. Live record imports require production activation; the public guides and source explain the boundaries before a visitor connects.

FinchNode connects the input, not the crystal ball

The FinchNode handoff in this project supplies authorized demographics to the connection service. The table lookup and reveal interaction belong to WhenWillIDie. This separation makes the integration’s limited role clear without implying that the connection provider endorses the entertainment output.

FinchNode’s authorized record access

Questions about this guide

Does the app analyze my medical history?

No. This implementation requests demographics only and uses the supplied birth date to derive age.

Will it guess an age if the birthday is missing?

No. Invalid or unsupported input produces no date to reveal.

Sources and implementation

Browse all public guides →