How to Develop an Interface Gap Analysis Document

By | Published: May 15th, 2014

Tip 10 in the Interoperability Tip Series

In the previous tip, we covered specifications. Another key requirements or scoping document you’ll need is a gap analysis. In this tip, we discuss how to develop an interface gap analysis document.

Many analysts develop their own gap analysis templates in Microsoft Word or Excel. To fill in templates, they look at messages, run queries when they can, and manually document their findings. This can be a fairly onerous process if they’re basing the analysis [...]

Read More

How to Develop an HL7 Interface Specification

By | Published: May 9th, 2014

Tip 9 in the Interoperability Tip Series

In Tip 8, we explained what an HL7 interface specification should include. In this tip, learn how to develop an HL7 interface specification, which you’ll need for each interface you develop.

(A quick note about terms. There is no standard term for a spec. Some people call them a profile, conformance profile, schema. We use the term profile or HL7 profile in our software. We use the terms specification, conformance profile, and profile interchangeably in [...]

Read More

Resources for CDA, CCD, and Consolidated CDA Documents

By | Published: May 7th, 2014

In our discussions with vendors and providers on these new standards, we’ve seen a wide range of learning curves. Some people are just getting started, while others are knee-deep in live exchange. What are the tools and resources that are out there? This blog post gives you a handy list  of resources for CDA, CCD and consolidated CDA documents to get started.

Start with HL7 International

HL7 International is the standards developing organization for healthcare data exchange and integration. They provide the [...]

Read More

What Should An HL7 Interface Specification Include?

By | Published: April 30th, 2014

Tip 8 in the Interoperability Tip Series

Critical Elements in an HL7 Interface Specification

These are critical elements a developer needs to create a interface that works (almost) out of the box with minimal testing. The more accurate the HL7 interface specification, the faster it’ll be implemented – and the less costly the work will be.

1. Interface nameHow do you refer to your interface in your integration environment? Some organizations manage thousands of interfaces. If you’ve got 10 or 20 interfaces, no [...]

Read More

Gap Analysis and CCD Document Specification

By | Published: April 28th, 2014

Bridging the Gaps

In a previous post on CCD, C-CDA, and CDA, we compared HL7 v2 messaging to CCD development. This week’s article is about the biggest roadblock with CCD document specification: gap analysis.

What is Gap Analysis?

Simply put, gap analysis is about understanding the differences in the data between two systems. The output of a gap analysis process is a list of all the differences between two systems charted in a requirements document. With HL7 v2 messaging, many organizations create their [...]

Read More 1 Comment(s)

Are You Using These Interfacing Project Assets?

By | Published: April 24th, 2014

Tip 7 in the Interoperability Tip Series

Communicating These Needs to Leadership

These are the most important assets you’ll need when you’re working on creating new interfaces or converting existing ones from one system to another. You’ll need to create them manually, or automate this work via interface lifecycle software.

Why These Assets?

Besides making sure that you have complete requirements so that you can accurately scope a project, you need to make sure you have all the parts and piece lined up and [...]

Read More

HL7v2 to CCD

By | Published: April 22nd, 2014

Confused? Start with What You Know

Over the past few months, we’ve heard a lot from our hospital-based customers about CCD and C-CDA readiness. There’s more urgency with Meaningful Use Stage 2 deadlines, even with the extension.

But the funny thing is: hardly anyone ever says, darn, but this is confusing.

Sometimes people express their frustration. “What the heck are those regulators doing? Why are they pushing more stuff at us, when we’re barely able to keep up as it is?”

Others bury their [...]

Read More 2 Comment(s)

The Good, The Bad, and The Ugly: Interoperability, Negotiation, and Culture

By | Published: April 17th, 2014

Tip 6 in the Interoperability Tip Series

This tip is for hospital or provider analysts and team leads.

You’ve got a firm grasp of the technical ins and outs of system and application interfacing. Because you’ve got the background, you know that contractual and cultural issues can affect your team’s ability to deliver on time and on budget. 

Make sure these issues are on the table with your leadership, ideally during negotiation before a deal is signed. Your leadership will thank you for [...]

Read More

What is One-Hour Interoperability?

By | Published: April 15th, 2014

The Status Quo

This is the world interface analysts, developers, and quality testers work in:

2 weeks to get a list of code values for a single field
1 week to get a list of custom field formats like lab order codes
20 hours to code a schema in an engine from a spec in Excel
9 days on gap analysis
30 days to test a 10-minute code change
8 versions of a spec before it’s baked enough for development

Productivity with Caristix

With our software, especially with the [...]

Read More

Laying the Foundation for Interoperability

By | Published: April 10th, 2014

Tip 5 in the Interoperability Tip Series

9 Critical Questions You Need to Ask Your Clinical System and Interface Vendors

Like our last two tips, this week’s tip is geared to hospital teams asking their vendors the right questions. Vendors who are on the ball will have the answers at their fingertips.

Why Should Health System Leadership Care About This?

These lay the foundation for interoperability. They are the basic format and content scoping questions that kick off each and every interfacing project. Your [...]

Read More
All posts