Administration
Roles and permissions in Integration Engine
Each role in Integration Engine: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Integration Engine as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Integration Engine. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Mirth / Rhapsody as part of the managed service.
Roles
Interface owner
Integration manager, interface team lead, director of application services. Owns the integration program on your side: decides what gets built, approves changes and holds Moraph to the agreed service.
- Sees: The full interface inventory with owners and status; Open requests, changes, incidents and their history; Monthly service review reports
- Does: Prioritizes interface requests; Approves specifications and production changes; Agrees maintenance windows for upgrades; Assigns application owners to each interface; Chairs the monthly service review
- Cannot: Make production changes outside the release process; Approve access to message content on the privacy officer's behalf
- Approvals: Approves specifications, production changes and maintenance windows; urgent changes can be approved by a delegate you name.
- Notified about: Changes waiting for approval, incidents affecting important interfaces, and upgrade plans.
Application analyst
EHR analyst, lab systems analyst, radiology systems analyst, revenue cycle systems analyst. Represents a connected system: confirms what it sends and expects, and fixes source data when messages fail because of it.
- Sees: Interfaces that touch their system; Errors and incidents involving their system; Specifications and test results for their interfaces
- Does: Provides sample messages and test accounts; Confirms the receiving system is ready for a change; Corrects source data and asks for reprocessing; Validates test results from their side
- Cannot: Approve production changes unless named as an approver; See message content for interfaces outside their area
- Approvals: Their readiness confirmation is required before a change to their system's interfaces is released.
- Notified about: Errors caused by their system's data, changes affecting their interfaces, and planned downtime.
Moraph integration engineer
Moraph integration engineer, interface developer, operations engineer. Builds and runs your interfaces on the engine, under your approvals and Moraph's change process.
- Sees: Engine configuration, channels and routes; Message queues, errors and logs needed to diagnose faults; The interface inventory and runbooks
- Does: Builds and tests interfaces in development and test environments; Deploys approved changes to production; Triages alerts and works failed messages; Applies engine and platform updates; Keeps documentation and the inventory current
- Cannot: Deploy to production without an approved change, except emergency fixes under the agreed emergency process; Grant engine access to anyone without your approval; Change which partners or systems receive PHI without approval
- Approvals: Their production changes are approved by your interface owner and peer-reviewed within Moraph before release.
- Notified about: Alerts on any monitored interface, approved changes ready to deploy, and vendor security notices.
Privacy or security officer
HIPAA privacy officer, information security officer, compliance officer. Makes sure each data flow has a purpose and an agreement behind it, and that only the right people can see message content.
- Sees: Which systems and partners receive which PHI; Who has access to message content; Access reviews and the audit trail
- Does: Approves new PHI flows to partners; Approves roles that can view message content; Runs periodic access reviews; Leads breach assessments where an interface misroutes data
- Cannot: Change interfaces or engine configuration; Edit the audit trail
- Approvals: Approves new external PHI flows and access to message content.
- Notified about: New partner connections waiting for approval, misrouting incidents, and access reviews due.
Service desk analyst
IT service desk analyst, clinical applications support. Answers questions such as whether an order or result was sent, without changing anything.
- Sees: Message status by order, encounter or patient where their role allows; Open incidents and their status
- Does: Traces a message to confirm delivery; Raises incidents with the details the engineer needs; Updates the caller when an incident is resolved
- Cannot: Reprocess or edit messages; See full message content unless your privacy officer allows it
- Approvals: None; their access is granted by the interface owner and approved by the privacy officer.
- Notified about: Status updates on incidents they raised.
Auditor (read-only)
Internal auditor, compliance reviewer, external assessor under temporary access. Reviews how interfaces are controlled without being able to change them.
- Sees: The interface inventory and PHI flow register; Change records with approvals and test evidence; Access reviews and the audit trail
- Does: Reads and exports records within their scope; Samples changes for approval evidence
- Cannot: Change, approve or reprocess anything; Keep access after its end date
- Approvals: Their access is approved by the interface owner or privacy officer, with a scope and an end date.
- Notified about: Nothing by default.
Engine administrator
Your IT administrator, where you keep administrative access. Holds break-glass or shared administrative access on your side where your policies require it.
- Sees: Engine users, roles and settings; The record of permission changes
- Does: Reviews and removes engine accounts; Uses break-glass access under your procedure; Runs access reports
- Cannot: Bypass the change process for routine changes; Delete audit records
- Approvals: Granting message-content access is approved by the privacy officer.
- Notified about: Access reviews due and break-glass use.
Permissions at a glance
| Action | Intf owner | App analyst | Moraph eng | Privacy | Service desk | Auditor | Admin |
|---|---|---|---|---|---|---|---|
| View interface inventory | View | View | Full | View | View | View | View |
| Request a new interface | Full | Full | – | – | – | – | – |
| Build and test interfaces | – | – | Full | – | – | – | – |
| Approve a production change | Approves | – | – | – | – | – | – |
| Deploy to production | – | – | Full | – | – | – | – |
| Approve a new external PHI flow | – | – | – | Approves | – | – | – |
| Trace message status | View | Own work | Full | View | View | – | View |
| View full message content | – | Own work | Full | – | – | – | – |
| Reprocess failed messages | Approves | Own work | Full | – | – | – | – |
| Grant engine access | – | – | – | Approves | – | – | Full |
| View audit trail | View | – | View | View | – | View | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Moraph engineers build and deploy, but your organization approves: nobody at Moraph moves a change to production or opens a new PHI flow to a partner without your recorded approval, except emergency fixes under the agreed emergency process, which are reviewed afterwards.
- Access to full message content is limited to the people who need it to diagnose faults. Service desk staff see status, not content, unless your privacy officer decides otherwise.
- Engine accounts follow your identity provider's groups, and access reviews list each person's roles for periodic certification by your privacy or security officer.
- Auditors get temporary read-only access with a defined scope and an end date, rather than shared accounts.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.