Why Document HL7 Profiles (or Specs)? Part 2
August 27, 2014
Tip 24 in the Interoperability Tip Series Read Part 1 here In our previous tip we asked: why document HL7 profiles and specs. In beginning
Tip 24 in the Interoperability Tip Series Read Part 1 here In our previous tip we asked: why document HL7 profiles and specs. In beginning
Tip 23 in the Interoperability Tip Series The last few tips have been about what to document and how to document. This one and the
In the design of Meaningful use, C-CDA – especially CCD – was supposed to solve the pressing issues in healthcare concerning interoperability and data
Tip 22 in the Interoperability Tip Series In the previous tip, we talked about documenting your interfaces and workflows – especially important for HIE organizations.
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
Tip 21 in the Interoperability Tip Series This tip is especially relevant for Healthcare Information Exchanges (HIEs), regardless of whether your exchange is internal to
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),
Tip 20 in the Interoperability Tip Series In our previous tip, we explained why you need to map processes and workflows. Many developers list their
Tip 19 in the Interoperability Tip Series Throughout the Interoperability Tip Series, we’ve stressed the need to complement the message structure and and content details
Tip 18 in the Interoperability Series What’s The Big Deal? If you’re just getting your feet wet with clinical and medical applications, you might think: