ConnectHealth: AI EHR Integration Platform (FHIR & HL7)

ConnectHealth v0.3.73 Release Notes

HIGHLIGHTS

Universal Data Mapping -- Any Format to Any Format

ConnectHealth now includes a complete data mapping capability, available from the new Mappings section of the dashboard. You can transform healthcare data between HL7 v2, X12 EDI, and JSON/FHIR in any direction, without writing integration code.

• Any source to any target -- HL7 v2, X12 EDI, and JSON/FHIR are supported as both input and output, so a single mapping can turn an HL7 admission message into FHIR, a claim into X12, or JSON back into HL7
• Visual mapping editor -- see your source message and your target structure side by side, drag a line between two fields to map them, and watch the transformed output update live as you work
• Automatic mapping suggestions -- ConnectHealth proposes field matches for you based on curated dictionaries for each format pair, and can attach transformations such as date reformatting or code translation to a suggestion; accept the ones you want and dismiss the rest
• Three ways to work, always in sync -- a visual tree, a spreadsheet-style table, and a template editor are three views of the same mapping, and an edit in one is reflected immediately in the others
• Repeating data handled properly -- repeating segments, arrays, and X12 loops are mapped once and applied to every occurrence, including nested structures
• Conditional mapping -- map a field only when a condition is met, using presence checks, value comparisons, and numeric operators
• Live preview and safety checks -- ConnectHealth warns you before saving if the preview is currently failing or if a mapping row is incomplete, and highlights the exact row that needs attention

Mapping in the Workflow Builder

• A new Mapping node brings your saved mappings into any workflow -- feed it a raw message and it identifies the message type, selects the right mapping, and produces the transformed output in a single step
• No per-node format configuration is required; the node detects the format automatically, or you can pin it to a specific template
• Works directly with inbound HL7 messages from the HL7 In node

Starter Samples and Template Catalog

Getting started no longer requires you to supply your own data.

• A validated library of starter sample messages covering common clinical and payer message types -- admissions, results, orders, prescriptions, referrals, scheduling, immunizations, documents, and charges
• An expanded X12 transaction catalog, now covering ten transaction sets including claim status, prior authorization, premium payment, enrollment, acknowledgements, and both institutional and dental claims
• Load an example with one click in the editor, tailored to the message type you are working with

Large and Complex Files

• Batch file support -- a file containing many messages is split, routed, and rendered message by message, with a clear failure if any single message is malformed rather than silently producing corrupted output
• Multi-transaction X12 files and batch-header HL7 files are both accepted
• Character-set handling -- messages that are not UTF-8 encoded are decoded correctly, preventing loss or corruption of patient data in international and legacy feeds

NEW EHR INTEGRATIONS

Open Dental

ConnectHealth now supports Open Dental, one of the most widely used practice management systems in dentistry.

• Full integration wired into the ConnectHealth workflow engine
• Bring-your-own-key authentication using your existing Open Dental API credentials -- no certificate or key generation required
• Configure a new Open Dental connection through the ConnectHealth dashboard in minutes

UNIFIED LOGS

Application and Audit Logs are now in one place.

• Both log types live under a single Logs section with tab navigation, so you no longer switch between screens to trace an issue
• Application Logs gain date-range filtering, search, and paging through large result sets
• The audit trail continues to record every access and change separately, with its own long-term retention

SECURITY IMPROVEMENTS

• No shared default administrator password -- deployments no longer ship with a built-in default admin credential. You supply the initial administrator password at deployment time, and it is delivered to you through AWS Secrets Manager. See the Migration Notes below for the action required on upgrade.
• Sealed EHR launch credentials -- when a clinician launches ConnectHealth from inside an EHR, the credentials for that session are now sealed with authenticated encryption and exchanged for a short-lived ConnectHealth session token. Embedded launches no longer require an API key to call your workflows.
• Protected error output -- all messages returned by the mapping engine pass through a single sanitizing boundary, so message content and patient data never appear in error responses or previews shown after a failure
• Ongoing penetration testing -- the automated security scanning pipeline was expanded with broader vulnerability coverage and reporting

CONNECTION IMPROVEMENTS

• Embedded launch reliability -- newly created embedded connections now use the correct callback address, resolving a failure when launching from within an EHR; ConnectHealth also tracks which connection in a family is the primary one, keeping embedded launches linked correctly when connections are added, updated, or removed
• Business-to-business keys are editable -- private and public keys on a B2B connection can be changed after the connection is created, and a generated key set now contains the complete key material
• Duplicate connection names are caught as you type, with a clear on-screen message instead of a failure on save
• Credential fields in Settings are protected from browser autofill, so saved browser passwords no longer overwrite keys you are editing

BUG FIXES AND REFINEMENTS

• Mapping editor -- hovering a source field now highlights every target it feeds, dismissed suggestions stay dismissed when you re-run automatic mapping, and a range of layout, spacing, and readability refinements were applied across the editor
• Mapping output -- HL7 and X12 output no longer carries a stray leading blank line, special characters in source values are escaped correctly, and validation no longer flags valid HL7 and X12 field references as errors
• API keys -- creating a key with a name that already exists now shows a clear conflict message, and the key list stays on screen instead of showing a loading error
• Connections -- the Publish button now enables correctly when scopes are selected from the Available Scopes list
• Workflows -- deleting a workflow uses an in-app confirmation dialog, the description is edited from the settings dialog rather than a separate popup, and importing with overwrite preserves the existing workflow identifiers
• Audit Logs -- search now returns the results you expect, table alignment holds when filtering by System in the Who column, and expanded rows reset correctly when paging
• Audit Logs -- workflow imports are recorded with their workflow identifier, and key-service failures are correctly recorded as failures rather than successes
• Session expiry -- a connection you were part-way through creating is recovered after your session expires and you sign back in
• Settings -- moved into the profile menu behind a gear icon, with dark-mode and tooltip improvements
• License activation -- a clearer first-time activation message with step-by-step guidance and a direct link to the AWS console
• Long error messages on the connection test screen are now clamped instead of overflowing the page

MIGRATION NOTES

• Administrator password -- action required. This release removes the shared default administrator password. When you deploy or upgrade, provide the administrator password parameter in the CloudFormation stack; the resulting credential is available from the stack's AWS Secrets Manager output. If your existing deployment still uses the previous default credential, rotate it after upgrading.
• Embedded and EHR launches -- the launch session token is derived from your deployment's configured application secret. Keep that secret set and unchanged across instances; changing it will invalidate any launch sessions that are already in progress.
• Standalone X12 Mapper node removed -- the separate X12 mapper node has been replaced by the unified Mapping node, which handles X12 along with HL7 and JSON. Any workflow that used the old node should be updated to use the Mapping node and a saved mapping.
• Mappings are new -- after upgrading, the Mappings section will be empty until you create your first mapping project. Starter samples and templates are available from within the editor, so no data of your own is needed to try it.
• Logs -- Application and Audit Logs are now served from a single Logs screen; update any bookmarks pointing at the previous separate audit log address.
• Custom mapping templates -- if you have authored your own templates that relied on X12-specific formatting behaviour applying globally, those helpers are now scoped to X12 and must be referenced explicitly.
• No database migration is required for this release. All other changes are backward-compatible; existing connections and workflows continue to run unchanged.