Transfer of Discrete Data to Cerner

Similar to PDF export from REDCap, the transfer of discrete values also uses DETs and the REDCap API. In this case, the export records API method was used. This method returns the values of the completed assessment fields (eg, PHQ-9) and system variables, such as timestamps. Once the discrete data are retrieved, the web service executes the code to format this information as a comma-separated values (CSV) file that follows a specified convention, as follows: [timestamp].csv for the name and [mrn],[encounter],[uid],[assessment_code],[timestamp], [assessment_field1],[assessment_field2],...,[assessment_fieldN] for CSV content.

UID is a unique identifier of a completed assessment within the REDCap instance generated using the project ID, record ID, instrument code, and visit code. This identifier ensures that the correct form is updated in Cerner if the data in REDCap are modified. At this step, assessment variables are also renamed to be correctly mapped to the corresponding Cerner fields. The CSV file is then written to a directory on a file transfer protocol server. This directory is periodically scanned by a custom Cerner interface, which converts the CSV data into an HL7 unsolicited results (ORU) message. The interface then routes the HL7 to the standard Cerner external systems inbound servers for processing and passes the values into the results view of the chart, where the data are displayed in a table format. Currently, the interface only accepts numerical results, but future updates may include the processing of REDCap data sent in JavaScript Object Notation (JSON) to allow greater flexibility for data import.