Skip to main content

Avatar PM 2022 Monthly Release 2022.04.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 80 Summary | Details
Accounts Receivable Management Widget - Financial Classes, Guarantors and Claims
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • View Definition
  • Dynamic Form - View Definition - Select Views
  • NX View Definition
  • Dynamic Form - NX View Definition
  • AR Console Configuration
  • AR Console User Defaults Setup
  • System Task Scheduler
  • Guarantors/Payors
  • Revenue Code Definition (PM)
  • CPT Code Definition (PM)
  • Dictionary Update (PM)
  • Service Codes
  • Program Maintenance
  • Dynamic Form - staff auto assign
  • Practitioner Enrollment
  • Admission (Outpatient)
  • Failed Authentication - Input Dialog
  • Financial Eligibility
  • Client Charge Input
  • Electronic Billing
  • Client Ledger
  • Dynamic Form - Non-Caseload Access
Scenario 1: Accounts Receivable Console - AR List - Search Filters
Specific Setup:
  • Agency uses the 'Accounts Receivable Console'.
  • 'AR Console User Defaults Setup' has been used to give the test access:
  • Select All 'Financial Classes', All 'Guarantors', All 'Treatment Settings', All 'Programs', All 'Client Last Name Initials to be Worked'.
  • The 'Accounts Receivable Console' widget has been added to the tester's home view.
  • Client 1, note the following: The clients last name initial, Note the client’s program, has three unpaid claims,
  • Use 'Client Ledger' to note the 'Guarantor', 'Claim Numbers', 'Date' (service date), 'Date Billed', 'Total amount due for each claim'.
  • A 'Claim-Follow-Up' record has been created for the first claim in the Accounts Receivable Console. Add values to the following fields, noting the values 'Follow-Up Date', 'Next Follow-Up Date', 'Follow-Up Status', 'Comments', 'Followed-Up' = Yes.
  • Client 2, note the following, clients last name initial, the client’s program, has three unpaid claims.
  • Use 'Client Ledger' to note the 'Guarantor', 'Claim Numbers', 'Date' (service date which should be after the service date for Client 1), 'Date Billed', 'Total amount due for each claim'.
  • The 'System Task Scheduler' has been used to process the 'Auto AR Batch Update' after the claims were created.
Steps
  1. Access the 'Accounts Receivable Console'.
  2. Verify that 'User Defaults' is the signed in user.
  3. Verify that 'Financial Classes' has all items selected.
  4. Verify that 'Treatment Settings' has all items selected.
  5. Verify that 'Client Last Name Initials to be Worked' has all items selected.
  6. Verify that 'Guarantors' has all items selected.
  7. Verify that 'Programs' has all items selected.
  8. Verify that 'Aged over # Days' is null.
  9. Verify that 'Claim #' is null.
  10. Verify that 'Client' is null.
  11. Verify that 'Service Date From' is null.
  12. Verify that 'Service Date From' is null.
  13. Verify that 'Service Date To' is null.
  14. Verify that 'Next Follow-Up Date From' is null.
  15. Verify that 'Next Follow-Up Date To' is null.
  16. Verify that 'Exclude Claims with Last Follow-Up Date Within Past # Days' is null.
  17. Verify that 'Claim Follow-Up Record Exists' is null.
  18. Verify that 'Claim Follow-Up Status' is null.
  19. Verify existence of 'Reset Default' button.
  20. Verify existence of 'Search' button.
  21. Deselect the 'Financial Class' for the guarantor of Client 1.
  22. Validate that 'Guarantors' does not contain the guarantor of Client 1.
  23. Deselect the 'Treatment Setting' for the program of Client 1.
  24. Validate that 'Programs' does not contain the program of Client 1.
  25. Click [Reset Default].
  26. Verify that 'Financial Classes' has all items selected.
  27. Verify that 'Treatment Settings' has all items selected.
  28. Verify that 'Guarantors' has all items selected.
  29. Verify that 'Programs' has all items selected.
  30. Deselect the 'Client Last Name Initials to be Worked' for Client 2.
  31. Click [Search].
  32. Verify that no claims for Client 2 are included in the 'Claims with Outstanding Receivables' grid.
  33. Click [Reset Default].
  34. Enter a value in 'Aged Over # Days' that would allow the oldest claim for the test clients to display. The 'Date Billed' determines the number of aged days.
  35. Click [Search].
  36. Validate that the claims for client 1 and the claims for client 2 are included in the 'Claims with Outstanding Receivables' grid.
  37. Click [Reset Default].
  38. Set 'Claim #' to a claim number for Client 2.
  39. Click [Search].
  40. Verify that only that claim for Client 2 is included in the 'Claims with Outstanding Receivables' grid.
  41. Click [Reset Default].
  42. Set 'Client' to Client 1.
  43. Click [Search].
  44. Verify that no claims for Client 2 are included in the 'Claims with Outstanding Receivables' grid.
  45. Click [Reset Default].
  46. Set 'Service Date From' to the fist service date for 'Client 1'.
  47. Set 'Service Date From' to the second service date for 'Client 1'.
  48. Click [Search].
  49. Verify that only claims 1 and 2 are included for Client in the 'Claims with Outstanding Receivables' grid.
  50. Click [Reset Default].
  51. Enter the 'Next Follow-Up Date' from Setup.
  52. Click [Search].
  53. Verify that the first claim for Client 1 is included in the 'Claims with Outstanding Receivables' grid.
  54. Click [Reset Default].
  55. Enter a value in 'Exclude Clients with Last Follow-Up Date Within the Past # Days that would include the 'Follow-Up Date' from Setup.
  56. Click [Search].
  57. Verify that the 'Claims with Outstanding Receivables' grid does not include the first claim for Client 1.
  58. Click [Reset Default].
  59. Set 'Claim Follow-Up Record' Exists' to 'Yes'.
  60. Click [Search].
  61. Click [Reset Default].
  62. Set 'Claim Follow-Up Record' Exists' to 'Yes'.
  63. Click [Search].
  64. Verify that the 'Claims with Outstanding Receivables' grid includes the first claim for Client 1.
  65. Click [Reset Default].
  66. Set 'Claim Follow-Up Status' to value from SETUP.
  67. Click [Search].
  68. Verify that the 'Claims with Outstanding Receivables' grid includes the first claim for Client 1.
  69. Click [Reset Default].
  70. Verify that the following fields are null: 'Aged over # Days', 'Claim #', 'Client', 'Service Date From', 'Service Date To', 'Next Follow-Up Date From', 'Next Follow-Up DateTo', Exclude Claims with Last Follow-Up Date Within Past # Days', Claim Follow-Up Record Exists' and Claim Follow-Up Status'.
  71. Click [Reset Default].
  72. Set "Claim Balance From" to a minimum claim balance amount to filter on.
  73. Set "Claim Balance To" to a maximum claim balance amount to filter on.
  74. Click [Search].
  75. Validate the "Claim Balance" columns in the "Claims with Outstanding Receivables" table contains balances that are between the "Claim Balance From - Claim Balance To" range.
  76. Double click on the column heading for "Claim Balance" column.
  77. Validate the rows are sorted in "Claim Balance" order.
