Health Standards

Healthcare & Technology Resources

  • Blog
  • Podcasts
  • #HITsm Chat
  • About
  • Authors

Job Titles for HL7 Engine Users

July 5, 2011 By Dave Shaver 3 Comments

What job title or job description do you give someone who spends much of their time solving integration issues within a hospital setting? In my opinion it’s pretty telling to see what titles the staff desires — often a mix of two concepts. Specifically, a typical HL7-aware, integration engine user at a hospital builds a title combining:

Interface, Integration, Application, or Systems

– along with –

Programmer, Developer, Specialist, or Analyst.

In the mix-and-match process, you can be an Interface Programmer, a System Analyst, or (my preferred title) Integration Analyst.

The telling part of the title is if the staff members want to focus on higher-level issues/concept (“Integration”) or lower-level details (“Interface”). Equally interesting is if they want to use more technical titles like Developer/Programmer or more work-flow focused terms like Analyst/Specialist.

My real point is three-fold:

  1. Who cares about titles anyway?
  2. What do your staff members actually do? Are they heads down, only-write-code, roll-the-pizza-under-the-door types or do they also get into the workflow efforts and solve higher-level issues?
  3. With modern integration engine tooling, the programming of interfaces is going away and the highest value work is analyzing the real integration issues. Said another way, as providers adopt more efficient integration platforms, it will become much more difficult to be only the low-level, “tell me what you want and I’ll code it” interface programmer.

Bottom line: IMO a successful healthcare integration career is more about clinical terminology, workflow and data models and way less about coding Tcl, Java, or Monk.

Thought questions — I welcome your comments below:

  1. What titles do you use?
  2. Is it time for a new title based on your current job functions?
  3. How challenging is it to title-hop within the political structure of pay grades and formal, institutional titles?
  4. If you view your inner self as a technical geek who loves to code, is it painful to drop the word “developer” or “programmer” from your title?
  5. Are you a less-satisfied geek if your title says “Integration Analyst” rather than “Java Developer”?
  6. How would a less geeky title positively impact your interactions with non-technical staff?

Additional reading: Thirteen Steps to Selecting the Right HL7 Interface Engine

The following two tabs change content below.
  • Bio
  • Latest Posts
My Twitter profileMy LinkedIn profile

Dave Shaver

Dave Shaver is the CTO for Corepoint Health. Dave has more than 20 years experience in training, consulting, and software development. He’s deeply involved in the HL7 standards community, including co-chair of HL7 Infrastructure and Messaging committee and co-chair of the HL7 FHIR Governance Board.
My Twitter profileMy LinkedIn profile

Latest posts by Dave Shaver (see all)

  • HL7 ADT Q&A with Dave Shaver - July 2, 2014
  • Health Standards Community Membership Archetypes: Who uses HL7? - August 6, 2013
  • Note from the Field: Meditech 6.0 HL7 Integration - September 6, 2011

Filed Under: Healthcare Integration, HL7 Integration

  • Grahame

    “HL7 guy”

  • Jamin Gray

    Integration Engineer is the preferred title at my organization.

  • Anonymous

    Systems Analyst here, but I do LIS and Administration as well.  Throw in some DB and some GUI development, and you have the whole package.

    I administer the Cloverleaf Engine for our site, and I think that both sides: clinical and technical are important.  At one point I may be untying a sticky ADT knot and calling on my understanding of both HL7 and clinical informatics.  At the next point, I’m using TCL to code a utility that splits FIN messages into two parts because the billing system chokes on more than 10 FT1s.  My background is 30 years as a lab tech.

API White Paper

Connect

  • 
  • 
  • 
  • 
Tweets by @HealthStandards

#HITSM Chat

[#HITsm chat 11.18.16] Celebrate Passing the #HITsm Torch

November 15, 2016

Moderated by Chad Johnson, @OchoTex, HealthStandards.com Editor and Corepoint Health Senior Marketing Manager. November 18th will be the last #HITsm chat under @HealthStandards. Celebrate ‘Passing the #HITsm torch’ to @techguy @HealthcareScene.

Passing the #HITsm torch

November 10, 2016

The first #HITsm tweet chat was held almost six years ago on Jan 10, 2011. Since that time, we have hosted approximately 280 #HITsm chats. While some of you may have participated in that very first chat (only 15 actually participated), I’m proud to say that the chats and the community have continued to grow […]

View More #HITSM Chat >

Podcasts

‘Hactivist’ Fred Trotter on the Cancer Moonshot, open source data in healthcare, and more

August 3, 2016

Artificial intelligence is a topic that isn’t going away in the health IT and medical community. One reason it’s come as far as it has is thanks to open sourcing, or shared data. Today’s guest, Fred Trotter, has a lot to say about the Vice President’s Cancer Moonshot initiative – which he was recognized for […]

Sue Schade on gender equality, CIO challenges, and value-based healthcare

July 27, 2016

View More Podcasts >

Copyright © 2019 Health Standards. All Rights Reserved.