Skip to main content

RADplus 2022 Update 2

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Product Update Form Description

The 'Alias Data Filed Upon Document Routing Completion' registry setting is added. This provides the ability to have alias data filed upon document routing completion rather than when the user modeled form is filed.

Note: RADplus 2022 Update 35 should also be installed to resolve an issue where table alias data may not be filed for secondary tables when the 'Alias Data Filed Upon Document Routing Completion' registry setting is enabled

Included Updates

1, 2022.00.00

Required Updates

None

Details
NEW1 CHANGED0 FIXED0
New (1)
Document Routing - Table Aliasing
The 'Alias Data Filed Upon Document Routing Completion' registry setting is added. This provides the ability to have alias data filed upon document routing completion rather than when the finalized user modeled form is filed.
Value Added: Document routing - User Modeled Forms - Table Aliasing
Topics
• Diagnosis • Document Routing • Modeling • NX
 
Acceptance Tests
AV-72087 Summary | Details
Document Routing - Table Aliasing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • App Dashboard
  • CWS General Form Test
  • DOCMANAGEMENT3000
  • Document Routing Setup (PM)
  • Dynamic Form - Admission - Client
  • Dynamic Form - Delete Document
  • Dynamic Form - Document Management Form Re-Mapping - Selection Dialog
  • Dynamic Form - document routing - sign
  • Dynamic Form - document routing - verify password
  • Dynamic Form - Document Routing Setup - Select Form
  • Dynamic Form - Form Definition - Confirm
  • Dynamic Form - OCR Template Import - Warning
  • Dynamic Form - Registry Settings - Registry Editor Filing
  • Dynamic Form - Select A Form
  • Dynamic Form Draft Final Document Routing
  • Dynamic Form Final To Draft Override
  • Dynamic Form ICD10 Diagnosis
  • Dynamic Forms - Document Routing - Route Document To Dialog
  • Envelope Import (CWS)
  • Final to Draft Override (CWS)
  • Final to Draft Override (PM)
  • Form Definition (CWS)
  • Ok - Cancel Dialog
  • Registry Settings (PM)
  • Table Definition (CWS)
  • Delete Document
  • Dynamic Form - Disclosure
  • Dynamic Form Disclosure Management Alias Primary
  • PM USER37
  • User Definition
Scenario 1: Child Namespace User Modeled Diagnosis form with table aliasing
Specific Setup:
  • A user modeled form set up with the primary table being aliased to the Diagnosis History (ICD10).
  • 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.client_diagnosis_record, 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.client_diagnosis_record, 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.client_diagnosis_record, 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.client_diagnosis_record, 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.client_diagnosis_record, 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.client_diagnosis_record, validate a row was not added to the table because the registry setting mentioned previously is enabled and the document routing is not finalized as yet.
  32. Log in as the user the document was routed to.
  33. Navigate to the "My ToDo" widget.
  34. Approve the document by electronic signing it.
  35. By viewing the SQL table from the PM namespace, SYSTEM.client_diagnosis_record, 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.client_diagnosis_record, 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.client_diagnosis_record, validate a row was added to the table because the registry setting mentioned previously is disabled and the therefor not waiting for document routing to be finalized as yet.
  48. Log in as the user the document was routed to.
  49. Navigate to the "My ToDo" widget.
  50. Approve the document.
  51. By viewing the SQL table from the PM namespace, SYSTEM.client_diagnosis_record, 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: 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.
  • 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 as yet.
  32. Log in as the user the document was routed to.
  33. Navigate to the "My ToDo" widget.
  34. Approve the document by electronic 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 and therefor not waiting for document routing to be finalized as yet.
  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.
Topics
• Diagnosis • Document Routing • Modeling • NX

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Reference
  2. Tags
    1. content:release
    2. llm-no-index
    3. role:sysadmin
    4. search:ready