HL7 2.6 and HL7 2.7

January 17th, 2008 by Dave Shaver

4 Votes | Average: 3.75 out of 54 Votes | Average: 3.75 out of 54 Votes | Average: 3.75 out of 54 Votes | Average: 3.75 out of 54 Votes | Average: 3.75 out of 5 (4 votes, average: 3.75 out of 5)

Loading ... Loading ...

Posted in HL7 Standards, HL7 Standard

HL7 Standards Update. HL7 2.X continues to march forward with new releases. HL7 2.6 is done (just published this week) and proposals for 2.7 have closed — the first ballot for HL7 2.7 will be in May 2008. From a practical perspective, this means that 2.7 will hit the streets sometime in late 2009.

Most users of HL7 2.X don’t pay attention to the newer releases of HL7 (both HL7 2.X and 3.X) because these current users are building interfaces between existing applications. These applications typically have “more-or-less 2.3″ interfaces and, broadly, those interfaces are “good enough” for most users. There is a comparatively small group that helps create new releases of HL7 or that has an opportunity to improve a vendor’s interface by upgrading to a new release of the HL7 Standard.

It is always interesting to see how the HL7 community continues to push HL7 2.X forward. It is fair to say that HL7 2.6 and, soon, HL7 2.7 are better standards than prior releases. They both have more functionality, better descriptions, and fewer errors.

In a free market, buyers choose (directly or indirectly) the version of HL7 they ask their vendor to create. With time, I hope that many vendors will move to the more-complete standards. In the United States, we must rely on market (buyer’s) pressure to ask purveyors of software to improve the functionality of their interfaces.

This blog post was entered in NEOTOOL’s HL7 Blogging Contest.

Last 5 posts by Dave Shaver
4 Responses to “HL7 2.6 and HL7 2.7”
  1. Rene Spronk says:

    Curiously enough (or maybe not) it’s those with a large installed v2.x base that are pushing for the introduction of v3 features in v2.x standards (for those in the know: examples include moodCode, and nullFlavors for all v2.x datatypes).

    Surely they propose this because a) they anticipate having to translate from v3 to v2.x, and/or b)they know they’ll have to migrate to v3 sooner or later .. better to introduce some of the best modeling practices from v3 into v2.x than do a big-bang migration to v3.

    Half jokingly it has been suggested that we create a pipe-bar ITS for v3 .. this would allow v3 to be parsed by legacy v2 parsers. If that would help ease the migration burden on some vendors we (as HL7) may actually have to create one.

    -René

  2. healthcare lean training says:

    Very good post. Keep up the good work!

  3. Jerry Sheehan says:

    Does anyone know if there are HL7 2.6 XML Schemas available? I can find them for previous versions as well as version 3, but not 2.6

  4. Frederic Laurent says:

    hello

    Where can we get information about HL7 2.6 (updates, news, schemas, etc.) ? On the HL7 website, the available releases are 2.5.1 and 3.0. Nothing about these 2 new versions ?

    thanks in advance
    regards

Leave a Reply

Discover the NeoTool Healthcare Integration Solution for Your Market.