Scenario 2: Accounts Receivable Console - Multi System Codes
Specific Setup:
  • This update should be tested in systems where there are multiple root system codes.
  • Must designate 2 root systems codes. One of the root system codes must be a system code of 98. The other system code must be something other than 98.
  • Each system code must have a guarantor with the same Guarantor ID but with different names, and different financial classes than the other system code.
  • The Accounts Receivable Console must be enabled by enabling the registry setting "Enable Accounts Receivable Management Functionality".
  • The Accounts Receivable Console must be placed on the user's home view.
  • The Accounts Receivable Console must be configured using the "AR Console User Defaults Setup" and "AR Console Configuration" forms.
  • Admit a test client into each system code, and in financial eligibility, assign them the guarantors with the same IDs, but different names and different financial classes.
Steps
  1. Log into the 98 system code.
  2. Using the "Client Charge Input" form, create charge(s) for this system code's test client.
  3. Using "Client Ledger", validate the charge is affiliated with the guarantor from setup.
  4. Using the "Close Charges" form close charges for that client.
  5. Using a program such as "Electronic Billing", turn the charge into a claim for the test client.
  6. Using "System Task Scheduler", schedule an "Auto AR Batch Update" for today in a few minutes.
  7. Sign out of the 98 system code.
  8. Log into the non 98 system code.
  9. Using the "Client Charge Input" form, create charge(s) for this system code's test client.
  10. Using "Client Ledger", validate the charge is affiliated with the guarantor from setup.
  11. Using the "Closed Charges" form, close charges for that client.
  12. Using a program such as "Electronic Billing", turn the charge into a claim for the test client.
  13. Using "System Task Scheduler", schedule an "Auto AR Batch Update" for today in a few minutes.
  14. Using the Accounts Receivable Console, validate the guarantors appear as appropriate when the financial class for the guarantor is selected/not selected.
  15. Validate the claims appear in the "Claims with Outstanding Receivables" if the financial class and/or guarantor is selected in the filters.
Topics
• Accounts Receivable Management • NX
Update 93 Summary | Details
NCPDP Enhancements
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • RxConnect
  • Avatar eMAR
  • Launch RxConnect
  • Compile Inbound HL7 Charge Batch File
  • Post Inbound HL7 Charge Batch File
  • Client Ledger
  • Compile/Edit/Post/Unpost Roll-Up Services Worklist
  • NCPDP Intermediary Authorizations
  • Electronic Billing
Scenario 1: NCPDP enhancements: support added for 'Quantity Dispensed' but limited to Schedule II meds, 'NCPDP Intermediary Authorizations' and ensuring charges are not included when an order was not active
Specific Setup:
  • Avatar must be configured to communicate with RxConnect via Avatar HL7.
  • Configuration must exist for all RxConnect connections.
  • CE2000 must be configured on the server where the application resides, but it must not be started.
  • The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
  • The user logged into the application must have access to the 'NCPDP Intermediary Authorizations' form and the 'SYSTEM.ncpdp_intermediary_auths' table.
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active inpatient episode. (Client A)
  • "Client A" must have an active 'Diagnosis' and must be associated with an NCPDP guarantor.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Create an order for a Schedule II order code (OXYCODONE HCL), ensuring that a 'Frequency Code' of "TWICE A DAY", with a 'Duration' of "28 Days", with a 'Start Date' of "05/01/2022" and a 'Start Time' of "0700".
  3. Create a second order for a non-controlled substance (IBUPROFEN) with a 'Frequency Code' of "AS NEEDED", with a 'Duration' of "30 Days", with 'Start Date' of "05/01/2022" and a 'Start Time' of "0700".
  4. Access the 'Launch RxConnect' form.
  5. Click [Launch RxConnect].
  6. Click the 'RxSummary' tab.
  7. Process the "OXYCODONE HCL" order for "Client A" and receive "Rx#1".
  8. Process the "IBUPROFEN" order for "Client A" and receive "Rx#2".
  9. Close the application and the form.
  10. Validate that "Client A" is selected and click on the 'eMAR' widget.
  11. Set the 'Administration Date' field to "05/01/2022" and click [Refresh].
  12. Validate the "OXYCODONE HCL" order is displayed with "0900" and "2100" in the cells under date columns for "05/01/2022" through "05/28/2022".
  13. Validate the "IBUPROFEN" order is displayed with no scheduled administration times.
  14. Administer the "OXYCODONE HCL" for the exact day at the correct time for "05/01/2022" through "05/30/2022".
  15. Administer the "IBUPROFEN" order for each day between "05/01/2022" through "05/30/2022".
  16. Note: Charges will be batched on a daily basis. The following steps are after the charges have been batched.
  17. Compile and Post the Inbound HL7 Charge Batch File.
  18. Access the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form and compile the worklist for a 'Through Date' of "05/31/2022".
  19. Validate the 'Roll-Up Service Worklist' report is displayed and contains the following:
  20. A 'Date' of "05/01/2022" for the "OXYCODONE HCL" order with a 'Quantity' of "56" and a 'Fill#' of "0" containing two rows for each date ranging from "05/01/2022" through "05/28/2022".
  21. A 'Date' of "05/29/2022" for the "OXYCODONE HCL" order with a 'Quantity' of "4" and a 'Fill#' of "1" containing two rows for each date ranging from "05/29/2022" through "05/30/2022".
  22. A 'Date' of "05/01/2022" for the "IBUPROFEN" order with a 'Quantity' of "28" and a 'Fill#' of "0" containing two rows for each date ranging from "05/01/2022" through "05/28/2022".
  23. A 'Date' of "05/29/2022" for the "OXYCODONE HCL" order with a 'Quantity' of "2" and a 'Fill#' of "1" containing two rows for each date ranging from "05/29/2022" through "05/30/2022".
  24. Post the worklist and close the form.
  25. Close the charges.
  26. Validate that "Client A" is selected and access the 'NCPDP Intermediary Authorizations' form.
  27. Set the 'Intermediary Authorization ID' field to "123ABC".
  28. Select "Intermediary Authorization" in the 'Intermediary Authorization Type' field.
  29. Set the 'Effective Date' field to "01/01/2022".
  30. Search for and select "OXYCODONE HCL" in the 'Select Service' field.
  31. Validate the 'Selected Service(s)' field contains "OXYCODONE HCL" with the checkbox checked.
  32. Set the 'Prescription Number' field to the 'Rx#' received when processing the order, "Rx#1".
  33. Click [Submit].
  34. Validate that "Client A" is selected and access the 'NCPDP Intermediary Authorizations' form.
  35. Validate a pre-display is displayed that contains the previous data entered.
  36. Click [Add].
  37. Set the 'Intermediary Authorization ID' field to "BC".
  38. Select "Not Specified" in the 'Intermediary Authorization Type' field.
  39. Set the 'Effective Date' field to "01/01/2022".
  40. Set the 'Expiration Date' field to "01/01/2023".
  41. Search for and select "IBUPROFEN" in the 'Select Service' field.
  42. Validate the 'Selected Service(s)' field contains "IBUPROFEN" with the checkbox checked.
  43. Validate the 'Prescription Number' field does not contain a value.
  44. Click [Submit].
  45. Access he 'Electronic Billing' form.
  46. Create a claim for "NCPDP" for a date range of "05/01/2022" through "05/31/2022" and click [Process].
  47. Validate the 'Compile Complete' message is displayed and click [OK].
  48. View the report and validate the 'NCPDP Claim Submission Data' report contains the following:
  49. A 'Service Date' of "05/01/2022" for a 'Service' of "OXYCODONE HCL" for 'Rx# (Actual)' of "206" with a 'Fill#' of "0" with a 'Days Supply' of "28" and a 'Quantity Dispensed' of "56".
  50. A 'Service Date' of "05/01/2022" for a 'Service' of "IBUPROFEN" for 'Rx# (Actual)' of "207" with a 'Fill#' of "0" with a 'Days Supply' of "28" and a 'Quantity Dispensed' of "28".
  51. Go back to the main page of the report and click 'NCPDP' Error Report'.
  52. Validate the report contains an 'Error Message' of "OE Order# was no longer active as of the date of service : OXYCODONE HCL - service date: 05/29/2022".
  53. Close the report.
  54. Create a file on the server.
  55. The file created would contain two messages:
  56. The first message is for the "OXYCODONE HCL" order and contains the following:
  57. A value of "56" in the 120th segment for 'Quantity Prescribed', because it is a Schedule II medication.
  58. A value of "1" in the 123rd segment for 'Intermediary Auth Type', which is the code for the value that was selected in the 'NCPDP Intermediary Authorizations' form.
  59. A value of "123ABC" in the 124th segment for 'Intermediary Auth ID', which was entered in the 'NCPDP Intermediary Authorizations' form.
  60. The second message is for the "IBUPROFEN" order and contains the following:
  61. No value in the 120th segment for 'Quantity Prescribed', because it is not a Schedule II medication.
  62. A value of "0" in the 123rd segment for 'Intermediary Auth Type', which is the code for the value that was selected in the 'NCPDP Intermediary Authorizations' form.
  63. A value of "BC" in the 124th segment for 'Intermediary Auth ID', which was entered in the 'NCPDP Intermediary Authorizations' form.
