Pharmacy Module: Pyxis CIISafe Knowledge Portal Export (If on Pyxis version 1.7.3 and lower)

[Deleted User]
[Deleted User] Posts: 0 👋
edited July 1 in BD Pyxis

Version: 1

Release Date: Jan 31, 2023


Pyxis CIISafe data is only exportable via the BD Knowledge Portal reporting portal. BD Knowledge Portal does not currently support automated data transfer to third-party systems, so ControlCheck Pharmacy Module users will need to download the Pyxis CIISafe data from BD Knowledge Portal on whatever cadence your hospital's policies and procedures dictate. Once downloaded to the user's computer, that data can be uploaded to ControlCheck to be reconciled with other source system data.

💡 Depending on your hospital’s settings for ControlCheck, data from your other source systems, such as wholesaler purchasing data, will be held in quarantine until the appropriate timeframe worth of CIISafe data is also uploaded to ControlCheck.

What is needed for Pre-Implementation and Data Validation

Your ControlCheck implementation team will need three months of historical data to complete the data validation exercise. Please coordinate with your implementation specialist.

File Requirements

  • Files must be formatted as .csv that conforms to RFC 4180 and utilize UTF-8 for character encoding.
  • File size should not exceed 50 MB
  • The file name should follow the schema and can only contain letters, numbers, and underscores.
    • bluesight_IDNname_hospitalname_pyxis_c2_eventdate.csv

Running the Knowledge Portal Report

  1. Log in to CareFusion Analytics.
  2. Launch Knowledge Portal.
  3. If you are a single facility site, you will not see an option to select Facility Group or Facility, and you can move on to the next step to run the report. If you are a multi-facility site, you’ll want to make sure the View Type is set to Facility Group and that the facilities you want to include are selected.
  4. Click on “Run a Report”.
  5. Click on the “All Transaction Activity Detail” Report.
  6. Set the appropriate date range, ensure only CII Safe is selected, and click Run.
  7. On the results page, click on Export and select CSV (All columns) as the export type. Optional: From the report results page, you can also save the report to make it easier to run in the future by clicking on the Save to My Reports button.

Uploading the CIISafe data to ControlCheck

  1. After exporting the report to CSV and saving it to your computer, you must log into ControlCheck to upload it. First, go to, click on the Upload navigation menu, and then the Upload Files submenu.
  2. Drag and drop the CSV file you downloaded from Knowledge Portal or click “Choose files” to select the appropriate file on your computer.
  3. Assuming the corresponding dataset from the other source systems (e.g. wholesaler invoice data) has already been uploaded to the system either manually or automatically, ControlCheck will begin processing the CIISafe data. The amount of time will largely depend on how much data there is to process. Once complete, however, any variances can be reviewed in the Pharmacy Module Audit Table.


  • maryryan
    maryryan Posts: 1 👋

    Thank you for providing an update on the processing of CIISafe data within ControlCheck. It's great to know that the corresponding dataset from other source systems has been successfully uploaded to the system, either through manual or automatic means. The transparency in this data integration process is crucial for ensuring accurate and efficient analysis.

    Understanding that the processing time for CIISafe data depends on the volume of information, it's commendable that ControlCheck is equipped to handle this variability. The emphasis on reviewing any variances in the Pharmacy Module Audit Table post-processing is a key feature. This step not only ensures data accuracy but also allows for proactive identification and resolution of any discrepancies, contributing to the overall integrity of the information.

    Efficient data processing and thorough auditing are vital components in the healthcare landscape, especially when dealing with complex datasets. It's reassuring to see ControlCheck addressing these aspects, which are instrumental in facilitating informed decision-making and maintaining compliance.

    Looking forward to continued updates on the progress and effectiveness of ControlCheck in optimizing and ensuring the accuracy of healthcare data.

    Best regards, Mary Ryan