ConnectHealth: AI EHR Integration Platform (FHIR & HL7)

ConnectHealth v0.3.73 Hotfix 1 Release Notes

This is a stabilization release for ConnectHealth v0.3.73. It adds multi-facility support to HL7 connectivity, closes a password-reset gap, makes data mapping substantially faster, and refines the mapping editor across a wide set of usability and accuracy fixes reported since the v0.3.73 launch.

There are no new sections in the dashboard and no changes to existing workflows, connections, or saved mappings.

HIGHLIGHTS

One HL7 Connection, Many Facilities

A single HL7 connection can now serve multiple sending facilities.

• Share one secure connection across a hospital group -- previously each facility required its own connection and its own VPN tunnel. A connection now accepts a list of sending facilities, and messages from any of them are routed correctly through the same tunnel
• Add facilities as you grow -- enter each facility identifier in the connection's HL7 configuration; add or remove them at any time without disturbing message flow from the others
• Existing connections keep working -- a connection configured with a single facility is carried forward automatically. No reconfiguration and no downtime are required on upgrade
• Clear setup feedback -- the connection screen tells you exactly which routing details are still missing before you save, so a connection is never left in a half-configured state

Faster Data Mapping

The mapping engine now processes roughly 70% more messages per second than in v0.3.73, with the largest gains on the loop-heavy mappings typical of real-world claims and clinical feeds.

• Higher throughput on the same infrastructure -- large batch files and high-volume inbound feeds complete noticeably sooner, with no change to your deployment size or cost
• Identical output -- the transformation results are exactly the same as before. Your saved mappings, templates, and downstream systems are unaffected, and no re-testing of existing mappings is required

Stronger Password-Reset Enforcement

When an administrator requires a user to reset their password, that requirement is now enforced everywhere.

• No way around the reset screen -- previously a user could reach the dashboard by reloading the page or navigating directly to a saved address. Access is now blocked across the entire application until the password is changed
• Recorded in the audit trail -- each blocked attempt is captured as a security event, so the activity is visible to your compliance team
• Genuinely new passwords -- the reset screen rejects a new password that matches the current one

MAPPING IMPROVEMENTS

Claim Accuracy

• Correct payer on institutional and dental claims -- 837I and 837D claims now take the insurer from the claim's payer information rather than the file envelope, so the payer name and identifier match the claim itself instead of the clearinghouse that transmitted it
• Dental procedure codes render cleanly -- a dental procedure code is now emitted as the code alone rather than combined with its qualifier

Working in the Editor

• Accept the suggestions you want -- automatic mapping suggestions can now be accepted or dismissed one row at a time instead of all at once, and a target you map by hand after a run no longer keeps showing a competing suggestion
• Clearer preview -- the live output is labelled as a preview while it is rendering from suggestions you have not accepted yet, so the mapped-field count and the visible output no longer appear to disagree
• Errors are shown, not swallowed -- if an edit to a mapping template produces invalid output, the editor tells you what went wrong instead of quietly showing an empty panel
• Reliable field connections -- connection points on the source and target trees are directly clickable, rows no longer overlap at narrow widths, and selecting a connection reliably targets the one you clicked
• Build out your target structure -- a new field added to a group is placed inside that group, an unused field or group can be deleted once it is no longer connected, and the tree no longer leaves a duplicate row behind when a field's type changes
• Sample data behaves as expected -- "Replace Target Sample" replaces the sample rather than merging into it, the sample buttons read "Add Sample" when there is nothing to replace, resource selections reflect what is actually loaded, and the output refreshes immediately after a sample change
• Your place is remembered -- the editor returns you to the tab you were last working in, the save confirmation no longer covers the Save button, and the output panel keeps a usable width when you resize your browser window
• Honest save state -- an unsaved template edit is shown as unsaved, and you are warned before saving when a row is incomplete

Project and Template Management

• Multiple templates per message type -- a mapping project can now hold more than one template for the same HL7 or X12 message type, so variations of the same message can live side by side
• Names stay unique and readable -- project names and template labels must be unique within their scope, with a clear on-screen conflict message as you type. Project names and descriptions have sensible length limits with a live character counter. Existing projects with longer names continue to save normally
• Deleted projects are flagged -- a workflow whose mapping project has been deleted now reports the problem on the node instead of appearing correctly configured
• More starter samples -- additional patient-update message types were added to the starter sample library

Compliance

• Synthetic-data attestation in the audit trail -- when a user confirms that a sample they are uploading contains no real patient data, that confirmation is recorded as its own distinguishable audit entry for your compliance records

LOGS

• Reliable paging through Application Logs -- paging no longer stalls or skips entries when a burst of events shares the same timestamp, which previously affected high-volume periods most

BUG FIXES AND REFINEMENTS

• Mapping editor presentation -- required fields are marked with an asterisk in the project and template dialogs, the message version field matches the styling of every other dropdown, the template toolbar's Clear button is no longer clipped, example text in new table rows reads clearly as a placeholder, and the Copy button is disabled when there is nothing to copy
• Condition preview accuracy -- numeric comparison values are shown in the table view exactly as they are applied, without misleading quotation marks
• Naming guidance -- the Edit Template dialog suggests an example name instead of repeating the message type code
• Interaction polish -- clicking a source field no longer interferes with the tabs above it, dropdown menus open downward when there is room, and a stale preview response can no longer replace a newer one

MIGRATION NOTES

• HL7 multi-facility -- no action required. Connections configured with a single sending facility are carried forward automatically on upgrade. To serve additional facilities from an existing connection, open its HL7 configuration and add each facility identifier. A connection still requires an incoming address, at least one sending facility, and a sending application before it will route messages.
• Password-reset enforcement -- review automated access. Any account flagged for a required password reset is now blocked from all application access, including programmatic access, until the reset is completed. If you have automation running under such an account, complete the password reset before upgrading.
• Mapping name rules -- new projects and renames only. Project names and template labels must now be unique within their scope, and names and descriptions have length limits. Existing entries that exceed the limits continue to save unchanged; the rules apply when you create a new entry or rename an existing one.
• Performance improvements are automatic. Mapping output is unchanged, so no template updates, workflow changes, or re-testing are needed.
• No database migration is required for this release. All changes are backward-compatible; existing connections, workflows, and mappings continue to run unchanged.