Knowledge Base - Qvera - Recent questions and answers

Answered: What is the construct of a QIE HPATH or Node Path?

Fri, 15 May 2026 15:28:33 +0000

HL7 is a messaging standard adopted by the healthcare industry for exchanging clinical and financial information between various healthcare IT systems. An HL7 node path (or HPath) is used to reference segments, fields, component and sub-components in an HL7 message. The HPath syntax conforms to the following pattern.

Segment ID [ Instance ] / Sub-Segment HPath – Field [ Field Instance ] . Component . Sub-Component

Here are some advanced Examples:

//Removes all nodes where OBX-3.1 equals SNO-F-01500

message.removeAllNodes('OBX[@3.1=SNO-F-01500]');

//Removes all nodes where OBX-3.1 equals CPT-90702

message.removeAllNodes('OBX-3[equals(@1, CPT-90702)]');

//gets all nodes where OBX-3.1 does not equal LOI-2532-0 and returns the enitre OBX segment

message.getAllNodes('OBX[@3.1!=LOI-2532-0]');

//gets all nodes where the OBX-5 value is greater 4.7 and returns the value found in OBX-5

message.getAllNodes('OBX[@5>4.7]-5');

//gets all nodes where the OBX-5 value is less than 4.7 and returns the entire OBX segment

message.getAllNodes('OBX[@5<4.7]');

// gets all the OBR segments and groups all following segments related to that OBR

message.getAllNodes('OBR[group=!OBR]');

//gets all OBX segments from the message

message.getAllNodes('OBX');

//gets all OBX segments from the message

message.getAllNodes('OBX[group=OBX]');

//gets all OBR segments and only the OBX segments related to that OBR. Note other segments like NTE will be omited from the group.

message.getAllNodes('OBR[group=OBR,OBX]');

//removes all OBX segments where the first field within the OBX contains CPT-90702

message.removeAllNodes('OBX[contains(@1, CPT-90702)]');

//removes all OBX segments where the first field within the OBX starts with CPT-90702

message.removeAllNodes('OBX[starts-with(@1, CPT-90702)]');

//removes all OBX segments where the first field within the OBX ends wiith CPT-90702

message.removeAllNodes('OBX[ends-with(@1, CPT-90702)]');

Note: In the above example we primarily used the message.getAllNodes and message.removeAllNodes functions. However, The example HPATH's or Node Paths can be used with any of the QIE functions where an Node Path or HPATH is required.

Answered: What are the basic JavaScript syntax conventions?

Fri, 15 May 2026 13:56:05 +0000

Syntax Conventions Description

Case sensitivity

myvariable is not the same as myVariable

--------------------------------------------------

var

All JavaScript variables and JavaScript functions must be identified with unique names called identifiers. Identifiers can be short names like x and y or they can be more descriptive like dateOfBirth or lastName.

The var keyword is used to create new variables. Variables are containers for storing data values.

Rules for creating variable or function names in JavaScript:

- Names must begin with a letter, $, or _

- Names can contain letters, digits, underscores, and dollar signs

- Names are case sensitive (y and Y are different variables)

- Reserved words (like JavaScript keywords) cannot be used as names

Best Practice:

When declaring variable and function names, use camel case methodology, which combines multiple words together always starting with a lower case letter and with each successive word starting with a capital letter.

Examples:

dateOfBirth

lastName

If using abbreviations, they should still be descriptive.

Example:

var lastName;

--------------------------------------------------

=

The equal sign (=) is used to assign values to variables.

Example:

var lastName = 'Watts';

--------------------------------------------------

;

All line statements must end with a semicolon character (;). As a general rule, block statements do not end with a semicolon.

--------------------------------------------------

Simple Statements

Simple statements perform one and only one function.

Example:

message.setNode('MSH-3', 'Radiology');

This statement hardcodes or sets the word 'Radiology' into the MSH-3 field of an HL7 message.

--------------------------------------------------

Compound Statements

Compound statements are comprised of multiple functions.

Example:

message.setNode('MSH-3', StringUtils.upperCase('radiology'));

This statement first changes the word 'radiology' to uppercase and then sets it into the MSH-3 field of an HL7 message.

--------------------------------------------------

Block Statements

Block statements start and end with curly brackets and are widely used with if statements, for loops, and other JavaScript functions.

There can be multiple simple or compound statements within a block.

Example:

{

    var sendingApp = StringUtils.upperCase('radiology');

    message.setNode('MSH-3', sendingApp);

}

--------------------------------------------------

White Space

JavaScript ignores extra spaces, allowing white space to be inserted into code to make it more readable.

However, if there is white space at the end of a line, the QIE JavaScript validation tool will flag it as a syntax error.

The error message will read:

line x col true – Trailing whitespace

Removing the extra spaces at the end of the indicated line will eliminate the error.

--------------------------------------------------

Splitting code across multiple lines

If a line of code does not fit on one line, it is best to break the line after an operator or comma, or within a string of text.

Example:

if (StringUtils.equalsIgnoreCase('CPS10', centricityVersion)) {

    message.setNode("/", qie.callWebService(

        channelCache.getValue('wsName'),

        "CCD Export",

        parameterMap));

}

In this example:

- The line is split at the opening parenthesis (

- Additional lines split after commas

- The statement ends with the closing parenthesis and semicolon

--------------------------------------------------

' and "

Single and double quotes are interchangeable within JavaScript, but must be matched within a given statement.

Examples:

'text'

"text"

A value that starts with a single quote must end with a single quote.

Quotes are typically used to surround textual values (strings and literals).

--------------------------------------------------

+

The plus symbol (+) has different meanings in JavaScript.

- With numerical values, it performs arithmetic addition

- With strings, it concatenates values together

Example:

var string1 = "Nothing is impossible, \n\r";

var string2 = "the word itself says I'm possible! \n\r";

var string3 = "Audrey Hepburn";

var quote = string1 + string2 + string3;

Result:

Nothing is impossible,

the word itself says I'm possible!

Audrey Hepburn

--------------------------------------------------

// Single line comments

Single line comments are made using two forward slashes.

Examples:

// This is a single line comment

var x = 5; // this is an inline comment

--------------------------------------------------

/* */ Multiple line comments

Multiple line comments start with:

/*

and end with:

*/

All lines between the opening and closing comment characters will be commented out.

Example:

/*

var x = '5';

var y = '3';

var z = x + y;

*/

Answered: How do I use a JSON array in QIE.

Thu, 14 May 2026 18:42:03 +0000

In QIE, JSON and XML arrays are referenced differently because JSON has explicit array syntax, while XML uses repeated elements selected with XPath predicates.

JSON: use JPath with / hierarchy plus an array qualifier.

Examples:

/phoneNumbers → the whole array

/phoneNumbers/[1] → first array item

/phoneNumbers/[usage="home"]/number → the number field from the matching array object

XML: use standard XPath. XML doesn’t have a native “array” type; what acts like an array is usually a set of repeating sibling elements.

Examples:

/bookstore/book → all repeated book elements

/bookstore/book[1] → first book

/bookstore/book[last()] → last book

A simple way to think about it:

JSON array item: /parentArray/[n]

XML repeated element: /parent/element[n]

QIE’s training docs summarize this as:

JSON JPath: {/ParentObject/ChildArray/[instance]/ChildProperty}

XML: standard XPath notation

So the practical difference is:

In JSON, the array itself is a node and you step into an item with /[n].

In XML, repeated elements are just matching nodes, and you select one with [n] directly on the element name.

Note: referencing an array in JSON using the XML repeated element node path nomenclature will return incorrect results.

Answered: Can I renumber segments in a HL7 message

Thu, 14 May 2026 18:11:58 +0000

Use HL7 group processing so each OBR group is handled separately. In QIE, the documented pattern is to get all OBR groups with message.getAllNodes('OBR[grp=!OBR]'), parse each group as its own HL7 message, count that group’s OBX segments, renumber OBX-1 from 1..n, and then write the updated group back into the original message. That exact OBR-group pattern is shown in the docs and the tutorial also shows renumbering OBX-1 inside a loop with message.setNode('OBX-1', ...) .

Example mapping script:

var obrGroups = message.getAllNodes('OBR[group=!OBR]');

for (var i = 0; i < obrGroups.length; i++) {
   var obrGroup = qie.parseHL7String(obrGroups[i]);
   var obxCount = obrGroup.getCount('OBX');

   for (var j = 1; j <= obxCount; j++) {
      obrGroup.setNode('OBX-1', j+'', j);
   }
   message.setNode('OBR[grp=!OBR]', obrGroup, (i + 1));
}

How it works;

OBR[group=!OBR] returns each OBR plus its child segments until the next OBR, so each array element is one OBR group
qie.parseHL7String(...) lets you treat that group as an HL7 message and access its local OBX segments
obrGroup.getCount('OBX') gets the number of OBX segments in that OBR group
obrGroup.setNode('OBX-1', j+'', j) sets OBX-1 to 1, 2, 3, etc. within that group
message.setNode('OBR[grp=!OBR]', obrGroup, i + 1) puts the modified group back in the correct OBR-group position

Answered: Can you review all errored messages and identify the most common patterns

Mon, 11 May 2026 16:48:58 +0000

The Show Distinct option on the Errors tab is used when you have a lot of errored messages and want QIE to group similar errors together by error text so you can work them in batches instead of one at a time.

What it does:

It searches the errors in the error tab and groups together unique or similar error messages.

This helps you quickly see how many different error types you actually have, which is useful for prioritizing cleanup and troubleshooting.
After you identify a group, you can use Search to pull up all messages in that group and then resolve, discard, or export those messages.

Main options in the Show Distinct dialog:

Match Precision Level: controls how strict the grouping is, from Exact Match to more relaxed similarity matching such as Somewhat Similar. The training material notes that Best Match and Very Similar Match are often the most useful settings.

Count: shows how many messages are in each grouped error.
Error Message: shows the text used to represent that error group.
Limit / First x number of groups: limits how many groups QIE will build before stopping the grouping process.
Stop: lets you manually stop a long-running distinct search.
Double-click a row: opens a sample error from that group for review.

Typical use:

Open the channel Errors tab.
Click Show Distinct.
Adjust the match precision and limit.
Let QIE group the errors.
Select a group and click Search to see all messages in that group.
Then act on them with the usual error-tab actions.

In short: Show Distinct is a triage tool for the error queue. It helps you identify repeated error patterns and then operate on all matching errored messages more efficiently.

Answered: What is the qie.addTimeToChannelStats function and how do you use it?

Thu, 30 Apr 2026 18:12:46 +0000

qie.addTimeToChannelStats(metricId, description, time) is a QIE method that adds a custom timing metric to the channel statistics display. It reports the metric in the channel’s overall stats view, and the value is treated as a time in milliseconds. The documented parameters are:

metricId (Integer): custom metric ID; QIE reports it as 9000 + metricId to avoid conflicts with channel node IDs

description (String): label shown for the metric

time (Long): elapsed time in milliseconds

For it to appear, channel stats must be enabled in the source node’s Advanced Options, and you can view the stats from the channel using View -> Stats menu in the to right corner of a channel

Example Code:

var start = qie.getSystemTimeMilliseconds();
// do some heavy logic you're interested in timing.
var pQuery = qie.getParameterizedQuery("SELECT firstName, lastName, dateofbirth FROM person WHERE patientID = :pid");

pQuery.setString("pid", source.getNode("PID-2"));
var queryResult = pQuery.doQuery(
   "dbConnectionName",
   false,
   false
);
message.setNode("PID-5.2", queryResult.getNode("firstName"));
message.setNode("PID-5.1", queryResult.getNode("lastName"));

var end = qie.getSystemTimeMilliseconds();
qie.addTimeToChannelStats (2, 'processTime', end - start);

Answered: What is table-split or 'Use individual tables for channel'?

Mon, 27 Apr 2026 21:58:12 +0000

Per-Channel Message Tables

Overview

QIE stores message processing data (source messages, processed messages, channel logs, message cache, filter results, and DICOM responses) in a set of database tables. Prior to version 25.4.1, every channel in the environment shared a common set of these tables. As environments grew — some customers reaching tens of millions of messages and hundreds of gigabytes of data — these shared tables became a performance bottleneck. Large shared indexes caused lock contention during routine queries (such as searching the completed queue), slowed down purge operations, and in some cases prevented users from logging in or navigating the application while a long-running query held locks.

To address this, starting with version 25.4.1 QIE now gives each channel its own dedicated set of message processing tables. This isolates each channel's data and indexes, dramatically reducing lock contention and improving throughput.

How It Works

When a new channel is created, QIE automatically creates a dedicated set of tables for that channel. The tables follow this naming convention:

z_{channelId}_{tableName}

For example, the message table for a channel with ID a80818699e490c30199e496d7a90001 is: z_8a80818699e490c30199e496d7a90001_message

The following tables are created per channel:

source: Original source message data
message: Processed message meta-data
message_blob: Message payload data
channel_log: Per-channel log entries
channel_log_blob: Log entry payload data
message_cache: Per-message cache data
source_filter_result: Saved-view filter results for source messages
message_filter_result: Saved-view filter results for processed messages
dicom_response: DICOM response data (DICOM channels)

All new channels created in QIE use per-channel tables automatically. No action is required.

Converting a Legacy Channel

Channels that existed before this feature was introduced continue to use the shared (legacy) tables until they are explicitly converted. Conversion is performed from the channel properties dialog under the Advanced Settings tab using the 'Use individual tables for channel' option.

Requirements for conversion:

The channel must be stopped.
All existing messages for the channel must be purged from the system. Conversion does not migrate existing messages — it switches the channel to a new, empty set of tables. Any messages still in the source, processing, outbound, completed, or error queues will become inaccessible if the channel is converted before they are purged.

To convert a channel:

Stop the channel.
Purge all messages for the channel.
Open the channel properties dialog and select the Advanced Settings tab.
Enable 'Use individual tables for channel'.
Save the channel. QIE will create the new per-channel tables.
Start the channel. New messages will be written to the dedicated tables.

Once a channel has been converted, it cannot be reverted to the shared legacy tables.

Answered: Can QIE do recursive subdirectory scanning for File, Network Share, and FTP Sources?

Mon, 20 Apr 2026 23:18:49 +0000

Recursive Subdirectory Scanning for File, Network Share, and FTP Sources

Overview

QIE adds an Include All Subdirectories option to File, Network Share, and FTP source nodes. When this option is enabled, QIE scans the configured source path recursively instead of only looking in the top-level folder.

This is useful when partners, devices, or upstream jobs drop files into date-based, customer-based, or location-based subfolders under a common root.

How to Configure It

Open the source node.
Configure the source path as usual.
Enable Include All Subdirectories.
Save the channel and test the source path.

The same option is available on:

File sources
Network Share sources
FTP sources

What Changes When It Is Enabled

QIE scans the source path and nested folders beneath the configured source path.
The source path test actions include matching files found in subfolders.
QIE preserves the source-relative folder structure as source metadata for the message.
If the archive directory lives under the same source root, QIE skips that archive tree during recursive scans, so archived files are not picked up again.

Source-Relative Example:

Source 'Path' set to: /incoming/files/source-root/
Include All Subdirectories enabled
File found in: /incoming/files/source-root/sub1/sub2/
source-relative path: sub1/sub2
So source.getFileDirectory() returns: sub1/sub2

Archiving Behavior

When recursive scanning is enabled via Include All Subdirectories, the incoming file may have a relative path such as orders/2026/03/input.hl7.

If the archive path does not use source metadata, QIE flattens that relative path into a single archive filename:

orders/2026/03/input.hl7 -> orders_2026_03_input.hl7

If you want to preserve the original folder structure in the archive, use the new source metadata tags in the archive path, especially {s-meta:FILE_DIRECTORY}.

Example

If the source path is:

/inbound/*.hl7

and files arrive in:

/inbound/west/2026/04/order1.hl7
/inbound/east/2026/04/order2.hl7

then enabling Include All Subdirectories allows QIE to find both files from the same source node.

Notes

The Include All Subdirectories option is only for directory-style sources (File, Network Share, and FTP). If you only want QIE to watch the top folder, leave it disabled.
Relative folder information becomes especially valuable when combined with source metadata node tags or the Code Wizard functions like source.getFileDirectory().

Archive Exclusion When Recursive Scanning Is Enabled Example

When recursive scanning is enabled via Include All Subdirectories, if the archive root directory lives under the source root, QIE skips that archive tree during recursive scans, so archived files are not picked up again. This behavior excludes the files in the archive root and its subfolders.

With this configuration and assumptions:

Channel Cache region set to: west
Source 'Path' set to: /incoming/files/source-root/
Include All Subdirectories is: enabled
Archive Path ("Move file to") set to: /incoming/files/source-root/archive-root/{cc:region}/{s-meta:FILE_DIRECTORY}/{s-meta:FILE_NAME}
This file found in: /incoming/files/source-root/sub1/sub2/example.hl7

then the source relative path will be:

`sub1/sub2`

The {s-meta:FILE_DIRECTORY} and {s-meta:FILE_NAME} node tags will resolve to:

sub1/sub2
and
example.hl7

The Archive Exclusion folder (not scanned by the recursive scan including subfolders) is:

archive-root

The file will be archived to:

/incoming/files/source-root/archive-root/west/sub1/sub2/example.hl7

Notice that when source-metadata tags are used the relative folder and filename of the archived file is not flattened and the folder structure returned by {s-meta:FILE_DIRECTORY} is preserved under the archive-root. Also notice that node tags like cc:region} can be used to alter where the file is archived.

If the archive-root folder is not under the source-root folder, then it is not scanned and no exclusion is applied.

Also see these related questions:

How to use source.getFileDirectory()?
What source metadata node tags are available in QIE?

Answered: How to use source.getFileDirectory()?

Mon, 20 Apr 2026 21:00:53 +0000

source.getFileDirectory() Code Wizard Function

Overview

QIE adds a new Code Wizard function under Source -> [selected format] -> File named Get File Directory. In scripts, this function is available as:

source.getFileDirectory()

It returns the source-relative directory path associated with the current source file, using / as the separator, when Include All Subdirectories is enabled.

Source-Relative Example:

Source 'Path' set to: /incoming/files/source-root/
Include All Subdirectories enabled
File found in: /incoming/files/source-root/sub1/sub2/
source-relative path: sub1/sub2
So source.getFileDirectory() returns: sub1/sub2

Return Value

Returns the source-relative directory path for the current file
Returns empty string ("") when the file is in the source root

Example return values:

""
"orders/2026/03"
"site-a/lab-results"

When to Use It

Use source.getFileDirectory() when your script needs to:

Route based on the subfolder the file came from
Rebuild part of the original folder structure in an archive or destination path
Add source folder details to logs or notifications

Example

var fileDirectory = source.getFileDirectory();
var archivePath = "/archive";
if (fileDirectory !== "") {
archivePath += "/" + fileDirectory;
}
// archivePath is now either "/archive" or something like "/archive/orders/2026/03"

Relationship to Recursive Sources

This function is only useful when Include All Subdirectories is enabled on a File, Network Share, or FTP source. When Include All Subdirectories is disabled it return an empty string ("").

For example, if the source file arrives in the source-relative path as:

[source path]/orders/2026/03/input.hl7

then:

source.getFileDirectory()

returns:

orders/2026/03

If the file is in the root of the source path, the function returns an empty string.

Related Functions

This function works well with the other file Code Wizard functions:

source.getFileName(): The filename including the extension.
source.getFileNameWithoutExt(): The filename without the extension.
source.getFileExt(): The file extension only.

Together, these functions let you build file-aware routing and naming logic without manually splitting strings.

Also see these related questions:

What source metadata node tags are available in QIE?
Can QIE do recursive subdirectory scanning for File, Network Share, and FTP Sources?

Answered: What source metadata node tags are available in QIE?

Mon, 20 Apr 2026 19:05:02 +0000

Source Metadata Node Tags

Overview

QIE adds a new Source Metadata category to Node Tag Lookup. These tags expose file-related values from the current source context so you can build paths, filenames, and messages dynamically without parsing the original filename yourself. These compliment the Code Wizard Functions.

This is especially helpful for archive paths "Move file to", outbound filenames, evaluated templates, and conditional scripting.

Available Tags

{s-meta:FILE_DIRECTORY}: The source-relative directory path. Returns an empty string ("") when the file is in the source root or Include All Subdirectories is disabled.
- Source-Relative Example:
  - Source 'Path' set to: /incoming/files/source-root/
  - Include All Subdirectories enabled
  - File found in: /incoming/files/source-root/sub1/sub2/
  - source-relative path: sub1/sub2
  - So {s-meta:FILE_DIRECTORY} returns: sub1/sub2

{s-meta:FILE_NAME}: The filename including the extension.
{s-meta:FILE_NAME_WITHOUT_EXT}: The filename without the extension.
{s-meta:FILE_EXT}: The file extension only.
{s-meta:REMOTE_IP_ADDRESS}: The remote IP address when the source context includes one; otherwise it resolves to blank.

Where to Find Them

Open Node Tag Lookup and select Source Metadata.

These tags are intended for places where node tags are supported and a current source context exists, such as:

Archive paths
Destination paths or filenames
Evaluated templates
Scripts and expressions that evaluate node tags

Common Examples

Preserve subfolders in an archive path:

/Archive/{s-meta:FILE_DIRECTORY}

Build a timestamped outbound filename:

processed/{s-meta:FILE_NAME_WITHOUT_EXT}_{SYSTEM_DATE[yyyyMMddHHmmss]}.{s-meta:FILE_EXT}

Reference the original filename in a log or message:

qie.evaluateTemplate("Processing {s-meta:FILE_NAME} from {s-meta:FILE_DIRECTORY}")

Why This Matters

Before this enhancement, file metadata was only available in scripts via the following Code Wizard functions:

source.getFileDirectory()
source.getFileName()
source.getFileNameWithoutExt()
source.getFileExt()
source.getRemoteIPAddress()

The new source metadata tags let you reference those values directly in templates and fields.

Notes and Limitations

FILE_DIRECTORY uses / as the separator in the resolved value.

REMOTE_IP_ADDRESS is only populated when the source format includes a usable IP address. For ordinary file paths, it is blank. Only applies to socket and DICOM sources.

When testing source "Move file to" paths in the UI, source metadata node tags cannot be resolved because a live source file is not available when testing. QIE shows a note during testing when source metadata segments cannot be evaluated. At runtime a valid source is available for proper evaluation.

Also see these related questions:

Can QIE do recursive subdirectory scanning for File, Network Share, and FTP Sources?
How to use source.getFileDirectory()?

Answered: What is a QIE NetFile and when should I use it?

Wed, 15 Apr 2026 20:46:14 +0000

The NetFile object in QIE provides a reliable way to interact with files located on remote SMB network shares using explicit credentials, instead of relying on the local system account that the QIE service runs under.

This is particularly useful in environments where:

The QIE service account does not have access to the network share
Access requires domain credentials
You need fine control over SMB behavior and connection settings

Why use NetFile instead of local file operations?

Standard file operations in QIE (e.g., readFile, writeFile) run under the QIE service account. This can cause issues when accessing remote shares that require authentication.

NetFile solves this by:

Allowing explicit credentials (domain + username + password)
Supporting direct SMB access to remote shares
Providing a consistent API similar to java.io.File, but for network locations

Key Benefits of NetFile

1. Access remote shares with credentials

NetFile connects to SMB shares using provided credentials instead of the QIE service account.

Supports domain;username format
Works even when the service account has no access

2. Full file manipulation support

NetFile can be used with standard QIE file operations such as:

readFile
writeFile
deleteFile
moveFile

Internally, it wraps SMB operations and exposes them in a familiar way.

3. Behavior consistent with local files

NetFile mimics the behavior of java.io.File:

Methods like exists(), delete(), mkdirs() return boolean results
Directory listing returns NetFile objects, not SMB-specific types

This makes it easier to write scripts without worrying about SMB-specific APIs.

4. Automatic SMB path handling

NetFile automatically:

Converts Windows-style paths (\\server\share) to SMB format
Ensures paths are prefixed with smb:// when needed

5. Connection lifecycle management (autoClose)

NetFile includes built-in connection management:

By default, connections are automatically closed after a period of inactivity
You can disable this with autoClose=false and manually call close()

This helps prevent:

Resource leaks
Stale SMB connections

6. Safe file access and locking

NetFile uses SMB share modes to:

Prevent reading files that are still being written
Detect if a file is in use by another process

This reduces the risk of:

Partial reads
Data corruption during file transfers

7. Configurable SMB behavior

Optional parameters allow customization of the SMB connection, such as:

File and directory modes
Timeout settings
Other jcifs-ng configuration options

Format:

key=value
key2=value2

For additional examples on usage of these optional parameters see what-are-the-network-share-configuration-parameters

When should I use NetFile?

Use NetFile when:

Accessing remote SMB shares
You need to provide credentials explicitly
The QIE service account cannot access the share
You need reliable file locking or concurrency handling

Do not use NetFile for:

Local file system access (use standard file APIs instead)
Simple file operations where the service account already has access

Additional Related Links:
what-are-the-network-share-configuration-parameters

filenotfoundexception-when-using-netfile-fileoutputstream

how-to-connect-to-remote-share-mapping-node-with-credentials

how-disable-dfs-network-shares-netfile-domain-environments

java.io.File

Answered: How do I protect the connection.password for the QIE database so that it is not stored in plain text

Tue, 14 Apr 2026 18:49:32 +0000

Securing the QIE database password

Starting with QIE 26.2.1, QIE supports storing the database password in encrypted form in the -Dconnection.password Java option, instead of plain text. The encryption key is stored separately in the QIE_DB_PASS_ENCRYPTION_KEY environment variable. When QIE starts, it uses that key to decrypt the password in memory and then uses the decrypted value to establish the JDBC connection.

To configure password encryption:

Create an environment variable named QIE_DB_PASS_ENCRYPTION_KEY.
Set the environment variable to a 32-byte key. This key length is required to use AES-256 encryption.
Restart the QIE service after setting the environment variable.
In QIE, navigate to System Config.
Scroll to Advanced Settings.
In the QIE Database Connection Password Encryption Utility section, click Encrypt Password.
Enter the database password in both fields, then click on the 'Encrypt Password' button.
Copy the generated encrypted value.
Update the Java option using the following format:
-Dconnection.password=ENC({encrypted_password})
Restart the QIE service again for the updated setting to take effect.

Answered: How do I use Channel Cache variables in QIE?

Fri, 10 Apr 2026 14:49:54 +0000

Channel cache is a simple key-value pair database associated with the channel. It can be used to store configuration parameters that change or modify the behavior of the channel. For example, you can store the name of a database or web service connection as a channel cache variable. This centralizes the configuration, making it easy to update the connection when moving a channel between environments (e.g., from testing to production) without having to modify the channel's mapping logic.

Values can be added, updated and deleted from channel node scripts. Values can also be manually added or deleted through the Channel Cache tab shown here.

Channel cache values are exported and imported with the channel. On import, if the channel cache already exists in a channel the value won’t be overwritten.

The channel cache is not thread-safe. It is designed for static configuration values. For frequently updated data, please use an external database to ensure data consistency and avoid performance issues.

Answered: What is the difference between the Add Inbound Message and Queue Inbound Message?

Tue, 07 Apr 2026 11:59:23 +0000

There are two functions that can be used on the Source Node to add messages to the channel for processing: qie.addInboundMessage(record, originalFilename) and qie.queueInboundMessage(record, originalFilename). What are the differences?

1. qie.addInboundMessage(record, originalFilename)

Adds messages to the inbound queue one at a time. Use this method when message order matters and the channel is configured to process messages in the order received.

It takes two parameters:

   record: a String or byte[]

   originalFilename: a String representing the filename of the message to be processed

2. qie.queueInboundMessage(record, originalFilename)

Adds messages to the inbound queue using a multi-threaded process. This allows for higher throughput, but the order in which messages are added and processed is not preserved.

It also takes the same two parameters:

   record: a String or byte[]

   originalFilename: a String representing the filename of the message to be processed

Note: Use qie.queueInboundMessage when message processing order does not matter and higher throughput is required. Use qie.addInboundMessage when message order matters and the channel is configured to process messages in the order received.

Answered: Can I set or change the end-of-line (EOL) characters in a message?

Tue, 31 Mar 2026 15:20:28 +0000

The message.setEndOfLine(eol) function allows you to explicitly control the end-of-line (EOL) character(s) used when processing or generating formatted messages.

This is useful when working with systems that require specific line termination formats.

Syntax

message.setEndOfLine(eol)

Parameter	Type	Description
`eol`	String	The end-of-line character(s) to use for the message

Value	Description
`'\r'`	Carriage Return (CR) — common in HL7
`'\n'`	Line Feed (LF) — Unix/Linux format
`'\r\n'`	CR + LF — Windows format
`''`	No line terminator (X12 only)

Supported Message Types

This method applies only to the following formatted message types:

HL7
ASTM
CSV
EDIFACT
Fixed Width (Old Fxd Width, Fxd Length)
JSON
X12

Behavior Notes

The EOL setting affects how the message is serialized or output, not how it is internally parsed.

For HL7 messages, the standard segment terminator is typically '\r'. Changing this may impact compatibility with downstream systems.

For X12 messages, an empty string ('') is allowed because segment terminators are defined differently (via delimiters within the ISA segment).

If an unsupported value is provided, the function may throw an error or be ignored depending on context.

Answered: What is the Refresh Script, and how is it used?

Tue, 24 Mar 2026 17:48:58 +0000

The Sample Message Refresh Script feature allows users to update sample messages with current or dynamic data. In QIE, sample messages are typically loaded manually on the Source Node by pasting a message from the clipboard or by using the File Import option. Over time, these messages may contain outdated information such as dates or other time-sensitive values. Updating them manually can be time-consuming, especially when multiple sample messages are used. The Refresh Script allows a user to write a custom script on the Sample Message tab that modifies the message before it is used. The script can call web services, run database queries, or access System Node Tags to retrieve values such as the current date and time or other QIE system information. The refresh script can be triggered to run from both the Sample Messages dialog and from the Test Window. After the script updates the message, QIE replaces the current sample message with the returned result. The returned message must be a String, and the final line of the script should assign the updated message to the message variable, for example: message = myNewSampleMessage where myNewSampleMessage contains the refreshed sample message.

Answered: HL7 Attachments handling

Tue, 17 Feb 2026 15:12:26 +0000

For HL7 ORU^R01 with Base64 in OBX, the practical/typical QIE pattern is:

Extract Base64 from OBX → decode → write to file (or external object store)
Replace OBX-5 with a lightweight reference (UNC path, URL, document ID, etc.) so the HL7 message is small during processing
Before sending to the destination, either:
- send the reference as-is (preferred), or
- re-hydrate: read the file back, Base64-encode, and put it back into OBX-5 before sending.

However, how each of these steps is accomplished will vary based on your specific requirements and environment, so it would be best to reach out to us at support@qvera.com so we can take a look at your individual situation.

Answered: Do you need to restart a channel when a global function it uses is changed

Thu, 22 Jan 2026 22:21:13 +0000

Whenever a global function or published function at the zone level is updated, you must restart the qie channels using it. This is because the function is cached when the channel is started and only reloaded when the channel is restarted.

Answered: Who is Awkward Al?

Sun, 21 Dec 2025 16:45:54 +0000

Awkward Al is stuck in the past - powered by legacy integration engines that can't keep up with modern healthcare. Qvera fixes awkward, retires outdated technology, and delivers intelligent interoperability for today's healthcare IT ecosystem.

Answered: Unable to upgrade database

Mon, 15 Dec 2025 14:12:27 +0000

The error indicates that the MariaDB upgrade process ran into an unspecified error. However, since that error is outside QIE itself we'll need to look at the MariaDB logs to try and discover why.

Note that MariaDB 11.4 is the newest supported version for QIE. The current version of QIE requires MariaDB 10.7 - 11.4, so your current database (being version 10.7.3) should be sufficient to upgrade to the latest QIE release. If QIE is unable to upgrade, there may be a QIE startup argument that is set incorrectly.

In either case, if you contact support directly, we can schedule a call to look at your system. Support can be reached via email at support@qvera.com, or via phone at 801-335-5101 extension 2.

Answered: Why does the script editor put a period and a space ". " instead of two spaces " " when I type two spaces.

Sat, 22 Nov 2025 02:27:12 +0000

If you are on a Mac computer it has a keyboard setting meant to do this replacement. To turn it off, try this (older macs may vary):

Open System Settings.

Go to Keyboard.

Under "Text Input," click the Edit... button next to "Input Sources."

Toggle OFF the switch for "Add period with double-space."

Click Done.

Answered: The memory reported in the "Monitor Server Resources" dialog is less than what is reported by the OS

Thu, 20 Nov 2025 21:52:11 +0000

That is a classic and frequent observation when monitoring a Java Virtual Machine (JVM). The reason the Operating System (OS) reports more memory usage than the sum of the JVM's memory pools is that the OS reports the entire process footprint, while the JVM's memory pool beans only report the areas managed by the Garbage Collector (GC) and JIT compiler.

The difference lies in the memory allocated for JVM Native Memory which is not tracked by the standard MemoryPoolMXBeans (like Eden, Old Gen, Metaspace, or CodeHeap).

The "missing" memory is primarily consumed by internal, non-heap allocations the JVM requires to function.

1. Thread Stacks

Every time a Java thread is created, the JVM allocates a fixed block of memory in native space for that thread's stack. This stack is used to hold local variables, method call frames, and return addresses.

Impact: This is usually the largest source of discrepancy. On 64-bit systems, the default stack size is often 1MB. An application with 200 threads would immediately reserve 200 * 1 {MB} = 200 {MB} of native memory that is not reported in any standard memory pool.
Programmatic Reporting: There is no standard JMX bean to report the sum of thread stack usage.

2. Garbage Collector (GC) Internal Data Structures

The G1 GC (and other modern collectors) requires significant internal data structures to manage the heap, track references, and enable concurrent collection. This memory is allocated in native space.

G1 Overhead: For the G1 GC, this includes structures like Remembered Sets (RSet) and Card Tables. These structures track cross-region references and can consume a notable amount of memory, especially with a large heap or a high number of regions.

3. Other JVM Internal Data

The JVM itself is a complex native C++ application that needs memory for:

Symbol Table: Storing constant pool entries, field names, and method signatures.
String Table: Storing interned strings (which are references to heap objects, but the table itself is native).
JNI (Java Native Interface) code and temporary buffers.
Loaded Libraries: The memory occupied by the JVM executables and loaded native libraries (like DLLs or SOs).

Answered: does anyone have an example HL7 to xml translation that you're willing to share?

Wed, 29 Oct 2025 17:02:53 +0000

You could do something like this:

message = qie.createXMLMessage("<person/>");
message.setNode("/person/@mrn", source.getNode("PID-3"));
message.setNode("/person/firstName", source.getNode("PID-5.2"));

Answered: How do I prepare the MSSQL user for the JDBC 13.x driver?

Wed, 22 Oct 2025 19:44:10 +0000

Steps (Jump to step 3 if you already know which permission is needed):

Step 1 — Identify SQL Server version

Run in SSMS/Azure Data Studio:

SELECT @@VERSION AS SqlVersion;

If it says SQL Server 2022 (16.x) or newer, you’ll grant VIEW DATABASE PERFORMANCE STATE. If it’s 2019 or earlier, grant VIEW DATABASE STATE. See Microsoft’s DMV permission note. Microsoft Learn

Step 2 — Check whether the QIE user already has the permission

Change database context to QIE DB (e.g., qie) and run:

USE [qie];
SELECT
  DB_NAME() AS database_name,
  HAS_PERMS_BY_NAME(
        DB_NAME(),
        'DATABASE',
        'VIEW DATABASE PERFORMANCE STATE'
  ) AS has_view_db_perf_state,
  HAS_PERMS_BY_NAME(
        DB_NAME(),
        'DATABASE',
        'VIEW DATABASE STATE'
  )AS has_view_db_state;

A result of 1 means the permission is present. HAS_PERMS_BY_NAME reference. Microsoft Learn Note which one applies based on step 1.

Step 3 — Grant the minimum required permission

Replace <DbUserName> with the QIE user used by the QIE application. Default is "qie".

If you are on SQL Server 2022+

USE [qie];
-- If the principal doesn't exist in this DB yet, create it (examples below).
GRANT VIEW DATABASE PERFORMANCE STATE TO [<DbUserName>];

If you are on SQL Server 2019 or earlier

USE [qie];
GRANT VIEW DATABASE STATE TO [<DbUserName>];

(Older versions use the classic VIEW DATABASE STATE for database-scoped DMVs.) Microsoft Learn

Summary

Before QIE can update to the latest Microsoft JDBC Driver this new permission must be granted to allow QIE to continue to correctly manage schema changes on upgrades. Starting with Microsoft JDBC Driver 13.x, the driver changed how it gathers index metadata. When QIE calls DatabaseMetaData.getIndexInfo to manage schema changes, the driver now queries DMVs instead of sp_statistics. On SQL Server 2022+, those DMV queries require the VIEW DATABASE PERFORMANCE STATE permission (on earlier versions it’s VIEW DATABASE STATE). If the QIE user lacks this permission, you’ll see errors like:

o VIEW DATABASE PERFORMANCE STATE permission denied in database 'qie'

o The user does not have permission to perform this action.

Grant the appropriate permission to the QIE database and the QIE user. Root cause details are in Microsoft’s release notes and DMV permission docs. Microsoft Learn+1

Affected

o Driver versions: Microsoft JDBC 13.x (e.g., 13.2.x). Microsoft Learn
o SQL Server versions:
- - SQL Server 2022 (16.x) and later: requires VIEW DATABASE PERFORMANCE STATE
- - SQL Server 2019 (15.x) and earlier: requires VIEW DATABASE STATE. Microsoft Learn

Symptoms you may see

o QIE fails during startup / schema validation.
o Messages similar to:
- - SQL Error: 262, SQLState: S0001
- - VIEW DATABASE PERFORMANCE STATE permission denied in database '<db>'
- - The user does not have permission to perform this action.
Stack traces showing SQLServerDatabaseMetaData.getIndexInfo(...).

Why this happens:

The JDBC 13.x driver replaced its older metadata path and now issues custom queries (covering all index types, including columnstore) instead of sp_statistics. Those queries hit DMVs that, on SQL Server 2022+, require the new PERFORMANCE STATE permission. Microsoft Learn

FAQ

Q: Which permission do I need?

o SQL Server 2022+ → VIEW DATABASE PERFORMANCE STATE
o SQL Server 2019 or earlier → VIEW DATABASE STATE Microsoft Learn

Q: Does this grant expose table data?

It grants visibility into performance-related DMVs for the database; it does not grant SELECT on user tables. See Microsoft’s DMV permission model for specifics. Microsoft Learn

Q: Our app uses a Managed Identity—what’s different?

Create the QIE database user from the external provider and grant the same permission in each DB:

USE [qie];
CREATE USER [MyManagedIdentityDisplayName] FROM EXTERNAL PROVIDER;
GRANT VIEW DATABASE PERFORMANCE STATE TO [MyManagedIdentityDisplayName];

Reference: CREATE USER ... FROM EXTERNAL PROVIDER. Microsoft Learn

References

o Microsoft JDBC Driver release notes — index metadata change in 13.x. Microsoft Learn
o DMV permission changes in SQL Server 2022+: VIEW DATABASE PERFORMANCE STATE. Microsoft Learn
o HAS_PERMS_BY_NAME function (permission checks). Microsoft Learn
o CREATE USER (SQL logins and Entra/Managed Identity contained users). Microsoft Learn

Answered: How to get IP from HL7 Connection

Mon, 06 Oct 2025 15:22:35 +0000

For a channel configured to receive messages via TCP/IP socket, the "filename" that we log is the source IP address. Thus, you can use qie.getFileName() to display the source IP address, which can then be used in a condition node to route your messages.

In addition, we also have source.getRemoteIPAddress(), which is specifically designed for TCP/IP socket source. Both methods will return the IP address of the source.

Answered: Documentation on using HAPI?

Thu, 25 Sep 2025 15:57:54 +0000

To add the HAPI library to QIE:

1. System Administration
2. System Configuration
3. Manage External Libraries

----------------------------------------------------------------------------

From here, you can download the HAPI library version from a list of available versions.

----------------------------------------------------------------------------

Below is an example of creating a FHIR Account using the HAPI functions:

var account = new hapi.r4.Account();
account.setId("exampleAccount");
account.addIdentifier().setValue("654321").setSystem("urn:oid:0.1.2.3.4.5.6.7");
account.setStatus(hapi.r4.Account.AccountStatus.ACTIVE);
var ctx = hapi.context.getR4FhirContext();
// Instantiate a new JSON parser
var parser= ctx.newJsonParser();
parser.setPrettyPrint(true);
// Serialize it
var accountString = parser.encodeResourceToString(account);
message = qie.createJSONMessage(accountString, 'UTF-8');

----------------------------------------------------------------------------

You can find more information about the HAPI resources on the HAPI website:

https://hapifhir.io/hapi-fhir/docs/

Answered: Why does QIE's postDICOMRequest() method require a DICOM Channel and a DICOM Connection

Tue, 23 Sep 2025 14:31:47 +0000

Here’s why QIE forces you to split things out into:

A DICOM connection (the “where do I send my request?” config, acting as SCU → SCP)
A DICOM channel (the “where do I listen for responses?” config, acting as SCP on your side)

This mirrors how DICOM associations actually behave in the real world:

Many DICOM services are asynchronous. When you send a request (N-ACTION-RQ, C-MOVE, etc.), the SCP may send multiple responses over time (intermediate pending responses, final responses).
Some services (especially C-MOVE) don’t even return the actual images in the same association — instead, the SCP initiates new C-STORE sub-associations back to the SCU (your side). That requires your system to be running as an SCP, waiting for those stores.

If QIE just “spun up a socket” inside your HL7 channel and blocked waiting for one response, it wouldn’t be able to handle these multi-response or callback situations correctly.

The enforced split is Qvera saying “we’re going to model DICOM correctly, including async behavior, whether you’re using it in that way today or not.”

We are aware this can cause some confusion. Hence this KB article . We're also aware that sometimes the timeouts of the receiving channel come into play and appear to override the timeouts configured in the DICOM connection, so watch out for that as well as it can be a "gotcha"

Now in your specific example above, the error you're receiving:
Channel 'C-FIND via JSON' is not running.
is due to the fact that all qie.postDICOMRequest() calls must have a DICOM channel as mentioned above to receive the responses. In this case the channel is an HTTP listener with a JSON payload, not a DICOM Listener. Although the documentation for the call says that the "channel*" is optional, it's really only optional in the sense that it defaults to the current channel and expects it to be a DICOM listener.

Answered: How do I update the qieLauncher package?

Thu, 18 Sep 2025 17:35:56 +0000

The qieLauncher service is used to monitor the main QIE service and restart it when needed for release updates and other tasks. The older version of the qieLauncher relied on a deprecated technology to talk to another running java service. This technology is being removed in java version 24 and will no longer work.

To prevent problems with the QIE environment, the qieLauncher needs to be updated. The update process is different when running windows vs linux.

Window

Simply update download the latest version of QIE and run the installer.

Once downloaded, stop the QIE service before running the installer.

Once the service is stopped, open the zip file and execute the .exe file. This will preserve all existing settings in your environment. The installer will install the latest version of the qieLauncher and update the QIE service to the latest version (unless the QIE service is already running the latest version, then it will only update the qieLauncher).

After the update, start the service.

Linux

Connect to the linux environment using ssh and then navigate to the qie home directory (usually /java/qie).

Once the file is download, stop the service using "#> sudo systemctl stop qie"

After the service is stopped extract the qieLauncher.jar file by running "#> unzip {downloaded QIE file} qieLauncher.jar. This step will replace the existing one in your qie home directory.

Now that it has been updated, start the service by running "#> sudo systemctl start qie"

Answered: Where can I find information about the different FHIR structures?

Fri, 05 Sep 2025 20:10:50 +0000

Information about the different version of FHIR can be found:
DSTU2: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-structures-dstu2/
DSTU3: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-structures-dstu3/
R4: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-structures-r4/
R5: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-structures-r5/

Answered: Can I validate a FHIR resource when it is read into QIE

Fri, 05 Sep 2025 20:05:31 +0000

QIE uses the HAPI java libraries to help process FHIR resources. This means that the HAPI FHIR validator can be used as well. To get the validator object you will call:
hapi.context.getFhirValidator()

Information on using the validator can be found at: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-base/ca/uhn/fhir/validation/FhirValidator.html

Information on the validation result object can be found at: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-base/ca/uhn/fhir/validation/ValidationResult.html

Answered: Where can I find information about converting FHIR from JSON to XML?

Fri, 05 Sep 2025 19:05:30 +0000

QIE has a standard function that will convert the FHIR resource from JSON to XML.

qie.convertFHIRJSONtoXML() will complete this for you.

Information about the specification can be found:
http://hl7.org/fhir/json.html

Answered: Where do I find information about a DICOM instance UID?

Fri, 05 Sep 2025 18:59:44 +0000

The specification information is at:
https://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_B.2.html

Answered: Does QIE have an official docker image?

Fri, 05 Sep 2025 18:56:13 +0000

Yes, QIE has official images that have been published to both Docker and AWS. You can find them at:
https://hub.docker.com/r/qvera/qie

public.ecr.aws/qvera/qie

Answered: How do I configure my MSSQL Server to use ssl-encryption?

Fri, 05 Sep 2025 18:49:20 +0000

The documentation for setting up a MSSQL Server to use ssl-connections can be found on the Microsoft website at:
https://docs.microsoft.com/en-us/sql/connect/jdbc/using-ssl-encryption

For information on setting the connection properties see:
https://docs.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties
https://docs.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver

Answered: Where can I find information about the Apache Camel Options available in QIE

Tue, 02 Sep 2025 22:40:14 +0000

Information about the latest available Apache Camel FTP options can be found at:
https://camel.apache.org/components/latest/ftp-component.html

Answered: What is the NDJSON Specification

Fri, 29 Aug 2025 18:46:23 +0000

The NDJSON allows batch JSON messages to be sent. Each line of the file represents a single record, so this means that the file is using unformatted JSON.

More information can be found at: https://github.com/ndjson/ndjson-spec

Answered: Does QVERA integration platform support NCPDP 2017071 standard?

Mon, 25 Aug 2025 17:03:20 +0000

Qvera does not have a built-in template or format for this; however, we can support it by building an XML message and setting the message to that specification.

You can reach out to support to explore this and discuss.

Answered: Cannot call property escapeCsv in object [JavaPackage org.apache.commons.lang.StringEscapeUtils].

Mon, 18 Aug 2025 19:39:49 +0000

This is caused by libraries in QIE switching from the older Apache commons-lang packages to the new commons-lang3 packages. This was necessary to ensure that the Apache libraries are kept up-to-date with the latest versions that do not have vulnerabilities.

However, the fix to this error is simple, but does required the channel to be updated. We can fix the script by replacing all instances of 'Packages.org.apache.commons.lang.' in the code with 'Packages.org.apache.commons.lang3.'. For example, to fix this script

var csv = Packages.org.apache.commons.lang.StringEscapeUtils.escapeCsv('select * from patient');

we will replace it with this

var csv = Packages.org.apache.commons.lang3.StringEscapeUtils.escapeCsv('select * from patient');

Once the references to commons.lang are replaced with commons.lang3 you will be able to save the channel and restart it. The process should start working as designed.

Answered: What version of the mssql-jdbc_auth-{version} file do I need.

Thu, 14 Aug 2025 15:57:44 +0000

25.2 - 12.10.0: https://repo1.maven.org/maven2/com/microsoft/sqlserver/mssql-jdbc_auth/12.10.0.x64/
24.3 - 12.8.1: https://repo1.maven.org/maven2/com/microsoft/sqlserver/mssql-jdbc_auth/12.8.1.x64/

Answered: QIE Build 25.2.1.16482 requires MariaDB 10.4 or greater, or MySQL 8.0 or greater.

Wed, 13 Aug 2025 15:51:02 +0000

QIE installer installed MariaDB 10.3 in the past. This is not compatible with Qvera version 25.2. These are the steps to update.

1. Stop QIE service using the qie service manager.
2. Download MariaDB Server 10.11.
3. Install MariaDB Server and when prompted you want a new DB or upgrade. You need to choose to upgrade the existing install. Run the install from there. On the last screen you need to choose to run the upgrade wizard.
4. In the upgrade wizard you will check the QIEMariaDB and then run the upgrade.
5. Once the upgrade is complete go to the qie service manager. In the startup tab update the dialect to this: com.qvera.qie.persistence.MariaDB107UnicodeDialect
6. Start QIE and once you can login go to System Administration -> System Configuration. Under QIE Update Status click on check now and then production. It should show 25.2 is available.
7. Click on Download Now and wait for it to download. Once complete click on install now.
8. Once the upgrade is complete you will want to stop the service in the qie service manager.
9. Update the dialect to: com.qvera.qie.persistence.MariaDB1011UnicodeDialect
10. Apply the changes and then start the service.

Answered: Security Cert expiry notifications

Tue, 12 Aug 2025 15:35:39 +0000

Unfortunately, the certificate expiration notifications are not user modifiable at this time. Currently QIE sends notifications when the certificate is 90 days, 30 days, 10 days, or less than 5 days from expiration.

Note that only certificates that have been imported into the Certificates page within QIE will be included in the alerts.

Answered: How do you set up a database connection using windows authentication?

Wed, 06 Aug 2025 21:28:43 +0000

You might see this error on startup when trying to use integratedSecurity:

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. ClientConnectionId:3502a431-3771-478d-a418-034b75fe2136

In a domain environment make sure to work with your Domain Administrator to ensure the following are properly configured:

Run the QIE service as a domain account.

QIE Server Logged in with domain account: The machine might be on a workgroup instead of a domain. Make sure the Windows service or process running your app is logged on as a domain user that SQL Server can trust.

Join the Domain: Ensure the machine running the QIE application is joined to the same Active Directory domain as the SQL Server.

Establish Trust: If the machines are in different domains, an administrator must configure a trust relationship between the two domains. This allows credentials from one domain to be authenticated by the other.

Grant Permissions: Once the trust is in place, the domain account you're using to run the QIE app must be granted appropriate permissions to the SQL Server database.

Check SQL Server Configuration:

Verify that:

SQL Server is configured to accept Windows Authentication
The SQL Server service is running under an appropriate domain account
Mixed mode authentication is enabled if you want to use SQL auth and Windows auth

Answered: Forcing DICOM Association Release

Tue, 08 Jul 2025 17:21:19 +0000

Currently there are no exposed or available methods to close an association between requests.

I have added an enhancement request to add a checkbox to the DICOM connection configuration that would force a new association to be established with every request. Would this satisfy the requirements of your scenario?

Answered: Json to HL7 mapping with array

Mon, 30 Jun 2025 13:05:15 +0000

You can loop through the JSON array and add the elements to your HL7 like this:

First we set up the HL7 message object:

message = qie.createHL7Message();

Then we loop through the AIG array, adding each element to the HL7 (in the example below, I've only added the "setId" element, but you can extrapolate how to add additional fields)

for (var i = 1; i <= source.getCount('/AIG/[]'); i++) {
   message.addChild('/', 'AIG', 'AIG|', i);
   message.setNode('AIG-1', source.getNode('/AIG/[' + i + ']/setId'), i);
}

Answered: Can a NTE immediately follow a ORC in HL7? If not, how do I remove it?

Tue, 17 Jun 2025 17:10:36 +0000

Yes a NTE is valid after A ORC segment. However some systems do not accept it. You can use the following mapping that uses a regex to remove them.

var nteRemoved = (message.getNode("/") + '').replace(/(ORC.*\r)(NTE.*\r)+(OBR.*)/gm,'$1$3');
message.setNode('/', nteRemoved);

Answered: What are parameter maps and how do I use them.

Thu, 12 Jun 2025 15:30:02 +0000

ParameterMaps, channelCache, and messageCache in QIE are all key-value variables that let you store and retrieve data using a unique key name. The main difference between them is scope and syntax. channelCache stores values shared across the entire channel and is accessible throughout the interface; messageCache stores data specific values for a single message as it moves through the channel; and parameterMaps typically hold named key-value values within a given script or step. While channelCache and messageCache use function-style access like getValue(key) and setValue(key, value), parameterMaps use Java-style methods such as get(key) and put(key, value). Despite the differences in how they're accessed, all three are used to temporarily manage data in the form of key-value pairs during interface execution.

For a list a parameterMap Methods see Java Docs HashMap methods: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/HashMap.html?utm_source=chatgpt.com

Here is a table listing the popular HashMap (parameterMap) methods along with the QIE channelCache and messageCache functions.

Operation	parameterMaps (Methods)	channelCache & messageCache (Functions)
Check if key exists	map.containsKey("key")	channelCache.checkValueExists("key") messageCache.checkValueExists("key")
Get value	map.get("key")	channelCache.getValue("key") messageCache.getValue("key")
Set value	map.put("key", "value")	channelCache.setValue("key", "value") messageCache.setValue("key", "value")
Remove value	map.remove("key")	channelCache.removeValue("key")
Get as boolean	(Use cast or comparison logic)	channelCache.getBoolean("key", defaultValue)
Get as number	Number(map.get("key"))	channelCache.getNumber("key", defaultValue)
Get as date	Use map.get then parse with QIE date functions	channelCache.getDate("key", defaultValue)
Iterate over keys	map.keySet().toArray()
Get size	map.size()
Clear all entries	map.clear()
Contains a Key	map.containsKey(Object key)
Contains a Value	map.containsValue(Object value)
Remove All entries	map.clear()
Returns all key entries	map.keySet()
Returns all Value entries	map.valueSet()
Returns all keys and entries	map.entrySet()

Answered: Global way to handle Error Management Alert Handler Script

Wed, 28 May 2025 21:01:09 +0000

In the "System Configuration" under the "Advanced Settings" There is a checkbox for "Error Management Alert Handler Script".

This script will change how all error emails are handled.

Here is an example of a sample script:

function createModifiedErrorBody (emailOrigin, alertEmail, newError) {
var parameterMap = qie.newParameterMap();
newError = StringUtils.replace(newError, '\r\n', '\r');
newError = StringUtils.replace(newError, '\r', '<br/>');
parameterMap.put('newError', newError);
parameterMap.put('zone', java.lang.String(emailOrigin.zoneName));
parameterMap.put('channel', java.lang.String(emailOrigin.channelName));
parameterMap.put('messageId', java.lang.String(emailOrigin.sourceId));
parameterMap.put('errorCount', java.lang.String(emailOrigin.errorCount));
parameterMap.put('threadName', java.lang.String(emailOrigin.threadName));
parameterMap.put('date', qie.formatDate('EEE, d MMM yyyy HH:mm:ss z', alertEmail.date));
return qie.evaluateTemplate(qie.getVariable('errorTemplate'), parameterMap, 'xml');
}
//todo - implement alert email handling here
//qie.sendEmail('sampleFakeZZZ@NotRealEmailZZZ.com', 'testing', 'zone: ' + emailOrigin.zoneName + ' channel: ' + emailOrigin.channelName + ' body: ' + alertEmail.htmlBody + 'excetpion: ' + exceptionMessage);
if (StringUtils.equalsIgnoreCase(emailOrigin.zoneName, 'Default') && StringUtils.equalsIgnoreCase(emailOrigin.channelName, 'Error Channel1')) {
try{
if (StringUtils.startsWithIgnoreCase(exceptionMessage, 'ack error:')) {
exceptionMessage = StringUtils.trim(StringUtils.substringAfter(exceptionMessage, 'ack Error:'));
}
var errorHl7 = qie.parseHL7String(exceptionMessage);
errorHl7.removeFirstNode('ERR');
sendOriginalEmail = false;
var emailBody = createModifiedErrorBody (emailOrigin, alertEmail, errorHl7.getNode('/'));
qie.sendEmail(alertEmail.to, alertEmail.subject, emailBody);
// var emailAttachments = qie.newEmailAttachmentMap();
// qie.addEmailAttachment(emailAttachments, 'bodyHtml', alertEmail.htmlBody);
// qie.sendEmail('sampleFakeZZZ@NotRealEmailZZZ.com', 'new error', errorHl7, emailAttachments);
} catch (e) {
qie.sendEmail('sampleFakeZZZ@NotRealEmailZZZ.com', 'error', e);
}
} else {
sendOriginalEmail = true;
}
//To send the original email after this script executes set sendOriginalEmail to true:
//To discard the original email set it to false:
// sendOriginalEmail = false;
//qie.sendEmail('sampleFakeZZZ@NotRealEmailZZZ.com', 'testing', 'this is a test');
//NOTE: If this script throws an exception the original email will be sent and a new
// email will be created and sent to administrators with the script exception.

Answered: Can Qvera connect using Microsoft SQL using Manged Idenity (Passwordless login)

Thu, 15 May 2025 20:38:45 +0000

QIE does support connecting to a Azure SQL db that is setup using Managed Identity for authentication.

This is how you connect to a DB in the Database Connection:

1. Select the Microsoft SQL Server as the Driver
2. Enter the Client ID from the managed Identity in the Username field
3. Check the "Manullay set the Connection URL" box
4. Use the following template for the connection URL:

jdbc:sqlserver://{sqlServerName}.database.windows.net;databaseName={dbName};encrypt=false;;Authentication=ActiveDirectoryManagedIdentity

This is the setup for using the managed identity as the QIE Database (Requires version 25.2 or higher):

1. Update the qie service manager or qie.service with the following java options. Note: spaces have been added for page formatting. These need to be removed when pasted into qie.service or start.sh:

-Dconnection.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver \
-Dconnection.url=jdbc:sqlserver://{serverName}.database.windows.net:1433; databaseName{dbName};Authentication=ActiveDirectoryManagedIdentity; encrypt=true;trustServerCertificate=true; \
-Dhibernate.dialect=com.qvera.qie.persistence.SQLServer2022UnicodeDialect \
-Dconnection.username={clientIdFromManagedIdentity} \
-Dconnection.ignorePassword=true \

Answered: Getting an error when using a String variable for the public key qie.pgpEncryptBytesNoSig

Thu, 08 May 2025 20:44:52 +0000

Using qie.getVariable() returns an object, rather than the String that qie.pgpEncryptBytesNoSig() is expecting. Try using this instead:

var PGPTrilliumPublic = qie.getVariable('PGPTrilliumPublic').getBytes();

Answered: Find all instances of a node reference in a channel

Sat, 19 Apr 2025 15:37:52 +0000

Control+Shift+F (Global Search) within QIE and then type: 1-7.1 (specifying the specific zone by name) . That search will point out all nodes that reference that node path.

Knowledge Base - Qvera - Recent questions and answers

Answered: What is the construct of a QIE HPATH or Node Path?

Answered: What are the basic JavaScript syntax conventions?

Answered: How do I use a JSON array in QIE.

Answered: Can I renumber segments in a HL7 message

Answered: Can you review all errored messages and identify the most common patterns

Answered: What is the qie.addTimeToChannelStats function and how do you use it?

Answered: What is table-split or 'Use individual tables for channel'?

Answered: Can QIE do recursive subdirectory scanning for File, Network Share, and FTP Sources?

Recursive Subdirectory Scanning for File, Network Share, and FTP Sources

Overview

How to Configure It

What Changes When It Is Enabled

Source-Relative Example:

Archiving Behavior

Example

Notes

Archive Exclusion When Recursive Scanning Is Enabled Example

Answered: How to use source.getFileDirectory()?

source.getFileDirectory() Code Wizard Function

Overview

Return Value

When to Use It

Example

Relationship to Recursive Sources

Related Functions

Answered: What source metadata node tags are available in QIE?

Source Metadata Node Tags

Overview

Available Tags

Where to Find Them

Common Examples

Why This Matters

Notes and Limitations

Answered: What is a QIE NetFile and when should I use it?

Key Benefits of NetFile

Answered: How do I protect the connection.password for the QIE database so that it is not stored in plain text

Answered: How do I use Channel Cache variables in QIE?

Answered: What is the difference between the Add Inbound Message and Queue Inbound Message?

Answered: Can I set or change the end-of-line (EOL) characters in a message?

Supported Message Types

Answered: What is the Refresh Script, and how is it used?

Answered: HL7 Attachments handling

Answered: Do you need to restart a channel when a global function it uses is changed

Answered: Who is Awkward Al?

Answered: Unable to upgrade database

Answered: Why does the script editor put a period and a space ". " instead of two spaces " " when I type two spaces.

Answered: The memory reported in the "Monitor Server Resources" dialog is less than what is reported by the OS

Answered: does anyone have an example HL7 to xml translation that you're willing to share?

Answered: How do I prepare the MSSQL user for the JDBC 13.x driver?

Step 1 — Identify SQL Server version

Step 2 — Check whether the QIE user already has the permission

Step 3 — Grant the minimum required permission

Summary

Affected

Symptoms you may see

Why this happens:

FAQ

References

See also

Answered: How to get IP from HL7 Connection

Answered: Documentation on using HAPI?

Answered: Why does QIE's postDICOMRequest() method require a DICOM Channel and a DICOM Connection

Answered: How do I update the qieLauncher package?

Window

Linux

Answered: Where can I find information about the different FHIR structures?

Answered: Can I validate a FHIR resource when it is read into QIE

Answered: Where can I find information about converting FHIR from JSON to XML?

Answered: Where do I find information about a DICOM instance UID?

Answered: Does QIE have an official docker image?

Answered: How do I configure my MSSQL Server to use ssl-encryption?

Answered: Where can I find information about the Apache Camel Options available in QIE

Answered: What is the NDJSON Specification

Answered: Does QVERA integration platform support NCPDP 2017071 standard?

Answered: Cannot call property escapeCsv in object [JavaPackage org.apache.commons.lang.StringEscapeUtils].

Answered: What version of the mssql-jdbc_auth-{version} file do I need.

Answered: QIE Build 25.2.1.16482 requires MariaDB 10.4 or greater, or MySQL 8.0 or greater.

Answered: Security Cert expiry notifications

Answered: How do you set up a database connection using windows authentication?