Topics
• HL7 • NX • NCPDP
Update 122 Summary | Details
"Enable Multiple Add-On Code Per Primary Code "
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (CWS)
  • Progress Notes (Group and Individual)
  • Registry Settings (PM)
  • Site Specific Section Modeling Import/Export (CWS)
Scenario 1: 'Site Specific Section Modeling' - Validate 'Add-On' fields enabled/disabled via the "Enable Multiple Add-On Code Per Primary Code" registry setting
Specific Setup:
  • Have a system with a copy of the "Progress Note (Group and Individual)" form, created via the "Create New Progress Note" form. [PNCopy1]
  • Have registry setting 'Enable Multiple Add-On Code Per Primary Code Functionality' set to "N".
Steps
  1. Open form "Site Specific Section Modeling"
  2. Select the "Progress Note (Group and Individual)" form
  3. Select the "Prompt Definition" section
  4. In the "Prompt Definition" grid,
  5. Locate and select the 'Add-On Service' field for edit,
  6. Verify the 'Exclude from Data Collection Instrument' field is disabled
  7. Locate and select the 'Add-On Duration', field for edit,
  8. Verify the 'Exclude from Data Collection Instrument' field is disabled
  9. Locate and select the 'Add-On Service Notes', field for edit,
  10. Verify the 'Exclude from Data Collection Instrument' field is disabled
  11. Locate and select the 'Save Add-On Service Notes' field for edit,
  12. Verify the 'Exclude from Data Collection Instrument' field is disabled
  13. Locate and select the 'Selected Add-On Services' field for edit,
  14. Verify the 'Exclude from Data Collection Instrument' field is disabled
  15. Locate and select the ''Select Add-On Service Entry to Edit/Remove' field for edit,
  16. Verify the 'Exclude from Data Collection Instrument' field is disabled
  17. Locate and select the 'Remove Add-On Service' field for edit,
  18. Verify the 'Exclude from Data Collection Instrument' field is disabled
  19. Close the form
  20. Repeat step 1 for the progress note form copy [PNCopy1]
  21. Validate results are as expected
  22. Open form "Progress Note (Group and Individual)"
  23. Validate fields 'Add-On Service', 'Add-On Duration', 'Add-On Service Notes', Save Add-On Services, 'Selected Add-On Services', 'Select Add-On Service Entry to Edit/Remove' and 'Remove Add-On Service', are not present on the form as expected
  24. Repeat step 3 for the progress note form copy [PNCopy1]
  25. Validate results are as expected
  26. Open form "Registry Settings"
  27. Search for registry setting " 'Enable Multiple Add-On Code Per Primary Code Functionality'
  28. Click to edit the registry setting and set the "Registry Setting Value" field to "Y"
  29. Submit the form
  30. Open form "Site Specific Section Modeling"
  31. Select the "Progress Note (Group and Individual)" form
  32. Select the "Prompt Definition" section
  33. In the "Prompt Definition" grid,
  34. Locate and select the 'Add-On Service' field for edit,
  35. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  36. Locate and select the 'Add-On Duration', field for edit,
  37. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  38. Locate and select the 'Add-On Service Notes', field for edit,
  39. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  40. Locate and select the 'Save Add-On Service Notes' field for edit,
  41. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  42. Locate and select the 'Selected Add-On Services' field for edit,
  43. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  44. Locate and select the ''Select Add-On Service Entry to Edit/Remove" field for edit,
  45. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  46. Locate and select the 'Remove Add-On Service' field for edit,
  47. Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No"
  48. Submit the form
  49. Return to form "Progress Note (Group and Individual)"
  50. Validate fields 'Add-On Service', 'Add-On Duration', 'Add-On Service Notes', Save Add-On Services, 'Selected Add-On Services', 'Select Add-On Service Entry to Edit/Remove' and 'Remove Add-On Service' are now present and enabled on the form, as expected
  51. Repeat step 6 and 7 for the progress note form copy [PNCopy1]
  52. Validate results are as expected
