Is HL7 Interface Trial and Error Working for You?

Typically, when you start an interfacing project, there’s a getting-your-feet-wet stage. “Where’s the MRN in that feed? Does it have leading zeros? Who’s got the lab codes? What do the z-segments contain?” There are a whole lot of questions at this stage. One question cascades into another. You check the interface documentation. Then send an email. And pretty soon, you’re in the deep end, with scope creep, a runaway timeline, and very little real data (read: specifications and test messages) to go on.

Is there a better way? We think so.

Here’s a slide deck that captures a new way of doing things — starting with a new concept, Interface Lifecycle Management. Just about every interfacing project goes through this lifecycle. But we think there’s a way to bring a little order to the process, and simplify development and go-lives. It starts with scoping, where an analyst captures a conformance profile that reflects the real environment: local code sets, segment structures (including z-segments), and real-world messages. This drives the rest of the lifecycle, reducing trial and error.

[slideshare id=10969857&doc=hl7interfacing-howtolosethetrial-and-errorandgolivefaster-120111130454-phpapp02]

Let us know what you think in the comments.