Recall from the explanation of the Primary Integration Engineer role that the core infrastructure work required to support a pure Chameleon SDK approach to interfacing is much higher than the work required if an Iguana approach is adopted. It naturally follows, then, that the effort required to do the quality assurance of a Chameleon-based core implementation is similarly much higher in comparison to an Iguana-based solution.

• With an Iguana-based solution the message delivery (networking, batch file, etc.), logging, administration, database access, etc. has been developed and QAed by iNTERFACEWARE. Not only has it been developed by iNTERFACEWARE, but it is deployed to hundreds of sites worldwide. As such, the only aspect of the core messaging infrastructure that requires QA by your team is your application's basic interaction with Iguana (i.e. the shared database or the interface with the client executable).

• With a Chameleon-SDK-based solution, however, there is much more core infrastructure that needs to be QAed. The message delivery, logging, administration, database access is all custom code implemented by the Primary Integration Engineer in this case. As such, it is absolutely critical to carry out thorough QA on all of these aspects of the core implementation. If networking code has been implemented to deliver messages via the Lower Layer Protocol over TCP/IP, for example, a thorough checking for all possible networking issues must be carried out. Some checklists to be aware of for a Chameleon-SDK-based implementation include:

Red Flag Quality Issues

HL7 Interface Network Issues