Patient File Overview

note refer to the patient file load examples docid\ gjiodrskv1uj7lzy4y4if 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 docid\ simnmgk3hla8mddiyzsjt 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