Skip to content

Moraph for clients

Sign in

Getting started

Getting started with Integration Engine

What Integration Engine is for, who uses it, what you need before you start, and your first steps.

Applies to Integration Engine as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

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.

What it is for

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.

  • Interface failures are noticed by clinicians before they are noticed by IT
  • Mappings and routing rules are undocumented and depend on a few people
  • Changes go straight to production without a tested, approved release
  • It is hard to show which systems and partners receive which PHI

Who uses it

  • 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

Before you start

  • Your organization uses Integration Engine as a managed platform from Moraph, under an agreement that covers it.
  • Licences for Mirth / Rhapsody, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for Integration Engine with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.