QIE Standard Mapping Functions¶
QIE includes many built-in mapping functions for the most common data manipulation operations. Using them instead of scripting eliminates a class of scripting errors, keeps the channel legible to whoever maintains it next, and significantly reduces channel development cost.
Every function is configured on the same dialog and shares the same Source, Node Path, Target, Apply Condition and Customize Script settings. Those are described once in Working with Mapping Functions. Each function below documents only what is specific to it.
Choosing a function¶
| Mapping Function | What it does |
|---|---|
| Standard: Map Input/Output Fields | Copies fields from the input source message to the output message. The function most channels are mostly made of. |
| Standard Mapping Wizard Dialog | A point-and-click way to build Standard mappings, showing the resulting output message as you go. |
| Change Case | Converts a value to upper, lower, or proper case. |
| Search & Replace | Performs a regular-expression search and replace against a value. |
| Substring | Copies part of a value by character position. |
| New Output Message | Replaces the output message with an empty message in a different format. This is how a channel converts CSV to XML, or HL7 to JSON. |
| Database Query | Queries a database and includes the result in the output message. |
| Evaluate Template | Evaluates a template, replacing embedded node tags with the data they represent. |
| Format Date/Time | Reformats a date or date/time value. |
| Table Lookup | Cross-references one value to another using a system variable table. |
| Stream to File | Streams a value to a file instead of holding it in memory. |
| Web Service Call | Submits data to, or retrieves data from, a web service. |
| Custom Script | Runs a custom JavaScript mapping script, which is also what you get by customizing any function above. |
Web service functions¶
The Web Service function takes its shape from the type of connection selected, so it is really four functions sharing one entry in the list:
| Function | Use it when |
|---|---|
| Web Services | Start here, the Service field and how the connection type decides the rest. |
| REST Web Services | Working with a REST response. |
| REST Web Service (Content Encoded) | The endpoint expects a request body you compose. |
| REST Web Service (URL Encoded) | The endpoint expects its parameters in the URL. |
| SOAP Web Service | The endpoint is SOAP, an IHE profile, or the deprecated QIE Web Service. |
| Google Cloud Healthcare API | Writing into a Google Cloud Healthcare datastore. |
Tip
If none of these fits, check whether a built-in function plus Apply Condition does the job before reaching for Custom Script. A condition on a Standard mapping covers a lot of what looks at first like scripting work, and it stays readable in the mapping grid.