Skip to main content

Avatar PM 2023 Update 103

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

Avatar PM required
RADplus required

Recommended Update Level

Avatar PM 2023 Monthly Release 2023.03.00
Avatar PM 2023 Update 63
RADplus 2023 Monthly Release 2023.03.00

Product Update Description

The following issues are resolved: 1) Users are not allowed to change a service code in the 'Edit Service Information' form if the new service code is not assigned to the original service program. 2) Financial Investigation web service will not allow a future date in the 'Financial Investigation Effective Date' field. 3) 'Disclosure Management' form will not display data from a user modeled form on the disclosure document if the modeled form has multiple sections consisting of multiple iteration tables. 4) 'Bed Management' grid will display the social security number for clients when the user is only allowed for initial data entry of social security number. 5) 'Disclosure Management' form may include a requested chart item with a data entry date outside of the authorization date range in the final disclosure packet.

Required Updates

None

Included Updates

10, 16, 17, 18, 21, 25, 29, 35, 39, 44, 56, 57, 62, 63, 66, 67, 72, 73, 76, 77, 78, 79, 82, 85, 88, 89, 93, 94, 96, 98, 101, 102

Details
NEW0 CHANGED0 FIXED5
Fixed (5)
Edit Service Information
The functionality for 'Edit Service Information' has been modified to allow the form to properly handle a service code that is not assigned to the program. KB0074588 v0.01
Topics
• Edit Service Information
 
Financial Investigation - Web Services
The web service functionality for Financial Investigation has been updated to allow future dates in the 'Financial Investigation Effective Date' field. KB0074590 v0.01
Topics
• Financial Investigation • Web Services
 
Disclosure Management - Site Specific Section Modeling
The functionality for Disclosure Management has been updated to correctly process multiple Site Specific Section Modeling fields that have multiple iteration tables. KB0074031 v0.01
Topics
• Disclosure • Modeling • Site Specific Section Modeling
 
Bed Management
The functionality for 'Bed Management' is updated to respect the 'User Definition' access to social security numbers. KB0074632 v0.01
Topics
• Bed Management • Client Management • Maintain Hospital Bed File
 
Disclosure Management
Resolves an issue to ensure that the requested chart items only include items within the specified date range. KB0075038 v0.01
Topics
• Disclosure
 
Acceptance Tests
AV-79959 Summary | Details
Edit Service Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission (Outpatient)
  • Client Charge Input
  • Program Maintenance
Scenario 1: Edit Service Information - Editing/Deleting an open service -the service code is configured for the work-flow
Specific Setup:
  • User Definition:
  • The logged in user (e.g. SYSADM) has a practitioner assigned.
  • Service Codes:
  • A new service code is created or an existing service code is identified. Note the service code.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Set System Defaults (CWS):
  • The service code identified above is configured for work-flow in the 'Workflow Service Setup' section of the form.
  • The 'Service Provider' is selected in the 'Send To Do Item To Which Staff Member' field.
  • Admission:
  • A new client is created or an existing client is identified. Note the Client id/Name, Admission date / program.
  • Client Charge Input:
  • A service rendered to the client using the service code identified above.
  • Client Ledger:
  • The service is in 'Open' status.
Steps
  1. Open the 'Edit Service Information' form.
  2. Select the desired client in the 'Client ID' field.
  3. Select desired episode from the 'Episode Number' field.
  4. Click [Select Service(s) To Edit].
  5. Verify the 'Select Service(s) To Edit' dialog is displayed.
  6. Select desired service from the 'Select Service(s) To Edit' dialog.
  7. Enter a different value in the 'Duration (Minutes)' field.
  8. Click [OK].
  9. Submit the form.
  10. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  11. Click [No].
  12. Query the 'SYSTEM.RADplus_workflow_to_do' SQL table.
  13. Validate the 'ENTITY_ID' column is equal to the correct client id identified in the setup.
  14. Validate the 'sending_user_desc' column is equal to the correct user associated with the rendering practitioner.
  15. Validate the 'outgoing_comments ' column contains correct comments for the specific service stating that it has been edited.
  16. Open the 'Delete Service' form.
  17. Select desired client from the 'Client ID' field.
  18. Set the Start Date input box to desired date.
  19. Set the End Date input box to desired date.
  20. Click [Display Client].
  21. Select desired service from the 'Service Delete' checklist.
  22. Click [OK].
  23. Click [Delete].
  24. Review the message about the services going to be deleted.
  25. Click [OK].
  26. Validate the WARNING! dialog contains "Continue Filing?"
  27. Click [Yes].
  28. Validate the 'Confirm' dialog contains "Deleted".
  29. Click [OK].
  30. Close the form.
  31. Query the 'SYSTEM.RADplus_workflow_to_do' SQL table.
  32. Validate the row is removed from the table.
