📣 We have moved! All of the most up-to-date information on WebPT Products can be found in its new home on WebPT Discover.

Premium Extract Resources Overview

We highly recommend reviewing all documentation referenced below before ingesting the data into your environment. Many tables have specific use-cases or were designed under a specific data model. We've put the documentation into the following recommended order.

  1. Catalog: Reporting and Transactional Tables
    1. This catalog provides a high-level description of available tables.
  2. Standard Extract ER Diagram
    1. Review a diagram showing how the tables with the ‘TYPE’: Standard Extract can be joined. We've also included information on how to cross over with a composite key from WebPT EMR to WebPT Billing tables
  3. Standard Extract Queries (Snowflake)
    1. Common queries showing joins and reports that can be created using only tables with the ‘TYPE’: Standard Extract.
  4. Environment Explanations FAQ
    1. Use these FAQS to better understand how specific workflows can affect resulting data in RevFlow. 
  5. RevFlow Transaction Tables: Detailed Summary
    1. Use this detailed summary to understand the different table relationships with â€˜SOURCE’: WebPT Billing.
  6. RevFlow Field FAQ
    1. Use these field definitions to understand the WebPT Billing data presented.
  7. RevFlow Logic: Top Business Uses
    1. Review common SQL logic for Billing reporting needs.
  8. SQL Logic: Revflow_Ins_Code_to_Name_to_Class
    1. Use this logic to understand how to navigate, for example, from a charge record to the insurance class for that charge.
  9. SQL Logic: Revflow_EOB_to_Billing_Charge_Connect
    1. Ise this logic to join EOB/835 tables to charge records.
  10. SQL Logic: RevFlow Definition of Charge
    1. Calculate charges correctly with this logic.
  11. SQL Logic: RevFlow Definition of Visit
    1. Calculate visits correctly with this logic. 
  12. SQL Logic: RevFlow New Patient
    1. Filter by New Patients
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.