Patch

Back in the Saddle

After a year of working to provide market research for VA's emerging Fileman Evolution projects - especially after OSEHRA's December sprint to upgrade MSC Fileman 22.2 in support of VA's test-plan contract with Leidos, and the January VISTA Community Meeting in Sacramento - my health finally collapsed for six weeks of February and March. I returned to the office just in time to watch VA's next Fileman 22.2E testing contract sail over the plate before I could respond to it, much to my dismay and disappointment.

MSC Fileman 22.2 Patches

One of the characteristics of the final stage of packaging a new version for a VISTA application is that we must paradoxically freeze development without freezing development.

We must freeze development because the distribution sent to the world has to be a specific, tested version of the software. Getting to that point requires constraining development toward satisfying the results of testing, not introducing new disruption late in the packaging process, when there won't be sufficient time to test it. In this pro-testing era, most people get this issue pretty well.

VistA patch available from OSEHRA.

In late July, a possible VistA security vulnerability was discovered as part of an academic exercise at a major university.  The VISTA Expertise Network validated the vulnerability for some VistA configurations, and contacted OSEHRA to coordinate a community response.  A special open-source project group was formed.  Operating under non-disclosure agreements (industry best practice in handling zero-day exploits), OSEHRA members and collaborating partners (including VA and IHS) worked jointly to create and test an applicable patch.

Subscribe to RSS - Patch