Scenario 2: Edit Service Information - Changing to a service code not assigned in Program Maintenance
Specific Setup:
  • Program Maintenance:
  • Program 1: ‘Assign Services To Program’ section has a service code assigned. Note the code to use in ‘Client Charge Input’. In additions, note a code that is not assigned.
  • Program 2: ‘Assign Services To Program’ section has does not have the code that will be used in ‘Client Charge Input’ assigned. It does have the above unassigned code assigned.
  • Identify a client in ‘Program 1’.
  • Client Charge Input is used to create a service for the client, using the service code assigned in ‘Program 1’.
Steps
  1. Open ‘Edit Service Information’.
  2. Enter the ‘Client ID’.
  3. Select the ‘Episode Number’ if there is more than one episode.
  4. If desired, enter the ‘Service Start Date’.
  5. If desired, enter the ‘Service End Date’.
  6. If desired, select a value in ‘Service Selection Default’.
  7. Click [Select Service(s) To Edit].
  8. Select the desired service.
  9. Click [OK].
  10. Change the service code to the service code that is not assigned to ‘Program 1’.
  11. Validate that no search results are returned.
  12. Set the service code to the original value.
  13. Change the ‘Program’ to ‘Program 2’.
  14. Validate that an error message is received.
  15. Click [OK].
  16. Delete the service code value.
  17. Change the ‘Program’ to ‘Program 2’.
  18. Change the service code to the code assigned to ‘Program 2’.
  19. Click [Submit].
  20. Click [No].
  21. Click [Submit].
Topics
• Edit Service Information
AV-81843 Summary | Details
Financial Investigation - Web Services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission (Outpatient)
  • Financial Investigation
  • SoapUI - AddFinancialInvestigation
Scenario 1: "Financial Investigation" form - field validation
Specific Setup:
  • An existing client is identified. Note the client's id/name.
