User Definition - User External Login
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: User Definition (Field Validation) - Enable/Disable a "Netsmart Identity and Access Management(NIAM)" User
Specific Setup:
- Have registry setting "Enable OpenID Connect Support" enabled in the system by Netsmart
- The system has been configured for (NIAM) functionality with the appropriate settings configured in the "OpenID Connect Configuration" section of form "System Security Defaults"
- An "(ODIC) Identity Provider" solution is enabled that will be used in conjunction with Avatar to authenticate a user set up as a "NAIM" user
- [NIAMuser] has been assigned an external login ID and password by "(ODIC) Identity Provider" to enable login as a "NIAM" user, once they are configured in "myAvatar"
- The logged in user has permissions to add and edit users in form "User Definition"
Steps
- Open form "User Definition"
- Enter a new user ID or existing user [NIAMuser] in "User ID" field, that will be enabled as a "NIAM" user
- Click the "Yes" in the "Use External Login" field
- Set the "External Login ID' field to the external login name assigned to [NIAMuser]
- Validate there is no value in "System Generated Password" field and the field is disabled
- Validate there is no value in "Password Term Duration (Days)" field and the field is disabled
- Validate there is no value in "Reminder Notice Number of Days" field and the field is disabled
- Validate the "Allow User Renewal" selection field is disabled
- Populate any other required and/or desired fields on the form
- Submit the form
- Validate the form files successfully
- Re-open form "User Definition"
- Select the [NIAMUser] just updated in step 1
- Validate the "Use External Login" field is set to "Yes"
- Validate there is no value in "System Generated Password" field and the field is disabled
- Validate there is no value in "Password Term Duration (Days)" field and the field is disabled
- Validate there is no value in "Reminder Notice Number of Days" field and the field is disabled
- Validate the "Allow User Renewal" selection field is disabled
- Validate the values of any other required and/or desired fields populated in step 1, are as expected
- Navigate back to the "Use External Login" field and set the value to "No"
- Validate the "System Generated Password" field is now enabled
- Populate the field with a desired password or click the [Generate New Password] button to auto generate a new password
- Validate the "Password Term Duration (Days)" field is now enabled
- Populate the field with a desired value
- Validate the "Reminder Notice Number of Days" field is now enabled
- Populate the field with a desired value
- Validate the "Allow User Renewal" selection field is now enable
- Select the desired value in the field
- Validate all other fields populated in step 2a, are still populated as expected
- Submit the form
- Validate the form files successfully
- Re-open form "User Definition"
- Select the [NIAMUser] just updated in step 2
- Validate all fields in step 2b are still enabled and populated as expected
- Validate all other fields populated as expected
- Navigate back to "Use External Login" field and set the value back to "Yes" again
- Validate the "External Login ID" field is populated with the login name assigned to [NIAMuser]
- Validate the value in "System Generated Password" field is cleared and the field is disabled
- Validate the value in "Password Term Duration (Days)" field is cleared and the field is disabled
- Validate the value in the "Reminder Notice Number of Days" field is cleared and the field is disabled
- Validate the "Allow User Renewal" selection field is still selected but the field is disabled
- Validate all other fields on the form are populated as expected
- Submit the form
- Validate the form files successfully
- Re-open form "User Definition"
- Select the [NIAMUser] just updated in step 3
- Validate all fields in step 3b are still populated as expected and disabled
- Validate all other fields populated as expected
- Close the form
|
Topics
• NX
• User Definition
|
Envelope Import - Doc Routing
Scenario 1: Envelope Import - Validate importing "Document Routing" enabled forms
Specific Setup:
- Have an envelope [DocEnvA] with a modeled form [DocFormA] that is enabled for document routing in form "Document Routing Setup' and has the following prompts set in the "Acknowledgments" section of the form:
- Prompt 'Acknowledgement Allowed' set to 'Yes'
- All other prompts in the section are not populated
- Have an envelope [DocEnvB] with a modeled form [DocFormB] that is enabled for document routing in form "Document Routing Setup' and has the following prompts set in the "Acknowledgments" section of the form
- Prompt 'Acknowledgement Allowed' set to 'No
- All other prompts in the section are disabled, as expected
Steps
- Open form "Envelope Export".
- At the "Select Envelope" prompt, select [DocEnvA]
- Click [Begin Export].
- At "File Explorer" dialog, navigate to a desired folder location to save the export file
- In the "File_Name" field, enter the desired name for the export file or use the default name already populated
- Click [Save].
- Close the form.
- Open form "Envelope Import"
- Click [Select Envelope Import File]
- In "File Explorer, navigate to the location of [DocEnvA] and select the file
- Click [Overwrite Existing]
- Click [Begin Import Scan]
- Validate the import scan contains no errors or warnings related to "Acknowledgement" related fields
- Click [Begin Import]
- Validate the envelope imports successfully
- Open form "Document Routing Setup"
- Click [Select Form] and select [DocFormA]
- Navigate to the "Acknowledgement" section of the form
- Validate prompt 'Acknowledgement Allowed' set to 'Yes', as expected
- Validate all the other prompts in the section are not populated, as expected
- Open form "Envelope Export".
- At the "Select Envelope" prompt, select [DocEnvB]
- Click [Begin Export].
- At "File Explorer" dialog, navigate to a desired folder location to save the export file
- In the "File_Name" field, enter the desired name for the export file or use the default name already populated
- Click [Save].
- Close the form.
- Open form "Envelope Import"
- Click [Select Envelope Import File]
- In "File Explorer, navigate to the location of [DocEnvB] and select the file
- Click [Overwrite Existing]
- Click [Begin Import Scan]
- Validate the import scan contains no errors or warnings related to "Acknowledgement" related fields
- Click [Begin Import]
- Validate the envelope imports successfully
- Open form "Document Routing Setup'
- Click [Select Form] and select [DocFormB]
- Navigate to the "Acknowledgement" section of the form
- Validate prompt 'Acknowledgement Allowed' set to 'No', as expected
- Validate all the other prompts in the section are disabled, as expected
|
Topics
• Document Routing
• Envelope Import
• NX
|
Console Widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validate "Console" Widgets using a "SQL Query Override"
Specific Setup:
- Have registry setting "Enable Console Widgets/Views" is set to "Y"
- In form "Console Widget Configuration", create a console widget [TestWidget] for any desired form, for this test the "Admission" form is used:
- In the "SQL Query Override" section, populate the field with a valid SQL query to display date. For this example, the following query is used: SELECT <LINK:PATIENT510:PATID:EPN_uniqueid:EPISODE_NUMBER>PATID,EPISODE_NUMBER, EPN_uniqueid, preadmit_admission_date FROM SYSTEM.episode_history WHERE FACILITY=?FACILITY AND PATID=?PATID
- Have a client [TetClient] who is admitted in two active episodes. [EpisodeA] and [EpisodeB]
- Have [TestWidget] and the "Console Widget Viewer" widget added to the logged in user's home view
Steps
- At the home view, select [TestClient]
- Select [EpisodeA] in the "Episodes" drop down list
- Navigate to [TestWidget]
- Validate a row is display with admission data for [TestClient] for the [EpisodeA], as expected
- Click the [Open Record] button.
- Validate the "Admission" form opens for edit and displays the data for [EpisodeA], as expected.
- Close the form
- Click the [View] button in the row
- Validate the "Console Widget Viewer" display data for [EpisodeA], as expected
- Click the [Open Record] button in the console viewer
- Validate the "Admission" form opens for edit display data for [EpisodeA], as expected
- Close the form
- Navigate back to the home view
- Select [EpisodeB] in the "Episodes" drop down list
- Navigate to [TestWidget]
- Validate a row is display with admission data for [TestClient] for the [EpisodeB], as expected
- Click the [Open Record] button.
- Validate the 'Admission" form opens for edit and displays the data for [EpisodeB], as expected.
- Close the form
- Click the [View] button in the row
- Validate the "Console Widget Viewer" display data for [EpisodeB], as expected
- Click the [Open Record] button in the console viewer
- Validate the "Admission" form opens for edit display data for [EpisodeB], as expected
- Close the form
|
Topics
• Console Widget
• NX
|
Envelope Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Envelope Export (PM)
- Form Designer (PM)
Scenario 1: Envelope Import - Importing an envelope containing "Form Designer" and "Form Definition" changes
Specific Setup:
- Create a new modeled envelope [TestEnvelope] containing a form [TestForm] with two or more sections containing any desired field types
Steps
- Open form "Form Designer"
- Select [TestForm]
- Select [Section1]
- Make any kind of form designer change to the section and click [Save]
- Select [Section2]
- Make any kind of form designer change to the section and click [Save]
- Select [Section3]
- Make any kind of form designer change to the section and click [Save]
- Repeat the last step for any other sections
- Submit the form
- Validate submission is successful
- Open "Form Definition"
- Select [TestForm]
- Navigate to "Section Def" section
- Select any desired section and delete the section
- Submit the form
- Validate the form submits successfully
- Open form "Form Designer"
- Select [TestForm]
- Click the "Sections" field
- Validate the section deleted in the previous step is not present in the list, as expected
- Validate the other sections are still present in the list
- Close the form
- Open form "Envelope Export"
- Select [TestEnvelope]
- Set prompt "Include Form Designer changes?" to "Yes"
- Export the envelope and save the file
- Close the form
- Open form "Envelope Import"
- Select the file exported in the previous step
- Select "Overwrite Existing"
- Set prompt "Include Form Designer changes?" to "Yes"
- Click [Begin Import Scan]
- Validate there are messages blocking import
- Click [Begin Import]
- Validate import is successful
- Open form "Form Designer"
- Select [TestForm]
- Click the "Sections" field
- Validate the section deleted in step 2 is not present in the list, as expected
- Validate the other sections are still present in the list
- Open [TestForm]
- Validate the section removed in step 2 is no longer present, as expected
- Navigate to each of the other sections of the form
- Validate the form designer changes made in those sections in step 1 are present, as expected
- Populate fields on the other sections
- Submit the form
- Validate the form submits successfully
|
Topics
• Envelope Import
• Form Designer
• NX
|
Modeled Form - Referral Sources
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Modeled Form (w/Primary Table "Date Sorted" )- field validations
Specific Setup:
- In form "Envelope Definition" create or have an envelope [TestEnvelope], that is defined with "Referral Sources" entity database selected in the "Entity Database" field
- In form "Table Definition" field create a table [TestTable], that is configured to used envelope [TestEnvelope] and has prompt "Is this Table Date or Order of Entry Sorted" set to "Date Sorted" and field "Column Name of Sort Date" populated with a desired column name [ReferralSortDate].
- Include any other desired field types in the table
- Have a modeled form [TestForm] created using table [TestTable] adding the desired columns from the table to the form. Note: the sort date column [RefferralSortDate] defined in step 2 will automatically be displayed as field on the form
- In form "Referral Source Maintenance"
- Have a "Referral Source" [RefSourceTestA] submitted that has a "Referral Source" code entered than includes an uppercase "P" character anywhere within its name along with any other desired characters
- Have a "Referral Source" [RefSourceTestB] submitted that has a "Referral Source" code entered than does 'not' include an uppercase "P" character anywhere within its name along with any other desired character
Steps
- Open form [TestForm]
- In the "Select Referral Source" field, select [RefSourceTestA]
- Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
- Populate all other required and desired fields on the form
- Submit the form
- Validate the form submits successfully
- Re-open form [TestForm]
- In the "Select Referral Source" field, select [RefSourceTestA]
- At the "Pre-Display" screen, select the row just submitted in step 1
- Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
- Validate all other fields populated in step 1, are populated as expected
- Open form [TestForm]
- In the "Select Referral Source" field, select [RefSourceTestB]
- Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
- Populate all other required and desired fields on the form
- Submit the form
- Validate the form submits successfully
- Re-open form [TestForm]
- In the "Select Referral Source" field, select [RefSourceTestB]
- At the "Pre-Display" screen, select the row just submitted in step 3
- Validate the [RefferralSortDate] field is automatically populated with today's date, as expected
- Validate all other fields populated in step 3, are populated as expected
|
Topics
• Modeling
• NX
• Referral
|