CAQH CORE 153 EDI Payload ID Basics (Connectivity Rule)
The payload ID does not get carried through to the content of the X12 271 response. In the real time usage, the submitter can link the X12 271 response to the payload ID because the X12 271 response in the real time mode is passed within the same communication session used to send the payload ID and requesting the X12 270. In the batch usage, the acknowledging response to the submission is sufficient to record that a particular payload was successfully delivered.
4. Is the payload ID unique for each transaction sent by the Submitter?
No. It is unique to each HTTP message instance and the payload being transported by HTTP.
5. What should be expected from trading partners regarding the Payload IDs, and how it should be used?
An entity should expect to receive a long, possibly alphanumeric, ID from its trading partners and should be able to store that ID and associate it with each X12 real time messages processed from the trading partner through the supported HTTP communication system. From a technical perspective, most submitters will use some sort of globally unique ID or universally unique ID (GUID or UUID) as their payload ID so receivers should allocate a data field that can contain at a minimum the 128 bits required to store a GUID/UUID. The Phase I CAQH CORE Operating Rules do not specify any detailed requirements in this area.