302 302 Msg #|1|, User A result is released Have results released by a Testing Scenario-2: |2| [DUZ: |3|] is not from GIM with a user with an active account A user will be an active user on the user that does not on VistA. configured in IM system. Auto Release have an Active OR Security setting that not allowed for VistA User Have a tech with an active does not exist on accession UID |4|. Record/Account account on VistA verify the VistA. A test will be result and resend to VistA ordered and run on an instrument. The result should be one that does not pass the rule set and is held in IM Workspace. Log into IM Workspace as the user configured above and release the result. This should cause an error on the Vista side since the user does not exist on VistA. Vista should send an ACK ERR message back to GIM which should appear on the Status screen. 303 303 Msg #|1|, No A result is released Consult the Install Guide verifying user or from GIM without and ensure that the application proxy a user or proxy required proxy users and found. Auto Release user in the valid VistA users are set up not allowed for message. on GIM. accession UID |2|. Alternatively, use LRVERIFY EA in VistA to release manually 304 304 Msg #|1|, User A result is released Need to transmit the |2| [DUZ: |3|] is not from GIM and identity of the actual user a valid user to verify indicated the (VistA DUZ number) or the results. Auto Release performing user application proxy LRLAB, not allowed for was the application AUTO VERIFY. Configured accession UID |4|. proxy LRLAB, AUTO in the COTS driver RELEASE This configuration. application proxy Alternatively, use LRVERIFY is invalid. EA in VistA to release manually
302 302 Msg #|1|, User |2| [DUZ: |3|] is not an active user on the system. Auto Release not allowed for accession UID |4|. A result is released from GIM with a user that does not have an Active VistA User Record/Account Have results released by a user with an active account on VistA. OR Have a tech with an active account on VistA verify the result and resend to VistA Testing Scenario-2: A user will be configured in IM Security setting that does not exist on VistA. A test will be ordered and run on an instrument. The result should be one that does not pass the rule set and is held in IM Workspace. Log into IM Workspace as the user configured above and release the result. This should cause an error on the Vista side since the user does not exist on VistA. Vista should send an ACK ERR message back to GIM which should appear on the Status screen. 303 303 Msg #|1|, No verifying user or application proxy found. Auto Release not allowed for accession UID |2|. A result is released from GIM without a user or proxy user in the message. Consult the Install Guide and ensure that the required proxy users and valid VistA users are set up on GIM. Alternatively, use LRVERIFY EA in VistA to release manually 304 304 Msg #|1|, User |2| [DUZ: |3|] is not a valid user to verify results. Auto Release not allowed for accession UID |4|. A result is released from GIM and indicated the performing user was the application proxy LRLAB, AUTO RELEASE This application proxy is invalid. Need to transmit the identity of the actual user (VistA DUZ number) or the application proxy LRLAB, AUTO VERIFY. Configured in the COTS driver configuration. Alternatively, use LRVERIFY EA in VistA to release manually