MEDRPT — EDIFACT Medical Service Report Message (D.21B)

The MEDRPT message is the medical service report sent by a healthcare provider (laboratory, imaging facility, specialist) to the prescriber or to another clinical actor: it carries the clinical context, the performed acts, the results, the conclusions and the recommendations. It is the structured back-channel of an exam or consultation in inter-facility healthcare exchanges. This page summarises the segment structure as published by UN/CEFACT for directory D.21B.

Purpose

The MEDRPT message is the medical service report sent by a healthcare provider (laboratory, imaging facility, specialist) to the prescriber or to another clinical actor: it carries the clinical context, the performed acts, the results, the conclusions and the recommendations. It is the structured back-channel of an exam or consultation in inter-facility healthcare exchanges.

This page focuses on the structure published by UN/CEFACT for directory D.21B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file medrpt_c.htm hosted on service.unece.org.

Segment structure

The MEDRPT D.21B message has 137 header entries, 0 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Header

Detail

No segment in this section.

Summary

No segment in this section.

Changes vs D.96A

The MEDRPT message is not published in directory D.96A. No "D.96A → D.21B" comparison line can therefore be produced — see the block below for details.

This message is not published in directory D.96A: it was introduced into the standard after that release and therefore has no historical baseline for comparison. The first directory indexed on ediverse.io sets the reference; later changes are then documented from one release to the next in subsequent directories.

Structural example

Minimal example of an MEDRPT D.21B message with mandatory segments only. The goal is to show the exact version declared in UNH (MEDRPT:D:21B:UN) — not to replicate a full business case.

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL021001'
UNH+1+MEDRPT:D:21B:UN'
BGM+380+MEDRPT-2026-R-0512+9'
DTM+137:20260514:102'
PNA+PAT+1820000007654::ZZZ+++SU:DUPONT+FN:JEAN'
ADR+CD+++75001:PARIS:::FR'
DTM+329:19720312:102'
IRQ+1'
EVE+1'
RSL+TXT++++HEMOGRAM normal — no clinically significant abnormality'
CIN+1'
UNT+10+1'
UNZ+1+CTRL021001'

Common errors

• Misaligned UNH tokens — The UNH+...+MEDRPT:D:21B:UN token must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator.
• Wrong UNT segment count — The value after UNT+ must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use.
• Stale code lists — Between D.96A and D.21B, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.

Related messages

Other versions of this message available on ediverse.io: MEDRPT D.10A, MEDRPT D.16B, MEDRPT D.24A.

← All EDIFACT versions