NEWFree ROI Calculators — quantify what prior auth and siloed data are costing your organization.Prior Auth ROI Siloed Data ROI
HL7 v2Segment3 min read

HL7 RMI Segment: Risk Management Incident

Overview

The RMI (Risk Management Incident) segment describes a single risk-management incident associated with a product-experience or adverse-event report. RMI travels inside the Product Experience (PEX) message family and provides a compact, coded statement of what happened, when it happened, and how the incident is classified. Unlike the Product Experience Observation (PEO) segment, which captures clinical observations about the event, RMI focuses on the risk-management facets that drive reporting workflows, regulatory submissions, and internal incident tracking.

RMI is small and structured: only three fields, all coded or timestamped, so receivers can route incidents to the correct queue, trigger regulatory clocks, and aggregate trend data without parsing narrative.

Used in

RMI is carried inside the PEX product-experience message family. Within a PEX, RMI follows the product-experience observation segment PEO and accompanies the patient-and-clinical-context segment PCR so that the incident is connected to the involved product, the observed event, and the relevant clinical history. RMI may also be referenced from internal incident-reporting interfaces that reuse the PEX skeleton.

Field-by-field

The table below lists each field defined for RMI in HL7 v2.5.1 as exposed by the HAPI structures. Length is shown as "—" because the HAPI javadoc does not publish per-field lengths for this segment. Req marks fields the standard requires for the segment to be meaningful. Repeat is "Y" where the javadoc models the field as a repeating accessor. Table # cites well-established HL7-defined tables.

SeqNameData TypeLengthReqRepeatTable #Description
RMI-1Risk Management Incident CodeceR[HL70427]Coded identifier for the incident.
RMI-2Date/Time IncidenttsO[HL70428]When the incident occurred.
RMI-3Incident Type CodeceO[HL70429]Classification of the incident type.

Examples

Minimal

RMI|MED-ERR^Medication Error^HL70427

Fully populated

RMI|MED-ERR^Medication Error^HL70427|20260610083000|WRONG-DOSE^Wrong Dose Administered^HL70429

Annotated breakdown

RMI | MED-ERR^Medication Error^HL70427 | 20260610083000 | WRONG-DOSE^Wrong Dose Administered^HL70429
 |    |                                  |                |
 |    RMI-1 Risk Management Incident Code (CE, HL70427)  RMI-3 Incident Type Code (CE, HL70429)
 |                                       RMI-2 Date/Time Incident (TS)
 RMI  Segment ID

In-context: PEX^P07 reporting a medication-administration incident

MSH|^~&|RM|VORRO|REG|HOSP|20260610090000||PEX^P07^PEX_P07|MSG000020|P|2.5.1
EVN|P07|20260610090000
PID|1||MRN000123^^^VORRO^MR||DOE^JANE^A||19800101|F
PV1|1|I|3W^310^A^VORRO
PES|1|REPORT000777^VORRO|20260610083500|VORRO^Vorro Hospital|RPT^Reporter^L
PEO|1|ADV^Adverse Drug Event^HL70450|20260610083000|||S^Severe^HL70484
RMI|MED-ERR^Medication Error^HL70427|20260610083000|WRONG-DOSE^Wrong Dose Administered^HL70429
PCR|HEPARIN-5000^Heparin 5000 units^L|D^Drug^HL70245|||||||20260610083000|||||A^Actual^HL70242
MSH|^~&|RM|VORRO|FDA|MAUDE|20260610130000||PEX^P07^PEX_P07|MSG000021|P|2.5.1
EVN|P07|20260610130000
PID|1||MRN000789^^^VORRO^MR||SMITH^JOHN^B||19720315|M
PV1|1|I|ICU^004^B^VORRO
PES|1|REPORT000812^VORRO|20260610125500|VORRO^Vorro Hospital|RPT^Reporter^L
PEO|1|DEV^Device Malfunction^HL70450|20260610124500|||M^Moderate^HL70484
RMI|DEV-FAIL^Device Failure^HL70427|20260610124500|INFUSION-OCCLUSION^Infusion Pump Occlusion^HL70429
PCR|PUMP-A1^Infusion Pump Model A1^L|D^Device^HL70245|||||||20260610124500|||||A^Actual^HL70242

Notes for implementers

  • RMI is paired with PEO; the incident in RMI explains the observation in PEO.
  • RMI-2 should align with the event time recorded in PEO; receivers commonly cross-validate the two.
  • RMI-3 narrows RMI-1; senders should use the most specific code available to support trending.
  • Regulatory submissions often gate clocks on RMI-2 and the severity captured upstream in PEO.
  • HAPI exposes all three RMI fields as non-repeating accessors; multiple incidents are conveyed via repeating PEX groups rather than repeating RMI.
← Back to HL7 v2 Guide

Ready to Integrate This Into Your Workflow?

Talk to a Vorro expert about implementing HL7 v2 in your specific environment.

Browse HL7 v2 Guides
HL7 RMI Segment: Risk Management Incident | Vorro Academy | Vorro