Steps
  1. Open 'Financial Investigation' form.
  2. Verify the 'Divide Sliding Fee Scale Amount by Number of Family Members Receiving Services' and 'Sliding Fee Scale - Number of Family Members Receiving Services' fields are on the form, and that 'Sliding Fee Scale - Number of Family Members Receiving Services' field is disabled.
  3. Set the 'Divide Sliding Fee Scale Amount by Number of Family Members Receiving Services' to "Yes".
  4. Verify the ''Sliding Fee Scale - Number of Family Members Receiving Services' field becomes enabled and required.
  5. Set the Sliding Fee Scale - Number of Family Members Receiving Services' field to desired value. Note the value.
  6. Set the 'Income-Responsible Party Annual Income' field to desired value.
  7. Set the Income-Household Gross Annual Income' field to desired value.
  8. Set the 'Sliding Fee Scale - Number Of Dependents' field to desired value.
  9. Set the 'Sliding Fee Scale - Income' field to desired value.
  10. Set the 'Family Size' field to desired value.
  11. Set the 'Financial Investigation Effective Date' field to desired value.
  12. Select desired value from the 'Income-Validation' dropdown list.
  13. Set the 'Number Of Dependents' field to desired value.
  14. Click [Submit].
  15. Open the 'Crystal Report' or any other SQL data viewer.
  16. Create a query against 'SYSTEM.call_intake_financial_inv' for the PATID identified in the setup.
  17. Validate that the appropriate row has been added in the SQL table SYSTEM.call_intake_financial_inv .
  18. Validate the 'income_resp_income column is equal to the value entered in the 'Financial Investigation' form.
  19. Validate the 'household_gannual_inc column is equal to the value entered in the 'Financial Investigation' form.
  20. Validate the 'fin_invest_eff_date' column is equal to the value entered in the 'Financial Investigation' form.
  21. Validate the 'family_size' column is equal to the value entered in the 'Financial Investigation' form.
  22. Validate the 'sliding_fee_fmsizerec_code' column is equal to the value entered in the 'Financial Investigation' form.
  23. Validate the 'sliding_fee_fmsizerec_num' column is equal to the value entered in the 'Financial Investigation' form.
  24. Validate the 'sliding_fee_fmsizerec_value' column is equal to the value entered in the 'Financial Investigation' form.
  25. Validate the 'sliding_fee_income' column is equal to the value entered in the 'Financial Investigation' form.
  26. Validate the 'sliding_fee_num_of_depend' column is equal to the value entered in the 'Financial Investigation' form.
  27. Open 'Financial Investigation' form.
  28. Validate the correct value displays in all the fields as entered.
  29. Update the value of 'Income-Responsible Party Annual Income' field to different value.
  30. Update the 'Family Size' field to different value.
  31. Update the Sliding Fee Scale - Number of Family Members Receiving Services' field to different value.
  32. Click [Submit].
  33. Open the 'Crystal Report' or any other SQL data viewer.
  34. Create a query against SYSTEM.call_intake_financial_inv for the PATID identified in the setup.
  35. Validate the 'income_resp_income' column is equal to the value updated in the 'Financial Investigation' form.
  36. Validate the 'family_size' column is equal to the value updated in the 'Financial Investigation' form.
  37. Validate the 'sliding_fee_fmsizerec_num' column is equal to the value updated in the 'Financial Investigation' form.
  38. Open 'Financial Investigation' form.
  39. Validate the correct values display in all the fields as updated.
  40. Click [Close Form].
Scenario 2: WebSvc.FinancialInvestigationV2 - Validate AddFinancialInvestigation method with "Financial Investigation" form
Specific Setup:
  • An existing client is identified. Note the client's id.
Steps
  1. Access SoapUI for the 'Financial Investigation' - 'AddFinancialInvestigation' web service.
  2. Set the 'FIEffectiveDate' item to desired value, which can include past, current or future dates. Note the value.
  3. Set the 'IHGrossAnnualIncome' item to desired value. Note the value.
  4. Set the 'IRPartyAnnualIncome' item to desired value. Note the value.
  5. Set the 'IncomeValidation' item to desired value. Note the value.
  6. Set the 'NumberOfDependents' item to desired value. Note the value.
  7. Set the 'SlidingFeeScaleDependents' item to desired value. Note the value.
  8. Set the 'SlidingFeeScaleIncome' item to desired value. Note the value.
  9. Set the 'FamilySize' item to desired value. Note the value.
  10. Set the 'SlidingFeeDivideNumFamMembers' to "Y". Note the value.
  11. Set the 'SlidingFeeDivideNumFamMembersNum' to desired value. Note the value.
  12. Set the 'ClientID' to the ClientID identified in the setup section. Note the value.
  13. Set the 'LoginSource' to 'SOAPUI'. Note the value.
  14. Run the request.
  15. Click [Run].
  16. Validate the 'Confirmation' field contains a value such as: "Unique ID: IBE.001".
  17. Validate the 'Message' field contains: "Financial Investigation web service has been filed successfully".
  18. Open the 'Financial Investigation' form for the test client.
  19. Validate that a row has been added to the pre-display.
  20. Select the new row and click [Edit].
  21. Validate the 'Financial Investigation Effective Date' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  22. Validate the 'Income-Responsible Party Annual Income' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  23. Validate the 'Income-Household Gross Annual Income' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  24. Validate the 'Number Of Dependents' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  25. Validate the 'Sliding Fee Scale - Number of Dependents' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  26. Validate the 'Sliding Fee Scale - Income' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  27. Validate the 'Family Size' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  28. Validate the 'Divide Sliding Fee Scale Amount by Number of Family Members Receiving Services' field contains "Yes".
  29. Validate the 'Sliding Fee Scale - Number of Family Members Receiving Services' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  30. Click [Submit].
