Message Linkage

message linkage overview message linkage requirements and best practices are described in the table below there are four key fields that are used to link messages together, and this linkage allows a software system to connect related messages to each other for example, on an rxrenewalrequest the prescribing system needs to find the original newrx to which the pharmacy is referring this linkage should be done in an automated manner s 210 customers shall support the scenarios in the message linkage section of this guide note ncpdp refers to message linkage as trace number ✅ quality check ensure electronic transactions are populated with the correct traceable elements for message linking when available when this information is not included, human intervention is introduced which brings an additional risk of transcription/matching errors messageid – the unique number assigned to each message this id initiates the electronic linking of subsequent message types relatestomessageid – the messageid of the most recent and relevant message in the workflow rxreferencenumber – the prescription number assigned by pharmacy system this number should be populated on pharmacy initiated messages rxreferencenumber must be populated on rxrenewalrequest, rxrenewalresponse, rxchangerequest, and rxchangeresponse prescriberordernumber – the prescription number created by the prescribing system prescriberordernumber must be populated on all fillable messages for other message types if prescriberordernumber is available, it should be sent the prescriberordernumber or the rxreferencenumber should be used as the primary criteria for matching messages if it cannot be used, the following data in the message should be used relatestomessageid patient demographics medication information prescriber information pharmacy information message linkage example note the following table is an example of message linking this example is not all inclusive and the same methodology applies to other message types newrx rxrenewal request rxrenewal request followup request rxrenewal response (2nd rxrenewal request) messageid 12345 444333 555222 888333 89999 relatesto messageid n/a 12345 444333 555222 888333 prescriber order number rx123 rx123 rx123 rx897 rx897 status/ error/ verify status/ error/ verify status/ error/ verify status/ error/ verify status/ error/ verify messageid 888 77777 999999 555555 111111 relatesto messageid 12345 444333 555222 888333 89999 notes for customers sending a newrx following a benefitresponse (either on demand formulary or real time prescription benefit, whichever is later in the workflow), populate the relatestomessageid with the messageid from the benefitresponse the only exceptions for this are for newrx that is following a newrxrequest a newrx following a cancelrxresponse in the ltpac environment surescripts encourages the use of electronic prescribing messages but also acknowledges situations where alternative means of communication are necessary messages sent electronically will contain a messageid which is later used in the relatestomessageid field of subsequent/related messages however, in instances where there is no messageid (e g , original message sent by fax), the relatestomessageid will not be available to send in electronic messages that follow in these instances, additional matching logic is needed to support subsequent workflows such as rxfill, rxrenewal, resupply, rxchange, and cancelrx long term and post acute care message linkage example note the following table is an example of prescribing system initiated change process message linking newrx cancelrx newrx messageid 12345 444333 888333 relatestomessageid n/a 12345 12345 prescriberordernumber rx123 rx123 rx123a status/error/verify status/error/verify status/error/verify messageid 888 77777 555555 relatestomessageid 12345 444333 888333