Healthcare · Moraph software

Patient Safety & Incident Reporting

Make reporting a near miss easy, and turn every report into learning and action

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Patient Safety & Incident Reporting gives staff a short, non-punitive way to report incidents, near misses and unsafe conditions from any workstation or phone. Reports are triaged by the patient safety team, investigated with root-cause analysis workflows, and tracked through to corrective actions. Event data is captured in a structure that supports AHRQ Common Formats, so you can submit to your Patient Safety Organization and report consistently over time.

The problem it solves

Many hospitals still collect incident reports through forms that take too long to complete, so staff report the serious events and skip the near misses that would have warned of them. Reports land in an inbox, root-cause analyses are run in documents and meeting notes, and corrective actions are tracked in spreadsheets that nobody owns. When the board asks what has changed since a serious event, or a surveyor asks how the hospital learns from errors, the evidence is scattered.

  • Reporting forms are long, so near misses and unsafe conditions go unreported
  • Triage and follow-up depend on one inbox and one person
  • Root-cause analyses and action plans live in separate documents
  • Corrective actions are hard to track to completion and prove effective

Who uses it

  • Patient safety officers and risk managers at hospitals and health systems
  • Quality and performance improvement teams who run root-cause analyses
  • Frontline clinical and support staff who report events
  • Department managers who follow up on events in their area
  • Medical staff leaders, safety committees and boards who oversee the program

Requirements it supports

Patient Safety and Quality Improvement Act of 2005 (42 U.S.C. 299b-21 to 299b-26)Patient Safety and Quality Improvement Rule (42 CFR Part 3)AHRQ Common Formats for Event ReportingCMS Conditions of Participation, quality assessment and performance improvement (42 CFR 482.21)The Joint Commission Sentinel Event PolicyHIPAA Privacy and Security Rules (45 CFR Parts 160 and 164)

The product supports these requirements; meeting them remains your organization’s responsibility.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    Reporting a near miss

    A reporter chooses the event type and answers only the questions for it, in a form built to be finished quickly.

    Near miss · Medication

    Event type
    Near miss: did not reach the patient
    Location
    Example Hospital (fictional), Unit 4 West
    Patient
    Patient 20581 (fictional), selected from EHR
    Medication category
    Anticoagulant
    Caught by
    Pharmacist verification
    Report as
    Named, identity visible to safety team only

    What happened

    • Order entered with a dose for a different weight
    • Pharmacist queried before dispensing
    • Reporter suggests a weight check prompt at order entry
    A reporter chooses the event type and answers only the questions for it, in a form built to be finished quickly.

  2. Step 2

    The triage queue

    The safety team sees every new report, sorted by harm level and age, and routes each to the area involved.

    EventTypeCategoryHarm levelLocationAge
    EV-50213IncidentFallHarm, temporaryUnit 3 East4 hours
    EV-50211Near missMedicationNo harmUnit 4 West6 hours
    EV-50207Unsafe conditionEquipmentNot applicableRadiology1 day
    EV-50202IncidentSurgery or procedureHarm, under reviewOperating rooms1 day
    EV-50196IncidentSkin integrityHarm, temporaryICU2 days
    The safety team sees every new report, sorted by harm level and age, and routes each to the area involved.

  3. Step 3

    Triage decision

    The reviewer confirms the category and harm level, routes the event and records whether it needs a deeper review.

    EV-50202 · Surgery or procedure

    Reported
    Named, by staff member
    Category
    Surgery or procedure (Common Formats)
    Harm level
    Under review
    Routed to
    Perioperative services manager
    Serious-event criteria
    Met, leadership notified

    Next steps

    • Immediate actions recorded by the area manager
    • Root-cause analysis recommended
    • Disclosure status recorded by risk management
    The reviewer confirms the category and harm level, routes the event and records whether it needs a deeper review.

  4. Step 4

    The root-cause analysis

    The analysis brings together the timeline, interviews, contributing factors and causal statements, with approval at the end.

    RCA-0418 · Event EV-50202

    1. Analysis opened and review team assignedPatient safety officer
    2. Event timeline built from report and follow-upFacilitator
    3. Interviews recorded with staff involvedReview team
    4. Contributing factors: handoff process, equipment availabilityReview team
    5. Causal statements and action plan draftedFacilitator
    6. Findings and actions approvedPatient safety officer
    The analysis brings together the timeline, interviews, contributing factors and causal statements, with approval at the end.

  5. Step 5

    Corrective actions

    Each action has an owner, due date and measure, and closes only with evidence that it was done and reviewed.

    ActionOwnerDueStatusEffectiveness
    Standardize handoff checklist for transfers to the ORPerioperative managerSample date 1CompleteMeasuring
    Add equipment check to the pre-procedure huddleOR charge nurseSample date 2In progressNot started
    Train staff on the revised handoff processClinical educatorSample date 3OverdueNot started
    Audit handoff checklist useQuality analystSample date 4Not startedNot started
    Each action has an owner, due date and measure, and closes only with evidence that it was done and reviewed.

  6. Step 6

    Trends for the committee

    Events are counted by category and harm level so the safety committee can see where risk is concentrated.

    CategoryNear missesNo harmHarmUnsafe conditions
    Medication8452611
    Fall931814
    Surgery or procedure12725
    Device or equipment1810127
    Healthcare-associated infection0346
    Events are counted by category and harm level so the safety committee can see where risk is concentrated.