Topics
• Site Specific Section Modeling
Update 126 Summary | Details
Guarantor/Program Billing Defaults - Select Segments To Suppress
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Guarantors/Payors
  • Site Specific Section Modeling (PM)
  • Practitioner Enrollment
  • Practitioner Numbers By Guarantor And Program
  • Admission (Outpatient)
  • Financial Eligibility
  • Dictionary Update (PM)
  • Client Charge Input
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
Scenario 1: Guarantor/Program Billing Defaults - 837 Professional - Select Segments To Suppress
Specific Setup:
  • Site specific Section Modeling:
  • A site specific Practitioner field (SS Treatment Practitioner 1) is set up on the 'Client Charge Input' via site specific section modeling as the Ordering Provider.
  • Check the 'Use As Ordering Provider (837P-2420E)' in the 'Product Custom Logic Definition' field.
  • Please note :The 'Client Charge Input' form use the Practitioner which is specified in the 'Practitioner Enrollment' as the ordering provider.
  • Practitioner Enrollment:
  • Create a new or identify an existing practitioner to be used as an ordering practitioner. Note the Practitioner id, Name, NPI Number, Taxonomy Code.
  • Guarantors/Payors:
  • Identify an existing guarantor or create a new guarantor. Note the guarantor's code/name.
  • Program Maintenance:
  • Identify an existing outpatient program to be used for the client's admission. Note the program code/name.
  • Practitioner Numbers By Guarantor and Program:
  • Create a record using a practitioner, guarantor and program identified above.
  • Service Codes:
  • A professional service code is identified. Note the service code.
  • Dictionary Update:
  • Following loop-segments set up in the 'Other Tabled Files' and dictionary 13150 'Select Segment's to Suppress' Dictionary:
  • 2420E-N3 - Ordering Provider Address (2420E-N3)
  • 2420E-N4 - Ordering Provider City (2420E-N4)
  • 2420E-REF - Ordering ProviderSec. Info (2420E-REF)
  • 2420E-PER - Ordering Provider Contact (2420E-PER)
  • Guarantor/Program Billing Defaults template:
  • Edit an existing template to assign the guarantor identified above. Note the template name.
  • 837 Professional section:
  • Following items are selected in the 'Select Segments To Suppress':
  • 2420E-N3 - Ordering Provider Address (2420E-N3)
  • 2420E-N4 - Ordering Provider City (2420E-N4)
  • 2420E-REF - Ordering ProviderSec. Info (2420E-REF)
  • 2420E-PER - Ordering Provider Contact (2420E-PER)
  • Admission:
  • A new client is admitted in the outpatient program with attending practitioner.
  • Financial Eligibility:
  • The guarantor assigned to the template configured in the 'Guarantor/Program Billing Defaults' is assigned to the client.
  • Diagnosis:
  • An admission diagnosis record is created for the client.
  • Client Charge Input:
  • A professional service is rendered to the client on the admission date. An ordering practitioner is added for these charges.
  • Charges are closed.
  • An interim billing batch is created to include client, services, and guarantor.
Steps
  1. Open the 'Electronic Billing' form.
  2. Compile the 837 Professional for the interim billing batch created in the setup section.
  3. Verify the bill compiles successfully.
  4. Review the dump file.
  5. Verify the segments display the attending provider identification information from the 'Practitioner Enrollment' form.
  6. Close the report.
  7. Close the form.
  8. Open the 'Guarantor/Program Billing Defaults' form.
  9. Go to '837 Professional section'.
  10. Select '2420E-N3 - Ordering Provider Address (2420E-N3)', '2420E-N4 - Ordering Provider City (2420E-N4)', '2420E-REF - Ordering ProviderSec. Info (2420E-REF)' and '2420E-PER - Ordering Provider Contact (2420E-PER)' in the 'Select Segments To Suppress' checklist.
  11. Submit the form.
  12. Open the 'Electronic Billing' form.
  13. Compile an 837 Professional bill for the interim billing batch created in the setup section.
  14. Verify the bill compiles successfully.
  15. Review the dump file.
  16. Locate the 2420E loop. The 2420E loop starts with NM1*DK.
  17. Verify the following segments are suppressed correctly from the 2420E loop of the bill.
  18. 2420E-N3 - Ordering Provider Address (2420E-N3)
  19. 2420E-N4 - Ordering Provider City/State/Zip Code (2420E-N4)
  20. 2420E-REF - Ordering ProviderSec. Info (2420E-REF)
  21. 2420E-PER - Ordering Provider Contact (2420E-PER)
  22. Close the report.
  23. Close the form.
  24. Open the 'Guarantor/Program Billing Defaults' form.
  25. Go to the '837 Professional section'.
  26. Deselect '2420E-N3 - Ordering Provider Address (2420E-N3)', '2420E-N4 - Ordering Provider City (2420E-N4)', '2420E-REF - Ordering ProviderSec. Info (2420E-REF)' and '2420E-PER - Ordering Provider Contact (2420E-PER)' in the 'Select Segments To Suppress' checklist.
  27. Submit the form.
  28. Open the 'Electronic Billing' form.
  29. Compile an 837 Professional bill for the interim billing batch created in the setup section.
  30. Verify the bill compiles successfully.
  31. Review the dump file.
  32. Locate to the 2420E loop. The 2420E loop starts with NM1*DK.
  33. Verify the following segments are not suppressed and included in the 2420E loop of the bill.
  34. 2420E-N3 - Ordering Provider Address (2420E-N3)
  35. 2420E-N4 - Ordering Provider City/State/Zip Code (2420E-N4)
  36. 2420E-REF - Ordering ProviderSec. Info (2420E-REF)
  37. 2420E-PER - Ordering Provider Contact (2420E-PER)
  38. Close the report.
  39. Close the form.
  40. Open the 'Guarantor/Program Billing Defaults' form.
  41. Go to the '837 Professional section'.
  42. Select '2420E-N3 - Ordering Provider Address (2420E-N3)', and '2420E-PER - Ordering Provider Contact (2420E-PER)' in the 'Select Segments To Suppress' checklist.
  43. Submit the form.
  44. Open the 'Electronic Billing' form.
  45. Compile an 837 Professional bill for the interim billing batch created in the setup section.
  46. Verify the bill compiles successfully.
  47. Review the dump file.
  48. Locate the 2420E loop. The 2420E loop starts with NM1*DK.
  49. Verify the following segments are suppressed correctly and not included in the 2420E loop of the bill.
  50. 2420E-N3 - Ordering Provider Address (2420E-N3)
  51. 2420E-PER - Ordering Provider Contact (2420E-PER)
  52. Verify the following segments are not suppressed and included in the 2420E loop of the bill.
  53. 2420E-N4 - Ordering Provider City/State/Zip Code (2420E-N4)
  54. 2420E-REF - Ordering ProviderSec. Info (2420E-REF)
  55. Close the report.
  56. Close the form.
Topics
• 837 Professional • Guarantor / Program Billing Defaults • NX
Update 130 Summary | Details
Guarantor/Program Billing Defaults - Select Segments To Suppress
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Admission
  • Financial Eligibility
  • Client Charge Input (Charge Fee Access and Diagnosis Entry)
  • Client Ledger
  • Create Interim Billing Batch File
  • Practitioner Enrollment
  • Practitioner Numbers By Guarantor And Program
  • Program Maintenance
  • Guarantors/Payors
  • Dictionary Update (PM)
  • Electronic Billing
