Charge Test Plans

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Revision as of 17:09, 11 February 2011 by Jerri.cowper (talk | contribs) (Created page with "Below is a list of test plans you will want to write, using your workflows as a foundation. *Interface testing - when charges are submitted from EHR do they go through the inte...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Below is a list of test plans you will want to write, using your workflows as a foundation.

  • Interface testing - when charges are submitted from EHR do they go through the interface and populate fields in the practice management system? Create a test plan that includes how each transaction goes through the interface. Test each field required to submit a claim.
  • Office Charges - charges that occur druing an office visit; include testing if your organization has the diagnosis populating from the assessed section of your note.
  • Patient List - when charges are entered on patients that are an inpatient status and are not on a surgery schedule. Does a task create when no charges are entered ? Do all preference setting realize the result you are seeking?
  • Surgery Charges - does your organization queue up the charges for the provider? test resequencing the charges by RVU order; does the sequency of diagnosis code match?
  • Charges Reviewed - does your organization utilize the feature of requiring the charges be reviewed prior to submission to the practice management system? if so then include this in your test plans
  • Cancel Surgery - if your organization queues up the charges for the provider, test removing the charge codes and replace with an internal n/c code. Does it clear the encounter?
  • Add local patients - Once a provider adds a local patient and submits the charge are the appropriate task generated by the system? Once the patient is merged does the charge release to the practice management system?
  • Test charge related tasks
  • Test each scenario when an encounter is modified
  • Discount applied - does the expected behavior occur?
  • Additional Info - test each additional info field built to ensure they meet the expectations and needs of your organizaton