Workflows

The principal workflows

  1. Report

    Any member of staff can report an incident, near miss or unsafe condition in a few structured questions, with the option to report anonymously where your policy allows.

    • Reporter chooses the event type: incident, near miss or unsafe condition
    • Short form asks only the questions for that event type
    • Patient, location and people involved selected rather than typed where possible
    • Reporter adds what happened and what might prevent it
    • Reporter receives an acknowledgment and, if named, later feedback

  2. Triage

    The patient safety team reviews each new report, sets its category and harm level, routes it to the right manager, and decides whether it needs a deeper review.

    • New reports queued by harm level, type and age
    • Safety reviewer confirms category and harm level
    • Report routed to the manager of the area involved
    • Events meeting your serious-event criteria flagged for leadership
    • Decision recorded: manager follow-up, focused review or root-cause analysis

  3. Investigate

    Serious events and patterns are investigated with structured root-cause analysis: a timeline, interviews, contributing factors and causal statements, with a team assigned to the review.

    • Review team and facilitator assigned
    • Event timeline built from the report and follow-up
    • Interviews and documents added to the review
    • Contributing factors classified and causal statements written
    • Findings approved by the patient safety officer

  4. Act and learn

    Each finding gets corrective actions with owners, due dates and a measure of whether it worked. Lessons are shared back with staff and event data is prepared for your Patient Safety Organization.

    • Actions assigned with owners, due dates and a measure
    • Owners update progress and attach evidence
    • Effectiveness reviewed once the measure has data
    • Lessons summarized and shared with the departments involved
    • Event data prepared for submission to your PSO

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Reporter

Any employee, contractor, physician or volunteer with access

Tells the organization about something that went wrong, nearly went wrong, or could go wrong, without having to work out how.

Sees

  • The reporting form for the event type they choose
  • Their own named reports and the status of each
  • Feedback the safety team shares on their reports

Does

  • Reports incidents, near misses and unsafe conditions
  • Reports anonymously where your policy allows
  • Adds information to their own report when asked
  • Reads lessons shared with their department

Cannot

  • See other people's reports
  • Change a report after triage has started, other than by adding information
  • See triage decisions, analyses or harm classifications beyond the feedback shared
Approvals
None; reports are submitted directly.
Notified about
Acknowledgment of each named report, requests for more information, and feedback when the safety team shares it.

Department manager

Nurse manager, department director, unit leader, service line manager

Follows up on events in their area, puts immediate safety measures in place, and carries out the actions agreed.

Sees

  • Reports routed to their area, with reporter identity only where your policy allows
  • Corrective actions they own and their due dates
  • Trends for their area