Topics
• Financial Investigation • Web Services
AV-83671 Summary | Details
Disclosure Management - Site Specific Section Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Delete Document
  • Document Routing Setup (PM)
  • Final to Draft Override (PM)
  • Registry Settings (PM)
  • User Definition
  • Disclosure Management
  • Disclosure Management Configuration
  • Site Specific Section Modeling (PM)
Scenario 1: Parent Namespace User Modeled Disclosure Management form with table aliasing
Specific Setup:
  • A user modeled form set up with the primary table being aliased to the Disclosure Management data. Please note: For internal testing purposes the disclosure management SQL table is validated. For your test, you may alias a different form. Note that table and validate it in place of SYSTEM.disclo_mgmt.
  • Admit or select a test client.
Steps
  1. Open the user modeled form from setup.
  2. Fill out all the fields on the form.
  3. Set "Draft/Final" to "Draft".
  4. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  5. Open the user modeled form from setup.
  6. Fill all the fields on the form.
  7. Set "Draft/Final" to "Final".
  8. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the form was flagged as Final.
  9. Open the "Document Routing Setup" form.
  10. Enable document routing for the user modeled created during setup.
  11. Open the user modeled form from setup.
  12. Fill out all the fields on the form.
  13. Set "Draft/Final" to "Draft".
  14. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  15. Open the user modeled form from setup.
  16. Fill all the fields on the form.
  17. Set "Draft/Final" to "Final".
  18. Click "Accept" or "Sign" on the "Confirm Document" screen.
  19. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the form was flagged as Final.
  20. Open the "Registry Settings" form.
  21. Enable the registry setting "RADplus->Document Routing->Routing Setup->->->Alias Data File Upon Document Routing Completion".
  22. Open the user modeled form from setup.
  23. Fill out all the fields on the form.
  24. Set "Draft/Final" to "Draft".
  25. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  26. Open the user modeled form from setup.
  27. Fill all the fields on the form.
  28. Set "Draft/Final" to "Final".
  29. Click "Accept and Route" or "Sign and Route" on "Confirm Document" pop up.
  30. Route to another user.
  31. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the registry setting mentioned previously is enabled and the document routing is not finalized.
  32. Log in as the user the document was routed to.
  33. Navigate to the "My ToDo" widget.
  34. Approve the document by electronically signing it.
  35. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the registry setting mentioned previously is enabled and the document routing is now finalized for the form.
  36. Open the "Registry Settings" form.
  37. Disable the registry setting "RADplus->Document Routing->Routing Setup->->->Alias Data File Upon Document Routing Completion".
  38. Open the user modeled form from setup.
  39. Fill out all the fields on the form.
  40. Set "Draft/Final" to "Draft".
  41. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  42. Open the user modeled form from setup.
  43. Fill all the fields on the form.
  44. Set "Draft/Final" to "Final".
  45. Click "Accept and Route" or "Sign and Route" on "Confirm Document" pop up.
  46. Route to another user.
  47. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the registry setting mentioned previously is disabled, the system is not waiting for document routing to be finalized.
  48. Log in as the user the document was routed to.
  49. Navigate to the "My ToDo" widget.
  50. Approve the document by electronic signing it.
  51. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the registry setting is disabled, and the record was filed when the form was routed.
  52. Open the "Final To Draft Override" form.
  53. Select a finalized document to return to draft status.
  54. A message should pop up noting that "Please note that filed Alias data will not be deleted or altered in any way as a result of filing the override for this row".
  55. Complete process.
  56. Open the "Delete Document" form.
  57. Choose to delete one of the user modeled/aliased documents.
  58. A message should pop up noting that "Please note that filed Alias data will not be deleted or altered in any way as a result of filing the override for this row".
  59. Complete the process.
