Patient Safety & Incident Reporting

Principal workflows

• 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.
• 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.
• 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.
• 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.

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

Reporting

• Reports awaiting triage and follow-up by area
• Events by Common Formats category and harm level
• Near misses and unsafe conditions as a share of all reports
• Root-cause analyses in progress and their stage
• Corrective actions by status and effectiveness
• Serious event summaries for leadership and the board

Features

• 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

• Electronic health record: Patient lookup from your EHR so reporters select the patient and encounter rather than typing identifiers, using standard interfaces agreed in implementation.
• Staff directory: Staff, departments and managers from your directory or HR system, used for routing and for selecting people involved.
• Patient Safety Organization: Event data exported in a structure that supports AHRQ Common Formats, for submission to the PSO you work with.
• Infection prevention: Events relevant to infection prevention shared with your infection control program, including Moraph's Infection Control & Contact Tracing.
• Claims and risk management: Events that may lead to a claim referred to your risk or claims system, under the access rules your counsel sets.
• Single sign-on: Staff sign in through your identity provider (SAML or OpenID Connect).
• Work API: Event, analysis and action data available to your data warehouse and quality reporting tools through the Moraph Work API.

Deployment

• 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 and privacy

• 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.

Limitations

• 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.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/patient-safety-and-incident-reporting. Purchasing routes and company information: www.moraph.com/how-to-buy.