Does

  • Records immediate actions taken after an event
  • Writes the follow-up for events routed to them
  • Updates progress on actions they own and attaches evidence
  • Shares lessons with their staff
  • Proposes an event for deeper review

Cannot

  • Change the harm level or category set by triage
  • See reports for other areas unless granted
  • Close an action without the evidence your process requires
Approvals
Their follow-up and action closures are reviewed by the patient safety team.
Notified about
Events routed to their area, actions coming due or overdue, and follow-up returned by the safety team.

Patient safety reviewer

Patient safety specialist, risk management specialist, quality nurse

Makes sure every report is read, classified consistently and sent to the people who need to act on it.

Sees

  • All new and open reports within their facilities
  • Reporter identity for named reports
  • Follow-up, analyses and actions on events they triaged
  • Trends across the organization

Does

  • Triages reports and sets category and harm level
  • Routes reports to managers and requests more information
  • Flags events meeting serious-event criteria
  • Reviews manager follow-up and action evidence
  • Prepares event data for PSO submission
  • Writes feedback to reporters

Cannot

  • Approve a root-cause analysis
  • Delete a report; reports can only be marked as duplicate or out of scope with a reason
  • Change a harm level after the analysis is approved without the patient safety officer
Approvals
Decisions to open a root-cause analysis and changes to a serious-event classification are approved by the patient safety officer.
Notified about
New reports, reports with high harm levels, information returned by reporters, and actions submitted for review.

Patient safety officer

Patient safety officer, director of risk management, chief quality officer

Owns the patient safety program: decides on serious events, approves analyses and reports to leadership and the board.

Sees

  • Every report, analysis and action across the organization
  • Serious and sentinel events and their status
  • Program reporting, trends and overdue actions
  • The full audit trail

Does

  • Decides which events need a root-cause analysis
  • Approves analyses, causal statements and action plans
  • Approves PSO submissions
  • Decides what is designated as patient safety work product
  • Prepares committee and board reporting
  • Maintains categories, harm scales and routing rules

Cannot

  • Approve an analysis they facilitated themselves where your policy requires a second approver
  • Edit or delete entries in the audit trail
  • Remove a report from the record
Approvals
Approves analyses, action plans, serious-event classifications and PSO submissions.
Notified about
Serious events as soon as they are flagged, analyses awaiting approval, overdue actions, and actions found not to be effective.

RCA team member

Clinicians, managers and subject-matter experts assigned to a review

Contributes knowledge and judgment to a specific root-cause analysis.

Sees

  • The analyses they are assigned to
  • The event report, timeline and documents for those analyses
  • Their own assigned tasks

Does

  • Adds to the timeline and interview notes
  • Proposes contributing factors and causal statements
  • Comments on draft findings and actions
  • Completes tasks assigned by the facilitator

Cannot

  • See other events or analyses
  • Approve findings or action plans
  • Export analysis documents unless the facilitator allows
Approvals
Their contributions are reviewed by the facilitator and the analysis is approved by the patient safety officer.
Notified about
Assignment to an analysis, tasks due, and meetings scheduled by the facilitator.

Auditor (read-only)

Internal auditor, compliance officer, surveyor or PSO contact (under temporary access)

Reviews how events were handled without being able to change anything.

Sees

  • Events, analyses and actions within the scope granted
  • Program reports and trends
  • The audit trail for records in scope

Does

  • Searches and reads records within their scope
  • Exports records and reports they have been given, with each export logged

Cannot

  • Change, approve or delete anything
  • See reporter identities unless specifically granted
  • Keep access after it expires
Approvals
Their access is approved by the patient safety officer, with a scope and an end date; access to patient safety work product follows your PSO arrangements.
Notified about
Nothing by default.

Administrator

Application administrator, IT systems analyst

Manages users, facilities, locations and integrations, without access to the content of events.

Sees

  • Users, roles, facilities and location lists
  • Integration status
  • The record of permission changes

Does

  • Adds and removes users, or maps them from single sign-on groups
  • Assigns roles and facility scopes
  • Maintains location and department lists
  • Runs access review reports

Cannot

  • Open reports, analyses or actions
  • See reporter identities
  • Grant themselves a patient safety role without the patient safety officer
Approvals
Role changes that grant access to reports or analyses are approved by the patient safety officer.
Notified about
Integration failures, access reviews coming due and accounts not used for a period your policy sets.

Permissions at a glance

ActionReporterManagerSafety reviewSafety officerRCA memberAuditorAdmin
Submit a reportFullFullFullFullFullNo accessNo access
View reportsOwn work onlyOwn work onlyFullFullOwn work onlyView onlyNo access
See reporter identityOwn work onlyNo accessFullFullNo accessNo accessNo access
Triage and set harm levelNo accessNo accessFullFullNo accessNo accessNo access
Write manager follow-upNo accessOwn work onlyFullFullNo accessNo accessNo access
Open a root-cause analysisNo accessNo accessNo accessApprovesNo accessNo accessNo access
Work an analysisNo accessNo accessFullFullOwn work onlyView onlyNo access
Approve findings and action planNo accessNo accessNo accessApprovesNo accessNo accessNo access
Update and close actionsNo accessOwn work onlyApprovesFullNo accessView onlyNo access
Approve PSO submissionNo accessNo accessNo accessApprovesNo accessNo accessNo access
View audit trailNo accessNo accessView onlyView onlyNo accessView onlyView only
Manage users and rolesNo accessNo accessNo accessApprovesNo accessNo accessFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Reporting is open to everyone, but reading reports is not: reporters see only their own, managers see their area, and reporter identities are limited to the patient safety team.
  • Roles are configured with you during implementation. You can rename them, add custom roles, and limit them by facility, department or event type.
  • Every permission change is recorded with who made it and when, and access review reports list each person's roles for periodic certification by the patient safety officer.
  • Staff sign in through your identity provider, and roles can follow its groups. RCA team members see only the analyses they are assigned to, and auditors get temporary read-only access with a defined scope and an end date.

Features

What it does

Short reporting form

Questions change with the event type, so reporters answer only what applies, from a workstation, tablet or phone.

Near misses and unsafe conditions

Events that did not reach the patient and hazards that have not yet caused one are reported and tracked as first-class events.

Anonymous and confidential reporting

Staff can report anonymously where your policy allows, and named reporters' identities are visible only to the roles you choose.

Common Formats structure

Event categories, harm scales and data elements organized to support AHRQ Common Formats, so reports can be aggregated and submitted to a PSO.

Triage queue

New reports sorted by harm level, type and age, with routing rules that send each to the manager of the area involved.

Root-cause analysis

Structured reviews with a timeline, interviews, contributing factor classification and causal statements, following the method your organization uses.

Corrective action tracking

Actions with owners, due dates, evidence and an effectiveness measure, tracked to completion and reviewed.

Serious event alerts

Events meeting your serious-event or sentinel-event criteria flagged to leadership as soon as they are triaged.

Patient safety work product

Reports and analyses can be designated as patient safety work product within your patient safety evaluation system, with access limited accordingly.

Reporter feedback

Named reporters are told what happened with their report, so staff see that reporting leads to change.

Trends and patterns

Events by category, location, harm level and contributing factor over time, to find the patterns behind single reports.

Complete record

Every report, triage decision, analysis and action kept with the person, time and reason.

Integrations

How it connects to your systems

Connects toHowWhat flows
Electronic health recordPatient lookup from your EHR so reporters select the patient and encounter rather than typing identifiers, using standard interfaces agreed in implementation.In: patient demographics and encounter details for selection.
Staff directoryStaff, departments and managers from your directory or HR system, used for routing and for selecting people involved.In: people, departments, managers and locations.
Patient Safety OrganizationEvent data exported in a structure that supports AHRQ Common Formats, for submission to the PSO you work with.Out: de-identified or PSO-ready event data, as your PSO agreement requires.
Infection preventionEvents relevant to infection prevention shared with your infection control program, including Moraph's Infection Control & Contact Tracing.Out: events flagged as infection-related.
Claims and risk managementEvents that may lead to a claim referred to your risk or claims system, under the access rules your counsel sets.Out: referred events and their status.
Single sign-onStaff sign in through your identity provider (SAML or OpenID Connect).In: user identity and group membership for role assignment.
Work APIEvent, analysis and action data available to your data warehouse and quality reporting tools through the Moraph Work API.Out: events, classifications, analyses and actions.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Staff sign in through your identity provider, so your password and multi-factor policies apply.

