You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Authorization numbers are unique therefore they should be treated as such by the database as well but mostly because it is super error prone entering the same identifier by hand multiple times (as it is currently done).
Complicating factors:
Multiple service areas per authorization
For example, AT, ILS, Braille, and O&M under one auth.
"TEMP" auths
Sometimes auths are not received by us, but clients are supposed to start receiving services on a certain date. Also, the previous items applies here as well, that further complicates the situation, because there can be multiple TEMP auths, all of which could apply to multiple service areas.
The text was updated successfully, but these errors were encountered:
Authorization numbers are unique therefore they should be treated as such by the database as well but mostly because it is super error prone entering the same identifier by hand multiple times (as it is currently done).
Complicating factors:
Multiple service areas per authorization
For example, AT, ILS, Braille, and O&M under one auth.
"TEMP" auths
Sometimes auths are not received by us, but clients are supposed to start receiving services on a certain date. Also, the previous items applies here as well, that further complicates the situation, because there can be multiple TEMP auths, all of which could apply to multiple service areas.
The text was updated successfully, but these errors were encountered: