Skip to content
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

[Provider Request]: VA (US Department of Veterans Affairs) [VistA EHR] #418

Open
gramaryen opened this issue Feb 20, 2024 · 2 comments
Open
Assignees
Labels
enhancement New feature or request provider issues related to healthcare institutions/integrations

Comments

@gramaryen
Copy link

Contact Details

[email protected]

Provider/Institution Name

VA (US Department of Veterans Affairs)

Provider/Institution Website

https://eauth.va.gov

Patient Portal Login Website

https://eauth.va.gov/mhv-portal-web/web/myhealthevet/home

Provider EHR Platform

VistA

Anything else we should know?

https://www.va.gov/vhie/

"Electronic Record Sharing Options
Beginning April 17, 2020, VA will seamlessly and securely share your electronic health record with community providers who are part of your care team through the Veterans Health Information Exchange (VHIE)."

@gramaryen gramaryen added enhancement New feature or request provider issues related to healthcare institutions/integrations labels Feb 20, 2024
@AnalogJ
Copy link
Member

AnalogJ commented Feb 20, 2024

hey @gramaryen thanks for opening this issue!
We're already working on an integration with the VA. We have support in our sandbox environment already, and we're in the process of getting production approval. Howerver, I expect this to take atleast another couple of weeks.

Thanks for opening this issue, its a good idea to keep track of the VA status here (instead of just in my email 😄 )

@AnalogJ
Copy link
Member

AnalogJ commented Mar 4, 2024

Just copy-pasting an update from Discord for everyone following along on Github:

I guess it can't always be rainbows and butterflies. I just got some bad news from the VA 😕
They've decided to deny our self-hosted version access to their production API, stating: VA must consider whether such access advances a shared objective, improves programmatic reputation/visibility, and/or achieves mutual programmatic goals and citing our potential for abuse of their API.

On the other hand it's not all bad news: they will continue considering production access to their APIs for the desktop version of Fasten.

I've sent them a follow up email asking for more clarifications around the self-hosted denial, asking if there are any legal, procedural or technical changes we can make that would all them to reconsider. I'll continue to keep you all updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request provider issues related to healthcare institutions/integrations
Projects
Development

No branches or pull requests

2 participants