My thinking has more to do with an "Open Platform" approach where device interoperability using open standard based API's are important in order to interface with VistA, ED, OR, ICU, and other applications that are currently part of the ecosystem. Not how medical device options will replace VistA per se, and not to be completely VistA centric.
I see this WG has been inactive for over a year. Given VA's pursuits to potentially outsource its EHR and platform support, does it makes sense to re energize this group in order to support medical device integration into a new ecosystem?
In lieu of an in informed opinion, I will give mine :). This is, I believe, the VA moving forward with Master File Standardization for both packages (for better or for worse). Similar to TIU and the relationship between 8925.1 TIU DOCUMENT DEFINITION and 8926.1 TIU VHA ENTERPRISE STANDARD TITLE. These files will be updated through the Master File pushes that are done to VA sites. So we will have to be able to work around that, as the process involves communicating direct with the VA NTRT team. Much like we have had to do with some of the other MFS files.