Note: Learn more about RALS Orders Interfacing

ADT (Admit Discharge Transfer)

• Patient transactions are sent from the Hospital Information System (HIS) to the RALS System.

• Patient test results are downloaded into the RALS System and may be verified against the ADT data to validate the patient identification and location.

• If ADT validation is active, the patient test results can be set up to automatically upload to the Laboratory Information System (LIS) and/or HIS.

• If this validation fails, the results can be held for evaluation by a POCC level RALS System user.

ADT Assignments

• When using In-Unit Verification, ADT unit locations must be mapped to RALS System locations.

• Below, ADT unit Room 1 is assigned to RALS System location BMH-1South, which is grouped together with BMH-ICU and BMH-Lab.

• This means that tests performed using devices assigned to BMH-1South (or other grouped locations) will have the patient ID verified against the patient encounters received for Room 1, Room 10...

Unit Verification

• This may be turned off for specific RALS System locations by entering #NUV# (No Unit Verification) in the location description field.

• This code is commonly used in Emergency Department locations where ADT may be delayed.

ADT Override

• When a test result fails ADT validation (e.g. a patient test is performed before RALS System receives ADT for the patient), the result can be uploaded using the ADT Override button.

• The ADT override will be customized for your particular LIS.

• If your LIS requires more than one patient identifier, the missing ID will need to be entered into the
  override for it to function correctly.

Sample Status

• Results can be evaluated for certain flags such as “Repeat Test” or “Critical Value,” as configured in
  Evaluation Criteria and Flag Configuration.

• Patient results that don’t meet all the criteria are held on the Flagged Results page with a sample status of Evaluate.

• Results that fail to upload successfully to the LIS are displayed on the Flagged Results page with a
  sample status of Upload Failed.

• When a result is waiting to upload to the LIS, it is shown on the Results Review page as Upload Pending.

• You may also see a sample status of Ack Pending when an acknowledgement has not been received on a bidirectional interface.

• Results on the Flagged Results page will remain there until a POCC releases them.

Common Upload Failures

• Messages that start with “INTF” are generated by the RALS System.
  A few common examples include:

  • “INTF: Client Connection Failed,” “INTF: Commit Acknowledgement Not Received.”

    • The connection to the LIS may be broken.

    • Call RALS System or your LIS Analyst to check the connection.

  • “INTF: Incorrect Number Format,” “INTF: Invalid Patient ID.”

    The result did not meet the requirements defined in the RALS LIS Interface.

    • Correct the patient ID, or contact RALS System if the requirements have changed.

  • “INTF: Incomplete Profile,” “INTF: No Profile.”

    The test performed did not match one of the pre-assigned profiles/panels/batteries defined in RALS System.

    • Contact RALS System to add a profile.

• Messages that start with “ADT” are generated by RALS System when there is an issue validating the patient ID. A few common examples include:

  • “ADT: Invalid Patient ID.” RALS System does not have ADT on the patient entered.

    • Possible solutions include: correct the patient ID and resend; call RALS System or your ADT Analyst to check the connection; call RALS System to troubleshoot.

  • “ADT: Patient Encounter Not Found.” The patient ID is found but the result was run before
    RALS System received the ADT.

    • This often happens in the Emergency dept.

    • In Flagged Results, select View ADT Events to determine if the result is valid for the
      patient, and if appropriate, select Override.

  • “ADT: Location [RALS System Location] vs [Mother Location]/[ADT Unit].” The patient location did not match the meter location mapping at the time of the test.

    • This may be caused by the meter being moved from its assigned location or an incorrect
      ADT assignment (mapping).

    • Possible solutions include: call RALS System if the ADT Assignments (mapping) should be changed; use ADT Override if it is available; relocate the meter to its assigned location.