Modeled forms - table aliasing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Modeled Forms - "Table Alias" field and data validations
Specific Setup:
- Have two clients who are active in an existing episode's. [TestClientA], [TestClientB] and [TestClientC]
- Have a modeled form [TestAlias] that contains a table with:
- Mapped "Table" aliased fields. For example "Service" alias type fields:
- "Date of Service", "Service Code", "Practitioner", "Program", and "Duration". (Note: these fields all must be populated to file the table alias)
- Any other fields. For example, a "Draft/Final" or a "Date" field
- Have a report [ReportA] created to display data in the "SYSTEM.Billing_tx_history" table
- Have a report [ReportB] created to display data filed in the table used in form [TestAlias]
Steps
- Open [AliasForm]
- Select [TestClientA]
- Populate all the required fields to file the table alias: "Date of Service", "Service Code", "Practitioner", "Program", and "Duration"
- Populate any other desired fields on the form
- Submit the form as "Final".
- Validate submission is successful
- Close the form
- Generate [ReportA] to display the fields in the "SYSTEM.billing_tx_history" table
- Validate a new row is found for the service created by the modeled form in step1a
- Validate the "Date of Service", "Service Code", "Practitioner, Program", "Duration" and "Join_To_Tx_history" fields are populated as expected
- Generate [ReportB] to display data in the table field in the modeled form
- Validate all fields populated in step1a, are populated as expected
- Open [AliasForm]
- Select [TestClientB]
- Populate just one or more but "not" all the required fields necessary, to file the table alias data
- Populate any other desired fields on the form
- Submit as the form as "Final"
- Validate there are no messages indicating required fields are missing and the form files successfully
- Generate [ReportA] to display the fields in the "SYSTEM.billing_tx_history" table
- Validate there is not a new row in the table for the row filed in step 2a as expected, since not all the required fields to file the table alias were not populated when submitting the form
- Generate [ReportB] to display data in the table field in the modeled form
- Validate all fields populated in step 2a, are populated as expected
- Open [AliasForm]
- Select [TestClientC]
- Populate none of the required fields necessary to file the table alias data
- Populate any other desired fields on the form
- Submit as the form as "Final"
- Validate there are no messages indicating required fields are missing and the form files successfully
- Generate [ReportA], to display the fields in the "SYSTEM.billing_tx_history" table
- Validate there is not a new row in the table for the row filed in step 3a as expected, since all the required fields to file the table alias were not populated when submitting the form
- Generate [ReportB] to display data in the table field in the modeled form
- Validate any fields populated in step 3a, are populated as expected
|
Topics
• Diagnosis
• NX
|
