UTC enabled - Data Entry Local Time
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- App Dashboard
- Practitioner Enrollment
- Admission
- Client Charge Input
- Client Ledger
- Dynamic Forms CADDS Data Collection Verification
Scenario 1: Validating Practitioner Enrollment with UTC Enabled
Specific Setup:
- The system must be configured to use UTC.
- A practitioner must be enrolled in the system.
Steps
- Open the "Practitioner Enrollment" form.
- Select the practitioner from setup and update their enrollment.
- Click "Submit" to file the data.
- Using the preferred method to validate SQL tables, validate the following columns exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset (e.g -4), data_entry_time_j (e.g. 12:26:13), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g EDT), data_entry_utc (e.g. 9/21/2022 16:26).
- Using the preferred method to validate SQL tables, validate the data_entry_time (e.g. 12:26 PM) in the SQL table SYSTEM.sfaff_category_history appropriately reflects the time of data entry.
Scenario 2: Validating Practitioner Enrollment with UTC disabled
Specific Setup:
- A practitioner must be enrolled in the system.
Steps
- Open the "Practitioner Enrollment" form.
- Select the practitioner from setup and update a field in the enrollment.
- Click "Submit" to file the data.
- Using the preferred method to validate SQL tables, validate the following columns don't exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset, data_entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short), data_entry_utc.
- Using the preferred method to validate SQL tables, validate the data_entry_time (e.g. 12:26 PM) in the SQL table SYSTEM.sfaff_category_history appropriately reflects the time of data entry.
Scenario 3: Validating Client Charge Input with UTC enabled
Specific Setup:
- The system must be configured to use UTC.
- Admit a new client or select an existing client for the test client.
Steps
- Open the "Client Charge Input" form.
- Enter a service charge for the test client.
- Using the "Client Ledger" form, validate the service was generated.
- Using the preferred method to validate SQL tables, validate the following columns in the SYSTEM.billing_tx_history table: data_entry_offset (e.g. -4), data _entry_time_j (e.g. 12:26:13), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g. EDT), data_entry_utc (e.g. 09/20/2022 16:26)
- Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry.
Scenario 4: Validating Client Charge Input with UTC disabled
Specific Setup:
- Admit a new client or select an existing client for the test client.
Steps
- Open the "Client Charge Input" form.
- Enter a service charge for the test client.
- Using the "Client Ledger" form, validate the service was generated.
- Using the preferred method to validate SQL tables, validate the following columns don't exist in the SYSTEM.billing_tx_history table: data_entry_offset, data _entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short, data_entry_utc.
- Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry.
|
Topics
• Client Charge Input
• NX
• Practitioner
|
