Manufacturer Programs Without the Manual Reporting

What they ask for, why files get sent back, and how to automate it so your team stops rebuilding spreadsheets every week. Written for owners, administrators, and directors of operations at infusion centers in a manufacturer or hub data program, with an appendix for whoever builds the files.

Cover of the white paper Manufacturer Programs Without the Manual Reporting, with a diagram showing one order as one line in the status file and each dose given as one line in the dispense file

Get the white paper

PDF, 17 pages, 165 KB

Your details go to Linus Tse at Greyfield Data, who may follow up about the paper. See the privacy policy.

What's inside

What the program asks for, and where it lives

The status, dispense, inventory, and patient files most programs require, what one line in each stands for, and the records in your system each one is built from.

Why files get sent back

The six decisions behind most returned files, why your status and dispense files will never match line for line, and why a blank should stay blank.

Checks before you send, and automating the weekly file

The checks to run before each file goes out, a worked example that compares both files patient by patient, and how to set up a saved report that delivers on a schedule.

Keeping it running, plus an appendix for the builder

A short weekly check that each file arrived and was complete, then field lists, file format, full file versus changes only, and a one-page checklist for whoever builds the files.

Contents

  1. Who this is forpage 3
  2. 1. What they ask forpage 4
  3. 2. Where it lives in your systempage 5
  4. 3. Why files get sent backpage 6
  5. 4. Checks before you sendpage 7
  6. Worked example: patient by patientpage 8
  7. 5. Automating the weekly sendpage 9
  8. 6. Keeping it runningpage 10
  9. For whoever builds the filepage 11
  10. File format, full file or changes onlypage 14
  11. The eight checks in detailpage 15
  12. One-page checklistpage 16