Tip 12 in the Interoperability Tip Series In tips from the past few weeks, we covered two requirements-related artifacts analysts must create: 1) profiles or
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
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,
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
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
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
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,
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
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
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