More from the engine
you already run.

A six-digit code after the password, for the people who run your engine.

• Codes from an authenticator app in the Administrator and the engine’s API.
• People set it up at their first sign-in and get ten one-time recovery codes.
• Five wrong codes lock that person for 15 minutes. Accounts used by scripts and our Hub need no code and sign in only from the addresses you list.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2.

On licensed Mirth Connect 4.7, it stays off if NextGen’s multi-factor extension is installed.

Give each person the access their job needs.

• Administrator, Developer, Operator and Viewer roles to start, or roles of your own.
• A role can cover all channels or only some channel groups or tags.
• The engine checks every request against the role. Refused actions go to the Event log.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2.

On licensed Mirth Connect 4.7, it stands aside if NextGen’s role extension is installed.

Sign in to the engine with the accounts your IT team already manages.

• Active Directory or LDAP over LDAPS or StartTLS. Plain LDAP is refused.
• Only members of the groups you allow get in. With User Roles, each group gives a role.
• The local admin account keeps its own password, so there is always a way back in.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2.

On licensed Mirth Connect 4.7, it stands down if NextGen’s LDAP extension is installed.

Keep connector certificates in one place and hear about them before they expire.

• TLS 1.3 and 1.2, with client certificates, on HTTP, Web Service, TCP/MLLP and SMTP connectors.
• Import a .pfx or PEM files, or create a key and signing request inside the engine. Private keys stay in the engine.
• Warnings 30, 14 and 3 days before a certificate expires.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2.

On licensed Mirth Connect 4.7, it stays off when NextGen’s SSL Manager is installed.

Take passwords and API keys out of channel settings.

• Stored encrypted with the engine’s own key.
• Channels use them by name, ${secret.NAME} in a connector field or secrets.get('NAME') in a script.
• Values can be added and replaced. Nobody can read them back.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2.

Anyone who can edit channels can still use a secret in a script, so review channel changes as you would any code.

Receive and send FHIR R4 from your channels.

• A FHIR Listener that takes create, update and transaction requests, checks them against R4 and answers with OperationOutcome errors.
• A FHIR Sender that creates, updates, posts transaction bundles and searches on a FHIR server.
• Basic, Bearer or SMART Backend Services sign-in.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2.

It checks structure against R4. Profiles such as US Core are not checked. NextGen’s FHIR connector uses the same connector names, so only one of the two can be installed.

Structured reports you can read in a transformer.

• Measurement, echo, OB and dose reports arrive as readable XML with each finding’s name, value and unit.
• Code templates for HL7 ORU^R01 and FHIR DiagnosticReport.
• Works with the engine’s own DICOM Listener.

Works with Open Integration Engine 4.5.2 and 4.6, BridgeLink and open-source Mirth Connect up to 4.5.2, with the engine’s DICOM connector installed.