Integration Engine

Moraph licenses, implements and runs your clinical integration engine on Mirth Connect or Rhapsody, the engines that move HL7 v2 messages, FHIR resources and documents between your EHR, labs, radiology, billing and partners. We build and test each interface, watch the message flows around the clock, and work queued and failed messages with your teams. Your organization decides which data flows where; every interface change is reviewed, approved and recorded.

The problem it solves

Hospitals and health systems depend on dozens or hundreds of interfaces, many built years ago by people who have since moved on. When an ADT feed stops or a lab result fails to file, the first sign is often a clinician asking where the result is. Interface knowledge lives in a few heads, changes are made directly in production, and nobody can say quickly which systems receive which patient data. Meanwhile, FHIR APIs and new partner connections keep being added on top.

Who it’s for

• Hospitals and health systems running Mirth Connect or Rhapsody, or planning to
• Integration and interface teams who are short of people or after-hours cover
• CIOs and IT directors who need a dependable record of every interface
• Privacy and security officers who must account for where PHI flows
• Health information exchanges, labs and physician groups connecting to hospital systems

1. BuildEach new interface starts as a written specification: source, destination, message types, triggers, mappings and what happens when a message fails. Moraph builds it in a development environment and tests it with your sample messages.
2. ReleaseInterfaces move to production through a change request that your change board or interface owner approves, with a planned cutover and a way back.
3. MonitorQueues, error counts, connection status and message volumes are watched continuously by Moraph's follow-the-sun operations team, with thresholds set for each interface's importance.
4. ResolveFailed and queued messages are worked to an outcome. Faults in the interface are fixed by Moraph; faults in source data go back to the sending system's owner, and reprocessing happens only once the fix is agreed.

Interface inventory

Every channel or route recorded with its source, destination, message types, business owner and the PHI it carries.

HL7 v2 messaging

The engine receives, transforms and routes HL7 v2 messages such as ADT, ORM, ORU, SIU, MDM and DFT over MLLP, files and web services.

FHIR interfaces

The engine exposes and consumes FHIR resources, so newer applications and partners can connect alongside existing HL7 v2 feeds.

Mapping and transformation

Code sets, identifiers and message structures translated between systems, with each mapping documented and versioned.

Round-the-clock monitoring

Queue depth, errors, failed connections and unexpected silence on each interface watched by Moraph's operations team.

Error queue management

Failed messages worked to an outcome, with the cause, the fix and any reprocessing recorded.

Controlled releases

Separate development, test and production environments, with every production change approved and recorded.

Runbooks per interface

What each interface does, who owns each end and what to do when it fails, written down rather than remembered.

Message search

Authorized staff can trace a message by patient, encounter or order number to see where it went and when.

Partner connections

Secure connections to labs, HIEs, payers and physician practices set up and documented, with each partner's data scope approved by you.

Upgrade management

Engine, Java and operating system updates planned, regression-tested against your interfaces and applied in agreed windows.

Monthly service review

Volumes, incidents, open changes, recurring errors and upcoming upgrades reviewed with your integration owner each month.

Interface owner

Your lead for integration: approves specifications and changes, and sets priorities

Application analyst

Owns a connected system such as the EHR or lab, and confirms readiness and source-data fixes

Moraph integration engineer

Builds, deploys, monitors and fixes interfaces under the agreed processes

Privacy or security officer

Approves PHI flows and who may view message content, and reviews access

Service desk analyst

Looks up message status to answer clinicians' and staff questions

Auditor (read-only)

Reviews the inventory, changes and audit trail without changing anything

EHR

Admissions, orders, results, documents, scheduling and charges exchanged with your EHR through its standard HL7 v2 and FHIR interfaces.

Laboratory and pathology

Orders to and results from your laboratory information system and reference labs.

Radiology and imaging

Orders, results and report status between the EHR, RIS and PACS.

Revenue cycle

Charges and patient account updates to your billing and revenue cycle systems.

Health information exchanges and partners

Connections to HIEs, physician practices and other partners you approve, over secure transport.

Public health reporting

Feeds such as immunization, electronic lab reporting and syndromic surveillance routed to the agencies your organization reports to.

Single sign-on

Engine and console users sign in through your identity provider where the engine supports it.

IT service management

Incidents and change requests raised in, or linked to, your service management tool.

Business associate agreement

Moraph signs a business associate agreement with you, since running the engine involves access to PHI.

Role-based access

Who can view message content, change interfaces or reprocess messages follows their role and is reviewed periodically.

Encrypted transport and storage

Connections use encrypted transport where the connected systems support it, and stored messages are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Complete audit trail

Changes, approvals, reprocessing and access to message content are logged with the person and time.

Tested releases

Moraph's security testing gates every release of its own tooling, and interface changes go through test before production.

Data residency

Where Moraph hosts the engine, data stays in the region you choose: the United States, the United Kingdom or Australia.

Moraph cloud

The engine runs in Moraph's hosted environment in the United States, United Kingdom or Australia region, with secure connections to your systems.

Your data center or cloud account

Where systems must stay on your network, the engine runs in your environment and Moraph operates it by agreement.

Your existing licence

Where you already license Mirth Connect or Rhapsody, Moraph takes over build and operation, subject to the vendor's terms.

Discovery and inventory

We document every existing interface: source, destination, message types, mappings, owners and the PHI it carries. We need access to the current engine and time with your interface and application teams.

Environment setup

Development, test and production environments are set up in Moraph cloud or your environment, with single sign-on, roles and monitoring.

Migration or takeover

Where you are moving engines or versions, interfaces are rebuilt or migrated and tested against sample messages; where you already run the engine, Moraph takes over operation in stages.

Monitoring baseline

Thresholds for queues, errors and silence are agreed per interface, along with who is called for what.

Runbooks and processes

Runbooks, change approval, emergency change and reprocessing rules are written down and agreed with you.

Cutover and handover

Interfaces move in planned groups with the receiving systems' owners on hand, and the service review rhythm begins.

• Moraph is not the vendor. NextGen Healthcare (Mirth Connect) and Rhapsody own their engines, and their own service commitments, support terms, roadmaps and outages apply.
• Licences are subject to the vendor's terms, which may limit the editions, connectors or environments available to you.
• Moraph does not operate or change your EHR, lab, radiology or other connected systems; interfaces are limited by what those systems expose, and their vendors' work is arranged by you.
• Decisions about which data goes to which system or partner, and the agreements behind them, are your organization's.
• Moraph fixes interface faults but does not correct clinical data in source systems; that stays with the system's owner.
• Clinical follow-up when a result or order is delayed is your organization's responsibility.
• Breach assessments and notifications after a misrouting incident remain your organization's responsibility, with Moraph's support.
• This service manages Mirth Connect and Rhapsody; other integration engines are not included.

• Pick three of your most important interfaces and ask Moraph to document them as they would in discovery
• Review a sample runbook and check that your on-call staff could follow it
• Walk through a change from request to approved production release
• Ask how a silent interface would be noticed and who would be called
• Review the PHI flow register format with your privacy officer
• Check the responsibilities split against your current vendor and support contracts