Please enable JavaScript.

Coggle requires JavaScript to display documents.

EDI Electronic Data Interchange exchange structured info agreed…

- - - - clearinghouse sends back
        a PDF sample of the e-bills
      - client approves the sample
  - - - Submitted statements are stored in the e-bills program
      - each charge is updated to point to the image of the bill
      - ecsview
        (partner program that oops calls to show the image of the bill)
    - - Usability issue
        
        using a large date range creates big bills with many pages which increases costs for client
        (client pays per bill: amount for page 1, more for addl pages)
      - Preview the bills before submitting
  - - - We should verify we are getting paid
        from McKesson the correct amount
        We need to audit the bills submitted
        (and # additional pages)
    - - "Flat" file generated from the billing program
        (this is a custom setup)
      - Clients submit the flat file to their vendor
      - any reports / feedback is between the client and vendor
    - - reevaluation of our vendor(s)
        (McKesson)
      - evaluation of potential vendors
- - - - partnercron runs at night
        
        submits batches as needed
        
        submits RT requests for upcoming appointments
      - stay on top of payers/ changes
      - We receive emails from the entities about connection interruptions/restoration that we would like to more automatically communicate to the client.
- - - - how do you standardize Insurance Table
        When IDs are not standardized?