Health Standards

Healthcare & Technology Resources

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

Why Filter HL7 Messages?

May 7, 2007 By Dave Shaver Leave a Comment

Sometimes it is necessary to have messages “filtered” on an HL7 Standard interface. Filtering reduces the number of messages that are sent on an interface due to business or technical requirements. For example:

  • A clinical application might have a performance problem with 30,000 ADT messages arriving on an interface each day – if the number could be reduced, the performance issue might be resolved.
  • A department might want to reduce the “excess patient noise” in the target application. For example:
    • Neonatal Intensive Care (NICU) application only had six beds, there is no need to have patient demographic information loaded into the NICU application for an adult patient checking in for dialysis or an outpatient lab test.
    • Likewise, the Radiology department might only want to see inpatients, emergency patients, and those outpatients checking in for mammogram.

In order to filter, the business rules for the filtering must be understood by both the technical (IT) and clinical staff. Ultimately these rules are translated into HL7 messaging segment or field values.

Continuing the examples from above, here is some example business logic to create filters:

  • The NICU filter could be built by only sending patients to the NICU application that are in the NICU nursing unit (PV1-3-1 = “NI”) or if their hospital service indicates NICU state (PV1-10 = “NICU”).
  • The Radiology filter could be built by selecting patients that have the correct patient class (PV1-2 = “I” or PV1-2 = “E”) or the correct admitting location (PV1-14 = “BCTR”).

Ultimately, the filtering is done in either the sending application, the receiving application, or an interface engine that sits between the two applications.

 

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: HL7 Integration, HL7 Messaging

HL7 FHIR Resources

HL7 FHIR Resources

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 © 2021 Health Standards. All Rights Reserved.