Role-based access

What each person can see and do follows their role and facility; reporter identities and analyses are limited to the roles you choose.

Protected health information

Reports can contain patient information, so Moraph signs a business associate agreement and handles that information under it.

Encryption and keys

Client data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Complete audit trail

Every view, change, decision and export is logged with the person and time, and cannot be edited.

Data residency

Data stays in the hosting region you choose: the United States, the United Kingdom or Australia.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Triage queue

For patient safety reviewers

Reports awaiting triage and reports waiting on more information, with harm level, type, location and age.

Break down by
Facility, Event type, Harm level, Age band
Delivered as
Live dashboard
Used for
Making sure every report is read and routed.

Open follow-up by area

For department managers and the patient safety team

Events routed to each area that still need manager follow-up, with their age and harm level.

Break down by
Department, Manager, Harm level, Age band
Delivered as
Live dashboard; scheduled email
Used for
Keeping follow-up moving and showing managers what is waiting on them.

Corrective actions

For action owners, managers and the patient safety officer

Every corrective action with its owner, due date, status, evidence and effectiveness result.

Break down by
Owner, Department, Status, Due date, Source event
Delivered as
Live dashboard; scheduled email; CSV export
Used for
Driving actions to completion and finding those that did not work.

Root-cause analyses in progress

For patient safety officer and facilitators

Open analyses with their team, stage, target dates set by your policy and outstanding tasks.

Break down by
Facility, Facilitator, Stage, Event type
Delivered as
Live dashboard
Used for
Keeping analyses on the timeline your policy sets.

Learning and trends

Events by category and harm

For patient safety committee and quality teams

Reported events by Common Formats category and harm level over time, including near misses and unsafe conditions.

Break down by
Category, Harm level, Facility, Department, Period
Delivered as
Live dashboard; PDF for committee packs; CSV export
Used for
Seeing where harm and risk are concentrated.

Reporting culture

For patient safety officer and department leaders

Report volumes by department and role, the share of near misses and unsafe conditions, and anonymous against named reporting.

Break down by
Department, Reporter role, Event type, Period
Delivered as
Live dashboard; CSV export
Used for
Finding areas where staff may be under-reporting.

Contributing factors

For patient safety committee and quality teams

Contributing factors identified in reviews and analyses, across events, to show common causes.

Break down by
Factor, Category, Facility, Period
Delivered as
Live dashboard; CSV export
Used for
Directing improvement work at causes that recur.

Leadership and board

Serious event summary

For senior leadership and the board

Serious and sentinel events in the period, the status of each analysis, and the actions agreed and completed.

Break down by
Facility, Event type, Status, Period
Delivered as
PDF; scheduled email
Used for
Board oversight of serious events and what changed as a result.

Program summary

For patient safety committee, quality committee and the board

A periodic summary of reporting, triage, analyses, action completion and effectiveness.

Break down by
Facility, Period, Service line
Delivered as
PDF; scheduled email
Used for
Showing how the organization learns from events, as part of its QAPI program.

Compliance and audit

PSO submission log

For patient safety officer

Event data prepared and submitted to your PSO, with dates, record counts and who approved each submission.

Break down by
Submission, Date, Event type, Approver
Delivered as
Live view; CSV export
Used for
Evidencing submissions under your PSO agreement.

Audit trail extract

For internal audit and compliance

Who viewed, changed, approved or exported a selected event, analysis or action, and when.

Break down by
Record, User, Action, Date range
Delivered as
On request in the product; CSV and PDF export
Used for
Answering audit and access questions without rebuilding the history.

