Patient File Overview
Note: Refer to the Patient File Load ExamplesPatient File Load Examples section of this guide to view the code structure.
Patient File Load Naming
The File Load naming convention is: <CustomerName>_PMA_<YYYYMMDD-XX>.<CompressionFormat>. Surescripts recommends compressing the file prior to transmitting it to Surescripts. The current zip protocols that are supported are gzip, bzip2 and zip.
Example: ACOCompany_PMA_20201204-01.gz
Patient Response File Naming
The naming convention is <InputFileName sans extension>.<sstimestamp>.<sstimestamp>.rsp.
Example: ACOCompany_PMA_20201204-01.20201204012025.20201204012025.rsp
Patient File Load Format
The Patient File Load format will be pipe-delimited (hex7c). Each field is delimited by the pipe character (|). If a pipe-character (hex7c) is used in field data, it must be escaped with \F\. For example, Main | Street would be listed as Main \F\ Street. Each line is to be separated by a new line (hex0A) character.
For detailed field information, refer to the Request File Elements and Patient File Load Examples sections. Validation and Error Code details are available in File Load Validation and Error Code Details .
Note: If mandatory fields are not included, the Patient File Load and/or patient record will not pass validation, and the patient will not be loaded or monitored. All conditional fields must be accounted for, either with data, or a placeholder delimiter.