File Overview
6 min
note refer to the panel history file examples docid\ qw9pcerdqimuhtnofcv0w section of this guide to view the example xml code file header (surescripts xml schema) surescripts uses an overall file header for each file, and every file contains a set of messages each message contains a common message header, which is described further in message header (ncpdp xml schema) docid 8 v0n7bpnxo1tiw jcgt in the following diagram, blocks that are solid are mandatory, whereas blocks that have dotted lines are conditional message header (ncpdp xml schema) surescripts uses a message header for all messages for panel, a message header is included in each patient’s rxhistoryresponse the message header, also called the xml wrapper, follows the ncpdp script standard version 10 6 with one addition; the sendersoftware element, which was added in the ncpdp script standard version 10 7 in the following diagram, blocks that are solid are mandatory, whereas blocks that have dotted lines are conditional panel history file the panel history file is created by surescripts and contains an ncpdp rxhistoryresponse for each patient in the patient file that was sent by the customer and successfully passed validation each rxhistoryresponse contains aggregated claim and fill data for one patient all of the rxhistoryresponses are concatenated together to create a single response file for all patients that were listed in the corresponding patient file up to 300 medication records can be sent in a single rxhistoryresponse in the case where the patient has more than 300 medication records, a second rxhistoryresponse will be sent a maximum of two rxhistoryresponses, with up to 600 medication records, is allowed note if a second rxhistoryresponse is sent for the same patient, this is not an error, but an indication that the patient has more than 300 medication records rxhistory response (xml) in the following diagram, blocks that are solid are mandatory, whereas blocks that have dotted lines are conditional note the medicationprescribed element is not used for panel rxhistory response file naming and formats the rxhistory response file naming convention is \<patientpopulationidentifier from the panel management load delimited file>\<surescripts’ assigned id> \<yyyymmddhhmmss> gz example rxhistory response file name aco132patientpopulationa12345 20141204012025 gz