Customer-Submitted File Information

this section details the file format which customers will use to submit standard targeted messaging files header information this section specifies and describes the different header fields included in the targeted messaging file, which surescripts uses to populate the message that will be sent to a member's provider field # field name data type code description 1 record type an3 mandatory identifies record type value hdr 2 version/release number an6 mandatory version number of this specification value med001 3 sender id an3 30 mandatory id as assigned by surescripts identifying customer sending the file examples p0100000000001, t0100000000001 4 not used empty element that must be included 5 receiver id an1 30 mandatory id identifying the receiver of the file value s00000000000001 6 not used empty element that must be included 7 transmission control number an1 10 mandatory unique identifier defined by the sender note the sender shall ensure that the combination of the sender id and the transmission control number remains unique for a minimum period of 18 months example 0000001000 8 transmission date dt8 mandatory date transaction was created (d8 – ccyymmdd) example 20251201 9 transmission time tm8 mandatory time transaction was created (hhmmssdd) example 12200101 10 transmission file type an1 3 mandatory identifier telling the type of transaction value pnl 11 transmission action an1 mandatory this is included to be consistent with other types of surescripts files value a 12 extract date dt8 mandatory date that file was created formatted as ccyymmdd example 20251201 13 file type an1 mandatory indicates if the file is meant for processing in either the testing or production environment t =test p =production 14 context code an 64 optional code used to indicate the intended purpose of the message, allowing provider vendor systems to optimize the workflows and routing of messages see section 4 6 for more information default 61357 0 record information this section specifies and describes the targeted messaging file’s different record fields, which surescripts will validate and use to populate the unique messages that will be sent to the targeted provider records that do not meet the base validations are not processed further and are included in the targeted messaging delivery report file with an applicable error code note validation does not test data types, valid value rules or formats all elements are treated as plain text during validation field # field name data type code description 1 record type an3 mandatory identifies the record type value pnl 2 record sequence number n1 10 mandatory unique number for each record in the file 3 source system id an1 70 mandatory the assigning authority id (oid) of the targeted message sender see assigning authority id usage docid 3pykqfjocedfa4ywdyswu for more information about populating this field 4 template id an1 20 mandatory identifier used to specify the targeted message template to be used for a given message available codes are assigned to the customer during implementation 5 clinical rule date dt8 mandatory date the data was entered/captured formatted as ccyymmdd example 20251201 recipient/target provider details 6 npi n10 conditional npi of the member’s provider note required for electronic delivery 7 first name an1 30 conditional first name of the member’s provider 8 last name an1 50 mandatory last name of the member’s provider 9 address, line 1 an1 120 conditional street information in mailing address of member’s provider note required for electronic and postal mail delivery 10 address, line 2 an1 120 conditional space for additional street information in mailing address of member’s provider 11 city an1 50 conditional city in mailing address of member’s provider note required for postal mail delivery 12 state an2 conditional usps state abbreviation for mailing address of member’s provider note required for postal mail delivery 13 zip code n 5/9 conditional zip code in mailing address of member’s provider use the format 99999 or 999999999 note required for electronic and postal mail delivery 14 phone number n10 conditional contact telephone number for the provider receiving the notification note do not include dashes ( ) or parentheses 15 fax number n10 conditional fax number for provider to receive confidential patient information note sender must verify this as a phi secure fax number patient/member details 16 first name an1 30 mandatory member’s first name 17 last name an1 50 mandatory member’s last name 18 address, line 1 an1 120 conditional street information in member’s mailing address 19 address, line 2 an1 120 conditional additional street information in member’s mailing address 20 city an1 50 conditional member’s city mailing address 21 state an2 conditional state in member’s mailing address note use usps state abbreviation 22 zip code n 5/9 conditional zip code in member’s mailing address use the format 99999 or 999999999 23 phone number n10 conditional member’s contact phone number note do not include dashes ( ) or parentheses 24 gender an1 conditional member’s administrative gender code values f = female m = male u = unknown/other 25 member id an1 15 mandatory sender’s internal identifier for the member note to ensure accuracy in patient matching, the patient id value should be consistent with the patient id value shared in other surescripts products 26 date of birth dt8 mandatory member’s date of birth formatted as ccyymmdd supporting evidence details 27 fill date dt8 conditional date the prescription was filled note use format ccyymmdd 28 medication label name an1 256 conditional medication name, strength, and units of measure 29 quantity an1 20 conditional medication quantity being dispensed 30 day's supply n1 3 conditional day’s supply of the medication for the patient 31 prescriber of record first name an1 30 conditional first name of medication prescriber 32 prescriber of record last name an1 50 conditional last name of medication prescriber 33 prescriber of record phone number n10 conditional contact telephone number for medication prescriber note do not include dashes ( ) or parentheses 34 pharmacy name an1 120 conditional dispensing pharmacy name 35 pharmacy phone n10 conditional contact telephone number for dispensing pharmacy note do not include dashes ( ) or parentheses 36 mutually defined an1 35 conditional this is a non required placeholder reserved for user specific elements 37 plan name an1 35 conditional member’s insurance plan name recommendation details 38 short recommendation an1 128 mandatory short description of the recommendation being notified 39 recommendation action an1 35 conditional suggested actions for provider to take against the recommendation 40 recommendation context an1 1024 mandatory extended description of the recommendation being sent 41 supplemental privacy an1 512 conditional a space for additional information on the recommendation being sent note this field is often used as a second paragraph for recommendation context electronic message customizations 42 context code override an0 64 mandatory replaces the context code assigned in the header or the default ( 61357 0 ) with a record specific value 43 subject override an0 256 conditional replaces the default message subject line text with a record specific value default healthcare recommendation 44 message override an0 1024 mandatory replaces the default message body text with a record specific value default a recent review of pharmacy claims has identified the following drug therapy opportunities for your patient please see attachment for details trailer information field # field name data type code description 1 record type an3 mandatory identifies record type value trl 2 total records n1 10 mandatory total number of detail records