NextGen Version convention

I’m confused about how NextGen does their version numbers. In addition to a number scheme they also have UD2 (update 2), UD3, SP1 (service pack 1), and then they have separate version control for templates (KBM 7.9, KBM 8.0).

When you login to NextGen, the version number appears at the top right of the login screen.

We are currently on version 5.6.5.73, but you’ll notice something about this… there is no mention of UD1, SP1, or KBM 7.9.

Todd Zantow offered this solution, which I agree would be a much better system than what NextGen is currently using.

In my opinion, the schema should be: V.SP.UD.P where:

V = MAJOR version, such as the change from 3.x to 5.x (Fusion) and/or a new look and feel like 5.6

SP = Significant revision – many new features and/or service pack level

UD = Regular revision – some new features

P = patch/build/hotfix level – no new features

In that model, you normally wouldn’t upgrade even from 5.6.5.73 to 5.6.5.82 unless you needed something that needed to be fixed.

5.6 should have been 6.0.x.x. Service Pack 1 should have been 6.1.x.x and the Updates (UD) should be 6.1.2.x.

I urge NextGen to drop the confusing practice of telling users that they need to upgrade to a SPy UDx, when internally and on their website use the x.x.x.x format! We have enough confusion with the HIPAA/ARRA/MU/5010/ICD-10 requirements, we don’t need more confusion.

Todd Zantow

Prairie Clinic

So how can you tell what version you are on, and how the different codes relate to each other…

SP is a service pack with significant bug fixes and new features, whereas UD is an update with just bug fixes.

5.6.5.73 is considered 5.6 SP1 UD2, but you could also have other similar version numbers that would also be considered 5.6 SP1 UD2.

KBM refers to the NextGen EHR templates and has its own versioning system separately from the NextGen application.

You can run this SQL query:

select * from btu_version

order by create_timestamp desc

Or, per the NextGen knowledgebase follow these steps below. In my case I get “7.8” but the SQL query gives me a more detailed result: “7.8.2.6 – Service Pack”

Every KBM template has a hidden version label. To determine which version is currently being utilized in the host database:

1. Log into Template Editor.
2. Open any KBM template (for example, ABN).
3. The version number appears in the upper, left-hand corner of the template.

Which means that you can be using templates from different KBM versions at the same time. The dermatology templates weren’t upgraded with the KBM 7.9 look, and remain at 7.8, but when you access a vital sign template you get the newer 7.9 template.

In addition to all of this, you also have to pay attention to see if certain versions are released as beta versions, or as general release versions.

Uggh