Non-routine Software Elements Part 1: Data and Definitions

Yes, but what is VISTA made of?
So at the MUMPS level, VISTA is made of two kinds of software elements, routines and globals. Routines are readily version-controlled and managed (in theory) using industry-standard tools, but globals are not. Globals need to be flattened and exported in some way that focuses on the database files we are storing in those globals.

MUMPS Software Elements

What is VISTA made of?
The OSEHRA Forum project is about upgrading how VISTA is developed, distributed, installed, and version-controlled. This makes a lot more sense if you know know what VISTA's made of. It's different from software written in other programming languages, which changes how you can manage it.
The VISTA server software - which is most of VISTA - is written in MUMPS, the only major programming language created specifically for writing medical software. OSEHRA Forum focuses on the MUMPS parts of VISTA.

OSEHRA Forum Sprint 5

OSEHRA Forum Sprint Five (15-19 September) took us back to our preferred schedule of one-week sprints. Here we dug into the tough work of managing required patches across multiple patch streams.
Joel Ivey continued on the patch-record side of the problem, ensuring that each patch distributes to each VISTA system a record describing itself, and which the Build and Install records at each site can point to, so we understand what we're installing.

OSEHRA Forum Sprint 4

OSEHRA Forum Sprint Four, the first of Milestone B, was a long sprint (three weeks, 25 August to 12 September) to work around the OSEHRA Summit. This sprint started into the challenge of ensuring required patches are properly identified and checked. This is a safety issue, since the list of required patches helps ensure that patches are not installed out of order, which could cause corruption of the data and/or algorithms.

3 - OSEHRA Forum Sprint 3

OSEHRA Forum Sprint Three, which wraps up Milestone A, focuses on finishing the work necessary to teach KIDS about patches and patch streams. Joel Ivey is extending the software-distribution formats used by KIDS and the Patch Module so they can also transport a Patch record. Larry Carlson is enhancing the process of installing a patch to include not just the creation of Build (the shipping manifest) and Install (the installation) records at the destination VISTA system, but also the creation of a Patch record, which the other two will point to.

2.2 - Sprints 1 & 2 and the Team

A VISTA project requires the Golden Pair to succeed - so decisions about direction are made by programmers and the medical professionals who will use the software, working together as a team to explore what's possible and useful. The Patch Module is a special case, though, because it's a VISTA infrastructure application. That means our direct users are not medical pros; they're other VISTA developers. As VISTA developers ourselves, that means we can be our own Golden Pairs.

2.1 - OSEHRA Forum and Agile

We run OSEHRA's Forum project as a hybrid Agile project. Some of its organization comes from decades of VISTA experience with the Golden Pair (as described in VISTA Mastery), some from the Agile Manifesto (http://www.agilemanifesto.org), some from the processes that have grown up around Agile, and some from other sources. Overall, we've broken the project up into three-month phases, multi-week milestones, weekly sprints, and daily scrums, and we're using OSEHRA's Atlassian tools to track all of this.


Subscribe to RSS - OSEHRA Forum