Get Answers Fast

QIE has an AI Companion built into it, and it is usually the quickest way past a problem while you are still learning the product. Before you spend twenty minutes searching for the right page, consider asking it.

Open it from Help -> AI Companion, or the AI Companion button on the right of the title bar.

What it is good at while you are getting started

Node paths. The syntax for addressing a field differs by message format, and looking it up is the single most common interruption when writing a first mapping. Ask for "the HPath for the patient's date of birth" and you get PID-7, and you can ask why.

Errors. Paste the error text, the stack trace, or the contents of a failed message straight in. You get what it means and what to change, which is faster than working backwards from a log line.

Reading someone else's channel. Most interface work is changing a channel somebody else built. Paste a script and ask what it does.

A second opinion on your own script. Ask what is wrong with it before it goes near a production message.

See AI Companion for the full description, including SQL mode and how conversations are saved.

Tip

Test what it writes before you trust it, the same as you would with code from a colleague. Run it against a sample message. The QIE Tutorial shows how in its first few pages.

The documentation is still worth reading

The AI Companion answers the question you asked. The tutorials teach you the questions worth asking: how a channel is put together, what the node types are for, why persistence levels matter. If you are new to QIE, work through the QIE Tutorial first; it takes an afternoon and everything afterwards is easier.