Multiple use tier - Give developers long-lasting access without refreshing

[healthbjk]

Developers and organizations using Flexpa's API don't always just want a single snapshot of a patient's data, but may require periodic or ongoing data access once authorized. The biggest obstacle to data retrieval is the refresh expiry period, dictated by the variability of refresh token validity periods across payers. The complexity of managing these refresh tokens has proven to be a considerable operational burden for our customers. To alleviate this, we are exploring the introduction of a "multiple use" tier so that Flexpa refreshes authorization and keeps data fresh for customers, offering simple, long-lasting access.

This new tier would grant long-lasting access to healthcare financial data without the hassle of keeping track of refreshValidFor timeframes or setting up complex backend cron jobs for token renewal. Under this tier, once a user authorizes access, the issued token would have an extended or even indefinite validity period. We believe this could significantly lower the barrier for customers to use data effectively and help patients.

We'd love your feedback and thoughts on this proposed feature.

[tomnz]

We (MedBill) would certainly love this! We were initially anticipating a pain point for users when asking them to re-link insurance for expired links.

[healthbjk]

As an update here - development on this project began at the start of the quarter. We expect to launch this feature in the coming months and are looking for early adopters/beta users.

[healthbjk]

This feature is now in general availability

[jnak]

Nice! Is there documentation about the expected length of session for each carrier?

[healthbjk]

@jnak Yep, that's detailed here as the max authorization period where known:
https://www.flexpa.com/docs/network/endpoints

It also returned on the endpoints API as maxAuthPeriod:
https://www.flexpa.com/docs/tools/api#endpoints

[jnak]

The first link you shared distinguishes between "Access token expiry", "Refresh token expiry", and "Max authorization period". Similarly, the second link distinguishes between "refreshValidFornumber" and "maxAuthPeriodnumber".
What do those mean if tokens are automatically refreshed/extended as long as possible?

[healthbjk]

@jnak great question. The refresh token expiry is used by customers using the legacy refresh functionality, where they had to refresh at certain intervals in order to maintain authorization. Flexpa now handles this on behalf of customers, attempting to maintain the authorization up to the maximum authorization period a payer allows.