VA changing licensing of VistA software

Ok, I'm giving up around p 7. Can you/someone summarize the license changes? What I skimmed read more like a refactoring for the purpose of creating a differently managed (I'm not sure I'm willing to believe "better", especially in that it looks like further development may be outsourced -- driven by some consensus of specifications delivered to the vendor) core that can accept both publicly developed (and, presumably, licensed) and privately developed... plugins, for lack of a better term.

I seem to recall VistA receiving more than a bit of praise -- if I'm not confusing it with something else. Broader adoption nonetheless has been slow -- probably hamstrung by the variegated demands and political pressures of private insurers.

Given the Obama Administration's mixed record on technological development, I was/am curious to see where VistA is now being taken.

P.S. I'm no expert in this stuff, and the above is simply from memory of past news stories and whatnot. I may have some or all of it wrong.

P.P.S. I originally started a comment in order to post a "friendlier" URL to the Word document, à la Google Docs:

http://docs.google.com/gview?url=https%3A%2F%2Fwww.vendorpor...