Avatar CareFabric 2023 is Installed
Scenario 1: Validate Upgrading Avatar CareFabric 2022 to 2023 is successful when 2022.04.00 is loaded
Specific Setup:
- Latest Monthly Release is installed.
Steps
- Open the "Product Updates" form.
- Select the appropriate [Namespace] from the Application dropdown list
- Click [Select Update/Customization Pack].
- Browse to the location for the updates and select the Update 1.
- Click [OK] on the "File Upload Complete" window.
- Click [Review Update/Customization Pack Contents].
- Verify Update 1 is included.
- Click [Install Update/Customization Pack].
- Click [OK] when the install completes.
- Click [Close Form].
|
Topics
• Upgrade
|
|
Topics
• Service Authorizations
• ProviderConnect Enterprise
|
CarePOV Management - 'Duplicate Name - Header' alert type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Lookup/Header Configuration Manager
- CarePOV Management
- Diagnosis
- Update Client Data
- Orders This Episode
- Pre-Display Confirmation
Scenario 1: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type based on 'Full Name (First and Last)'
Specific Setup:
- "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form.
- The user has access to the 'Client Information Header' on the HomeView.
- Two clients are defined with the same first & last name (Client A & Client B).
- A third client is defined with a different first & last name (Client C).
Steps
- Access the 'CarePOV Management' form.
- Select the "Client Alerts" section.
- Click "Add" in the 'Add or Edit Alert' field.
- Select "Duplicate Name - Header" in the 'Alert Type' field.
- Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
- Select "Full Name (First and Last)" in the 'Base Duplicate Name On' field.
- Enter the desired value in the 'Client Alert Description' field.
- Select the desired icon in the 'Select Icon' field.
- Select "Yes" in the 'Active' field.
- Select "Yes" in the 'Include in Client Header' field.
- Click [Save].
- Validate a message is displayed stating: Saved.
- Click [OK] and close the form.
- Select "Client A" and navigate to the 'Client Information Header'.
- Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
- Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
- Select "Client B" and navigate to the 'Client Information Header'.
- Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
- Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
- Select "Client C" and navigate to the 'Client Information Header'.
- Validate the duplicate name alert is not displayed.
Scenario 2: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type based on 'First Name, Last Initial'
Specific Setup:
- "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form.
- The user has access to the 'Client Information Header' on the HomeView.
- Two clients are defined with the same first name & last initial (Client A & Client B).
- A third client is defined with a different first name & last initial (Client C).
Steps
- Access the 'CarePOV Management' form.
- Select the "Client Alerts" section.
- Click "Add" in the 'Add or Edit Alert' field.
- Select "Duplicate Name - Header" in the 'Alert Type' field.
- Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
- Select "First Name, Last Initial" in the 'Base Duplicate Name On' field.
- Enter the desired value in the 'Client Alert Description' field.
- Select the desired icon in the 'Select Icon' field.
- Select "Yes" in the 'Active' field.
- Select "Yes" in the 'Include in Client Header' field.
- Click [Save].
- Validate a message is displayed stating: Saved.
- Click [OK] and close the form.
- Select "Client A" and navigate to the 'Client Information Header'.
- Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
- Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
- Select "Client B" and navigate to the 'Client Information Header'.
- Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
- Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
- Select "Client C" and navigate to the 'Client Information Header'.
- Validate the duplicate name alert is not displayed.
Scenario 3: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type based on 'Last Name & First Initial'
Specific Setup:
- "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form.
- The user has access to the 'Client Information Header' on the HomeView.
- Two clients are defined with the same last name & first initial (Client A & Client B).
- A third client is defined with a different last name & first initial (Client C).
Steps
- Access the 'CarePOV Management' form.
- Select the "Client Alerts" section.
- Click "Add" in the 'Add or Edit Alert' field.
- Select "Duplicate Name - Header" in the 'Alert Type' field.
- Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
- Select "Last Name, First Initial" in the 'Base Duplicate Name On' field.
- Enter the desired value in the 'Client Alert Description' field.
- Select the desired icon in the 'Select Icon' field.
- Select "Yes" in the 'Active' field.
- Select "Yes" in the 'Include in Client Header' field.
- Click [Save].
- Validate a message is displayed stating: Saved.
- Click [OK] and close the form.
- Select "Client A" and navigate to the 'Client Information Header'.
- Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
- Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
- Select "Client B" and navigate to the 'Client Information Header'.
- Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
- Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
- Select "Client C" and navigate to the 'Client Information Header'.
- Validate the duplicate name alert is not displayed.
Scenario 4: CarePOV Management - Client Alerts - Field Validations
Steps
- Access the 'CarePOV Management' form.
- Select the "Client Alerts" section.
- Click "Add" in the 'Add or Edit Alert' field.
- Validate "Duplicate Name - Header" is displayed in the 'Alert Type' field.
- Validate the previous "Duplicate Name" alert has been renamed as "Duplicate Name - BedBoard" in the 'Alert Type' field.
- Validate the 'Base Duplicate Name Alert On' field is displayed and initially disabled. This field will become enabled/required when the "Duplicate Name - Header" alert type is selected.
- Validate the 'Base Duplicate Name Alert On' field contains the following values: "First Name, Last Initial", "Full Name (First and Last)", and "Last Name, First Initial".
- Select "Duplicate Name - Header" in the 'Alert Type' field.
- Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
- Select the desired value in the 'Base Duplicate Name Alert On' field.
- Enter the desired value in the 'Client Alert Description' field.
- Select the desired icon in the 'Select Icon' field.
- Select "Yes" in the 'Active' field.
- Select "Yes" in the 'Include in Client Header' field.
- Click [Save].
- Validate a message is displayed stating: Saved.
- Click [OK].
- Select "Edit" in the 'Add or Edit Alert' field.
- Select the alert added in the previous steps in the 'Client Alert' field.
- Validate all previously filed data is displayed.
- Close the form.
|
Topics
• Client Alerts
• CarePOV Management
|
Avatar CareFabric - 'GetOrganization' SDK action
Scenario 1: Validate the 'GetOrganization' payload
|
Topics
• CareFabric
|
Mobile CareGiver+ - Appointment Tasks
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- CarePOV Management
- Scheduling Calendar - Status Update
Scenario 1: Mobile Caregiver+ - Validate the 'EvvAppointmentUpdated' outgoing event for a scheduled appointment
Specific Setup:
- Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative.
- A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A).
- "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element:
- Extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" is set to "Home".
- If the above dictionary data element is not defined, then the extended dictionary data element "(578) Place Of Service (HCFA 24-B)" will be used.
- A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A).
- Dictionary values must be defined for the 'Other Tabled Files' - '(424) Available Electronic Visit Verification Tasks' Data Element in 'Dictionary Update (PM)'.
- Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A).
- The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form:
- "Yes" is selected in the 'Enable Mobile CareGiver+' field.
- "Yes" is selected in the 'Send Non EVV Payers' field.
- "No" is selected in the 'Require Authorization' field.
- "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid.
- A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A).
- A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A).
Steps
- Access the 'Scheduling Calendar' form.
- Right click in any available time slot for "Practitioner A" and click [Add Appointment].
- Select "Service Code A" in the 'Service Code' field.
- Select "Client A" in the 'Client' field.
- Validate the 'Program' field contains "Program A".
- Validate the 'Location' field contains "Location A".
- Select the desired value(s) in the 'Available Tasks' field.
- Populate all other required and desired fields.
- Click [Submit].
- Validate the new appointment is displayed.
- Click [Dismiss].
- Access the 'CareFabric Monitor' form.
- Enter the current date in the 'From Date' and 'Through Date' fields.
- Select "Client A" in the 'Client ID' field.
- Select "EvvAppointmentUpdated" in the 'Event/Action Search' field.
- Click [View Activity Log].
- Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record.
- Click [Click To View Record].
- Validate the 'appointmentAuthorization' field contains "null".
- Validate the 'appointmentID' - 'id' field contains the appointment ID.
- Validate the 'canceledDate' field contains "null".
- Validate the 'canceledReasonCode' field contains "null".
- Validate the 'providerOrganizationID' - 'id' field contains the 'Provider Organization ID' assigned to "Program A".
- Validate the 'clientID' - 'id' field contains the ID for "Client A".
- Validate the 'diagnosisCodes' - 'code' field contains the diagnosis code on file for "Client A".
- Validate the 'diagnosisCodes' - 'displayName' field contains the diagnosis value on file for "Client A".
- Validate the 'endDate' field contains the appointment end date/time.
- Validate the 'insPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
- Validate the 'insPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
- Validate the 'isEVV' field contains "true".
- Validate the 'locationOfService' fields contain "Client A's" home address.
- Validate the 'mcgInsPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
- Validate the 'mcgInsPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
- Validate the 'services' - 'description' field contains the description for "Service Code A".
- Validate the 'services' - 'name' field contains the code for "Service Code A".
- Validate the 'services' - 'procedureCode' - 'code' field contains the code for "Procedure A".
- Validate the 'services' - 'procedureCode' - 'displayName' field contains the name for "Procedure A".
- Validate the 'serviceID' - 'id' field contains the code for "Service Code A".
- Validate the 'tasks' - 'taskCode' fields contain the value(s) selected in the 'Available Tasks' field when scheduling the appointment.
- Validate the 'startDate' field contains the appointment start date/time.
- Validate all other relevant information is displayed for "Client A" and "Practitioner A".
- Close the report and the form.
Scenario 2: Mobile Caregiver+ - Validate the 'McgEvvVisitDocumented' incoming event for a completed visit
Specific Setup:
- Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative.
- A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field.
- In the 'Code Mappings' section of the 'CareFabric Integration Management' form, must have a "Note Type" mapping for the "MobileCareGiver+" product with "EVV" populated in the 'CareFabric Code' and 'Description' fields. This note type will be used for creating a progress note when the 'McgEvvVisitDocumented' incoming SDK event is received.
- A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A).
- "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element:
- Extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" is set to "Home".
- If the above dictionary data element is not defined, then the extended dictionary data element "(578) Place Of Service (HCFA 24-B)" will be used.
- A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A).
- Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A).
- The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form:
- "Yes" is selected in the 'Enable Mobile CareGiver+' field.
- "Yes" is selected in the 'Send Non EVV Payers' field.
- "No" is selected in the 'Require Authorization' field.
- "No" is selected in the 'Require Cancellation Reason' field.
- "Yes" is selected in the 'Save Progress Notes' form.
- A progress note form selected in the 'Progress Note Form' and/or other progress note forms defined in the 'Progress Notes Form Mapping' grid. If nothing is defined in the 'Progress Notes Form Mapping' grid, the default progress note selected in the 'Progress Note Form' field will be used.
- "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid.
- The 'Progress Notes' widget must be accessible from the HomeView.
- A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A).
- A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A).
- "Client A" has a visit with "Practitioner A" that has been started in Mobile CareGiver+.
Steps
- Complete the visit for "Client A" with "Practitioner A" in the Mobile CareGiver+ application.
- Ensure the visit includes completed tasks & notes.
- Access the 'Scheduling Calendar' form.
- Validate the appointment for "Client A" is displayed at the correct start/end times for the visit.
- Validate the appointment for "Client A" is displayed with the posted and finalized note disposition icons.
- Click [Dismiss].
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the progress note created when the visit was completed is displayed with the appropriate data for the visit.
- Validate the 'Notes Field' field for the progress note contains the notes entered when completing the visit, followed by a list of the tasks completed during the visit.
- Access Crystal Reports or other SQL Reporting tool.
- Select the PM namespace.
- Create a report using the 'SYSTEM.appt_data' SQL table.
- Navigate to the appointment for "Client A".
- Validate the 'carefabric_appt_stat_code' field contains "COMP".
- Validate the 'carefabric_appt_stat_value' field contains "Completed".
- Close the report.
Mobile CareGiver+ - Unscheduled Visits
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- CareFabric Integration Reconciliation
Scenario 1: Mobile Caregiver+ - Validate the 'McgEvvAppointentUpdated' incoming event when the 'Enable 'Admission vs. Service Program' Functionality' registry setting is enabled
Specific Setup:
- Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative.
- A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field.
- The 'Enable 'Admission vs. Service Program' Functionality' registry setting is set to "Y".
- An admission program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A).
- "Program A" must have an associated service program in the 'Associated Service Program' field in the 'Program Maintenance' form (Program B).
- "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element:
- Extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" is set to "Home".
- If the above dictionary data element is not defined, then the extended dictionary data element "(578) Place Of Service (HCFA 24-B)" will be used.
- A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A).
- Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A).
- The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form:
- "Yes" is selected in the 'Enable Mobile CareGiver+' field.
- "Yes" is selected in the 'Send Non EVV Payers' field.
- "No" is selected in the 'Require Authorization' field.
- "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid.
- A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A).
- A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A).
Steps
- Add an unscheduled visit in the Mobile CareGiver+ application with associated tasks for "Client A" with "Practitioner A".
- Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form.
- Access the 'Scheduling Calendar' form.
- Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed.
- Right click on the appointment and click [Details/Edit].
- Validate the appointment details are displayed as expected.
- Validate the 'Service Code' field contains "Service Code A".
- Validate the 'Client' field contains "Client A".
- Validate the 'Episode Number' field contains the episode in "Program A".
- Validate the 'Practitioner' field contains "Practitioner A".
- Validate the 'Program' field contains "Program B".
- Validate the 'Available Tasks' field contains the tasks sent from Mobile CareGiver+.
- Close the form and click [Dismiss].
|
Topics
• Scheduling Calendar
• Add New Appointment
• CareFabric Monitor
• Electronic Visit Verification
• Registry Settings
|
Bells Notes Integration - Document Approver
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Dynamic Form - document routing - Route Document To
- HomeView - Progress Notes Widget
- HomeView - my Clients
Scenario 1: Validate the 'SelectDocumentApprover' SDK action
Avatar CareFabric - Service Strategy Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Ambulatory Progress Notes (Diagnosis Entry)
Scenario 1: Progress Notes (Group and Individual) - Service Strategy Codes
Specific Setup:
- The logged in user is associated to a staff member ("Staff Member A").
- A client is enrolled in an existing episode ("Client A").
- Document Routing is enabled in the 'Document Routing Setup' form for 'Progress Notes (Group and Individual)' form.
- "Avatar PM->Services->->->->Enable Evidence Based Practice Fields" registry setting is set to "Y".
- "Avatar PM ->California Required EDI->CSI->->->Enable MHSA/DIG Data Collection Fields" registry setting is set to "N"
- Existing Progress Note with 'Evidence-Based Practices / Service Strategies (CSI)' field enabled in 'Site Specific Section Modeling' form: 'Exclude From Data Collection Instrument' field set to "No".
- One or more service strategy dictionary codes defined in CWS (70680) "Evidence-Based Practices / Service Strategies (CSI)" with selected values.
- One or more service strategy dictionary codes defined in PM (10560) "Evidence-Based Practices" with selected values.
Steps
- Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
- Select any value from the 'Select Episode' field.
- Select "New Service" from the 'Progress Notes For' field.
- Select any value from the 'Note Type' field.
- Set the 'Notes Field' to any value.
- Set the 'Date Of Service' field to the current date.
- Set the 'Service Charge Code' field to any value.
- Select the desired value in the 'Evidence Based Practices' field.
- Select the desired value in the 'Evidence Based Practices / Service Strategies (CSI)' field.
- Complete the required fields with the desired value.
- Select "Draft" from the 'Draft/Final' field.
- Click [File Note].
- Validate a 'Progress Notes message' is displayed stating: "Note Filed".
- Click [OK] and close the form.
- Select "Client A" and navigate to the "Progress Notes" widget.
- Locate the note that was just filed in the previous steps.
- Validate the saved strategy service codes are displayed under the "Evidence Based Practices" section.
- Validate the saved strategy service codes are displayed under the "Evidence Based Practices / Service Strategies (CSI)" section.
Bells Notes Integration - CPT Code Calculation
Scenario 1: Progress Notes (Group and Individual) - Validate CPT code calculation
Specific Setup:
- Have two users: [UserA] and [UserB]
- Both users have the "My To Do's" widget on their home view
- [UserA] is defined with the following:
- An associated staff member ("Staff Member A").
- User with existing client admitted with financial eligibility on file ("Client A").
- Document Routing is enabled in the 'Document Routing Setup' form for 'Progress Notes (Group and Individual)' form.
- "Avatar CWS->Progress Notes->Additional Fields->->->Guarantors To Capture Additional Service Info On Progress Notes" registry setting is set to multiple guarantor codes (e.g. 1&2&100)
- The 'Progress Notes (Group and Individual)' form has a 'Scrolling Free Text' field (CPT Code, Modifiers, Total Units) enabled with a 'Product Custom Logic Definition' for "Capture CPT Code, Modifiers, Total Units For All Rendered Services". This can be done via 'Site Specific Section Modeling'.
- [UserB] with an associated staff member ("Staff Member B")
Steps
- Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
- Select any value from the 'Select Episode' field.
- Select "New Service" from the 'Progress Notes For' field.
- Select any value from the 'Note Type' field.
- Set the 'Notes Field' to any value.
- Set the 'Date Of Service' field to the current date.
- Set the 'Service Charge Code' field to any value.
- Complete the required fields with the desired value.
- Verify the existence of the 'CPT Code, Modifier, Total Units' field.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Validate that the 'Confirm Document' dialog is displayed with the progress note data, including an electronic signature at the bottom for "Staff Member A" as the Author.
- Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the document.
- Click [Accept and Route].
- Enter the desired value in the 'Password' field.
- Click [OK].
- Validate the 'Route Document To' dialog is displayed.
- Search for "Staff Member B" in the "Add Approver" field.
- Click [Add].
- Validate "Staff Member B" is added as an "Approver" and the "Approver" check box is selected.
- Click [Submit].
- Validate a 'Progress Notes message' is displayed stating: "Note Filed".
- Click [OK].
- Click [Discard].
- Log in as [UserB] and navigate to the "My To Do's" widget.
- Validate there is a To-Do for the progress note filed in the previous steps.
- Click [Approve Document].
- Validate the document is displayed with the progress note data, including an electronic signature at the bottom for "Staff Member A" as Author and "Staff Member B" as Final Approver.
- Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the document.
- Click [Acknowledge].
- Enter the password for "User B" in the 'Verify Password' dialog and click [OK].
- Validate the To-Do is no longer displayed.
- Log in as [UserA] and navigate to the "Progress Notes" widget.
- Select "ClientA" in the 'Select Client' field.
- Locate the note that was just finalized in the previous steps.
- Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the progress note.
- Access the 'Clinical Document Viewer' form.
- Select "Individual" in the 'Select All or Individual Patient' field.
- Select "Client A" in the 'Select Client' field.
- Select the desired value in the "Episode" field.
- Click [Process].
- Select the document that was just finalized from the document list.
- Validate the document is displayed with the progress note data, including an electronic signature at the bottom for "Practitioner A" as Author and "Practitioner B" as Attending Practitioner.
- Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the document.
- Click [Close All Documents].
- Validate the document is closed.
|
Topics
• CareFabric
• Progress Notes
|
Flowsheet - Administered Medications
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Flowsheet - Validate display of medications in the 'Graph' section
Specific Setup:
- A client is enrolled in an existing episode (Client A) with the following:
- Active medications that have been administered via Avatar eMAR with different administration dosage amounts.
Steps
- Navigate to the 'Flowsheet' application.
- Select "Client A" and navigate to the "Graph" section.
- Select the "Meds" sub-section.
- Validate the list of active medications for "Client A" are displayed.
- Select an administered medication.
- Validate the graph displays the appropriate data including:
- Recorded administration date/time
- Dosage
- Units
- Validate the graph points are displayed as expected.
|
Topics
• Active Medications
|
Orders This Episode - Lab Orders with multiple diagnosis
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: OE NX - Orders This Episode - Multiple Diagnosis on Lab Orders
Specific Setup:
- Avatar OE 2023 Update 8, Avatar CareFabric 2023 Update 9, and Avatar NX Release 2023.03.00 are required in order to utilize full functionality.
- The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Enable Supplemental Diagnoses for Lab Orders in OE Console (Orders This Episode)' registry setting must be set to "Y".
- A lab-type order code must have an external lab vendor selected in the 'External Lab Definition' portion of the 'Order Code Setup' form. (Complete Blood Count)
- Please log out of the application and log back in after completing the above configuration.
- A client must have an active inpatient episode. (Client A)
- “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
- "Client A" must have two values filed in the 'Diagnosis' form. (Diagnosis A and Diagnosis B)
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select "Complete Blood Count" in the 'New Order' field.
- Validate the 'External Lab Vendor Destination' field contains a value.
- Set the 'Duration' field to any value and click [Days].
- Validate a [+] is displayed in front of the 'Diagnosis' fields.
- Validate the 'Diagnosis' fields are not required.
- Click the [+] three times.
- Validate two additional 'Diagnoses' rows were added.
- Validate that all 'Diagnoses' fields are required.
- Select "Diagnosis A" in the 1st 'Diagnosis' selection field.
- Search for and select any value in the 1st 'Diagnosis' search field and validate the 1st 'Diagnosis' selection field is cleared.
- Select "Diagnosis A" in the 1st 'Diagnosis' selection field and validate the 1st 'Diagnosis' search field is cleared.
- Click in the 2nd 'Diagnosis' selection field and validate that "Diagnosis A" is not displayed.
- Select "Diagnosis B" in the 2nd 'Diagnosis' selection field.
- Search for and select any value in the 3rd 'Diagnosis' search field.
- Validate the 4th 'Diagnoses' fields do not contain a value.
- Click [Add to Scratchpad].
- Validate the order is displayed in the 'Scratchpad' with a red flag in the 'Action' column.
- Select the order in the 'Scratchpad' and click the red [x] next to the 4th 'Diagnoses' fields and click [Update Order].
- Validate the red flag is no longer displayed and click [Sign].
- Validate the 'Order grid' contains the "Complete Blood Count" order.
- Select the order in the 'Order grid' and click [Copy].
- Validate the 'Diagnoses' fields contain the same values that were selected and that all values appear in the search fields on the right.
- Click Refresh.
- Select the order in the 'Order grid' and click [Modify].
- Validate the 'Diagnoses' fields contain the same values that were selected and that all values appear in the search fields on the right.
- Click Refresh.
|
Topics
• Order Entry Console
• NX
|
Avatar CareFabric - 'ListIntegratedCareVisit' SDK action
Scenario 1: Validate the 'ListIntegratedCareVisit' SDK action
|
Topics
• CareFabric
|
Avatar CareFabric - BedBoard
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Summary Display
- Diagnosis
- Allergies and Hypersensitivities
- Financial Eligibility
Scenario 1: BedBoard - Field/Data Validations
Specific Setup:
- The 'BedBoard' POV is configured and accessible on the user's HomeView.
- A client (Client A) is enrolled in an existing inpatient episode with the following on file: Emergency Contact, Alias, Diagnosis, Financial Eligibility, Allergies, Date of Birth, Race, New Order.
Steps
- Access the 'BedBoard' POV.
- Select the unit "Client A" is admitted into from the left-hand side.
- Validate "Client A" displays under the correct room.
- Click on "Client A" to launch the client summary.
- Validate the 'Client Name' field contains the first name, last initial, age, gender, and any applicable client alerts.
- Validate the 'Attending Physician' field contains the attending physician for "Client A".
- Validate the 'Discharge Status' field contains the discharge status for "Client A".
- Validate the 'Room Assignment' field contains the room "Client A" is assigned to.
- Validate the 'Bed Assignment' field contains the bed "Client A" is assigned to.
- Validate the 'Emergency Contact' field contains the emergency contact on file for "Client A".
- Validate the 'Alias' field contains the alias on file for "Client A".
- Validate the 'Primary Dx' field contains the primary diagnosis on file for "Client A".
- Validate the 'Treatment Team' field contains the treatment team for "Client A".
- Validate the 'Payor' field contains the guarantor on file in 'Financial Eligibility' for "Client A".
- Validate the 'Allergies' field contains the allergy on file for "Client A".
- Validate the 'DOB' field contains the date of birth for "Client A".
- Validate the 'Admission Date' field contains the admission date for "Client A".
- Validate the 'Race' field contains the race on file for "Client A".
- Validate the 'Next Med Admin Time' field contains the time of next medication administration for "Client A".
- Close the client summary.
|
Topics
• Bed Board
• CareFabric
|
Avatar CareFabric - Practitioner Credentials
Scenario 1: Validate the 'ListBehavioralHealthEpisode' SDK action
Scenario 2: Validate the 'GetBehavioralHealthEpisode' SDK action
|
Topics
• CareFabric
|
ProviderConnect Enterprise - 'Diagnosis' data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Diagnosis
- Women's Health History
Scenario 1: ProviderConnect Enterprise - Validate the 'PutDiagnosis' and 'PutDiagnosisEntry' actions
Specific Setup:
- The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
- The 'Managing Organization Definition' form must be defined for a valid managing organization.
- A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
- A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A).
Steps
- Select "Client A" and access the 'Diagnosis' form.
- Select the episode mapped to the managing organization from the Pre-Display.
- Click [OK].
- Select the desired value in the 'Type Of Diagnosis' field.
- Enter the desired date in the 'Date Of Diagnosis' field.
- Enter the desired time in the 'Time Of Diagnosis' field.
- Click [New Row].
- Enter the desired value in the 'Diagnosis Search' field.
- Validate the 'Ranking' field contains "Primary".
- Enter "Practitioner A" in the 'Diagnosing Practitioner' field.
- Select the "Additional Diagnosis Information" section.
- Select the desired value in the 'Trauma (CSI)' field.
- Select the desired value(s) in the 'General Medical Condition Summary Code (CSI)' field.
- Select "Yes" in the 'Substance Abuse / Dependence (CSI)' field.
- Select the desired value in the 'Substance Abuse / Dependence Diagnosis (CSI)' field.
- Click [Submit].
- Validate a "Pre-Display Confirmation" message is displayed stating: Do you want to return to Pre-Display?
- Click [No].
- Access the 'ProviderConnect Enterprise Action Log'.
- Enter the desired dates in the 'From Date' and 'Through Date' fields.
- Enter the desired times in the 'From Time' and 'Through Time' fields.
- Select the desired organization in the 'Managing Organization' field.
- Select "PutDiagnosis" in the 'Action Name' field.
- Click [View Action Log].
- Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
- Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutDiagnosis' action that was triggered from the 'Diagnosis' form with a "Success" result.
- Close the report.
- Select "PutDiagnosisEntry" in the 'Action Name' field.
- Click [View Action Log].
- Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
- Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutDiagnosisEnry' action that was triggered from the 'Diagnosis' form with a "Success" result.
- Close the report and the form.
|
Topics
• Diagnosis
• ProviderConnect Enterprise
|
Avatar CareFabric - 'GetClient' SDK action
Scenario 1: Validate the 'GetClient' SDK action
Avatar CareFabric - 'GetProvider' SDK action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validate the 'GetProvider' SDK action
|
Topics
• CareFabric
|
Review Results - 'ClinicalNoteFinalized' SDK event
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Results Entry
- Review Results
- Review Results (CLIENT)
Scenario 1: Review Results - Validate the 'ClinicalNoteFinalized' SDK event
Specific Setup:
- A client is enrolled in an existing episode and has lab results on file (Client A).
Steps
- Access the 'Review Results' form.
- Select "Client A" in the 'Client ID' field.
- Select the lab results on file in the 'Select Results' field.
- Enter the desired value in the 'Comments' field.
- Populate any other desired fields.
- Click [Submit] and close the form.
- Access the 'CareFabric Monitor' form.
- Enter the current date in the 'From Date' and 'Through Date' fields.
- Select "Client A" in the 'Client ID' field.
- Select "ClinicalNoteFinalized" in the 'Event/Action Search' field.
- Click [View Activity Log].
- Validate a "ClinicalNoteFinalized" record is displayed, triggered from the 'Review Results' form.
- Click [Click To View Record].
- Validate the 'clientID' - 'id' field contains "Client A".
- Validate the 'clinicalNotes' - 'notes' field contains the value entered in the 'Comments' field in the previous steps.
- Validate the 'notingProviderID' - 'id' field contains the logged in user.
- Validate the 'documentDescription' field contains "LAB".
- Validate the 'documentTitle' field contains "LAB".
- Close the report and the form.
'ClinicalNoteFinalized' SDK event - 'Diagnosis' section
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Ambulatory Progress Notes (Diagnosis Entry)
- Inpatient Progress Notes (Diagnosis Entry)
Scenario 1: Clinical Notes Mapping - Ambulatory Progress Notes (Diagnosis Entry) - Validate the 'ClinicalNoteFinalized' SDK event
Specific Setup:
- A client is enrolled in an outpatient episode (Client A).
- The 'Ambulatory Progress Notes (Diagnosis Entry)' form is flagged in the 'Flag Assessment Forms' form.
Steps
- Access the 'Clinical Notes Mapping' form.
- Select "Consultation Note" in the 'Type of CCDA Document' field.
- Select "[Avatar CWS] Ambulatory Progress Notes (Diagnosis Entry) (CWS7003)" in the 'Care Record Form to Map' field.
- Select "Activities" in the 'Note Type to Map' field.
- Validate the 'CCDA Document Title' field contains "Consultation Note".
- Select "Discharge Diagnosis" in the 'Standard Sections To Include To CCD' field.
- Select "Yes" in the 'Enabled' field.
- Click [New Row] in the 'Field Settings' grid.
- Select "Progress Note" in the 'CCDA Field Name' field.
- Select "[Avatar CWS] Ambulatory Progress Notes (Diagnosis Entry) (CWS7003)" in the 'Care Record Form/Assessment' field.
- Select "Notes Field" in the 'Care Record Field Name' field.
- Click [Submit] and close the form.
- Select "Client A" and access the 'Ambulatory Progress Notes (Diagnosis Entry)' form.
- Select "New Service" in the 'Progress Note For' field.
- Select "Activities" in the 'Note Type' field.
- Enter the desired value in the 'Notes Field' field.
- Enter the current date in the 'Date Of Service' field.
- Enter the desired service code in the 'Service Charge Code' field.
- Select the desired value in the 'Diagnosis 1' field.
- Validate the 'Are you releasing to myHealthPointe or External providers?' field is visible and required. Please note: this field will only become visible when a note type that is mapped in the 'Clinical Notes Mapping' form is selected for the progress note form being used.
- Select "myHealthPointe" in the 'Are you releasing to myHealthPointe or External providers?' field.
- Select "Final" in the 'Draft/Final' field.
- Click [Submit] and close the form.
- Access the 'CareFabric Monitor' form.
- Enter the current date in the 'From Date' and 'Through Date' fields.
- Select "Client A" in the 'Client ID' field.
- Select "ClinicalNoteFinalized" in the 'Event/Action Search' field.
- Click [View Activity Log].
- Validate a 'ClinicalNoteFinalized' record is displayed.
- Click [Click To View Record].
- Validate the 'clinicalNotes' - 'notes' field contains the value entered in the 'Notes Field' in the previous steps.
- Validate the 'diagnoses' section is populated with the information for the 'Diagnosis 1' value selected in the previous steps.
- Validate the 'documentDescription' field contains "Consultation Note".
- Validate the 'documentID' - 'id' field contains a unique identifier.
- Validate the 'documentTitle' field contains "Consultation Note".
- Validate the 'includedSectionCodes' - 'code' field contains "Discharge Diagnosis".
- Validate the 'includedSectionCodes' - 'displayName' field contains "Discharge Diagnosis".
- Validate the 'isReleaseExternal' field contains "false".
- Validate the 'isReleaseToPatient' field contains "true".
- Close the report and the form.
Scenario 2: Clinical Notes Mapping - Inpatient Progress Notes (Diagnosis Entry) - Validate the 'ClinicalNoteFinalized' SDK event
Specific Setup:
- A client is enrolled in an inpatient episode (Client A).
- The 'Inpatient Progress Notes (Diagnosis Entry)' form is flagged in the 'Flag Assessment Forms' form.
Steps
- Access the 'Clinical Notes Mapping' form.
- Select "Discharge Summary" in the 'Type of CCDA Document' field.
- Select "[Avatar CWS] Inpatient Progress Notes (Diagnosis Entry) (CWS7002)" in the 'Care Record Form to Map' field.
- Select "Activities" in the 'Note Type to Map' field.
- Validate the 'CCDA Document Title' field contains "Discharge Summary".
- Select "Discharge Diagnosis" in the 'Standard Sections To Include To CCD' field.
- Select "Yes" in the 'Enabled' field.
- Click [New Row] in the 'Field Settings' grid.
- Select "Progress Note" in the 'CCDA Field Name' field.
- Select "[Avatar CWS] Inpatient Progress Notes (Diagnosis Entry) (CWS7002)" in the 'Care Record Form/Assessment' field.
- Select "Notes Field" in the 'Care Record Field Name' field.
- Click [Submit] and close the form.
- Select "Client A" and access the 'Inpatient Progress Notes (Diagnosis Entry)' form.
- Select "New Service" in the 'Progress Note For' field.
- Select "Activities" in the 'Note Type' field.
- Enter the desired value in the 'Notes Field' field.
- Enter the current date in the 'Date Of Service' field.
- Enter the desired service code in the 'Service Charge Code' field.
- Select the desired value in the 'Diagnosis 1' field.
- Validate the 'Are you releasing to myHealthPointe or External providers?' field is visible and required. Please note: this field will only become visible when a note type that is mapped in the 'Clinical Notes Mapping' form is selected for the progress note form being used.
- Select "None" in the 'Are you releasing to myHealthPointe or External providers?' field.
- Select "Final" in the 'Draft/Final' field.
- Click [Submit] and close the form.
- Access the 'CareFabric Monitor' form.
- Enter the current date in the 'From Date' and 'Through Date' fields.
- Select "Client A" in the 'Client ID' field.
- Select "ClinicalNoteFinalized" in the 'Event/Action Search' field.
- Click [View Activity Log].
- Validate a 'ClinicalNoteFinalized' record is displayed.
- Click [Click To View Record].
- Validate the 'clinicalNotes' - 'notes' field contains the value entered in the 'Notes Field' in the previous steps.
- Validate the 'diagnoses' section is populated with the information for the 'Diagnosis 1' value selected in the previous steps.
- Validate the 'documentDescription' field contains "Discharge Summary".
- Validate the 'documentID' - 'id' field contains a unique identifier.
- Validate the 'documentTitle' field contains "Discharge Summary".
- Validate the 'includedSectionCodes' - 'code' field contains "Discharge Diagnosis".
- Validate the 'includedSectionCodes' - 'displayName' field contains "Discharge Diagnosis".
- Validate the 'isReleaseExternal' field contains "false".
- Validate the 'isReleaseToPatient' field contains "false".
- Close the report and the form.
|
Topics
• Progress Notes
• Clinical Notes Mapping
• Final to Draft Override
• Results
• Diagnosis
|
Order Entry Console - ONC certification
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: OE NX - Home Medications - Schedule III (Xyrem) - New order
Specific Setup:
- A client must have an active episode. (Client A)
- “Client A” must have a ‘Date of Birth’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Diagnosis’ form.
Steps
- Select "Client A" and access the Order Entry Console.
- Select the 'Home Medications' tab.
- Uncheck the 'Reported' checkbox.
- Search for and select "Xyrem 500 MG/1 ML Solution Oral (Schedule III)" in the 'New Order' field.
- Populate the required fields.
- Validate the 'Reason' field is not required.
- Validate the 'Reason Text' field is required.
- Enter "TEST" in the 'Reason Text' field.
- Validate the 'Note to Pharmacist' field is required and contains "TEST".
- Click [Add to Scratchpad].
- Validate the 'Scratchpad' contains an order for "Xyrem 500 MG/1 ML Solution Oral" with a 'Reason' ' and 'Note to Pharmacist' of "TEST".
- Click [Final Review].
- Validate the 'Final Review' dialog is displayed and contains the order for "Xyrem 500 MG/1 ML Solution (Schedule III)" with "Reason: TEST" and a note icon. Click the note icon and validate that it contains "TEST" and click [Close].
- Select "None" in 'Output' and click [Sign].
- Validate the 'Order grid' contains an order for "Xyrem" with a 'Reason' and 'Note To Pharmacist' of "TEST".
Scenario 2: OE NX - Orders This Episode - Create new order with PRN Frequency code - external pharmacy mode
Specific Setup:
- The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Hide Duration In OE Console (Orders This Episode) For External Pharmacy Mode' registry setting must be set to "Y".
- A pharmacy-type order code "Order Code A" must be configured to have a default duration in days.
- A "PRN" 'Frequency Code' must exist.
- Please log out of the application and log back in after completing the above configuration.
- A client must have an inpatient episode whose program or unit are configured in the ‘External Pharmacy Setup’ form. (Client A).
- “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select a pharmacy-type order code.
- Populate the required fields selecting any "PRN" frequency code in the 'Frequency' field.
- Validate the 'Stop Date' and 'Stop Time' fields remain populated.
- Click [Add to Scratchpad].
- Click the order in the 'Scratchpad' and validate the 'Stop Date' and 'Stop Time' fields remain populated.
- Click [Update Order] and file the order.
- Validate the order created is displayed within the 'Order grid'.
Scenario 3: OE NX- Admission Med Reconciliation - Create new order with PRN Frequency code - External Pharmacy Mode
Specific Setup:
- The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Hide Duration In OE Console (Orders This Episode) For External Pharmacy Mode' registry setting must be set to "Y".
- A pharmacy-type order code must be configured to have a default duration in days. (Order Code A)
- A "PRN" 'Frequency Code' must exist.
- Please log out of the application and log back in after completing the above configuration.
- A client must have an inpatient episode whose program or unit are configured in the ‘External Pharmacy Setup’ form. (Client A).
- “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
- Select "Client A" and access the Order Entry Console.
- Select the 'Home Medications' tab and create a 'Reported' order.
- Check the 'Medication history reviewed and completed for Episode #1' checkbox.
- Select the 'Admission Med Reconciliation' tab.
- Select the order in the 'Home Medications (Pre-Admission)' order grid and click [Hold].
- Search for and select any non-controlled pharmacy-type order code in the 'New Order' field.
- Set the 'Dose' field to "2" and validate the 'Dose Unit' field contains "Tablet".
- Select any "PRN" frequency code in the 'Frequency' field.
- Validate the 'Stop Date' and 'Stop Time' fields remain populated.
- Click [Add to Scratchpad].
- Select the order in the 'Inpatient Medications Scratchpad' and validate the 'Stop Date' and 'Stop Time' fields remain populated.
- Click [Cancel Update] and [Reconcile & Review].
- Validate the 'Final Review' dialog is displayed.
- Select "None" in 'Output' and click [Sign].
- Validate the 'Admission Med Reconciliation' tab is displayed in view-only mode.
Scenario 4: OE NX - Discharge Med Reconciliation - New Schedule II order
Specific Setup:
- The 'Avatar Order Entry->Facility Defaults->Medication Reconciliation->->->Require 'Discharge Disposition' in OE Console (Discharge Med Rec section)' registry setting must be set to "Y".
- The 'Avatar Order Entry->Facility Defaults->Medication Reconciliation->->->Default for 'Discharge Disposition' in OE Console (Discharge Med Rec section)' registry setting must be set to "DF".
- The 'Avatar Order Entry->Facility Defaults->Medication Reconciliation->->->Create OE Discharge Order during Discharge Medication Reconciliation' registry setting must be set to "2".
- The 'Avatar Order Entry->Facility Defaults->Medication Reconciliation->->->Internal Pharmacy Fills Discharge Orders' registry setting must be set to "Y".
- Please log out of the application and log back in after completing the above configuration.
- A client must have an active inpatient episode. (Client A)
- "Client A" must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as an allergy to "Ritalin" filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
- Select "Client A" and access the Order Entry Console.
- Click the 'Discharge Reconciliation' tab.
- Validate the 'Discharge Disposition' field contains "Discharge to Facility".
- Uncheck the 'No Prescription Required' checkbox.
- Search for and select "Ritalin 5 MG Tablet Oral (Schedule II)" in the 'New Order' field.
- Set the 'Dose' field to "2".
- Validate the 'Dose Unit' field contains "Tablet".
- Select "TWICE A DAY" in the 'Frequency' field.
- Search for and select any value in the 'Diagnosis' field.
- Set the 'Days Supply' field to "12" and press Tab.
- Validate the 'Dispense Qty' field contains"48".
- Validate the 'Dispense Qty Unit' field contains "Tablet".
- Set the 'Start Date' field to the current date.
- Validate the 'Stop Date' field contains a date that is 12 days in the future of the current date.
- Validate the 'Earliest Fill Date' contains the current date.
- Click [Add to Scratchpad].
- Validate the 'Discharge Medications Scratchpad' contains an order for "Ritalin 5 MG Tablet Oral 5 MG Tablet (Schedule II) Take two (2) tablets by mouth twice a day (Refills: 0, Dispense Quantity: 48)".
- Set the 'Inhouse Pharmacy' field to "12" and click [Review and Sign].
- Validate the 'Final Review' dialog is displayed.
- Select "None" in 'Output' and click [Sign].
- Validate the 'Discharge Medications Scratchpad' is in view-only mode.
|
Topics
• Order Entry Console
• NX
|
Avatar CareFabric - support for the 'Treatment Plan' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Treatment Plan - Validate the 'CarePlanCreated', 'CarePlanGoalCreated', 'CarePlanInterventionCreated', and 'CarePlanProblemCreated' SDK events
Specific Setup:
- A client is enrolled in an existing episode (Client A).
- The extended dictionary "(60150) FHIR Care Plan Category" must be defined for the dictionary values defined for "(52003) Plan Type".
- The following extended dictionaries must be defined for the "(16214) Status" CWS dictionary values for 'Problem Status':
- (16254) ONC Clinical Status
- (16255) ONC Verified Status
Steps
- Select "Client A" and access the 'Treatment Plan' form.
- Enter the desired date in the 'Plan Date' field.
- Select the desired value in the 'Plan Type' field.
- Select "Draft" in the 'Treatment Plan Status' field.
- Validate "Draft" is selected in the 'Current Status' field.
- Enter the desired value in the 'Strengths' field.
- Enter the desired value in the 'Weaknesses' field.
- Enter the desired value in the 'Discharge Planning' field.
- Click [Launch Plan].
- Add a problem, goal, objective, and intervention.
- Populate all required and desired fields.
- Click [Back To Plan Page].
- Select "Final" in the 'Treatment Plan Status' field.
- Select "Active" in the 'Current Status' field.
- Click [Submit].
- Access the 'CareFabric Monitor' form.
- Enter the current date in the 'From Date' and 'Through Date' fields.
- Click [View Activity Log].
- Validate the 'CareFabric Monitor Report' contains a "CarePlanCreated", "CarePlanGoalCreated", "CarePlanInterventionCreated", and "CarePlanProblemCreated" record.
- Click [Click To View Record] for the "CarePlanCreated" record.
- Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
- Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
- Validate the 'carePlanDetails' - 'statusCode' - 'code' field contains "active".
- Validate the 'carePlanDetails' - 'statusCode' - 'displayName' field contains "Active".
- Validate the 'planTypeCode' - 'code' field contains the "FHIR Care Plan Category" extended dictionary code for the plan type selected.
- Validate the 'planTypeCode' - 'codeSystem' field contains "2.16.840.1.113883.6.96".
- Validate the 'planTypeCode' - 'displayNAme' field contains the "FHIR Care Plan Category" extended dictionary value for the plan type selected.
- Validate the 'summaryText' - 'xhtmlContent' field contains the values entered in the 'Strengths', 'Weaknesses', and 'Discharge Planning' fields.
- Validate all other information displays.
- Navigate back to the 'CareFabric Monitor Report'.
- Click [Click To View Record] for the "CarePlanGoalCreated" record.
- Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
- Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
- Validate the 'goalCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.271".
- Validate all other information displays.
- Navigate back to the 'CareFabric Monitor Report'.
- Click [Click To View Record] for the "CarePlanInterventionCreated" record.
- Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
- Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
- Validate all other information displays.
- Navigate back to the 'CareFabric Monitor Report'.
- Click [Click To View Record] for the "CarePlanProblemCreated" record.
- Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
- Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
- Validate the 'clinicalStatusCode' - 'code' field contains the "ONC Clinical Status" extended dictionary code defined for the status selected.
- Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
- Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
- Validate the 'clinicalStatusCode' - 'displayName' field contains the "ONC Clinical Status" extended dictionary value defined for the status selected.
- Validate the 'verificationStatusCode' - 'code' field contains the "ONC Verified Status" extended dictionary code defined for the status selected.
- Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
- Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
- Validate the 'verificationStatusCode' - 'displayName' field contains the "ONC Verified Status" extended dictionary value defined for the status selected.
- Validate all other information displays.
- Close the reports and the form.
|
Topics
• Treatment Plan
• CareFabric Monitor
• NX
|
Avatar CareFabric - Laboratory Results
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Results Entry
- Review Results
- Review Results (CLIENT)
Scenario 1: Review Results - Validate the 'LaboratoryResultUpdated' SDK event
Specific Setup:
- A client is enrolled in an existing episode and has lab results with details on file (Client A).
Steps
- Access the 'Review Results' form.
- Select "Client A" in the 'Client ID' field.
- Select the lab results on file in the 'Select Results' field.
- Enter the desired value in the 'Comments' field.
- Populate any other desired fields.
- Click [Submit] and close the form.
- Access the 'CareFabric Monitor' form.
- Enter the current date in the 'From Date' and 'Through Date' fields.
- Select "Client A" in the 'Client ID' field.
- Select "LaboratoryResultUpdated" in the 'Event/Action Search' field.
- Click [View Activity Log].
- Validate a "LaboratoryResultUpdated" record is displayed, triggered from the 'Review Results' form.
- Click [Click To View Record].
- Validate the lab result data is displayed.
- Validate the 'notes' - 'auditInformation' - 'createdDate' field contains the reviewed date/time.
- Validate the 'notes' - 'notes' field contains the value entered in the 'Comments' field in the 'Review Results' form.
- Validate the 'notes' - 'notingProviderID' - 'id' field contains the logged in user.
- Validate the 'notes' - 'typeCode' - 'code' field contains "11502-2".
- Validate the 'notes' - 'typeCode' - 'codeSystem' field contains "2.16.840.1.113883.6.1".
- Validate the 'notes' - 'typeCode' - 'codeSystemName' field contains "LOINC".
- Validate the 'notes' - 'typeCode' - 'dispayName' field contains "Results".
- Close the report and the form.
|
Topics
• Results
|
| |