Scenario 2: Disclosure Management - Validate Site specific fields
Specific Setup:
  • Using the "Disclosure Management Configuration" form, set up the system for Disclosure Management.
  • Using "Site Specific Section Modeling" form, add 3 fields of the type SS Disclosure Management Free Text to the Disclosure Management Disclosure section (PATIENT4000 (Disclosure Management) Disclosure).
  • Note: For NX only, on the Disclosure screen, once the items have been disclosed and viewed, you have to click 'Cancel' to go back to the main form to click "Submit" to finalize the process. This will be addressed in a future NX release to mimic the workflow in myAvatar.
Steps
  1. Open the "Disclosure Management" form.
  2. Fill out the Request, Authorization and Disclosure sections.
  3. In the "Disclosure" section, populate the site specific section modeling fields.
  4. Click "Process" button.
  5. Validate the correct items are included in the disclosure packet.
  6. Click "Disclose" button.
  7. Click the "Printer" icon.
  8. Print the disclosure packet.
  9. Return to the pre-display.
  10. Add another request, authorization, and disclosure.
  11. In the disclosure section, validate the site specific section modeling fields are blank after the last record was filed.
  12. Populate the site specific section modeling fields.
  13. Select "Other" in the "Disclosure Method" field.
  14. Set the "Disclosure Method - Specify Other" to "Mail".
  15. Click the "Process" button.
  16. Click the "Disclose" button.
  17. Return to the pre-display.
  18. Select a row in the pre-display.
  19. Click the "Delete" button.
  20. Validate the disclosure record is removed.
  21. Select one of the previously filed disclosure records that has a date in the "Disclosure Date" column.
  22. Click "Edit".
  23. Validate a message displays indicating the disclosure record was previously finalized because it has a disclosure date and can't be edited. It can only be displayed.
  24. Validate the Request, Authorization and Disclosure data is retrieved as it was entered, including the fields added via "Site Specific Section Modeling".
  25. Remain in the form by returning to the pre-display.
  26. Add another disclosure record.
  27. Fill out the request, authorization, and disclosure sections.
  28. In the disclosure section, Set "Disclosure Method" to "Electronic".
  29. Click the "Submit" button.
  30. Exit the form.
  31. Open the "Disclosure Management" form.
  32. In the disclosure record pre-display, select the disclosure record without a "Disclosure Date" that was just filed.
  33. Click the "Edit" button.
  34. Navigate to the "Disclosure" Section.
  35. Fill in the "Disclosure Date" and "Disclosure Time".
  36. Populate the site specific section modeling fields.
  37. Validate the "Disclosure Method" is set to "Electronic".
  38. Click the "Process" button.
  39. Click the "Disclose" button.
  40. Click the PDF download icon.
  41. Browse to the location on the server where you want to store the file.
  42. Give the file a name with a .pdf extension.
  43. Click the "Save" button.
  44. Validate a message pops up stating that once this Disclosure Management record is filed with a Disclosure Date entered it will no longer be available for edit. This record will only be available to view and print.
  45. Return to the pre-display.
  46. Validate a row was added to the disclosure pre-display.
  47. Exit the form.
Topics
• Disclosure • Modeling • Site Specific Section Modeling
AV-90698 Summary | Details
Bed Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Bed Management (View Only)
  • Crystal Report Viewer
  • User Definition
Scenario 1: Bed Management (View Only)
Specific Setup:
  • Client: Is enrolled in an inpatient program and has a value in ‘Social Security Number’, noting the number.
  • Note the 'Preadmit/Admission Date', 'Date of Birth', 'Episode #', 'Program', ‘Unit’, ‘Room’ and ‘Bed’.
  • Use the 'Diagnosis' form to note the diagnosis.
  • User Definition is updated for the signed in tester to select ‘Initial Data Entry’ in ‘Social Security Number Access’.
