[Source]: Anthem

[srwareham]

Contact Details

No response

What happened?

Attempting to connect to Anthem CA on the main branch of Fasten returns an error after redirecting to patientca.anthem.com. I am unable to connect to this source.

"The client application is not known or is not authorized."

This notice appeared after being redirected to this URL. Some other attempts didn't make it this far and just hung at "Redirecting..." while still being at a lighthouse url

I started fasten by running the command listed in the documentation in an empty directory:

docker run --rm \
 -p 9090:8080 \
 -v ./db:/opt/fasten/db \
 -v ./cache:/opt/fasten/cache \
 ghcr.io/fastenhealth/fasten-onprem:main 

Thank you for introducing such a valuable product to this ecosystem.

Flavor

Docker

Version

main#3b6d262

Relevant log output

No response

[AnalogJ]

That's strange, I have some records at Anthem myself, and it has worked for me in the past.
I'll take a look at this tomorrow

[sid3ff3ct]

same message here, same flavor and all

[srwareham]

@AnalogJ is this error reproducible for you with Anthem CA on a clean install? Would you have guidance how to try to debug this further?

[AnalogJ]

I've opened a ticket with Anthem (Careevolution is their EHR). I'll update this issue once they have resolved the problem.

[talmuth]

Same for me for non-CA Anthem

[srwareham]

@AnalogJ any chance you've heard back? Still getting the same issue when trying to use fasten. Thank you!

[rbrowning85]

I am receiving the same error with both Anthem and Blue Cross Blue Shield of Kansas City.

[AnalogJ]

Apologies for the lack of updates. This is a known issue, Anthem migrated to a new API platform, which broke my integration. I haven't had much time to figure out what their new endpoints look like.

[srwareham]

Hi @AnalogJ, would you have a sense where this fits into your priorities? I imagine you're tackling larger boulders but sometimes a smaller thing is nice to throw in the mix. No worries either way.

Thank you