Community Response to the RFI on VistA Standardization, Virtualization, Consolidation, and Security Remediation

OSEHRA Responds to VA Virtualization RFI

Many thanks to those of you who participated in our community call regarding this RFI, and those of you who shared your thoughts regarding our response. As promised, OSEHRA submitted a response focused on the many ways in which open source could contribute to successful implementation of the tasks described in the RFI. We know that many of you responded directly, and we hope that our response is complementary. We have posted the full response here, and welcome any feedback you may have for us.

VA VistA Virtualization RFI Update

We have spoken with several of our members, and we have been watching the discussion group carefully. It appears that most participants are currently “heads down” on their responses. At this point, it does not appear a second community conference call is necessary.

Notes on RFI

VA wants to put all VistA instances on one [virtual probably] "node".  This could facilitate a slow migration towards a heterogenous environment front-ended by some kind of master broker.  On the call mention was made of the fact that different sites configure VistA to run differently.  This is ameliorated by site parameter files, which allow for multiple sets of parameters by site, that would allow each user to be associated with a particular site on log on through a broker and view VistA through the lens of those parameters.  In addition, access to non-VistA

OSEHRA Responds to VA Virtualization RFI

Many thanks to those of you who participated in our community call regarding this RFI, and those of you who shared your thoughts regarding our response. As promised, OSEHRA submitted a response focused on the many ways in which open source could contribute to successful implementation of the tasks described in the RFI. We know that many of you responded directly, and we hope that our response is complementary. We have posted the full response here, and welcome any feedback you may have for us.

VA VistA Virtualization RFI Update

We have spoken with several of our members, and we have been watching the discussion group carefully. It appears that most participants are currently “heads down” on their responses. At this point, it does not appear a second community conference call is necessary.

Notes on RFI

VA wants to put all VistA instances on one [virtual probably] "node".  This could facilitate a slow migration towards a heterogenous environment front-ended by some kind of master broker.  On the call mention was made of the fact that different sites configure VistA to run differently.  This is ameliorated by site parameter files, which allow for multiple sets of parameters by site, that would allow each user to be associated with a particular site on log on through a broker and view VistA through the lens of those parameters.  In addition, access to non-VistA

No questions have been added to this group.
No documents have been added to this group.
No wikis have been added to this group.