WeInfuse to Snowflake and Power BI
WeInfuse holds your orders, appointments, authorizations and inventory. Putting its reports in one central database lets every Power BI dashboard show the same numbers.
The short answer
What you can load from WeInfuse
- Orders and their status
- Every treatment order, including ones with no appointment yet, which are often the orders waiting on authorization.
- Appointments
- Scheduled and completed visits, location, chair and the drugs given. Times are scheduled times, not check-in or check-out.
- Authorizations and treatment counts
- Current authorization status and approved versus received treatments. This shows where things stand today, not how they got there.
- Inventory on hand
- Drug on hand by location, with history over time, adjustments and purchase orders.
How we set it up
- 1
Pick the reports that matter
We start with the weekly questions: orders and status, completed appointments, authorizations and expiry dates, and inventory on hand.
- 2
Choose how the reports leave WeInfuse
For a few weekly reports, scheduled files are enough. For many reports, several sites or daily updates, a small scheduled program pulls them, using access requested from WeInfuse support.
- 3
Load one central database
Every file or pull lands in Snowflake, where numbers like active patients are defined once and sites are rolled up with one set of rules.
- 4
Check every load and connect Power BI
We record row counts for every load, compare them with WeInfuse, and point Power BI or Sigma at the same tables.
What breaks, and how we handle it
- Orders repeat once per visit
- Reports that mix orders and visits show the order on every visit. Add up dollars across those rows and the total comes out too high. We count each order once.
- Missed sends are not resent
- In our experience a failed scheduled send is not retried, and the next one covers the next week. We overlap date ranges and run a periodic full refresh.
- Files that stop at 5,000 rows
- Scheduled files can be cut short unless “All Results” is chosen. We set it on purpose and check the row count of every file.
- Appointment times in the wrong time zone
- WeInfuse stores scheduled appointment start times in universal time (UTC). We convert them once, using each site’s local time, so visits near midnight land on the right day.
- Patient information in the wrong place
- Every tool and person that touches the data needs approval from your compliance team, and a business associate agreement where patient information is involved. We load only the fields your dashboards use.
Reports we build on top
- Weekly orders, appointments and authorizations scorecard
- Multi-site rollup with one set of definitions
- Expiring authorizations list
- Inventory on hand by location and drug
- Daily load history to see how orders and authorizations changed
Common questions
Can I connect Power BI directly to WeInfuse?
Not as a direct database connection in the setups we have worked with. Schedule WeInfuse reports as files, or pull them automatically into a central database, and point Power BI at that.
Do I need Snowflake to use Power BI with WeInfuse data?
No. A few scheduled files can feed Power BI directly. A central database becomes worth it when you have several sites, many reports, or other systems such as billing or payroll to combine.
Is Greyfield Data part of WeInfuse?
No. WeInfuse is a trademark of its owner; Greyfield Data is independent. We work with the reports and access your WeInfuse account already provides.
How do I know every row made it into the dashboard?
Record row counts for every load and compare them with WeInfuse for the same dates. A job that ran is not proof that every row arrived.
Why do my WeInfuse totals look too high?
Usually because an order repeats once per appointment and something adds up those rows. Count each order once, or start from a report built around orders instead of visits.
Want WeInfuse data you can trust?
Bring the WeInfuse reports that don't match. We'll trace them to the source and show you where to start.