Blaise can be implemented in a manner that is HIPAA compliant and is able to implement security controls that are considered best practices for HIPAA compliance.


Blaise has always sought backward-compatibility. This means that a system developed by Blaise 4.8 can, in principle, also run in Blaise 5. However, the reverse may not always be true. It is recommended to check if older applications still run correctly after the transition to a new version.

Changes from previous versions are described in the Blaise 5 help file under "What's new". Also look at the chapter "Blaise 5 for 4 developers". You can find help through the Control Centre in Blaise 5 or online via this link.

Connecting to other processes

Within a Blaise survey application one can interact with other processes, running executables, DLLs, and ActiveX components from the survey menu.

Use of DLLs and ActiveX

If you have a special need and Blaise can not handle it, you can extend the system by using the Blaise components. Using Dynamic Link Libraries (DLLs) and ActiveX components extend the system in various ways the designers of Blaise did not implement in the basic system. You can use DLLs to display graphics, read data from a serial port, invoke specialised coding software, or perform a complex calculation already programmed elsewhere.

Additional Capabilities

Blaise has an open system architecture that supports the integration of Blaise with non-Blaise systems and software.

Easy to use

Subject matter specialists, statisticians, and programmers can become adept at authoring Blaise instruments. The modular and reusable structure of the language allows many surveys to use the same blocks of code with little or no modification. This results in faster, surer development and better comparability between surveys. The multi-mode nature of Blaise encourages (and can enforce!) consistent specifications and conventions between multiple modes of use.

Gaining deeper understanding