There are scenarios where coverage-information returns that "no auth is required" based on a policy that is only valid until the end of the year, and if the care happens after that then prior auth could potentially be required.

We should support returning an expiration date on coverage-information so provider systems can know that if they try to schedule an appointment past the expiration, the previous response should be ignored and CRD should be run again to get an updated response.

In trying to get CRD running in the meantime we've been discussing handling this with a custom extension.