Scenario 1: Guarantor/Program Billing Defaults - 837 Institutional - Select Segments To Suppress
Specific Setup:
  • Practitioner Enrollment:
  • Create a new or identify an existing practitioner to be used as an attending practitioner. Note the Practitioner id, Name, NPI Number, Taxonomy Code.
  • Guarantors/Payors:
  • Identify an existing guarantor or create a new guarantor. Note the guarantor's code/name.
  • Program Maintenance:
  • Identify an existing inpatient program to be used for the client's admission. Note the program code/name.
  • Practitioner Numbers By Guarantor and Program:
  • Create a record using a practitioner, guarantor and program identified above.
  • Dictionary Update:
  • Add/ Edit dictionary code/value for the 'Attending Provider Specialty Information' segment which is 2310A-PRV.
  • Add/Edit dictionary code/value for the 'Attending Provider Name' segment which is 2310A-NM1.
  • Guarantor/Program Billing Defaults template:
  • Edit an existing template to assign the guarantor identified above. Note the template name.
  • 837 Institutional section:
  • Select Segments To Suppress:
  • The 2310A-PRV (Attending Provider Specialty Information) segment and 2310A segments is available in the checklist.
  • Nothing is selected in the 'Select Segments To Suppress' dictionary
  • Admission:
  • A new client is admitted in the inpatient program with attending practitioner.
  • Financial Eligibility:
  • The guarantor assigned to the template configured in the 'Guarantor/Program Billing Defaults' is assigned to the client.
  • Recurring Client Charge Input:
  • 5-6 room and board charges are rendered beginning on the admission date. A rendering practitioner is added for these charges.
  • Charges are closed.
  • An interim billing batch is created to include client, services, and guarantor.
Steps
  1. Open the 'Electronic Billing' form.
  2. Compile the 837 Institutional for the interim billing batch created in the setup section.
  3. Verify the bill compiles successfully.
  4. Review the dump file.
  5. Verify the NM1*71 and PRV*AT segments display the attending provider identification information from the 'Practitioner Enrollment' form.
  6. Close the report.
  7. Close the form.
  8. Open the 'Guarantor/Program Billing Defaults' form.
  9. Go to '837 Institutional section'.
  10. Select the 2310A-PRV (Attending Provider Specialty Information) segment in the 'Select Segments To Suppress' checklist.
  11. Submit the form.
  12. Close the form.
  13. Open the 'Electronic Billing' form.
  14. Compile the 837 Institutional for the interim billing batch created in the setup section.
  15. Verify the bill compiles successfully.
  16. Review the dump file.
  17. Verify the NM1*71 segments display the attending provider identification information from the 'Practitioner Enrollment' form and suppress the PRV-AT segment to include in the bill.
  18. Close the report.
  19. Close the form.
  20. Open the 'Guarantor/Program Billing Defaults' form.
  21. Go to '837 Institutional section'.
  22. Select the 2310A (Attending Provider Name) segment in the 'Select Segments To Suppress' checklist.
  23. Submit the form.
  24. Close the form.
  25. Open the 'Electronic Billing' form.
  26. Compile the 837 Institutional for the interim billing batch created in the setup section.
  27. Verify the bill compiles successfully.
  28. Review the dump file.
  29. Verify the NM1*71 segment and PRV*AT segments are suppressed and not included in the bill.
  30. Close the report.
  31. Close the form.
Topics
• 837 Institutional • NX
Update 140 Summary | Details
Diagnosis - 'SearchDiagnosisCodes' web service
Scenario 1: Diagnosis - Validate the 'SearchDiagnosisCode' web service
Steps
  1. Access SoapUI for the 'DiagnosisV2' - 'SearchDiagnosisCodes' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired diagnosis search term in the 'ClinicalSearchTerm' field.
  6. Click [Run].
  7. Validate the 'SearchDiagnosisCodeResult' field contains all related diagnosis codes.
Dictionary Update - 'Pregnancy Status' dictionary
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Women's Health History
  • CareFabric Monitor
  • Dictionary Update (PM)
Scenario 1: Women's Health History - Validate the 'PregnancyCreated' and 'PregnancyUpdated' SDK events
Specific Setup:
  • The following extended dictionaries must be defined for the "(357) Pregnancy Status" PM dictionary values:
  • (70492) Clinical Status - Pregnancy (FHIR)
  • (70493) Verification Status (FHIR)
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Women's Health History' form.
  2. Enter the desired date in the 'Assessment Date' field.
  3. Enter the desired date in the 'Pregnancy Start Date' field.
  4. Select the desired value in the 'Pregnant Status' field.
  5. Click [Submit].
  6. Access the 'CareFabric Monitor' form.
  7. Enter the current date in the 'From Date' and 'Through Date' fields.
  8. Select "Client A" in the 'Client ID' field.
  9. Select "PregnancyCreated" in the 'Event/Action Search' field.
  10. Click [View Activity Log].
  11. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary code defined for the status selected.
  12. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  13. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  14. Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary value defined for the status selected.
  15. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected.
  16. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  17. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  18. Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected.
  19. Close the report and the form.
  20. Select "Client A" and access the 'Women's Health History' form.
  21. Select the record filed in the previous steps and click [Edit].
  22. Enter the desired value in the 'Pregnancy End Date' field.
  23. Select any new value in the 'Pregnant Status' field.
  24. Click [Submit].
  25. Access the 'CareFabric Monitor' form.
  26. Enter the current date in the 'From Date' and 'Through Date' fields.
  27. Select "Client A" in the 'Client ID' field.
  28. Select "PregnancyUpdated" in the 'Event/Action Search' field.
  29. Click [View Activity Log].
  30. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary code defined for the status selected.
  31. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  32. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  33. Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary value defined for the status selected.
  34. Validate the 'endDate' field contains the 'Pregnancy End Date'.
  35. Validate the 'startDate' field contains the 'Pregnancy Start Date'.
  36. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected.
  37. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  38. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  39. Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected.
  40. Close the report and the form.
Scenario 2: Dictionary Update - Validate the 'Pregnancy Status' dictionary
Steps
  1. Access the 'Dictionary Update' form.
  2. Select "Client" in the 'File' field.
  3. Select "(357) Pregnancy Status" in the 'Data Element' field.
  4. Enter an existing code in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Validate the 'Extended Dictionary Data Element' field contains the following:
  7. "(70492) Clinical Status - Pregnancy (FHIR)"
  8. "(70493) Verification Status (FHIR)"
  9. Select "(70492) Clinical Status - Pregnancy (FHIR)" in the 'Extended Dictionary Data Element' field.
  10. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  11. Select "(70493) Verification Status (FHIR)" in the 'Extended Dictionary Data Element' field.
  12. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  13. Click [Apply Changes].
  14. Validate a message is displayed stating: Filed!
  15. Click [OK].
  16. Select the "Print Dictionary" section.
  17. Select "Client" in the 'File' field.
  18. Select "Individual Data Element" in the 'Individual or All Data Elements' field.
  19. Select "(357) Pregnancy Status" in the 'Data Element' field.
  20. Click [Print Dictionary].
  21. Validate the report displays the updated dictionary with the "(70492) Clinical Status - Pregnancy (FHIR)" and "(70493) Verification Status (FHIR)" extended dictionary values populated.
  22. Close the report and the form.
