QIE 5.0.50 adds parameterized queries and per-endpoint TLS

QIE 5.0.50 is available. This release focuses on how QIE talks to databases and to secured endpoints, along with a change to default text encoding that affects any channel handling non-ASCII patient data.

Parameterized database queries

Source and destination database nodes can bind parameters instead of assembling SQL by string concatenation. Queries are protected against injection and the database can reuse the query plan.

TLS protocol selection per endpoint

An interface can be pinned to the TLS version a partner system requires, so a modern payer API and a legacy device can run on the same engine without a global compromise.

UTF-8 by default for text messages

The Text message type now defaults to UTF-8 rather than ISO-8859-1, so accented and non-Latin characters survive a round trip. Existing channels that relied on the old default should be reviewed.

Static and OAuth2 HTTP headers

Web service connections can carry fixed headers, which is what many vendor REST APIs require for API keys and tenant identifiers.

Storage engine warning

QIE now raises an administrator alert if it finds itself running on the MyISAM engine, which is not transactional.

Published retroactively in September 2026 to complete the release archive. QIE 5.0.50 shipped on 17 September 2021.