HL7 RMI Risk Management Incident
HL7 field reference RMI fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
RMI carries risk-management incident information.
The standard describes RMI this way: The RMI segment is used to report an occurrence of an incident event pertaining or attaching to a patient encounter.
These segments describe clinical goals, problems, roles, referrals, requisitions, incidents, variances, and resource groupings that sit around the core patient/order/result traffic.
They are most useful when responsibilities, dates, identifiers, and status values are kept explicit. Otherwise they become narrative fragments that are hard to act on.
The v2.5.1 structures show RMI in BAR_P05 - Update account. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
RMI-1 identifies the Risk Management Incident Code for this care-plan or referral workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0427; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RMI-2 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
RMI-3 identifies the Incident Type Code for this care-plan or referral workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0428; many real interfaces narrow that list further, so follow the receiver's implementation guide.