Dictionary Update - 'Diagnosis Status' dictionary
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • CareFabric Monitor
Scenario 1: Dictionary Update - Validate the 'Diagnosis Status' dictionary
Steps
  1. Access the 'Dictionary Update' form.
  2. Select "Client" in the 'File' field.
  3. Select "(1800) Status" in the 'Data Element' field.
  4. Enter an existing code in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Validate the 'Extended Dictionary Data Element' field contains the following:
  7. "(70494) Clinical Status - Diagnosis (FHIR)"
  8. "(70493) Verification Status (FHIR)"
  9. Select "(70494) Clinical Status - Diagnosis (FHIR)" in the 'Extended Dictionary Data Element' field.
  10. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  11. Select "(70493) Verification Status (FHIR)" in the 'Extended Dictionary Data Element' field.
  12. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  13. Click [Apply Changes].
  14. Validate a message is displayed stating: Filed!
  15. Click [OK].
  16. Select the "Print Dictionary" section.
  17. Select "Client" in the 'File' field.
  18. Select "Individual Data Element" in the 'Individual or All Data Elements' field.
  19. Select "(357) Pregnancy Status" in the 'Data Element' field.
  20. Click [Print Dictionary].
  21. Validate the report displays the updated dictionary with the "(70494) Clinical Status - Diagnosis (FHIR)" and "(70493) Verification Status (FHIR)" extended dictionary values populated.
  22. Close the report and the form.
Scenario 2: Diagnosis - Validate the 'DiagnosisCreated' and 'DiagnosisUpdated' SDK events
Specific Setup:
  • The following extended dictionaries must be defined for the "(1800) Status" PM dictionary values for 'Diagnosis Status':
  • (70494) Clinical Status - Diagnosis (FHIR)
  • (70493) Verification Status (FHIR)
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select the desired value in the 'Type Of Diagnosis' field.
  3. Enter the desired date in the 'Date Of Diagnosis' field.
  4. Enter the desired time in the 'Time Of Diagnosis' field.
  5. Click [New Row].
  6. Select the desired value in the 'Diagnosis Search' field.
  7. Select "Active" in the 'Status' field.
  8. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  9. Click [Submit].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Select "DiagnosisCreated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary code defined for the status selected.
  16. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  17. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  18. Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary value defined for the status selected.
  19. Validate the 'programAdmissionID' - 'id' field contains the program admission ID for "Client A".
  20. Validate the 'programCode' - 'code' field contains the program code "Client A" is enrolled in.
  21. Validate the 'programCode' - 'displayName' field contains the program name "Client A" is enrolled in.
  22. Validate the 'statusCode' - 'code' field contains "1".
  23. Validate the 'statusCode' - 'displayName' field contains "Active".
  24. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected.
  25. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  26. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  27. Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected.
  28. Close the report and the form.
  29. Select "Client A" and access the 'Diagnosis' form.
  30. Select the diagnosis record filed in the previous steps and click [Edit].
  31. Select "Resolved" in the 'Status' field.
  32. Enter the desired date in the 'Resolved Date' field.
  33. Click [Submit].
  34. Access the 'CareFabric Monitor' form.
  35. Enter the current date in the 'From Date' and 'Through Date' fields.
  36. Select "Client A" in the 'Client ID' field.
  37. Select "DiagnosisUpdated" in the 'Event/Action Search' field.
  38. Click [View Activity Log].
  39. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary code defined for the status selected.
  40. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  41. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  42. Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary value defined for the status selected.
  43. Validate the 'programAdmissionID' - 'id' field contains the program admission ID for "Client A".
  44. Validate the 'programCode' - 'code' field contains the program code "Client A" is enrolled in.
  45. Validate the 'programCode' - 'displayName' field contains the program name "Client A" is enrolled in.
  46. Validate the 'statusCode' - 'code' field contains "4".
  47. Validate the 'statusCode' - 'displayName' field contains "Resolved".
  48. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected.
  49. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  50. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  51. Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected.
  52. Close the report and the form.
Topics
• Diagnosis • Web Services • CareFabric • Women's Health History • Dictionary • CareFabric Monitor
Update 141 Summary | Details
Data Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Update Client Data
Scenario 1: PM - Gender Identity and Sexual Orientation - dictionary validation
Specific Setup:
  • Dictionary Update:
  • Print ‘Client (730) Gender Identity’. Save for later comparison.
  • Print ‘Client (731) Sexual Orientation’. Save for later comparison.
  • Client: Select an existing client to use in ‘Update Client Data’.
Steps
  1. Open ‘Update Client Data’ for the client.
  2. Go to the ‘Gender Identity’ field.
  3. Validate that all dictionary values printed above are available in the dropdown list.
  4. Select the desired value in ‘Gender Identity’.
  5. Go to the ‘Sexual Orientation’ field.
  6. Validate that all dictionary values printed above are available in the dropdown list.
  7. Select the desired value in ‘Sexual Orientation’.
  8. Submit the form.
  9. Reopen ‘Update Client Data’ for the client.
  10. Validate that the values selected in ‘Gender Identity’ and ‘Sexual Orientation’ display.
  11. Close the form.
Topics
• Demographics • NX
Update 143 Summary | Details
Facility Defaults - 'Provider Country' field
Scenario 1: Validate the 'GetOrganization' payload
Steps

Internal testing only.

Scenario 2: 'Facility Defaults' form - field validations
Steps
  1. Access the 'Facility Defaults' form.
  2. Populate any desired fields.
  3. Validate the 'Provider Country' field is displayed.
  4. Select the desired value in the 'Provider Country' field. Note: this field is populated based off the dictionary values under the 'Client' file, '(150) Country Of Origin' data element in 'Dictionary Update'.
  5. Click [Submit].
  6. Access Crystal Reports or other SQL Reporting tool.
  7. Create a report using the 'SYSTEM.table_facility_defaults' SQL table.
  8. Validate a row is displayed for the data on file.
  9. Validate the 'provider_country_code' field contains the code associated to the 'Provider Country' selected.
  10. Validate the 'provider_country_value' field contains the value associated to the 'Provider Country' selected.
  11. Close the report.
Topics
• Facility Defaults • Query/Reporting
Update 144 Summary | Details
Call Intake - Demographic fields - Add Demographics to 'Call Intake'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (PM)
  • Admission (Outpatient)
  • Discharge
  • Call Intake
  • Registry Settings (PM)
Scenario 1: Site Specific Section Modeling - Validating Site Specific Demographic fields - Registry Setting 'Add Demographics to Call Intake'
Specific Setup:
  • Registry Setting 'Add Demographics to Call Intake' is set to 'Y'.