Exports, access and evidence

  • Every report can be exported to CSV, and summary and evidence reports to PDF. Reports can be scheduled to arrive by email for the people entitled to see them.
  • Each report can be filtered and the filters saved, so a manager or the patient safety officer can keep their own views. Reports that need a different shape can be built in your own tools from the Work API.
  • Event, analysis and action data is available through the Moraph Work API, with patient safety work product and reporter identities excluded unless your patient safety officer includes them.
  • Reports respect each viewer's role: a manager sees their area, the patient safety team sees the organization, and reporter identities never appear in trend reports.
  • Committee and board reports can be run as of a past date and give the same result each time. Running and exporting a report is itself recorded in the audit trail.

Deployment

Where and how it runs

Moraph cloud

Hosted and operated by Moraph in the United States region. United Kingdom and Australia regions are available for organizations outside the US.

Dedicated environment

A single-tenant environment for health systems whose policies require isolation, scoped in the proposal.

With a managed service

Optionally run alongside Moraph support for form changes, routing rules and new facilities.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Program design

We work with your patient safety officer to agree event types, harm scales, serious-event criteria and how your patient safety evaluation system is defined.

Form configuration

Reporting forms are configured for each event type, kept short, and tested with frontline staff before go-live.

Routing and roles

Locations, departments, managers, routing rules, roles and facility scopes are configured to match your structure.

Analysis method

Root-cause analysis templates, contributing factor lists and action effectiveness measures are configured for the method your organization uses.

Integrations and history

EHR patient lookup, directory feeds and PSO export are set up and tested. Past events can be loaded so trends start from your history.

Training and launch

Reporters, managers, reviewers and facilitators are trained on their own tasks, and the launch is communicated to staff in the way you choose.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not a Patient Safety Organization. The app supports your patient safety evaluation system and prepares data for the PSO you contract with.
  • Whether a report or analysis is privileged as patient safety work product depends on your PSO arrangements and policies, and on advice from your counsel; the app records the designation you make.
  • Supporting AHRQ Common Formats means the data is structured to align with them; the formats are versioned by AHRQ and mapping is reviewed when a new version is adopted.
  • It does not decide harm levels, causes or actions. Your patient safety team classifies events and approves analyses.
  • It does not report to state agencies or accreditors on your behalf. Reports needed for state adverse event reporting or accreditor review are prepared by your team from the data held.
  • It is not a claims management system. Events can be referred to your claims or risk system.
  • Anonymous reports cannot be followed up with the reporter, and their usefulness depends on what the reporter provides.
  • Patient lookup depends on an interface to your EHR; without it, patient details are entered by the reporter.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Ask frontline staff to report a near miss on a phone and a workstation, and listen to what they say about the form
  2. Triage a set of sample reports and check that categories and harm levels match how your team classifies them
  3. Run a sample root-cause analysis from opening to approved action plan
  4. Check how reporter identities and patient safety work product are protected for each role
  5. Review the PSO export with your PSO contact
  6. Confirm role separation: who can triage, approve analyses and close actions

Questions

Frequently asked questions

Is it AHRQ compliant?

AHRQ publishes the Common Formats as a standard for event reporting rather than a certification. The app structures event data to support them, so it can be aggregated and submitted to the PSO you work with.

Can staff report anonymously?

Yes, where your policy allows. Named reporters' identities are limited to the roles you choose and never appear in trend reporting.

Do we need a business associate agreement?

Yes. Reports can include patient information, so Moraph signs a business associate agreement before any is entered.

Can we use our own root-cause analysis method?

Yes. Templates, contributing factor lists and approval steps are configured for the method your organization uses.

How is it priced?

As a subscription, usually measured by the size of the organization, such as facilities or beds, with implementation charged separately. See Working with Moraph for what drives a quotation.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the version you are evaluating.

Next steps

Evaluate Patient Safety & Incident Reporting

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Patient Safety & Incident Reporting guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Patient Safety & Incident Reporting support guide.

Related products