Blog

What is Reverse-Engineering?

By margo.ellis@caristix.com | Published: September 2nd, 2014

Why consider reverse-engineering? Lack of accurate specs

If you’ve worked on an interfacing team or for HIE, one of the issues you’ll hear about is a lack of accurate interface specifications. For instance, the vendor spec might be missing. Or the source or destination spec on hand might no longer match the production version.

So what do you do?

Lack of specs: what’s the impact on your ability to deliver?

Well, you might be facing weeks of digging and research. You’re missing a lot [...]

Read More
Categories : HL7 Data HL7 Interfacing

What is Gap Analysis in HL7 Interfacing?

By jeanluc.morin@caristix.com | Published: August 4th, 2014

First, what’s the problem?

One of the problems we hear about from HL7 team leads and their management is that interfaces take a long time to configure. The reasons why boil down to missing information. Here’s what they typically hear back from the team members:

“The fields need fine-tuning.”

“We don’t know up-front which message types will need the most work.”

“That field mapping was a bear because we couldn’t get a complete code set from the source and destination systems.”

“These code sets have [...]

Read More

HIEs, Business Models, and Interfacing

By jeanluc.morin@caristix.com | Published: July 29th, 2014

Healthcare Information Exchange Types

There are three basic types of healthcare information exchanges (HIEs): some cover a geographic region (for instance, NCHIE in North Carolina), others a community; and yet others that cover a single hospital system (which in turn may be spread out geographically – for instance, Catholic Health Initiatives).

HIE Business Models: Grants vs. Revenue Generation

While some regional and community HIEs got their start via government grants, many of those grants are coming to their end. Even though they might [...]

Read More

HL7 Interface Testing Checklist

By sovita.chander@caristix.com | Published: July 8th, 2014

Over the past few weeks, we’ve reviewed multiple HL7 testing topics. So you know how critical it is to test interfaces during interface configuration, the validation phase, and during maintenance.   This HL7 interface testing checklist will help you design a testing process that covers your most important needs. And if you already have a testing process in place, it will help you identify any areas of concern.

1. We’re running tests to make sure we’re not injecting errors during interface development, [...]

Read More
Categories : HL7 Interfacing Testing

What is an HL7 Profile?

By sovita.chander@caristix.com | Published: June 17th, 2014

We get this question a lot. Over the past few years, we’ve come up with a few answers. Let’s bring this full circle into 3 simple bullet points:

A profile captures an interface specification. So profile = spec.
Some people use the terms profile, spec, and specification interchangeably.
Why build a profile? So that you save time building an interface and getting it into production.

Why build an HL7 profile?

The profile or spec also gives you interface documentation you can share with your team [...]

Read More 1 Comment(s)

Interfacing Management Maturity Model: Part 2

By sovita.chander@caristix.com | Published: May 27th, 2014

9 Diagnostic Questions: Interfacing Management Maturity Model

Last week, we introduced a maturity model for interfacing management. We explained how organizations progress through 3 distinct stages: Manual, Message, and  System.

This week, we’ll cover key diagnostic questions. These 9 questions will help you determine which stage you’re in and whether you should consider moving to the next stage.

1. How many sample messages are you using when scoping?

This gives you an idea of which stage you’re at. A handful of messages and you’re [...]

Read More

Interface Gap Analysis: 3 Reasons Why You Can’t Skip It

By sovita.chander@caristix.com | Published: May 23rd, 2014

Tip 11 in the Interoperability Tip Series

Last week, you learned about doing a gap analysis – mapping differences  between the systems you’re interfacing. Today, we’ll cover why you need this artifact.

1. Interface Requirements

No interface matters unless those coding the engine can accurately scope the interfaces they need to build. You need a way to communicate who does what on an interface. Is the vendor changing a field? Is the interface engine handling the field transformation? It’s critical that you pin [...]

Read More

Introducing an Interfacing Management Maturity Model

By sovita.chander@caristix.com | Published: May 20th, 2014

It’s clear that the needs around interfacing and integration are exploding. To match that need, Caristix is introducing an interfacing management maturity model. If you’re reading this, you know that there is a lot of implementation expertise available from analysts, developers, and consultants. But at the organization level, capabilities vary. Many organizations are seeking benchmarks to see where and how they can grow and adapt to meet their needs. That’s where our model can help.

This interfacing management maturity model is [...]

Read More

What is One-Hour Interoperability?

By sovita.chander@caristix.com | 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

Workgroup Software Demo Webinar: Part 6

By sovita.chander@caristix.com | Published: April 8th, 2014

A 16-minute Introduction to Caristix Workgroup: Part Six

We’re wrapping up our Introduction to Workgroup with Part 6 (1:30 minutes) We designed this demo webinar to give you a bird’s-eye view of Workgroup software. And we’ve covered a lot in a short 16 minutes, demonstrating just how comprehensive Workgroup truly is.

In the wrap-up, you’ll learn:

the key business reason why analysts and developers need more than ad-hoc tools to deliver interoperability
what enables better customer collaboration
why Workgroup

We’re open to any and all feedback [...]

Read More
All posts