Steps
  1. Open 'Bed Management (View Only).
  2. Select the 'Unit'.
  3. Select the 'Room'.
  4. Click [Bed Management].
  5. Access the team, room, and bed for the client.
  6. Hover over the client’s name.
  7. Validate that the correct data displays and that the social security number does not display but displays as '***_**_****'.
  8. Close the grid.
  9. Close the form.
Topics
• Client Management • Maintain Hospital Bed File
AV-91919 Summary | Details
Disclosure Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Client
  • Disclosure Management
  • Disclosure Management Configuration
  • Document Routing Setup (PM)
  • Progress Notes (Group and Individual)
  • Registry Settings (PM)
  • Treatment Plan
  • Clinical Document Viewer
Scenario 1: Disclosure Management - Date Created vs. Date Signed - Document Routing disabled
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be enabled.
  • Using the "Document Routing Setup" form, disable document routing for Progress Notes (Group and Individual), Treatment Plan and a user modeled form.
  • Using "Disclosure Management Configuration", include "Progress Notes (Group and Individual), Treatment Plan and a user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Using the "Progress Notes (Group and Individual)" form:
  2. Generate a progress note.
  3. Finalize the note.
  4. Using the "Treatment Plan" form:
  5. Generate a new treatment plan.
  6. Finalize the note.
  7. Using a user modeled form:
  8. Generate a new form.
  9. Finalize the form.
  10. Open the "Disclosure Management" form:
  11. Generate a disclosure packet.
  12. On the Request section, select the client, episode and Request Information Start and End Dates that will encompass the forms previously generated for this test.
  13. Click "Apply Filters to Document Images" button.
  14. In the "Requested Chart Items" box, select "Progress Notes (Group and Individual)", Treatment Plan, user modeled forms you want to include in the disclosure packet.
  15. In the "Requested Document Images" box, select the forms for Progress Notes (Group and Individual), Treatment Plan and user modeled form you want to include in the disclosure packet.
  16. Navigate to the "Authorization" section.
  17. Select the same Episode and the Authorization Start and End Dates.
  18. Click "Yes - Default All Chat Items to Yes" radio button.
  19. Click "Update Chart Items Authorized for Disclosure" button.
  20. Click "Save" button.
  21. Click "Refresh Chart Items" button.
  22. Click "Yes - Default All Document Items To Yes" radio button.
  23. Click the "Update Document Images Authorized for Disclosure" button.
  24. Click "Save" button.
  25. Click "Refresh Document Images" button.
  26. Navigate to the "Disclosure" section.
  27. Populate the "Disclosure Date" and "Disclosure Time".
  28. Select all items in the "Chart Disclosure Information" box.
  29. Select all items in the "Disclosure Images" box.
  30. Select "Electronic" in the "Disclosure Method" field.
  31. Click "Process" button.
  32. Select various forms and then press "View".
  33. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  34. Click "Disclose" button.
  35. The final disclosure packet is presented.
  36. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  37. Click "Save" to generate the disclosure packet into a PDF document to be provided for the request, authorization, and disclosure.
  38. Open the "Disclosure Management" form:
  39. Select to edit the disclosure that was just filed.
  40. Validate it displays as it was previously saved.
  41. Open the "Document Routing Setup".
  42. Disable document routing for the progress note form.
  43. Open the "Progress Notes (Group and Individual)" form.
  44. Finalize a note for today's date.
  45. Open the "Disclosure Management" form.
  46. Set the "Request Date" to today's date.
  47. Select the episode the progress note was filed under.
  48. Set the "Information Start Date" to yesterday's date.
  49. Set the "Information End Date" to yesterday's date.
  50. Select the progress that was just filed in the "Requested Chart Items" field.
  51. Fill out the organization information.
  52. Navigate to the "Authorization" section.
  53. Set "Authorization Start Date" to yesterday's date.
  54. Set "Authorization End Date" to yesterday's date.
  55. Select the episode the progress note was filed under.
  56. Select the "Chart Items Authorized for Disclosure".
  57. Navigate to the "Disclosure" section.
  58. Set the "Disclosure Date" and "Disclosure Time".
  59. Click "Process".
  60. Validate the progress note for today isn't included in the disclosure packet because the progress note is outside of the date range for authorization.
