-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Packard Health (athena health) issue - NetworkError when attempting to fetch resource. #396
Comments
can you open up the background jobs page (click the (please be sure to remove any ids/personally identifiable information before copy-pasting in this issue) |
Ah, thank you! Yes I see a line item for each time I tried where it has the status of The details show
|
ugh. thats not helpful at all. Let me make some changes to the main branch and add some additional debugging if I can. In the meantime, can you check your Browser console and docker terminal for errors that could be related? |
This is for another athena health connection (MedHelp). Ive sanitized the ids, but the big one seems to be the stack in error_data. Running as a docker image on Mac. Potentially missing/unavailable resources in the web assets? { |
Having the same issue for HealthPartners
|
thanks for all the info @Eschguy @abuettner93 @eldridgea @abuettner93: the references in the stack trace field just mean that the failure occurred in the frontend javascript, not that there's a missing resource. Do you see anything in your browser console logs? There should be something there, or in the network tab at the very least. |
I did have some console areas. This is a little out of my wheelhouse so not sure if this is relevant but attached the erros below that I got in the console after try to add Packard Health again. There did seem to be some issues with the callbac urls.
![]() There were also a few errors in the Network tab: ![]()
|
This is exactly what I needed, thanks @eldridgea
|
confirmed, I was able to replicate this issue locally (it took me a while because I had to find a healthcare institution that uses Athena, and allows me to register as a patient) The error was actually working on a fix now |
Fix is in place, letting it run though CI. I'll merge it after dinner. |
Hey @eldridgea @Eschguy @abuettner93 Can you pull the latest docker image and verify that the Athena providers you were trying to connect are now working? I was able to replicate this issue locally and I've since made a fix |
Thanks! I updated but looks like there's still one CORS issue: The Fasten job history was still
|
Hey @eldridgea can you confirm which version of the Docker image you're running? There should be some version information in the footer once you login. |
Looks like v1.1.0. |
that'll be locked to a specific tag. Can you try pulling and running |
Ahh, that did it! (version This is great, thanks so much for the amazingly quick turnaround and the great software overall! |
Still no luck with a fresh pull
Do I need to have a domain tied to the instance or anything? With it being health records I didn't want to expose it anywhere and keep it internal (my 172.16.X.X IP). I have my docker logs if you want them, Pastebin seems down at the moment though. |
@Eschguy I think you're running into a different error actually. Your provider seems to be using
Nope, that shouldn't effect it at all. If I had to guess, this is related to the version of the Epic software that your provider uses. I have a |
Done, see #400 |
Contact Details
[email protected]
What happened?
When adding the data source Packard Health, I am able to login and am redirected back to Fasten, where a tile for Pakcard Health appears. However after a moment, it vanished and showed an error toast message
An error occurred while initialize external data source connection: '{}'
Apologies fir the lack of log attachments -- are you looking for the docker container logs or something else?
(Loving the software so far -- thanks so much for the efforts!)
Flavor
Docker
Version
1.1.0
Relevant log output
No response
The text was updated successfully, but these errors were encountered: