Styxis
Company
Knowledge

Passwordless patient access needs a visible unsupported-path policy

Keep an untested mobile verification path separate from a patient's failed login.

A simpler journey has a coverage boundary

Removing an SMS step can simplify a patient journey, but only for a path the service actually supports. A mobile operator or device combination that has not been evaluated should not become an unexplained login failure. Truthound can check a proposed accessibility test matrix. It cannot authenticate patients or establish the security of network-based verification.

The healthcare agreement

Nokia announced a commercial agreement with BeeHealthy on September 3, 2026 to integrate Network as Code into healthcare applications, replacing SMS one-time passcodes with network-based verification. The release describes intended access and security benefits. It does not establish universal operator coverage or document every patient's experience across the named markets.

Separate three access conditions

Begin with the combinations the care provider intends to support: country, mobile operator, device category and verification route. Give each one a test state and an alternative access route. An unknown result, an unavailable route and a genuine authentication rejection are different conditions. Combining them can send a patient into repeated retries when the application should explain another way to proceed.

Check the approved route pair

For the access-route and fallback table prepared as a Polars DataFrame, Truthound Core Python SDK 3.3.4's ColumnPairInSetValidator can compare a prepared operator-and-route pair with an approved list. Its null handling must be specified; missing coverage evidence should not quietly pass as support. Additional conditional rules can require a fallback entry where the primary route is not available. The approved list needs direct confirmation from the responsible service team.

Keep a tested coverage rule

Pandera 0.35.0 can retain a similar policy using schema and custom predicates, including a Polars workflow. A team with a tested derived coverage key can keep it, rather than changing libraries during an access redesign. The check establishes consistency with a supplied list. Neither tool determines whether the fallback is usable by a particular person or whether identity proofing is sufficient.

Review the user-facing alternative

Have care-service and accessibility staff review the unsupported combinations before a pilot. Use approved test accounts or synthetic cases and examine the explanation shown to a user, the handoff to support and the alternative route. Do not invent patient experiences from the press release or from a successful table validation.

Do not blame an unsupported patient path

Accept a rollout cohort only when its required paths and alternatives have evidence and a named owner. Preserve unresolved combinations in the matrix, with a plan to test or exclude them transparently. Repeat the review as coverage changes. Reducing a login burden starts with distinguishing a service limitation from something the patient did wrong.

Evidence

Event checked
Subject checked
Modified