Steps
  1. Open the 'Site Specific Section Modeling' form.
  2. Select "PATIENT510 (Admission) Demographics" in the drop-down.
  3. Click [OK].
  4. Select the 'Prompt Definition' section.
  5. Select desired site specific prompt to add to the 'Demographic' section of the form. Note the name of the fields.
  6. Select 'No' in the 'Exclude from Data Collection Instrument' field.
  7. Submit the form.
  8. Open the 'Admission' or 'Admission(Outpatient)' form.
  9. Select the 'Demographics' section of the form.
  10. The correct site specific fields are added which are set to 'No' in the 'Exclude from Data Collection Instrument' field of the 'Site Specific Section Modeling' form from the above step.
  11. Open the 'Discharge' form.
  12. Go to the 'Demographics' section of the 'Discharge' form.
  13. The correct site specific fields are added which are set to 'No' in the 'Exclude from Data Collection Instrument' field of the 'Site Specific Section Modeling' form from the above step.
  14. Open the 'Call Intake' form.
  15. The correct site specific fields are added which are set to 'No' in the 'Exclude from Data Collection Instrument' field of the 'Site Specific Section Modeling' form from the above step.
  16. Open the 'Site Specific Section Modeling' form.
  17. Select "PATIENT510 (Admission) Demographics" in the drop-down.
  18. Click [OK].
  19. Select the 'Prompt Definition' section.
  20. Select desired site specific prompt to remove from the 'Demographic' section of the form. Note the name of the fields.
  21. Select 'Yes' in the 'Exclude from Data Collection Instrument' field.
  22. Submit the form.
  23. Open the 'Admission' or 'Admission(Outpatient)' form.
  24. Select the 'Demographics' section of the form.
  25. The correct site specific fields are removed which are set to 'Yes' in the 'Exclude from Data Collection Instrument' field of the 'Site Specific Section Modeling' form from the above step.
  26. Close the form.
  27. Open the 'Discharge' form.
  28. Go to the 'Demographics' section of the 'Discharge' form.
  29. The correct site specific fields are removed which are set to 'Yes' in the 'Exclude from Data Collection Instrument' field of the 'Site Specific Section Modeling' form from the above step.
  30. Close the form.
  31. Open the 'Call Intake' form.
  32. The correct site specific fields are removed which are set to 'Yes' in the 'Exclude from Data Collection Instrument' field of the 'Site Specific Section Modeling' form from the above step.
  33. Close the form.
Scenario 2: Call Intake - Demographics section - Registry setting 'Add Demographics to Call Intake'
Specific Setup:
  • Registry Setting:
  • The 'Add Demographics to Call Intake' is set to 'Y'. Please note: Selecting 'Y' adds the 'Demographics' tab and the prompts, 'Sex', 'Age' and 'Date Of Birth', to the 'Call Intake' form.
Steps
  1. Open 'Call Intake' form.
  2. Verify the form contains 'Demographics' section.
  3. Set 'Last Name' to any last name (not an existing client).
  4. Set 'First Name' to any first name.
  5. Select any gender in the 'Sex' drop down list
  6. Click [Search].
  7. Click [New Client].
  8. Click [Call] in the 'Call Or Walk-in' field.
  9. Set the 'Caller Name' to any LastName, FirstName.
  10. Set the 'Call Date' to any date.
  11. Set the 'Call Time' to any time.
  12. Select any value from the 'Program' drop down list.
  13. Select any value from the 'Disposition' drop down list.
  14. Enter any text in the 'Comments for the call intake' text box.
  15. Set the 'Date of Birth' to any date in the past.
  16. Set the 'Social Security Number' to any SSN.
  17. Click the 'Demographics' tab.
  18. Select any value in the 'Prefix' drop down list.
  19. Set the 'Client's Address - Street' to any address.
  20. Set the 'Client's Address - Zipcode' to any Zipcode.
  21. Set the 'Client's Home Phone' to any phone number.
  22. Set the 'Client's Work Phone' to any phone number.
  23. Set the 'Client's Cell Phone' to any phone number.
  24. Set the 'Client's Email Address' to any email address.
  25. Select any value in the 'Communication Preference' field.
  26. Select any value in the 'Primary Language' drop down list.
  27. Select any value in the 'Client Race' drop down list.
  28. Select any value in the 'Other Race(s)' list.
  29. Select any value in the 'Ethnic Origin' drop down list.
  30. Select any value from the 'Religion' drop down list.
  31. Set the 'Place of Birth' to any value.
  32. Select any value from the 'Marital Status' drop down list.
  33. Select any value from the 'Education' drop down list.
  34. Select any value from the 'Employment Status' drop down list.
  35. Select any value from the 'Occupation' drop down list.
  36. Select any value from the 'Are you heterosexual, lesbian, gay, bisexual, transgender or do you question your sexual orientation?' field.
  37. Select any value from the 'Smoker' drop down list.
  38. Set the 'Smoking Status Assessment Date' to any date.
  39. Set the 'Client's Mailing Address - Street' to any address.
  40. Set the 'Client's Mailing Address - Street 2' to any address.
  41. Set the 'Client's Mailing Address - Zipcode' to any Zipcode.
  42. Set the 'Client's Mailing Address - City' to any City.
  43. Set the 'Client's Mailing Address - State' to any State.
  44. Select any value from the 'Client's Mailing Address - County' field.
  45. Click [Submit].
  46. Open the 'Call Intake' form for the same client.
  47. Verify the Demographic data is retained and correct.
  48. Close the form.
  49. Open the 'Registry setting' Form.
  50. Set the 'Add Demographics to Call Intake' to 'N'.
  51. Submit the form.
  52. Open 'Call Intake' form.
  53. Verify the form does not contain 'Demographics' section.
  54. Submit the form.
Topics
• Site Specific Section Modeling • NX • Call Intake
Update 147 Summary | Details
AR Console User Defaults Setup
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • AR Console Configuration
  • AR Console User Defaults Setup
  • System Task Scheduler
  • Registry Settings (PM)
Scenario 1: AR Console User Defaults Setup - field validation
Specific Setup:
  • The following registry setting has a value of Y: Avatar PM->Billing->Accounts Receivable Management->->->Enable Accounts Receivable Management Functionality.
  • User Definition has been used to give the signed in user access to the form: Avatar PM / Billing / AR Management / AR Console User Defaults Setup.
  • View Definition / NX View Definition has been used to place the widget on the tester's home view.
  • Note the ID of at least two more users.
  • Guarantors/Payor: Multiple guarantors exist that contain different 'Financial Classes'.
  • AR Console Configuration: At least one 'Financial Class' is selected in 'Exclude Financial Class(es) from AR Console'.
  • System Task Scheduler:
  • The 'Auto AR Batch Update' was processed after the claims were created.