Scenario 2: Disclosure Management - Date Created vs. Date Signed - Document Routing Enabled
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be enabled.
  • Using the "Document Routing Setup" form, enable document routing for Progress Notes (Group and Individual), Treatment Plan and a user modeled form.
  • Using "Disclosure Management Configuration", include "Progress Notes (Group and Individual), Treatment Plan and a user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Using the "Progress Notes (Group and Individual)" form:
  2. Generate a progress note.
  3. Finalize and route the note.
  4. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  5. Using the "Treatment Plan" form:
  6. Generate a new treatment plan.
  7. Finalize and route the note.
  8. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  9. Using a user modeled form:
  10. Generate a new form.
  11. Finalize and route the form.
  12. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  13. Open the "Disclosure Management" form:
  14. Generate a disclosure packet.
  15. On the Request section, select the client, episode and Request Information Start and End Dates that will encompass the forms previously generated for this test.
  16. Click "Apply Filters to Document Images" button.
  17. In the "Requested Chart Items" box, select "Progress Notes (Group and Individual), Treatment Plan, user modeled forms you want to include in the disclosure packet.
  18. In the "Requested Document Images" box, select the forms for Progress Notes (Group and Individual), Treatment Plan and user modeled form you want to include in the disclosure packet.
  19. Navigate to the "Authorization" section.
  20. Select the same Episode and the Authorization Start and End Dates.
  21. Click "Yes - Default All Chat Items to Yes" radio button.
  22. Click "Update Chart Items Authorized for Disclosure" button.
  23. Click "Save" button.
  24. Click "Refresh Chart Items" button.
  25. Click "Yes - Default All Document Items To Yes" radio button.
  26. Click the "Update Document Images Authorized for Disclosure" button.
  27. Click "Save" button.
  28. Click "Refresh Document Images" button.
  29. Navigate to the "Disclosure" section.
  30. Populate the "Disclosure Date" and "Disclosure Time".
  31. Select all items in the "Chart Disclosure Information" box.
  32. Select all items in the "Disclosure Images" box.
  33. Select "Electronic" in the "Disclosure Method" field.
  34. Click "Process" button.
  35. Select various forms and then press "View".
  36. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  37. Click "Disclose" button.
  38. The final disclosure packet is presented.
  39. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  40. Click "Save" to generate the disclosure packet into a PDF document to be provided for the request, authorization, and disclosure.
  41. Open the "Disclosure Management" form:
  42. Select to edit the disclosure that was just filed.
  43. Validate it displays as it was previously saved.
  44. Open the "Document Routing Setup".
  45. Enable document routing for the progress note form.
  46. Open the "Progress Notes (Group and Individual)" form.
  47. Finalize a note for today's date.
  48. Route to another approver.
  49. Log in as the approver.
  50. Navigate to the "ToDo" widget.
  51. Accept and Sign the document.
  52. Open the "Disclosure Management" form.
  53. Set the "Request Date" to today's date.
  54. Select the episode the progress note was filed under.
  55. Set the "Information Start Date" to yesterday's date.
  56. Set the "Information End Date" to yesterday's date.
  57. Select the progress that was just filed in the "Requested Chart Items" field.
  58. Fill out the organization information.
  59. Navigate to the "Authorization" section.
  60. Set "Authorization Start Date" to yesterday's date.
  61. Set "Authorization End Date" to yesterday's date.
  62. Select the episode the progress note was filed under.
  63. Select the "Chart Items Authorized for Disclosure".
  64. Navigate to the "Disclosure" section.
  65. Set the "Disclosure Date" and "Disclosure Time".
  66. Click "Process".
  67. Validate the progress note for today isn't included in the disclosure packet because the progress note is outside of the date range for authorization.
Topics
• Disclosure