Try it now Login

Message type

UN/EDIFACT MEDPID

Medical product identification message. It is published in 58 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A MEDPID specification
Message
MEDPID
Directory versions
58
Latest
D24A

Sending and receiving

Exchange MEDPID with your trading partners

The specification tells you what a valid MEDPID looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.

Browse integrations Connect MEDPID to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a MEDPID flow with us

Specifications

MEDPID in every directory version

A trading partner names both the message and the directory, for example D00A MEDPID, because the segments differ between versions. Open the one your partner specified.

58 directory versions

Related messages

Messages in the MED set

UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.

MEDPRE UN/EDIFACT message. MEDREQ UN/EDIFACT message. MEDRPT UN/EDIFACT message. MEDRUC UN/EDIFACT message.

Frequently asked questions

What is the MEDPID message?

Medical product identification message. It is one of the UN/EDIFACT message types, identified by the six-letter name MEDPID in every directory version that publishes it.

Which directory version of MEDPID do I need?

The one your trading partner specifies. MEDPID is published in 58 directory versions and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.

How do I send a MEDPID message?

Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.

Sources and further reading