Steps
  1. Open ‘AR Console User Defaults Setup’.
  2. Click ‘New Row’ and add a row for the signed in user, or if the signed in user exists in a row select the row.
  3. Click ‘All’ in the following fields: ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’ and ‘Client Last Name Initials to be Worked’.
  4. Add desired value to ‘Aged Over # Days’. Note the value.
  5. Click ‘New Row’ and add a row for the first additional user from ‘Setup’, or if the user exists in a row select the row.
  6. Select desired values in ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’, ‘Client Last Name Initials to be Worked’, and ‘Aged Over # Days’.
  7. Note the values of each field.
  8. Click ‘New Row’ and add a row for the second additional user from ‘Setup’, or if the user exists in a row select the row.
  9. Select desired values in ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’, ‘Client Last Name Initials to be Worked’, and ‘Aged Over # Days’.
  10. Note the values of each field.
  11. Click [Submit].
  12. Open ‘AR Console User Defaults Setup’.
  13. Select the row for the signed in user.
  14. Validate that the following fields have every available item in the checklist selected: ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’ and ‘Client Last Name Initials to be Worked’.
  15. Verify that ‘Aged Over # Days' contains the value entered above.
  16. Deselect one or more items in 'Financial Class(es)'.
  17. Select the row for the first additional user.
  18. Validate that the values that were submitted were retained.
  19. Select the row for the second additional user.
  20. Validate that the values that were submitted were retained.
  21. Click [Submit].
  22. Open ‘AR Console User Defaults Setup’.
  23. Select the row for the signed in user.
  24. Verify that the ‘Financial Class(es)’ does not contain the deselected items.
  25. Open the 'Account Receivable Console' widget for the signed in user.
  26. Verify that the ‘Financial Class(es)’ does not contain the deselected items.
  27. Close the widget.
Topics
• Accounts Receivable Management
Update 150 Summary | Details
Spreadsheet Charge Input - Form validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Client Ledger
  • Admission (Outpatient)
  • Financial Eligibility
  • Client Charge Input With Diagnosis Entry
  • Spreadsheet Edit Service Information
Scenario 1: Spreadsheet Edit Service Information - Registry setting 'Allow Only Active Diagnoses' and 'Hide Medical Diagnosis Fields'
Specific Setup:
  • Registry Setting:
  • The Avatar PM \ Services \ Ancillary/Ambulatory Services \ Spreadsheet Edit Service Information \ Hide Medical Diagnosis Fields' registry setting is set to "Y".
  • Admission:
  • An existing client is identified or a new client is admitted.
  • Client Charge Input with Diagnosis Entry
  • Three charges are added for the client. Enter a diagnosis for two of the charges.
Steps
  1. Open 'Spreadsheet Edit Service Information' form.
  2. Select "All" in the 'Individual Or All Practitioners' field.
  3. Select "All" in the 'Individual Or All Programs' field.
  4. Select the client from the setup section in the 'Individual Or All Clients' field.
  5. Enter the date rage to include all three services created in the setup section in the 'Begin Date Of Service' and 'End Date Of Service' fields.
  6. Select "No" in the Only Show Services That Require A Diagnosis Or Are Primary Medical Program Services field.
  7. Select all the options in the 'Only Load Services With This Status' field.
  8. Click 'Edit Service Information' button to display the Spreadsheet Edit Service Information grid.
  9. Verify that all Diagnosis fields are hidden.
Scenario 2: Spreadsheet Charge Input - Registry setting 'Allow Only Active Diagnoses' and 'Hide Medical Diagnosis Fields' = Y
Specific Setup:
  • Registry Setting:
  • Set the 'Allow Only Active Diagnoses' registry setting to "Y".
  • Set the 'Avatar PM->Services->Ancillary/Ambulatory Services->Spreadsheet Charge Input->->Hide Medical Diagnosis Fields' registry setting to "Y".
  • Admission:
  • Add a new client or identify an existing client. Note the client id/ name.
  • Financial Eligibility:
  • Assign an existing guarantor to the client.
  • Service Code:
  • Identify an existing service code to be used. Note the service code.
Steps
  1. Open the 'Spreadsheet Charge Input' form.
  2. Verify the form opens successfully.
  3. Render a service to the client using the service code identified in the setup.
  4. Save the grid.
  5. Submit the form.
  6. Open the 'Client Ledger' form.
  7. Verify the service displays correctly and charges distributed correctly to the guarantor assigned to the client.
Topics
• NX • Spreadsheet Charge Input
Update 151 Summary | Details
Payor Based Authorizations
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Guarantors/Payors
  • Admission
  • Financial Eligibility
  • Program Maintenance
  • Client Charge Input
  • Payor Based Authorizations
  • Client Ledger
  • Practitioner Numbers By Guarantor And Program
  • Electronic Billing
Scenario 1: PM - Payor Based Authorization - Location
Specific Setup:
  • Registry Settings:
  • Enable Payor Based Authorizations = 'Y'.
  • Enable CPT Based Payor Authorizations = desired value.
  • Require Authorizations At Guarantors/Payors Level = desired value.
  • Dictionary Update:
  • Client File (10006) Location = note active locations.
  • Staff File (79) Practitioner Category = note active categories.
  • Guarantors/Payors:
  • Guarantor A: Identify a guarantor to be used with 'Payor Based Authorizations'.
  • Note the values in the 'Authorization Section'.
  • Verification Level For Authorizations For Client Charge Input and Verification Level For Authorizations For Appointment Scheduling:
  • 'Disallow Service If Authorization Is Missing' will not allow the service to be submitted.
  • 'Warn User If Authorization Is Missing' will allow the service to be submitted.
  • Verification Level For Authorizations For 837 Electronic Billing:
  • 'None' will allow services that were submitted and closed to be billed.
  • 'Report As Error And Include On Bill' will allow services that were submitted and closed to be billed. An error message will be included in the 837 Billing report.
  • 'Report As Error And Do Not Include On Bill' will not allow services that were submitted and closed to be billed
  • Payor Based Authorizations: Create or edit a definition to not include a 'Locations' and any other desired fields. An error message will be included in the 837 Billing report. Note the value of each field.
  • Client A: Identify an active client that is assigned to the guarantor above.
Steps
  1. Open 'Payor Based Authorizations'.
  2. Create a new record that matches the record from setup.
  3. Validate that the following message displays: An authorization already exists for this date range. Overlapping authorizations are not allowed.
  4. Remove the 'Expiration Date'.
  5. Select a 'Location'.
  6. Enter an 'Expiration Date'.
  7. Submit the form and validate that it files successfully.
  8. Open ‘Scheduling Calendar’.
  9. Create an appointment for Client A.
  10. Validate that the appropriate submission event occurs based on the values in the ‘Guarantors/Payors’, 'Authorization Section'.
  11. Close the form.
  12. Open ‘Client Charge Input’.
  13. Create a service for Client A.
  14. Validate that the appropriate submission event occurs based on the values in the ‘Guarantors/Payors’, 'Authorization Section'.
  15. Close the form.
  16. Open 'Close Charges’ and close charges for Client A if submission was allowed.
  17. Close the form.
  18. Open ‘Electronic Billing’ if submission was allowed.
  19. Create the bill for Client A and validate that the appropriate billing action occurs based on the values in the ‘Guarantors/Payors’, 'Authorization Section'.
  20. Close the form.
  21. Open ‘Client Ledger’ for Client A if submission was allowed.
  22. Review the ‘Simple’, ‘Ledger Type’ to confirm the billing activity.
  23. Close the form.
Topics
• Client Charge Input • Payor Based Authorizations • NX