PSOERXI1 INCERX (4477)    REMOTE PROCEDURE (8994)

This RPC receives incoming eRx messages that are in the 2017 script 
format. This RPC replaces PSOERXA1 INCERX, which was the RPC used for the 
10.6 script format.

• XML
  PARAMETER TYPE:   LITERAL
  REQUIRED:   YES
  SEQUENCE NUMBER:   1
  DESCRIPTION:   

  Part of the XML of the incoming eRx message. The XML can be large enough 
  that it is split into multiple parts.
  

• XML3
  PARAMETER TYPE:   LITERAL
  REQUIRED:   NO
  SEQUENCE NUMBER:   10
  DESCRIPTION:   

  This is the third segment of XML for the message.
  

• PRCHK
  PARAMETER TYPE:   LIST
  REQUIRED:   NO
  SEQUENCE NUMBER:   2
  DESCRIPTION:   

  This is the provider check results from the eRx middleware.
  

• PACHK
  PARAMETER TYPE:   LIST
  REQUIRED:   NO
  SEQUENCE NUMBER:   3
  DESCRIPTION:   

  This is the patient check information from the eRx processing hub.
  

• DACHK
  PARAMETER TYPE:   LIST
  REQUIRED:   NO
  SEQUENCE NUMBER:   4
  DESCRIPTION:   

  The drug autocheck information from the eRx processing hub.
  

• STATION
  PARAMETER TYPE:   LITERAL
  REQUIRED:   NO
  SEQUENCE NUMBER:   5
  DESCRIPTION:   

  This is the station number the prescription is being sent to.
  

• DIV
  PARAMETER TYPE:   LITERAL
  REQUIRED:   NO
  SEQUENCE NUMBER:   6
  DESCRIPTION:   

  The division associated with the incoming eRx.
  

• ERXHID
  PARAMETER TYPE:   LITERAL
  REQUIRED:   NO
  SEQUENCE NUMBER:   7
  DESCRIPTION:   

  This the eRx processing hub ID.
  

• ERXVALS
  PARAMETER TYPE:   LIST
  REQUIRED:   NO
  SEQUENCE NUMBER:   8
  DESCRIPTION:   

  These are the human readable codes from the NCIT code list.
  

• XML2
  PARAMETER TYPE:   LITERAL
  REQUIRED:   NO
  SEQUENCE NUMBER:   9
  DESCRIPTION:   

  The second section of XML for the message.