Avatar PM 2022 is Installed
Scenario 1: Validate Upgrading Avatar PM 2021 to 2022 is successful when 2021.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
|
Avatar State Forms 'Enable Texas TMHP Billing' Registry Setting - Financial Eligibility Field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Cross Episode Financial Eligibility
- Family Financial Eligibility
- Financial Eligibility Web Service
- Cross Episode Financial Eligibility Web Service
Scenario 1: 'Cross Episode Financial Eligibility' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Client record eligible for Cross Episode Financial Eligibility entry
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Cross Episode Financial Eligibility' form.
- Select client for Cross Episode Financial Eligibility view/entry/update.
- Navigate to 'Guarantor Selection' section of 'Cross Episode Financial Eligibility' form.
- Click 'Add New Item' to add/enter new Guarantor information (or select existing Guarantor information row and click 'Edit Selected Item' button to view/update).
- Enter/select 'Guarantor #' value.
- Ensure 'TMHP Waiver Reference Number' field is present in form.
- Ensure that field help message (lightbulb icon) is present for 'TMHP Waiver Reference Number' field; click the help message icon and ensure the following field help text is displayed:
- 'This field is for Texas TMHP Waiver Billing. This will populate in 2300-REF-02.'
- Enter value for 'TMHP Waiver Reference Number' field.
- Enter/select values for all other 'Cross Episode Financial Eligibility' form fields as required/desired.
- Navigate to 'Cross Episode Financial Eligibility' main/first form section; select Guarantor order for entry.
- Click 'Submit' button to file 'Cross Episode Financial Eligibility' form/record.
- Re-open 'Cross Episode Financial Eligibility' form for same/previously filed client.
- Navigate to 'Guarantor Selection' section of 'Cross Episode Financial Eligibility' form, and select previous Guarantor information entry.
- Ensure that previously entered/filed value for 'TMHP Waiver Reference Number' field is present in form.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.billing_guar_subs_data_no_ep', ensure that field 'tmhp_waiver_ref_num' is present and contains value filed for 'TMHP Waiver Reference Number' field via 'Cross Episode Financial Eligibility' form.
Scenario 2: 'Family Financial Eligibility' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Family entry/record eligible for Family Financial Eligibility entry (defined via 'Family Registration' form)
Steps
- Open Avatar PM 'Family Financial Eligibility' form.
- Select family record for Family Financial Eligibility view/entry/update.
- Navigate to 'Guarantor Selection' section of 'Family Financial Eligibility' form.
- Click 'Add New Item' to add/enter new Guarantor information (or select existing Guarantor information row and click 'Edit Selected Item' button to view/update).
- Enter/select 'Guarantor #' value.
- Ensure 'TMHP Waiver Reference Number' field is present in form.
- Ensure that field help message (lightbulb icon) is present for 'TMHP Waiver Reference Number' field; click the help message icon and ensure the following field help text is displayed:
- 'This field is for Texas TMHP Waiver Billing. This will populate in 2300-REF-02.'
- Enter value for 'TMHP Waiver Reference Number' field.
- Enter/select values for all other 'Family Financial Eligibility' form Guarantor Selection' fields as required/desired.
- Navigate to 'Guarantor Assignment' form section; enter/select family member clients for Guarantor assignment.
- Navigate to 'Family Financial Eligibility' main/first form section; select Guarantor order for entry.
- Click 'Submit' button to file 'Family Financial Eligibility' form/record.
- Re-open 'Family Financial Eligibility' form for same/previously filed family.
- Navigate to 'Guarantor Selection' section of 'Family Financial Eligibility' form, and select previous Guarantor information entry.
- Ensure that previously entered/filed value for 'TMHP Waiver Reference Number' field is present in form.
Scenario 3: 'Financial Eligibility' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Client record/episode eligible for Financial Eligibility entry
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Financial Eligibility' form.
- Select client/episode for Financial Eligibility view/entry/update.
- Navigate to 'Guarantor Selection' section of 'Financial Eligibility' form.
- Click 'Add New Item' to add/enter new Guarantor information (or select existing Guarantor information row and click 'Edit Selected Item' button to view/update).
- Enter/select 'Guarantor #' value.
- Ensure 'TMHP Waiver Reference Number' field is present in form.
- Ensure that field help message (lightbulb icon) is present for 'TMHP Waiver Reference Number' field; click the help message icon and ensure the following field help text is displayed:
- 'This field is for Texas TMHP Waiver Billing. This will populate in 2300-REF-02.'
- Enter value for 'TMHP Waiver Reference Number' field.
- Enter/select values for all other 'Financial Eligibility' form fields as required/desired.
- Navigate to 'Financial Eligibility' main/first form section; select Guarantor order for entry.
- Click 'Submit' button to file 'Financial Eligibility' form/record.
- Re-open 'Financial Eligibility' form for same/previously filed client/episode.
- Navigate to 'Guarantor Selection' section of 'Financial Eligibility' form, and select previous Guarantor information entry.
- Ensure that previously entered/filed value for 'TMHP Waiver Reference Number' field is present in form.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.billing_guar_subs_data', ensure that field 'tmhp_waiver_ref_num' is present and contains value filed for 'TMHP Waiver Reference Number' field via 'Financial Eligibility' form.
Scenario 4: 'FinancialEligibility' Web Service - Verification of 'UpdateFinancialElig' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'FinancialEligibility' web service
Steps
- Using Avatar PM 'FinancialEligibility' web service, submit request to 'UpdateFinancialElig' method to update existing Avatar PM Financial Eligibility record, including value for 'TMHPWaiverRefNum' field/segment.
- Confirm 'FinancialEligibility' web service responds with confirmation data on successful filing of 'UpdateFinancialElig' method.
- Example: "<Confirmation>Unique ID: 123~1</Confirmation>"
- Confirm 'FinancialEligibility' web service responds with confirmation message on successful filing of 'UpdateFinancialElig' method.
- Example: "<Message>Financial Eligibility web service has been filed successfully.</Message>"
- Confirm 'FinancialEligibility' web service responds with successful status value on successful filing of 'UpdateFinancialElig' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Financial Eligibility' form and select client/episode filed via web service for view/update.
- Confirm Financial Eligibility record is updated in Avatar PM, with values/data submitted via web service including 'TMHP Waiver Reference Number' field value.
Scenario 5: 'FinancialEligibility' Web Service - Verification of 'AddFinancialElig' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'FinancialEligibility' web service
Steps
- Using Avatar PM 'FinancialEligibility' web service, submit request to 'AddFinancialElig' method to create new Avatar PM Financial Eligibility record, including value for 'TMHPWaiverRefNum' field/segment.
- Confirm 'FinancialEligibility' web service responds with confirmation data on successful filing of 'AddFinancialElig' method.
- Example: "<Confirmation>Unique ID: 123~1</Confirmation>"
- Confirm 'FinancialEligibility' web service responds with confirmation message on successful filing of 'AddFinancialElig' method.
- Example: "<Message>Financial Eligibility web service has been filed successfully.</Message>"
- Confirm 'FinancialEligibility' web service responds with successful status value on successful filing of 'AddFinancialElig' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Financial Eligibility' form and select client/episode filed via web service for view/update.
- Confirm new Financial Eligibility record is created in Avatar PM, with values/data submitted via web service including 'TMHP Waiver Reference Number' field value.
Scenario 6: 'CrossEpisodeFinancialEligibility' Web Service - Verification of 'AddCrossEpFinancialElig' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'CrossEpisodeFinancialEligibility' web service
Steps
- Using Avatar PM 'CrossEpisodeFinancialEligibility' web service, submit request to 'AddCrossEpFinancialElig' method to create new Avatar PM Cross Episode Financial Eligibility record, including value for 'TMHPWaiverRefNum' field/segment.
- Confirm 'CrossEpisodeFinancialEligibility' web service responds with confirmation data on successful filing of 'AddCrossEpFinancialElig' method.
- Example: "<Confirmation>Unique ID: 123~POR.00001</Confirmation>"
- Confirm 'CrossEpisodeFinancialEligibility' web service responds with confirmation message on successful filing of 'AddCrossEpFinancialElig' method.
- Example: "<Message>Cross Episode Financial Eligibility web service has been filed successfully.</Message>"
- Confirm 'CrossEpisodeFinancialEligibility' web service responds with successful status value on successful filing of 'AddCrossEpFinancialElig' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Cross Episode Financial Eligibility' form and select client filed via web service for view/update.
- Confirm new Cross Episode Financial Eligibility record is created in Avatar PM, with values/data submitted via web service including 'TMHP Waiver Reference Number' field value.
Scenario 7: 'CrossEpisodeFinancialEligibility' Web Service - Verification of 'UpdateCrossEpFinancialElig' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'CrossEpisodeFinancialEligibility' web service
Steps
- Using Avatar PM 'CrossEpisodeFinancialEligibility' web service, submit request to 'UpdateCrossEpFinancialElig' method to update existing Avatar PM Cross Episode Financial Eligibility record, including value for 'TMHPWaiverRefNum' field/segment.
- Confirm 'CrossEpisodeFinancialEligibility' web service responds with confirmation data on successful filing of 'UpdateCrossEpFinancialElig' method.
- Example: "<Confirmation>Unique ID: 123~POR.00001</Confirmation>"
- Confirm 'CrossEpisodeFinancialEligibility' web service responds with confirmation message on successful filing of 'UpdateCrossEpFinancialElig' method.
- Example: "<Message>Cross Episode Financial Eligibility web service has been filed successfully.</Message>"
- Confirm 'CrossEpisodeFinancialEligibility' web service responds with successful status value on successful filing of 'UpdateCrossEpFinancialElig' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Cross Episode Financial Eligibility' form and select client filed via web service for view/update.
- Confirm Cross Episode Financial Eligibility record is updated in Avatar PM, with values/data submitted via web service including 'TMHP Waiver Reference Number' field value.
Avatar State Forms 'Enable Texas TMHP Billing' Registry Setting - Service Code Fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Service Code Upload Process
- Service Code Upload Accepted Codes
Scenario 1: 'Service Code Upload Process' - Verification of Service Code Upload
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Avatar PM Service Code Upload file containing one or more valid rows/entries including values for 'TMHP Type Of Service' field (Import File Segment/Location 134) and 'Line Item Control Number - Positions 5 to 20 (2400-REF)' (Import File Segment/Location135)
- Please refer to updated 'Avatar_PM_Service_Code_Upload_Layout.xls' document included with Avatar PM 2022 Update 3 for Service Code Upload format/layout
Steps
- Open Avatar PM 'Service Code Upload Process' form.
- Click 'Select File' button, and select Avatar PM Service Code Upload file containing one or more valid rows/entries including values for 'TMHP Type Of Service' and 'Line Item Control Number - Positions 5 to 20 (2400-REF)' fields/segments.
- Select 'Compile' in 'Compile Or Post' field.
- Select Yes or No value for 'Override Existing Service Codes' field.
- Click 'Submit' button to file form/compile Service Code Upload file.
- Ensure that dialog noting 'Compile Completed' is presented; click 'OK' button to close dialog/proceed.
- Open Avatar PM 'Service Code Upload Accepted Codes' form.
- Select compiled file in 'Select Desired Service Code Import File Name' field.
- Click 'Process' button to file form/display Service Code Upload Accepted Codes report.
- Ensure 'TMHP Type Of Service' and 'Line Item Control Number - Positions 5 to 20 (2400-REF)' fields are included in Service Code Upload Accepted Codes report display, and contains value filed for 'TMHP Type Of Service'/'Line Item Control Number - Positions 5 to 20 (2400-REF)' fields/segments for valid compiled rows/entries.
- Close Service Code Upload Accepted Codes report.
- Return to Avatar PM 'Service Code Upload Process' form.
- Select 'Post' in 'Compile Or Post' field to post compiled Service Code Upload file row(s).
- Click 'Submit' button to file form/post Service Code Upload file.
- Ensure that dialog noting 'Posting Completed' is presented; click 'OK' button to close dialog/proceed.
- Return to Avatar PM 'Service Code Upload Accepted Codes' form.
- Select posted file in 'Select Desired Service Code Import File Name' field.
- Click 'Process' button to file form/display Service Code Upload Accepted Codes report.
- Ensure 'TMHP Type Of Service' and 'Line Item Control Number - Positions 5 to 20 (2400-REF)' fields are included in Service Code Upload Accepted Codes report display, and contains value filed for 'TMHP Type Of Service'/'Line Item Control Number - Positions 5 to 20 (2400-REF)' fields/segments for valid/posted rows/entries.
- Open Avatar PM 'Service Codes' form.
- Select 'Edit Existing' action and select Service Code filed via 'Service Code Upload Process' file posting.
- Ensure that value for 'TMHP Type Of Service' field is present/selected in form as defined in Service Code Upload file row/entry.
- Ensure that value for 'Line Item Control Number - Positions 5 to 20 (2400-REF)' field is present/selected in form as defined in Service Code Upload file row/entry.
Scenario 2: 'Service Codes' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Service Codes' form.
- Select 'Add New' or 'Edit Existing' action (and select existing Service Code if 'Edit Existing' selected).
- Ensure 'TMHP Type Of Service' field is present in form, and allows the following selections:
- 'EVV'
- 'Nursing and Transportation'
- 'Non-Accumulated'
- Select value for 'TMHP Type Of Service' field.
- Ensure 'Line Item Control Number - Positions 5 to 20 (2400-REF)' field is present in form.
- Ensure that field help message (lightbulb icon) is present for 'Line Item Control Number - Positions 5 to 20 (2400-REF)' field; click the help message icon and ensure the following field help text is displayed:
- 'This field is for Texas TMHP Billing. This will represent positions 5 to 20 for the 'Line Item Control Number' in 2400-REF.'
- Enter value for 'Line Item Control Number - Positions 5 to 20 (2400-REF)' field.
- Enter/select values for all other 'Service Codes' form fields as required/desired.
- Click 'Submit' button to file 'Service Codes' form/record.
- Click 'Yes' in the 'Form Return' dialog to return to 'Service Codes' form.
- Select 'Edit Existing' action and select previously filed Service Code.
- Ensure that previously selected/filed value for 'TMHP Type Of Service' field is present/selected in form.
- Ensure that previously entered/filed value for 'Line Item Control Number - Positions 5 to 20 (2400-REF)' field is present/selected in form.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.billing_tx_master_table', ensure that fields 'tmhp_type_of_service_code' / 'tmhp_type_of_service_value' are present and contain value filed for 'TMHP Type Of Service' field via 'Service Codes' form.
- In Avatar PM SQL table 'SYSTEM.billing_tx_master_table', ensure that field 'line_item_control_num' is present and contains value filed for 'Line Item Control Number - Positions 5 to 20 (2400-REF)' field via 'Service Codes' form.
Avatar State Forms 'Enable Texas TMHP Billing' Registry Setting - Practitioner Enrollment Field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'ClinicianServices' Web Service - Verification Of 'putClinicianCreation' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'ClinicianServices' web service
Steps
- Using Avatar PM 'ClinicianServices' web service, submit request to 'putClinicianCreation' method to create new Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record), including value for 'AttendantID' field/segment.
- Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm new Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Attendant ID' field value (as well as values assigned for Avatar MSO 'Performing Provider' and 'Performing Provider Registration' practitioner association/link fields if enabled).
Scenario 2: 'ClinicianServices' Web Service - Verification Of 'putClinicianUpdate' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'ClinicianServices' web service
Steps
- Using Avatar PM 'ClinicianServices' web service, submit request to 'putClinicianUpdate' method to edit/update Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record if linked), including value for 'AttendantID' field/segment.
- Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including 'Attendant ID' field value.
Scenario 3: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianCreation' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'ClinicianServicesV2' web service
Steps
- Using Avatar PM 'ClinicianServicesV2' web service, submit request to 'putClinicianCreation' method to create new Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record), including value for 'AttendantID' field/segment.
- Confirm 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm new Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Attendant ID' field value (as well as values assigned for Avatar MSO 'Performing Provider' and 'Performing Provider Registration' practitioner association/link fields if enabled).
Scenario 4: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianUpdate' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'ClinicianServicesV2' web service
Steps
- Using Avatar PM 'ClinicianServicesV2' web service, submit request to 'putClinicianUpdate' method to edit/update Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record if linked), including value for 'AttendantID' field/segment.
- Confirm 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including 'Attendant ID' field value.
Scenario 5: 'Practitioner Enrollment' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Practitioner Enrollment' form.
- Enter/select existing Practitioner Enrollment record for viewing/update (or click 'New Staff' button for new Practitioner Enrollment entry).
- Ensure new input field 'Attendant ID' is added to 'Practitioner Enrollment' form (in 'Practitioner Enrollment' first/primary form section).
- Ensure that field help message (lightbulb icon) is present for 'Attendant ID' field; click the help message icon and ensure the following field help text is displayed:
- 'This field allows users to enter the Attendant ID for EVV services when billing Texas TMHP. The system will print this Attendant ID in positions 5 to 20 of the 'Line Item Control Number' in 2400-REF for EVV services for guarantors whose financial class has 'Texas TMHP Billing' set to Yes. Services are designated as EVV services when 'TMHP Type of Service' is set to 'EVV' in the Service Code form.'
- Enter value for 'Attendant ID' field.
- Enter/select values for all other form fields as required/desired.
- Click 'Submit' button to file 'Practitioner Enrollment' form/record.
- Re-open Avatar PM 'Practitioner Enrollment' form and select same/previously filed Practitioner Enrollment record for view/update.
- Ensure that previously entered/filed value for 'Attendant ID' field is present/displayed in form for selected record.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.staff_enrollment_history', ensure that field 'attendant_ID' is available, and contains value filed for 'Attendant ID' via Avatar PM 'Practitioner Enrollment' form.
Scenario 6: 'PractitionerRegister' Web Service - Verification Of 'PractitionerRegister' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'PractitionerRegister' web service
Steps
- Using Avatar PM 'PractitionerRegister' web service, submit request to 'PractitionerRegister' method to create new Avatar PM Practitioner Enrollment, including value for 'AttendantID' field/segment.
- Confirm 'PractitionerRegister' web service responds with confirmation data/ID on successful filing of 'PractitionerRegister' method.
- Example:"<Confirmation>Unique ID : 000056</Confirmation>"
- Confirm 'PractitionerRegister' web service responds with confirmation message on successful filing of 'PractitionerRegister' method.
- Example:"<Message>Practitioner Enrollment web service has been filed successfully.</Message>"
- Confirm 'PractitionerRegister' web service responds with successful status value on successful filing of 'PractitionerRegister' method.
- Example:" <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm new Practitioner/Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Attendant ID' field value.
Scenario 7: 'PractitionerRegister' Web Service - Verification Of 'EditPractitionerRegister' Filing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Application utilizing the Avatar PM 'PractitionerRegister' web service
Steps
- Using Avatar PM 'PractitionerRegister' web service, submit request to 'EditPractitionerRegister' method to edit/update Avatar PM Practitioner Enrollment, including value for 'AttendantID' field/segment.
- Confirm 'PractitionerRegister' web service responds with confirmation data/ID on successful filing of 'EditPractitionerRegister' method.
- Example:"<Confirmation>Unique ID : 000056</Confirmation>"
- Confirm 'PractitionerRegister' web service responds with confirmation message on successful filing of 'EditPractitionerRegister' method.
- Example:"<Message>Practitioner Enrollment web service has been filed successfully.</Message>"
- Confirm 'PractitionerRegister' web service responds with successful status value on successful filing of 'EditPractitionerRegister' method.
- Example:" <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm Practitioner/Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including 'Attendant ID' field value.
Avatar State Forms 'Enable Texas TMHP Billing' Registry Setting - Guarantors/Payors Field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'Guarantors/Payors' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
Steps
- Open the Avatar PM 'Guarantors/Payors' form.
- Select Add or Edit action in 'Add New or Edit Existing Guarantor' field.
- Enter new (or select existing) Guarantor Code.
- Complete all required/desired fields in main section of 'Guarantors/Payors' form.
- Navigate to '837' section of 'Guarantors/Payors' form.
- Ensure that the 'TMHP Waiver Skip 2300-REF Segment' field is available in form.
- If 'Yes' is selected in this field, 837 Professional files sorted/created for this Guarantor via 'Electronic Billing' forms/functions (and subject to 'Enable Texas TMHP Billing' functionality/values) will conditionally skip/omit the 2300-REF segment/value for 'TMHP Waiver Reference Number'
- Select value for 'TMHP Waiver Skip 2300-REF Segment' field (and any other desired fields in '837' section of form).
- Navigate to main section of 'Guarantors/Payors' form.
- Click 'File' button to save/file Guarantor/Payor definition information.
- Select 'Edit' action and select previously filed Guarantor Code.
- Navigate to '837' section of 'Guarantors/Payors' form.
- Ensure that previously selected/filed value for 'TMHP Waiver Skip 2300-REF Segment' field is present/selected in form.
Avatar State Forms 'Enable Texas TMHP Billing' Registry Setting - 837 and 835 Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- Practitioner Enrollment
- 835 Health Care Claim Payment/Advice (PM)
- 835 Health Care Claim Payment/Advice Report
Scenario 1: 'Electronic Billing' - Support for 837 Professional 2300-REF Referral Number 'Texas TMHP Billing' Reporting
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Extended Dictionary Data Element entry '(941) Texas TMHP Billing' (under Data Element '(1000) Financial Class') must be set to 'Yes' for selected Guarantor/Financial Class
- 'TMHP Waiver Skip 2300-REF Segment' value (Yes/No) must be defined for selected Guarantor (via Avatar PM 'Guarantors/Payors' form)
- Financial Eligibility/Cross Episode Financial Eligibility/Family Financial Eligibility record for client(s) where 'TMHP Waiver Reference Number' value is defined
- One or more 837 Professional /HCFA1500 service(s) eligible for Electronic Billing inclusion
Steps
- Open Avatar PM 'Electronic Billing' form. (Note, acceptance testing may also be confirmed via Avatar PM 'Quick Billing' form/functionality.)
- Select '837 Professional' in the 'Billing Form' field.
- Select 'Sort File' in the 'Billing Options' field.
- Enter/select 837 Professional file sorting criteria.
- Click 'Process' button to sort/generate 837 Professional file.
- Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
- Select 'Print' in the 'Print Or Delete Report' field.
- Select 837 Professional file sorted which includes services(s), and click 'Process' button to display 837 Professional outbound file data.
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional claim data includes 2300-REF Referral Number/Reference Identification loop/segment with 'TMHP Waiver Reference Number' value defined for client via applicable Financial Eligibility form/record. (2300-REF-01 Qualifier = '9F' Referral Number)
- Examples:
- 'REF*9F*TMHP12345678A~'
- 'REF*9F*TMHPW-9999~'
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional claim data does not include 2300-REF Referral Number/Reference Identification loop/segment with 'TMHP Waiver Reference Number' value in case where 'TMHP Waiver Skip 2300-REF Segment' is set to 'Yes' for selected/applicable Guarantor.
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional claim data does not include 2300-REF Referral Number/Reference Identification loop/segment with 'TMHP Waiver Reference Number' value in case where Extended Dictionary Data Element entry '(941) Texas TMHP Billing' is set to 'No' (or not defined) for selected/applicable Guarantor/Financial Class.
- Select 'Run Report' in the 'Billing Options' field.
- Select 'Print' in the 'Print Or Delete Report' field.
- Select 837 Professional file sorted which includes services(s), and click 'Process' button to display 837 Professional outbound file report/errors.
- Click 'Required Data Missing: Patient Claim Data' link in 837 Professional outbound report to open error sub-report/section.
- In Avatar PM 837 Professional format outbound electronic billing file report - ensure that where 2300-REF Referral Number/Reference Identification loop/segment cannot be created due to missing 'TMHP Waiver Reference Number' value for client via applicable Financial Eligibility form/record, client/claim is included in 'Required Data Missing: Patient Claim Data' sub-report/section with Error Message 'Required Data Missing: Patient Claim Data (Loop: 2300 Segment REF).'
Scenario 2: 'Electronic Billing' - Support for 837 Professional 2400-REF Line Item Control Number 'Texas TMHP Billing' Reporting
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Extended Dictionary Data Element entry '(941) Texas TMHP Billing' (under Data Element '(1000) Financial Class') must be set to 'Yes' for selected Guarantor/Financial Class
- 'TMHP Type Of Service' must be defined for Service Code (via Avatar PM 'Service Codes' form)
- 'Attendant ID' must be defined for Practitioner where applicable for 'TMHP Type Of Service' value 'EVV' (via Avatar PM 'Practitioner Enrollment' form)
- 'Line Item Control Number - Positions 5 to 20 (2400-REF)' must be defined for Service Code where applicable for 'TMHP Type Of Service' value 'Nursing and Transportation Services' (via Avatar PM 'Service Codes' form)
- One or more 837 Professional /HCFA1500 service(s) eligible for Electronic Billing inclusion, where 'Service Start Time' value is entered/defined
Steps
- Open Avatar PM 'Electronic Billing' form. (Note, acceptance testing may also be confirmed via Avatar PM 'Quick Billing' form/functionality.)
- Select '837 Professional' in the 'Billing Form' field.
- Select 'Sort File' in the 'Billing Options' field.
- Enter/select 837 Professional file sorting criteria.
- Click 'Process' button to sort/generate 837 Professional file.
- Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
- Select 'Print' in the 'Print Or Delete Report' field.
- Select 837 Professional file sorted which includes services(s), and click 'Process' button to display 837 Professional outbound file data.
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional claim data includes 2400-REF Line Item Control Number loop/segment with values defined for Service Start Time, Service Code/Practitioner Enrollment information and Service ID information as follows (2400-REF-01 Qualifier = '6R' Provider Control Number )
- Segment 2400-REF-02 Reference Identification positions 1-4 will be populated with 'Service Start Time' value entered/filed for service (24 hour/military time format 0000-2359)
- Examples:
- REF*6R*0930...~
- REF*6R*1445...~
- Segment 2400-REF-02 Reference Identification positions 5-20 will be populated with 'Attendant ID' value for applicable Practitioner Enrollment record where Service Code 'TMHP Type Of Service' value = 'EVV' (padded with spaces on end of value if required)
- Examples:
- REF*6R*09301122GREEN_______...~
- REF*6R*14453344SMITH-WEST__...~
- Segment 2400-REF-02 Reference Identification positions 5-20 will be populated with 'Line Item Control Number - Positions 5 to 20 (2400-REF)' value for Service Code where Service Code 'TMHP Type Of Service' value = 'Nursing and Transportation' (padded with spaces on end of value if required)
- Examples:
- REF*6R*0930ACCUM.NUR_______...~
- REF*6R*1530(ACCUM.LVN)_____...~
- Segment 2400-REF-02 Reference Identification Positions 5-20 will be populated with 'Name' value for applicable Practitioner Enrollment record (LastName,FirstName format) where Service Code 'TMHP Type Of Service' value = 'Non-Accumulated' (padded with spaces on end of value if required, truncated if value exceeds 16 characters)
- Examples:
- REF*6R*0930GREEN,SUE_______...~
- REF*6R*1445GREEN-SMITH,SUSA...~
- Segment 2400-REF-02 Reference Identification Positions 21-30 will be populated with the Avatar PM internal Claim/Service Unique ID value for service (from Patient Control Number/Service Date)
- Examples:
- REF*6R*09301122GREEN_______66132.0001~
- REF*6R*1530ACCUM.NUR_______66115.001~
- REF*6R*1445GREEN-SMITH,SUSA66129.002~
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional service data does not include 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values in case where 'Service Start Time' value is not entered/filed for service. Note that 2400-REF Line Item Control Number loop/segment may be included according to other Avatar PM Billing configurations for Claim/Service Unique ID, such as 'IDX475X1X66114.001' or 'CX154X66110.001~'. etc.
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional service data does not include 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values in case where 'TMHP Type Of Service' value is not defined for Service Code. Note that 2400-REF Line Item Control Number loop/segment may be included according to other Avatar PM Billing configurations for Claim/Service Unique ID, such as 'IDX475X1X66114.001' or 'CX154X66110.001~', etc.
- In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 837 Professional service data does not include 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values in case where Extended Dictionary Data Element entry '(941) Texas TMHP Billing' is set to 'No' (or not defined) for selected/applicable Guarantor/Financial Class. Note that 2400-REF Line Item Control Number loop/segment may be included according to other Avatar PM Billing configurations for Claim/Service Unique ID, such as 'IDX475X1X66114.001' or 'CX154X66110.001~', etc.
- Select 'Run Report' in the 'Billing Options' field.
- Select 'Print' in the 'Print Or Delete Report' field.
- Select 837 Professional file sorted which includes services(s), and click 'Process' button to display 837 Professional outbound file report/errors.
- Click 'Required Data Missing: Patient Service Data' link in 837 Professional outbound report to open error sub-report/section.
- In Avatar PM 837 Professional format outbound electronic billing file report - ensure that where 2400-REF Line Item Control Number loop/segment cannot be created due to missing 'Name'/'Attendant ID' value for applicable Practitioner Enrollment record or missing 'Line Item Control Number - Positions 5 to 20 (2400-REF)' value for Service Code, client/service is included in 'Required Data Missing: Patient Service Data' sub-report/section with Error Messages 'Required Data Missing: Patient Service Data (Loop: 2400 Segment REF). Missing Field/Invalid Format: Reference Identification (Loop: 2400 Segment: REF Iteration: For Practitioner. Unable To Create Segment: REF (Loop: 2400)'.
Scenario 3: 'Dictionary Update' - Verification of 'Financial Class' Extended Dictionary for 'Texas TMHP Billing'
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
Steps
- Open Avatar PM 'Dictionary Update' form ('Input Dictionary Code(s)' main/first form section).
- Select 'Payor' in 'File' field.
- Enter/select '(1000) Financial Class' in 'Data Element' field.
- Enter value for existing or new Financial Class entry in 'Dictionary Code' field.
- Click to expand 'Extended Dictionary Data Element' field.
- Ensure Extended Dictionary Data Element entry '(941) Texas TMHP Billing' is available for selection; select '(941) Texas TMHP Billing' in field.
- Click to expand 'Extended Dictionary Value (Single Dictionary)' field.
- Ensure values 'Yes' and 'No' are available for selection; select 'Yes' or 'No' value for Extended Dictionary Data Element entry '(941) Texas TMHP Billing'.
- Click 'Apply Changes' to file form/Dictionary updates.
- Select previously filed '(1000) Financial Class' Data Element/Dictionary Code value.
- Select '(941) Texas TMHP Billing' in 'Extended Dictionary Data Element' field.
- Ensure that previously selected/filed value for '(941) Texas TMHP Billing' Extended Dictionary Data Element is present/selected in form.
Scenario 4: '835 Health Care Claim Payment/Advice' - Support for 2400-REF Line Item Control Number 'Texas TMHP Billing' Processing
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled
- Extended Dictionary Data Element entry '(941) Texas TMHP Billing' (under Data Element '(1000) Financial Class') must be set to 'Yes' for applicable Guarantor/Financial Class
- Inbound 835 Health Care Claim Payment/Advice file containing one or more successfully compiled entries for Avatar PM claims where outbound/original 837 Professional Claim/Service information includes 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values in 2400-REF-02
- Outbound/original 837 Professional 2400-REF Line Item Control Number Examples:
- REF*6R*09301122GREEN_______66132.0001~
- REF*6R*1530ACCUM.NUR_______66115.001~
- REF*6R*1445GREEN-SMITH,SUSA66129.002~
Steps
- Open Avatar PM '835 Health Care Claim Payment/Advice' form.
- Select 'Load File' in the 'Options' field.
- Enter 'File Path/Name' value for 835 inbound file to be loaded, and click 'Process File' button.
- Ensure 835 file is successfully loaded.
- Select 'Compile File' in the 'Options' field.
- Select loaded inbound 835 file in the 'Select File' field, and click 'Process File' button.
- In 835 Compile Report - In case where Avatar PM outbound/original 837 Professional Claim/Service information includes 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values in 2400-REF-02 (and thus not using Avatar PM Claim/Service Unique ID combination), ensure that inbound 835 payments/adjustments are successfully compiled/matched to Avatar PM claim/service using 2100-CLP Claim Payment Information (as compared to original 837 Professional 2300-CLM Claim Information) and do not require full/exact 2110-REF-02 segment match where loop/segment is present in 835 information.
- Select 'Post File' in the 'Options' field.
- Select compiled inbound 835 file in the 'Select File' field, enter values for 'Posting Date' and 'Date of Receipt' fields (as well as any other fields as required/desired), and click 'Process File' button.
- In 835 Posting Report - In case where Avatar PM outbound/original 837 Professional Claim/Service information includes 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values in 2400-REF-02 (and thus not using Avatar PM Claim/Service Unique ID combination), ensure that inbound 835 payments/adjustments are successfully posted/matched to Avatar PM claim/service using 2100-CLP Claim Payment Information (as compared to original 837 Professional 2300-CLM Claim Information) and do not require full/exact 2110-REF-02 segment match where loop/segment is present in 835 information.
- Open 'Client Ledger' form.
- Enter/select values for 'Client ID', 'Claim/Episodes/All Episodes' and 'Ledger Type' fields (and any other fields as required/desired).
- Click 'Process' button to display Client Ledger information.
- In Client Ledger information display - for service(s) where Avatar PM outbound/original 837 Professional Claim/Service information includes 2400-REF Line Item Control Number loop/segment with Texas TMHP Billing values, ensure that inbound 835 Health Care Claim Payment/Advice file payments/adjustments successfully posted are present/displayed in ledger.
|
Topics
• Registry Settings
• Financial Eligibility
• NX
• Web Services
• Service Codes
• Service Code Upload Process
• Practitioner
• Practitioner Enrollment
• Guarantor/Payors
• Electronic Billing
• 837 Professional
• Dictionary
• 835 Health Care Claim Payment/Advice
|
Electronic Billing 837 Professional - Rendering Provider Name (Loop 2310B)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Dynamic Form - Edit Service Fee Definition
- Practitioner Enrollment
- Practitioner Numbers By Guarantor And Program
Scenario 1: 837 Professional bill - Select Type Of Information To Include In Rendering Provider Name (2310B) = Rendering Practitioner for the Majority of Services in the 'Guarantor Program Billing Defaults'
Specific Setup:
- Guarantors/Payors:
- An existing guarantor is identified. Note the guarantor name / id.
- Guarantor/Program Billing Defaults:
- 837 Professional section:
- Set the 'Select Type Of Information To Include In Rendering Provider Name (2310B)' field to the 'Rendering Practitioner for the Majority of Services' option.
- Practitioner Enrollment:
- Two practitioners are identified, or two new practitioners are created with NPI number. Note the practitioner id/name.
- Admission:
- A new client is admitted in the outpatient program. Note the client id / name.
- Financial Eligibility:
- The guarantor identified above is assigned to the client as the primary guarantor.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Service Codes:
- Two existing professional service codes are identified. Note the service code.
- Service Fee/Cross Reference Maintenance:
- Make sure the fee definition is created for the service code and CPT Code is assigned to the service fee definition.
- Client Charge Input: The test will require one practitioner to provide more services than the other practitioner.
- Enter desired number of services for practitioner 1, using service code 1. Note the dates of service.
- Enter desired number of services for practitioner 2, using service code 2, different dates of service, and providing at least one more service that practitioner 1 provided.
- Client Ledger:
- All the services rendered to the client are distributed correctly to the guarantor assigned to the client.
- Close Charges:
- All the services rendered to the client are closed.
- Create Interim Billing Batch:
- An interim billing batch is created to include client, guarantor and services rendered to the client.
Steps
- Open an 'Electronic Billing' form.
- Compile an 837 professional bill.
- Verify the bill compiles successfully.
- Review the dump file.
- Verify the dump file includes rendering practitioner with the highest service count in the 2310B loop (NM1*82 at claim level) of the bill.
- Close the form.
Scenario 2: 837 Professional bill - Select Type Of Information To Include In Rendering Provider Name (2310B) = 'Supervising Practitioner for the Majority of Services' in the 'Guarantor Program Billing Defaults'
Specific Setup:
- Guarantors/Payors:
- An existing guarantor is identified. Note the guarantor name / id.
- Guarantor/Program Billing Defaults:
- 837 Professional section:
- Set the 'Select Type Of Information To Include In Rendering Provider Name (2310B)' field to the 'Rendering Practitioner for the Majority of Services' option.
- Practitioner Enrollment:
- Two practitioner are identified, or two new practitioners are created with NPI number to be used as a rendering practitioner while rendering services to the client. Note the practitioner id / name.
- Two practitioner are identified, or two new practitioners are created with NPI number to be used as a supervising practitioner of the rendering practitioner. Note the practitioner id/name.
- Practitioner Numbers by Guarantor and Program:
- A supervising practitioner is selected for each rendering practitioner.
- Admission:
- A new client is admitted in the outpatient program. Note the client id / name.
- Financial Eligibility:
- The guarantor identified above is assigned to the client as the primary guarantor.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Service Codes:
- Two existing professional service codes are identified. Note the service code.
- Service Fee/Cross Reference Maintenance:
- Make sure the fee definition is created for the service code and CPT Code is assigned to the service fee definition.
- Client Charge Input: The test will require one practitioner to provide more services that the other practitioner.
- Enter desired number of services for practitioner 1, using service code 1. Note the dates of service.
- Enter desired number of services for practitioner 2, using service code 2, different dates of service, and providing at least one more service that practitioner 1 provided.
- Client Ledger:
- All the services rendered to the client are distributed correctly to the guarantor assigned to the client.
- Close Charges:
- All the services rendered to the client are closed.
Steps
- Open an 'Electronic Billing' form.
- Compile an 837 professional bill.
- Verify the bill compiles successfully.
- Review the dump file.
- Verify the dump file includes correct supervising practitioner with the highest service count in the 2310B loop (NM1*82 at claim level) of the bill.
- Close the form.
Scenario 3: 837 Professional - When the service counts are equal for all rendering practitioners - the practitioner with the earliest service date as a rendering practitioner in loop 2310B
Specific Setup:
- Guarantors/Payors:
- An existing guarantor is identified. Note the guarantor name / id.
- Guarantor/Program Billing Defaults:
- 837 Professional section:
- Set the 'Select Type Of Information To Include In Rendering Provider Name (2310B)' field to the 'Rendering Practitioner for the Majority of Services' option.
- Practitioner Enrollment:
- Two practitioners are identified, or two new practitioners are created with NPI number. Note the practitioner id/name.
- Admission:
- A new client is admitted in the outpatient program. Note the client id / name.
- Financial Eligibility:
- The guarantor identified above is assigned to the client as the primary guarantor.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Service Codes:
- Two existing professional service codes are identified. Note the service code.
- Service Fee/Cross Reference Maintenance:
- Make sure the fee definition is created for the service code and CPT Code is assigned to the service fee definition.
- Client Charge Input: The test will require same count of the services are rendered by each practitioner.
- Enter desired number of services for practitioner 1, using service code 1. Note the dates of service.
- Enter desired number of services for practitioner 2, using service code 2, different dates of service. Note the id/name of the practitioner used as a rendering practitioner.
- Client Ledger:
- All the services rendered to the client are distributed correctly to the guarantor assigned to the client.
- Close Charges:
- All the services rendered to the client are closed.
- Create Interim Billing Batch:
- An interim billing batch is created to include client, guarantor and services rendered to the client.
Steps
- Open an 'Electronic Billing' form.
- Compile an 837 professional bill.
- Verify the bill compiles successfully.
- Review the dump file.
- Verify the dump file includes the practitioner with the earliest service date in the 2310B loop (NM1*82 at claim level) of the bill.
- Close the form.
Scenario 4: 837 Institutional - Validating rendering or attending practitioner in the loop 2310 A of the bill.
Specific Setup:
- Guarantors/Payors:
- An existing guarantor is identified. Note the guarantor name / id.
- Guarantor/Program Billing Defaults:
- 837 Institutional section:
- Set the ‘Specify Rendering Practitioner As Attending Practitioner In Loop 2310A (Attending Physician Name)’ field to 'Y'.
- Practitioner Enrollment:
- Four practitioners are identified, or new practitioners are created with NPI number to be used as an admitting, attending, and rendering practitioner. Note the practitioner id/name.
- Admission:
- A new client is admitted in the inpatient program. Note the client id / name.
- Financial Eligibility:
- The guarantor identified above is assigned to the client as the primary guarantor.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Service Codes:
- Two existing professional service codes are identified. Note the service code.
- Service Fee/Cross Reference Maintenance:
- Make sure the fee definition is created for the service code and CPT Code is assigned to the service fee definition.
- Client Charge Input: Client Charge Input: The test will require one practitioner to provide more services that the other practitioner.
- Enter desired number of services for practitioner 1, using service code 1. Note the dates of service.
- Enter desired number of services for practitioner 2, using service code 2, different dates of service, and providing at least one more service that practitioner 1 provided.
- Client Ledger:
- All the services rendered to the client are distributed correctly to the guarantor assigned to the client.
- Close Charges:
- All the services rendered to the client are closed.
- Create Interim Billing Batch:
- An interim billing batch is created to include client, guarantor and services rendered to the client.
Steps
- Open an 'Electronic Billing' form.
- Compile an 837 professional bill.
- Verify the bill compiles successfully.
- Review the dump file.
- Verify the dump file includes attending practitioner in the 2310A loop (NM1*71 at claim level) of the bill.
- Close the form.
- Open the ' Guarantor / Program Billing Defaults' form.
- Set the ‘Specify Rendering Practitioner As Attending Practitioner In Loop 2310A (Attending Physician Name)’ field to 'Y'.
- Open the 'Practitioner Numbers By Guarantor And Program' form.
- Create an entry of rendering practitioner, Guarantor and Program.
- Open an 'Electronic Billing' form.
- Compile an 837 professional bill.
- Verify the bill compiles successfully.
- Review the dump file.
- Verify the dump file includes rendering practitioner as an attending practitioner in the 2310A loop (NM1*71 at claim level) of the bill.
- Close the file.
- Close the form.
|
Topics
• 837 Professional
• NX
• 837 Institutional
|
CPT Place of Service Override - System.table_cpt_place_override
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Maintenance
- CPT Place Of Service Override
- Dynamic Form - Edit Service Fee Definition
- Print Bill
Scenario 1: CPT Place of Service Override - Validating 'Crystal report' and SQL table 'System.table_cpt_place_override' - 837 Professional
Specific Setup:
- Admission:
- An existing outpatient client is identified, or a new client is admitted to the outpatient program. Note the client ID/name, admission program code/value, admission date.
- Financial Eligibility:
- An existing non contract guarantor is identified. Note the Guarantor name and ID.
- Diagnosis:
- A diagnosis record is created for the client.
- Client Charge Input:
- The professional service is rendered to the client. Make sure there is a practitioner for the services. Note the practitioner category of your test practitioner via the Practitioner Enrollment form (Categories/Taxonomy section). Note the service code, date of the service and place of service.
- Client Ledger:
- Verify the services distributed correctly to the guarantor assigned to the client.
- Close Charges:
- Close the charges rendered to the client.
Steps
- Open the 'CPT Place of Service Override' form.
- Select desired financial class(es) in the 'Financial Class Selection' field.
- Select desired guarantor(s) in the 'Guarantor' field.
- Select desired treatment setting(s) in the 'Treatment Setting Selection' field.
- Select desired program(s) for the override in the 'Program' field. Note: This is the program of admission and not the program of service. Note the admission program code/value.
- Select desired value in the 'All or Individual Service Code' field. Note: Specify whether the override should apply to all service codes or just one individual code. If Individual, select the specific code in the Service Code field. Note the code/value.
- Select desired value in the 'All or Individual CPT Code' field. Note: Specify whether the override should apply to all CPT codes or just one individual code. If Individual, select the specific code in the CPT Code field. Note the CPT code/value.
- Select desired value in the 'All or Individual Location' field, specify whether the override should apply to all locations or just one specific location. If Individual, select the same location that is used during rendering the service to the client from the setup section. Note the code/value.
- Select the place of service for use on the paper HCFA bill in the 'Place of Service (HCFA 24-B)' field. Note the location code/value.
- Select the place of service for use on the 837 Professional bill in the 'Place of Service (837 Professional)' field.
- Click [Display CPT Place of Service Overrides].
- Verify a CPT Place of Service Overrides report launched.
- Review the report.
- Verify the 'HCFA 24-B' and '837 Professional' fields display the correct data.
- Click [Submit].
- Open the 'Crystal Report' or any other 'SQL Data Viewer'.
- Query the 'System.table_cpt_place_override' table.
- Verify the 'HCFA 24-B' and '837 Professional' fields display the correct data.
- Open the 'Electronic Billing' form.
- Compile the 837 Professional bill for the interim billing batch created in the setup section.
- Verify the file compiles successfully.
- Dump the file.
- Review an 837 professional file.
- Verify the 2300-CLM 05 and 2400-SV1 05 segments displays the correct place of the service.
- Close the file.
- Close the form.
Scenario 2: CPT Place of Service Override - Validating 'Crystal report' and SQL table 'System.table_cpt_place_override' - HCFA 1500 - NPI version 1500
Specific Setup:
- Admission:
- An existing outpatient client is identified, or a new client is admitted to the outpatient program. Note the client id/name, admission program code/value, admission date.
- Financial Eligibility:
- An existing non contract guarantor is identified. Note the Guarantor name and ID.
- Diagnosis:
- A diagnosis record is created for the client.
- Client Charge Input:
- The professional service is rendered to the client. Make sure there is a practitioner for the services. Note the practitioner category of your test practitioner via the Practitioner Enrollment form (Categories/Taxonomy section). Note the service code, date of the service and place of service.
- Client Ledger:
- Verify the services distributed correctly to the guarantor assigned to the client.
- Close Charges:
- Close the charges rendered to the client.
Steps
- Open the 'CPT Place of Service Override' form.
- Select desired financial class(es) in the 'Financial Class Selection' field.
- Select desired guarantor(s) in the 'Guarantor' field.
- Select desired treatment setting(s) in the 'Treatment Setting Selection' field.
- Select desired program(s) for the override in the 'Program' field. Note: This is the program of admission and not the program of service. Note the admission program code/value.
- Select desired value in the 'All or Individual Service Code' field. Note: Specify whether the override should apply to all service codes or just one individual code. If Individual, select the specific code in the Service Code field. Note the code/value.
- Select desired value in the 'All or Individual CPT Code' field. Note: Specify whether the override should apply to all CPT codes or just one individual code. If Individual, select the specific code in the CPT Code field. Note the CPT code/value.
- Select desired value in the 'All or Individual Location' field, specify whether the override should apply to all locations or just one specific location. If Individual, select the same location that is used during rendering the service to the client from the setup section. Note the code/value.
- Select the place of service for use on the paper HCFA bill in the 'Place of Service (HCFA 24-B)' field. Note the location code/value.
- Select the place of service for use on the 837 Professional bill in the 'Place of Service (837 Professional)' field.
- Click [Display CPT Place of Service Overrides].
- Verify a CPT Place of Service Overrides report launched.
- Review the report.
- Verify the 'HCFA 24-B' and '837 Professional' fields display the values selected in the form correctly.
- Click [Submit].
- Open the 'Crystal Report' or any other 'SQL Data Viewer'.
- Query the 'System.table_cpt_place_override' table.
- Verify the 'hcfa_place_of_svc_value' and 'p837_place_of_svc_value' fields display the values selected in the form correctly.
- Open the 'Print Bill' form.
- Select 'No' in the 'Create Claims (Y/N)' field.
- Select 'HCFA-1500 NPI Version' in the 'Print On What Form' field.
- Select 'No' in the 'Print For Interim Batch'.
- Select desired guarantor in the 'Guarantor #' field.
- Select 'Individual' in the 'Print For An Individual Or All Clients' field.
- Select desired client in the 'Client ID' field.
- Select 'Yes' in the 'All Episodes' field.
- Click [Process].
- Review the report.
- Verify the correct place of value displays on the bill.
- Click [X].
- Click [No].
|
Topics
• NX
• myAvatar/myAvatar NX
|
Avatar PM 'Enable Supervising Practitioner Based on Rendering Practitioner (2310B)' and 'Enable Submitter Identification Definition' Registry Settings
Scenario 1: Avatar PM Registry Settings - Verification of 'Enable Supervising Practitioner Based on Rendering Practitioner (2310B)' Registry Setting
Steps
- Open 'Registry Settings' form.
- Set 'Include Hidden Registry Settings' field to 'Yes'.
- Enter search value 'Enable Supervising Practitioner Based on Rendering Practitioner (2310B)' and click 'View Registry Settings' button.
- Ensure Registry Setting is returned (under 'Avatar PM -> Billing -> Electronic Billing -> 837 Professional -> Enable Supervising Practitioner Based On Rendering Practitioner (2310B)' path).
- Ensure 'Registry Setting Details' field contains the following explanation text:
Selecting 'Y' gives an end-user the ability to optionally specify whether to include the information for the supervising practitioner associated with the rendering practitioner in loop 2310B. This is accomplished by the addition of a new selection of 'Supervising Practitioner Based On Rendering Practitioner' to the 'Select Type Of Information To Include In Rendering Provider Name (2310B)' field within the '837 Professional' tab of the 'Guarantor/Program Billing Defaults' form. When 'Supervising Practitioner Based On Rendering Practitioner' is selected, loop 2310B will be populated based upon the supervising practitioner associated with the rendering practitioner as defined in the 'Practitioner Numbers By Guarantor and Program' form. If a supervising practitioner is not defined then loop 2310B will be populated based upon the rendering practitioner. If multiple services are within the claim then 2130B will be populated based upon the first service within the claim for which the rendering practitioner has a defined supervising practitioner. The selection of 'Supervising Practitioner Based On Rendering Practitioner' will result in the suppression of loop 2310D. Selecting 'N' removes the selection of 'Supervising Practitioner Based On Rendering Practitioner' and disables the logic. Please Note: The logic associated with this registry setting is only applicable when the registry setting 'Avatar PM -> Billing -> Electronic Billing -> 837 Professional -> Rendering Provider Name (Loop 2310B)' is set to a value of 'Y'.
Scenario 2: Avatar PM Registry Settings - Verification of 'Enable Submitter Identification Definition' Registry Setting
Steps
- Open 'Registry Settings' form.
- Set 'Include Hidden Registry Settings' field to 'Yes'.
- Enter search value 'Enable Submitter Identification' and click 'View Registry Settings' button.
- Ensure Registry Setting is returned (under 'Avatar PM -> Billing -> Electronic Billing -> All 837 Submissions- > Enable Submitter Identification Definition' path).
- Ensure 'Registry Setting Details' field contains the following explanation text:
Enabling this functionality gives an end-user the ability to optionally specify identification information based on guarantor, program, service code, and client combination for a specific date range. This is accomplished by adding the 'Submitter Identification Definition' form under 'Avatar PM -> System Maintenance -> System Definition'. In addition, the following 837 logic is enabled:
When generating an 837 bill, a check will be made to see if a value of 'ZZZ' is in 'Billing Provider Secondary Identification Code Qualifier (2010BB-REF)' field.
If '1' is selected, the 'Submitter Primary Identification Qualifier (1000A-NM1-08)' and 'Submitter Primary Identification Number (1000A-NM1-09)' will be populated with the values specified in the 'Submitter Identification Code Qualifier' and 'Submitter Identification Number' fields of the above form respectively.
If '2' is selected, the 'Billing Provider Secondary Identification Code Qualifier (2010BB-)' and 'Billing Provider Secondary Identification # (2010BB-)' will be populated with the same values specified for any iteration that contains the 'ZZZ' dictionary code.
Selecting '1&2' will populate both 1000A-NM1 and 2010BB-REF with the values specified. The dictionary code would need to be added to the 'Billing Provider Secondary Code Qualifier (2010BB-)'. This also necessitates that the bills will be sorted by submitter identification number. Selecting '0' will remove the form from the menu and disable the 837 logic. Note: This functionality is used to meet a PA State requirement.
|
Topics
• Registry Settings
• NX
|
Service Fee/Cross Reference Maintenance - Pro-Rated Fees
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Maintenance
- Post Residential/Inpatient Worklist
- Discharge
- Leaves
Scenario 1: Validate Pro-Rated Fees Calculation - Client without leave or discharge
Specific Setup:
- The following registry setting has a value of '2', at a minimum: Avatar PM->System Maintenance->Service Code Maintenance->->->Additional Service Fee Configuration Fields.
- The following registry setting has a value of '5': Avatar PM->Services->Inpatient/Residential->->->Number Of Daily Charge Codes.
- Guarantors/Payors 1 is an active guarantor.
- Service Code 1: Is an active service code that will be used for pro-rated services room and board charges.
- Service Code 2: Is an active service code that will be used for pro-rated services daily charge (1).
- Service Code 3: Is an active service code that will be used for pro-rated services daily charge (2).
- Service Code 4: Is an active service code that will be used for pro-rated services daily charge (3).
- Service Code 5: Is an active service code that will be used for pro-rated services daily charge (4).
- Service Code 6: Is an active service code that will be used for pro-rated services daily charge (5).
- Service Fee/Cross Reference Maintenance:
- Service Code 1 - Service Code 6:
- From Date = desired date.
- Fee = desired amount, which is distributed across the monthly services. Note each value.
- UB-94 Revenue Code = desired value.
- Fee type = Monthly.
- Pro-Rate Fee For = desired values.
- Pro-Rated Fee Calculation = Fee/Monthly Days.
- Client A:
- Is admitted to an inpatient program on or after the earliest 'Service Fee/Cross Reference Maintenance', 'From Date'. Note the ‘Unit’ the client is assigned to. Client has not been placed on leave or discharged during the month.
- Has a 'Financial Eligibility' record for Guarantors/Payors 1.
- Equations are used for fee verification based on the value in 'Pro-Rated Fee Calculation'
- The value of 'Pro-Rated Fee Calculation' is 'Fee/Monthly Days'. The equation is: the 'Fee' divided by the number of days in the month, times the number of valid days, divided by the number of days in the month.
- Example 1: Fee is 350.00. Days in month = 31. Valid days = 31. 350/31 = 11.29 for days 1-30, and 11.30 for day 31.
- Example 2: Fee is 120.00. Days in month = 30. Valid days = 15. 120.00/30x15/30 = 2.00 for the valid days.
Steps
- Open ‘Compile Residential/Inpatient Charges’.
- Select ‘Individual’ in ‘Individual Or All Units’.
- Select desired Unit in ‘Select Unit(s)’.
- Set the ‘Compile Charges From Date’ to desired value.
- Set the ‘Compile Charges Through Date’ to desired value.
- Select ‘Yes’ in ‘Do You Wish To Recreate The Residential/Inpatient Worklist’
- Click [Process].
- Validate that the report fees are correct for each service code, ensuring that at a minimum the first and last page of the report are verified. Calculate the fees to verify that the fee in ‘Service Fee/Cross Reference Maintenance’ is correct for the valid number of days in the month.
- Open ‘Post Residential/Inpatient Worklist’.
- Select ‘Individual’ in ‘Individual Or All Units’.
- Select desired Unit in ‘Select Unit(s)’.
- Set the ‘Post Charges From Date’ to desired value.
- Set the ‘Post Charges Through Date’ to desired value.
- Click [Process].
- Validate that the report fees are the same as above.
- If desired, open ‘Client Ledger’ and verify the fees for the date range and services.
Scenario 2: Validate Pro-Rated Fees Calculation - Discharged client
Specific Setup:
- The following registry setting has a value of '2', at a minimum: Avatar PM->System Maintenance->Service Code Maintenance->->->Additional Service Fee Configuration Fields.
- The following registry setting has a value of '5': Avatar PM->Services->Inpatient/Residential->->->Number Of Daily Charge Codes.
- Guarantors/Payors 1 is an active guarantor.
- Service Code 1: Is an active service code that will be used for pro-rated services room and board charges.
- Service Code 2: Is an active service code that will be used for pro-rated services daily charge (1).
- Service Code 3: Is an active service code that will be used for pro-rated services daily charge (2).
- Service Code 4: Is an active service code that will be used for pro-rated services daily charge (3).
- Service Code 5: Is an active service code that will be used for pro-rated services daily charge (4).
- Service Code 6: Is an active service code that will be used for pro-rated services daily charge (5).
- Service Fee/Cross Reference Maintenance:
- Service Code 1 - Service Code 6:
- From Date = desired date.
- Fee = desired amount, which is distributed across the monthly services. Note each value.
- UB-94 Revenue Code = desired value.
- Fee type = Monthly.
- Pro-Rate Fee For = desired values.
- Pro-Rated Fee Calculation = Fee/Monthly Days.
- Client A:
- Is admitted to an inpatient program on or after the earliest 'Service Fee/Cross Reference Maintenance', 'From Date'. Note the ‘Unit’ the client is assigned to. Client has not been placed on leave during the month. The client has been discharged before the end of the month. Note how many days that client was in the program.
- Has a 'Financial Eligibility' record for Guarantors/Payors 1.
- Equations are used for fee verification based on the value in 'Pro-Rated Fee Calculation'
- The value of 'Pro-Rated Fee Calculation' is 'Fee/Monthly Days'. The equation is: the 'Fee' divided by the number of days in the month, times the number of valid days, divided by the number of days in the month.
- Example 1: Fee is 350.00. Days in month = 31. Valid days = 31. 350/31 = 11.29 for days 1-30, and 11.30 for day 31.
Steps
- Open ‘Compile Residential/Inpatient Charges’.
- Select ‘Individual’ in ‘Individual Or All Units’.
- Select desired Unit in ‘Select Unit(s)’.
- Set the ‘Compile Charges From Date’ to desired value.
- Set the ‘Compile Charges Through Date’ to desired value.
- Select ‘Yes’ in ‘Do You Wish To Recreate The Residential/Inpatient Worklist’
- Click [Process].
- Validate that the report fees are correct for each service code, ensuring that at a minimum the first and last page of the report are verified. Calculate the fees to verify that the fee in ‘Service Fee/Cross Reference Maintenance’ is correct for the valid number of days in the month. Validate that the fees are not calculated after the client was discharged.
- Open ‘Post Residential/Inpatient Worklist’.
- Select ‘Individual’ in ‘Individual Or All Units’.
- Select desired Unit in ‘Select Unit(s)’.
- Set the ‘Post Charges From Date’ to desired value.
- Set the ‘Post Charges Through Date’ to desired value.
- Click [Process].
- Validate that the report fees and days are the same as above.
- If desired, open ‘Client Ledger’ and verify the fees for the date range and services.
Scenario 3: Validate Pro-Rated Fees Calculation - Client with leave
Specific Setup:
- The following registry setting has a value of '2', at a minimum: Avatar PM->System Maintenance->Service Code Maintenance->->->Additional Service Fee Configuration Fields.
- The following registry setting has a value of '5': Avatar PM->Services->Inpatient/Residential->->->Number Of Daily Charge Codes.
- Guarantors/Payors 1 is an active guarantor.
- Service Code 1: Is an active service code that will be used for pro-rated services room and board charges.
- Service Code 2: Is an active service code that will be used for pro-rated services daily charge (1).
- Service Code 3: Is an active service code that will be used for pro-rated services daily charge (2).
- Service Code 4: Is an active service code that will be used for pro-rated services daily charge (3).
- Service Code 5: Is an active service code that will be used for pro-rated services daily charge (4).
- Service Code 6: Is an active service code that will be used for pro-rated services daily charge (5).
- Service Fee/Cross Reference Maintenance:
- Service Code 1 - Service Code 6:
- From Date = desired date.
- Fee = desired amount, which is distributed across the monthly services. Note each value.
- UB-94 Revenue Code = desired value.
- Fee type = Monthly.
- Pro-Rate Fee For = desired values. If 'Missing Service Code' is not selected in the field, leave days will be counted as valid days.
- Pro-Rated Fee Calculation = Fee/Monthly Days.
- Client A:
- Is admitted to an inpatient program on or after the earliest 'Service Fee/Cross Reference Maintenance', 'From Date'. Note the ‘Unit’ the client is assigned to. Client has a non-billable leave during the month. Note the number of leave days. The client has not been discharged during the month.
- Has a 'Financial Eligibility' record for Guarantors/Payors 1.
- Equations are used for fee verification based on the value in 'Pro-Rated Fee Calculation'
- The value of 'Pro-Rated Fee Calculation' is 'Fee/Monthly Days'. The equation is: the 'Fee' divided by the number of days in the month, times the number of valid days, divided by the number of days in the month.
- Example 1: Fee is 350.00. Days in month = 31. Valid days = 31. 350/31 = 11.29 for days 1-30, and 11.30 for day 31.
- Example 2: Fee is 120.00. Days in month = 30. Valid days = 15. 120.00/30x15/30 = 2.00 for the valid days.
Steps
- Open ‘Compile Residential/Inpatient Charges’.
- Select ‘Individual’ in ‘Individual Or All Units’.
- Select desired Unit in ‘Select Unit(s)’.
- Set the ‘Compile Charges From Date’ to desired value.
- Set the ‘Compile Charges Through Date’ to desired value.
- Select ‘Yes’ in ‘Do You Wish To Recreate The Residential/Inpatient Worklist’
- Click [Process].
- Validate that the report fees are correct for each service code, ensuring that at a minimum the first and last page of the report are verified. Calculate the fees to verify that the fee in ‘Service Fee/Cross Reference Maintenance’ is correct for the valid number of days in the month.
- Open ‘Post Residential/Inpatient Worklist’.
- Select ‘Individual’ in ‘Individual Or All Units’.
- Select desired Unit in ‘Select Unit(s)’.
- Set the ‘Post Charges From Date’ to desired value.
- Set the ‘Post Charges Through Date’ to desired value.
- Click [Process].
- Validate that the report fees are the same as above.
- If desired, open ‘Client Ledger’ and verify the fees for the date range and services.
|
Topics
• NX
• Pro Rated Fee
|
Compile/Edit/Post/Unpost Roll-Up Services Worklist for "NCPDP"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Orders This Episode
- HL7 Connection Monitor
- Launch RxConnect
- Compile Inbound HL7 Charge Batch File
- Post Inbound HL7 Charge Batch File
- Compile/Edit/Post/Unpost Roll-Up Services Worklist
- National Drug Code Reporting
- Rx Summary
- Order Tracking
Scenario 1: NCPDP Roll-Up Billing via the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form- Ensuring excluded component services are not included on the worklist or in National Drug Code Reporting
Specific Setup:
- myAvatar must be configured to communicate with RxConnect via Avatar HL7 and vice versa.
- Avatar HL7 must be installed and configured with an 'ADT-RXCONNECT', 'ORDERS-RXCONNECT', 'BILLING-RXCONNECT' and 'FILLDETAILS-RXCONNECT'.
- The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
- The applications must be configured for NCPDP Billing.
- A client must have an active inpatient episode. (Client A)
- "Client A" must be associated with a NCPDP guarantor in the 'Financial Eligibility' form.
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select "PRILOSEC (OMEPRAZOLE) 20 MG CAPSULE, DELAYED RELEASE ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Capsule" in the 'Dose Unit' field.
- Select "Twice A Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad].
- Search for and select "ADVIL 200 MG TABLET ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Tablet" in the 'Dose Unit' field.
- Select "Every Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad] and [Sign].
- Validate the 'Order grid' contains an order for "ADVIL 200 MG ORAL TABLET 1 Tablet, EVERY DAY" and an order for "PRILOSEC (OMEPRAZOLE) 20 MG ORAL CAPSULE, DELAYED RELEASE 1 Tablet, TWICE A DAY".
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) ORDERS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "ORM^O01" for "Client A".
- Close the report and the form.
- Access the 'Launch RxConnect' form.
- Click [Launch RxConnect].
- Validate that 'RxConnect' is displayed.
- Access 'RxSummary'.
- Find "Client A's" orders for "PRILOSEC 20 MG ORAL CAPSULE, DELAYED RELEASE" and "ADVIL 200 MG TABLET ORAL" and process the orders, which will result in an 'Rx #'s' being displayed for each order.
- Click 'Order Tracking'.
- Select the hospital that is associated with the Avatar application and click [Change and Resume].
- Set the 'Rx #' field to the value for the "PRILOSEC" order and press Enter.
- Validate the 'Order Item(s) - Drug' cell contains "Omeprazole(et PRILOSEC)".
- Validate the 'Order Item(s) - Strength' cell contains "20 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Set the 'Apply On' field to the date that the order was created and a time that is in the evening.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Repeat steps 3j - 3s until the 29th day.
- On the 30th day set the 'Apply On' field to the 30th day and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "PRILOSEC" order.
- Set the 'Rx #' field to the value received for the "ADVIL" order and click [Enter].
- Validate the 'Order Item(s) - Drug' cell contains "Ibuprofen(et IBUPROFEN)".
- Validate the 'Order Item(s) - Strength' cell contains "200 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "1.0000".
- Click [Post].
- Repeat steps 3ae - 3ai through the 30th of the month.
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "ADVIL" order.
- Wait until the files batch, this is done at a specific time each day.
- Once that has been completed access the 'Order Tracking' section and validate that for each 'Rx #' that the administrations were batched.
- Click 'Logout' and close the form.
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) FILL DETAILS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "O01-RDE" for "Client A".
- Select "(Outbound) BILLING-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "P03" for "Client A".
- Close the report and the form.
- Access the 'Compile Inbound HL7 Charge Batch File' form
- Select "Pharmacy" in the 'Compile For Which Charge Type' field.
- Validate a message is displayed stating "The system will now populate those fields for which a default value has been defined for the charge type selected." and click [OK].
- Set the 'Through Date of Service' field to the 30th day of the month and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Post Inbound HL7 Charge Batch File' form.
- Select "Pharmacy" in the 'Charge Type' field.
- Select "Post" in the 'Action' field.
- Select the batch that was just compiled in the 'HL7 Charge Batch File' field.
- Select "Yes, but in the background after posting has finished" in the 'Run Liability Update' field and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form.
- Set the 'Through Date' field to the 30th day of the month.
- Check off "NCPDP ***System Generated***" in the 'Roll-Up Definitions' field.
- Set the 'From Date' field to the first date of the month in which the orders were compiled and posted.
- Click [Compile Worklist].
- Validate a message is displayed stating "Compile complete" and click [OK].
- Click [Run Report].
- Validate that the 'Roll-Up Services Worklist' report is displayed and contains "29.00" under 'Days' and "58.00" under 'Quantity' for the "OMEPRAZOLE" charge code.
- Validate that the charge on the 30th of the month has been excluded from roll-up totals.
- Close the report.
- Select the 'Post Roll-Up Services Worklist' menu item.
- Select the through date with NCPDP rules included in the 'Through Date' field.
- Select any value in the 'Write Off Posting Code' field.
- Click [Post Worklist].
- Validate a 'Post Complete' message is displayed and click [OK] and close the form.
- Access the 'National Drug Code Reporting' form.
- Select "Client A" in the 'Client ID' field.
- Validate the 'Episode Number' field contains "Episode #1".
- Set the 'Service Start Date' field to the first date of the month for the charges that were billed.
- Set the 'Service End Date' field to the last date of the month for the charges that were billed.
- Select the "PRILOSEC (OMEPRAZOLE)" service in the 'Service To Record Information For' field.
- Click [Launch NDC Input].
- Validate that the 'Quantity' field and the 'Medicare Billing Units' field both contain "58".
- Click [Close/Cancel].
- Select the 'Additional Drug Information' section.
- Validate the 'Days Supply' field contains "29".
- Close the form.
Scenario 2: NCPDP Roll-Up billing via the Compile/Edit/Post/Unpost Roll-Up Services Worklist
Specific Setup:
- myAvatar must be configured to communicate with RxConnect via Avatar HL7 and vice versa.
- Avatar HL7 must be installed and configured with an 'ADT-RXCONNECT', 'ORDERS-RXCONNECT', 'BILLING-RXCONNECT' and 'FILLDETAILS-RXCONNECT'.
- The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
- The application must be configured for NCPDP billing.
- A client must have a posted Inbound HL7 Charge Batch file. (Client A).
- "Client A" must have open charges going to a NCPDP guarantor.
Steps
- Access the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form.
- Enter the current date in the 'Through Date' field.
- Select "NCPDP ***System Generated***" in the 'Roll-Up Definitions' field.
- Click [Compile Worklist].
- Validate that an 'Information' message is displayed that states: "Compile complete."
- Click [OK].
- Click [Run Report].
- Validate the 'Roll-Up Services Worklist' report is displayed.
- Validate that Client A's name is displayed in the format of Last Name,First Name (PATID).
- Validate the contents of the Roll-Up are displayed.
- Close the report.
- Select "Post Roll-Up Services Worklist"
- Select the only value in the 'Through Date' field.
- Select any value in the 'Write Off Posting Code' field. (ex. Contractual Write Off - CR)
- Click [Post Worklist].
- Validate that a Post complete message is displayed.
- Click [OK] and close the form.
- Access the 'Client Ledger' form.
- Select "Client A" in the 'Client ID' field.
- Select "Episode" in the 'Claim/Episode/All Episodes' field.
- Select "Episode 1" in the 'Episode Number' field.
- Validate the 'From Date' field contains the admission date of the episode.
- Validate the 'To Date' field contains the last date of service that is included in the Client ledger.
- Select "Simple" in the 'Ledger Type' field.
- Click [Process].
- Validate that the 'Client Ledger Report' is displayed.
- Validate that the 'Client Ledger Report' contains Client A's Name in the format of Last Name,First Name next to the 'Name' label.
- Validate the 'Client Ledger Report' contains "Roll-Up" in the 'Claim Number' column.
- Validate that a 'Processing Report has Completed. Do You wish to Return to form?' message is displayed.
- Click the [No].
Scenario 3: NCPDP Roll-Up Billing via the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form- Ensuring excluded component services are not included on the worklist or in National Drug Code Reporting
Specific Setup:
- myAvatar must be configured to communicate with RxConnect via Avatar HL7 and vice versa.
- Avatar HL7 must be installed and configured with an 'ADT-RXCONNECT', 'ORDERS-RXCONNECT', 'BILLING-RXCONNECT' and 'FILLDETAILS-RXCONNECT'.
- The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
- The applications must be configured for NCPDP Billing.
- A client must have an active inpatient episode. (Client A)
- "Client A" must be associated with a NCPDP guarantor in the 'Financial Eligibility' form.
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select "PRILOSEC (OMEPRAZOLE) 20 MG CAPSULE, DELAYED RELEASE ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Capsule" in the 'Dose Unit' field.
- Select "Twice A Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad].
- Search for and select "ADVIL 200 MG TABLET ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Tablet" in the 'Dose Unit' field.
- Select "Every Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad] and [Sign].
- Validate the 'Order grid' contains an order for "ADVIL 200 MG ORAL TABLET 1 Tablet, EVERY DAY" and an order for "PRILOSEC (OMEPRAZOLE) 20 MG ORAL CAPSULE, DELAYED RELEASE 1 Tablet, TWICE A DAY".
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) ORDERS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "ORM^O01" for "Client A".
- Close the report and the form.
- Access the 'Launch RxConnect' form.
- Click [Launch RxConnect].
- Validate that 'RxConnect' is displayed.
- Access 'RxSummary'.
- Find "Client A's" orders for "PRILOSEC 20 MG ORAL CAPSULE, DELAYED RELEASE" and "ADVIL 200 MG TABLET ORAL" and process the orders, which will result in an 'Rx #'s' being displayed for each order.
- Click 'Order Tracking'.
- Select the hospital that is associated with the Avatar application and click [Change and Resume].
- Set the 'Rx #' field to the value for the "PRILOSEC" order and press Enter.
- Validate the 'Order Item(s) - Drug' cell contains "Omeprazole(et PRILOSEC)".
- Validate the 'Order Item(s) - Strength' cell contains "20 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Set the 'Apply On' field to the date that the order was created and a time that is in the evening.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Repeat steps 3j - 3s until the 29th day.
- On the 30th day set the 'Apply On' field to the 30th day and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "PRILOSEC" order.
- Set the 'Rx #' field to the value received for the "ADVIL" order and click [Enter].
- Validate the 'Order Item(s) - Drug' cell contains "Ibuprofen(et IBUPROFEN)".
- Validate the 'Order Item(s) - Strength' cell contains "200 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "1.0000".
- Click [Post].
- Repeat steps 3ae - 3ai through the 30th of the month.
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "ADVIL" order.
- Wait until the files batch, this is done at a specific time each day.
- Once that has been completed access the 'Order Tracking' section and validate that for each 'Rx #' that the administrations were batched.
- Click 'Logout' and close the form.
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) FILL DETAILS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "O01-RDE" for "Client A".
- Select "(Outbound) BILLING-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "P03" for "Client A".
- Close the report and the form.
- Access the 'Compile Inbound HL7 Charge Batch File' form
- Select "Pharmacy" in the 'Compile For Which Charge Type' field.
- Validate a message is displayed stating "The system will now populate those fields for which a default value has been defined for the charge type selected." and click [OK].
- Set the 'Through Date of Service' field to the 30th day of the month and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Post Inbound HL7 Charge Batch File' form.
- Select "Pharmacy" in the 'Charge Type' field.
- Select "Post" in the 'Action' field.
- Select the batch that was just compiled in the 'HL7 Charge Batch File' field.
- Select "Yes, but in the background after posting has finished" in the 'Run Liability Update' field and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form.
- Set the 'Through Date' field to the 30th day of the month.
- Check off "NCPDP ***System Generated***" in the 'Roll-Up Definitions' field.
- Set the 'From Date' field to the first date of the month in which the orders were compiled and posted.
- Click [Compile Worklist].
- Validate a message is displayed stating "Compile complete" and click [OK].
- Click [Run Report].
- Validate that the 'Roll-Up Services Worklist' report is displayed and contains "29.00" under 'Days' and "58.00" under 'Quantity' for the "OMEPRAZOLE" charge code.
- Validate that the charge on the 30th of the month has been excluded from roll-up totals.
- Close the report.
- Select the 'Post Roll-Up Services Worklist' menu item.
- Select the through date with NCPDP rules included in the 'Through Date' field.
- Select any value in the 'Write Off Posting Code' field.
- Click [Post Worklist].
- Validate a 'Post Complete' message is displayed and click [OK] and close the form.
- Access the 'National Drug Code Reporting' form.
- Select "Client A" in the 'Client ID' field.
- Validate the 'Episode Number' field contains "Episode #1".
- Set the 'Service Start Date' field to the first date of the month for the charges that were billed.
- Set the 'Service End Date' field to the last date of the month for the charges that were billed.
- Select the "PRILOSEC (OMEPRAZOLE)" service in the 'Service To Record Information For' field.
- Click [Launch NDC Input].
- Validate that the 'Quantity' field and the 'Medicare Billing Units' field both contain "58".
- Click [Close/Cancel].
- Select the 'Additional Drug Information' section.
- Validate the 'Days Supply' field contains "29".
- Close the form.
|
Topics
• Compile/Edit/Post/Unpost Roll-up Services Worklist
• NX
• NCPDP
|
Unbilled Services Compile Definition and Export - error messages
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- Dynamic Form - Dictionary Update - Locked Dictionary
- Guarantors/Payors
- Form Designer (PM)
- Program Maintenance
- Practitioner Enrollment
- Practitioner Numbers By Guarantor And Program
- Dynamic Form - Edit Service Fee Definition
- Unbilled Services Compile Definition and Export
- Dynamic Form - Unbilled Services Compile Definition
- System Task Scheduler
- Ambulatory Progress Notes
- Dynamic Form - document routing - sign
- Dynamic Form - document routing - verify password
- Dynamic Forms - Document Routing - Route Document To Dialog
- Dynamic Form - Delete Compile Definition
- Discharge
- Treatment Plan
- Failed Authentication - Input Dialog
- Dynamic Form - Treatment Plan
- Dynamic Form Client Treatment Plan
- Dynamic Form Plan Date
- Individual Cash Posting (PM)
- Dynamic Form - Individual Cash Posting - Information
- Dynamic Form - Individual Cash Posting - Alert
- Dynamic Form - Individual Cash Posting - Client
- Document Routing Setup (PM)
- Dynamic Form - Document Routing Setup - Select Form
Scenario 1: Unbilled Services Compile Definition and Export - Error message priority validation
Specific Setup:
- The following error messages have been added to the ‘Unbilled Services Compile Definition and Export’ processing:
- 837 Institutional Only:
- Episode cannot be billed due to 3 day billing rule. Priority 33.
- This Service Would Result In The Generation Of More Than One Institutional Service Line (2400-SV2) Segment, Per Claim Information (2300-CLM), For Room And Board Services. Priority 34.
- Service Code Is Missing Rate Code Information For Guarantor. Priority 37.
- 837 Professional Only:
- Missing 'Place Of Service (837 Professional)' Extended Dictionary Off Of Location. Priority 31.
- Service Code Does Not Have A Professional Component. Priority 35.
- Missing Note Description (2400 NTE). Priority 36.
- Both 837 Institutional and 837 Professional:
- Missing Subscriber Group #. Priority 29.
- An Add-On or Interactive Complexity service code can only be billed if the primary service is also on the claim. Priority 30.
- This Service Is Being Excluded From The Bill Due To Crossover Claim Logic Associated With Guarantor. Priority 32.
- Unable to Bill Service Due To Same Day Service Hold For Progress Notes. Priority is always last.
- Due To Coordination Of Benefits Logic This Claim Cannot Be Billed Out Until Prior Covering Guarantor(s) Have Received Payment. Priority 38.
- Treatment Plan Service Count Exceeded For This Program Of Service. Priority 40.
- Missing Field Line Adjudication Information Identification Code. Priority 41.
- Progress Note On File For Service Requires A Co-Signature But One Is Not Present. Priority 28, processes at the same time as the no progress note on file error.
- Unbillable services that would fall to the above errors exist.
- Dictionary Update:
- Client Dictionary – 83701 - 837 Error Classification is updated as desired.
- Client Dictionary – 83700 - 837 Error Code is updated as desired.
- Desired number of ‘Unbilled Services Compile Definition and Export’ exist for the unbillable services.
- System Task Scheduler has been used to schedule the task of processing the Unbilled Services Compile Definition and Export. Note the scheduled dates/times to note when to begin the verification process.
Steps
- Open ‘Unbilled Services Compile Definition and Export’.
- Select the ‘Export Unbilled Services’ section.
- Click [Export Unbilled Services Data].
- Save the ‘NetsmartExport.csv’ file to desired location.
- Open the saved file with ‘Notepad’ or another desired tool.
- Validate that the expected errors exist in the export and the priority for the errors places the lowest priority as the ‘Primary Unbilled Reason’ and all other errors are listed as ‘Other Reasons’.
- Update the necessary data to the ‘Primary Unbilled Reason’ for at least one service that contains other errors.
- Process the ‘System Task Scheduler’ for the ‘Unbilled Services Compile Definition and Export’.
- Open ‘Unbilled Services Compile Definition and Export’.
- Select the ‘Export Unbilled Services’ section.
- Click [Export Unbilled Services Data].
- Save the ‘NetsmartExport.csv’ file to desired location.
- Open the saved file with ‘Notepad’ or another desired tool.
- Validate that the original ‘Primary Unbilled Reason’ does not exist and that the lowest priority ‘Other Reasons’ is now the ‘Primary Unbilled Reason’.
|
Topics
• Unbilled Services Report
• myAvatar/myAvatar NX
|
'Admission' form - Bed Assignment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Admit Client to a Unit that is different than the default for a Program in Program Maintenance
Specific Setup:
- Two 'Units' must exist with the same 'Rooms' and 'Beds'. (Unit A & Unit B)
- A practitioner must exist for Admission. (Practitioner A)
Steps
- Access the 'Program Maintenance' form.
- Select "Edit" from the 'Add Or Edit Program' field.
- Select "Inp. Adult Psych." from the 'Program' field.
- Select "Unit A" from the 'Unit' field.
- Click [File Program] and [Discard].
- Validate a message is displayed that states: "Are you sure you want to Close without saving?" and click [Yes].
- Access the 'Admission' form.
- Fill out all fields for a unique client and click [Search] and [New Client].
- Validate a message is displayed that states: "Auto Assign Next ID Number?" and click [Yes].
- Set the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' fields to the current date and time.
- Select "Inp. Adult Psych." from the 'Program' field.
- Select "First Admission" from the 'Type Of Admission' field.
- Select "Clinic Referral" from the 'Source Of Admission' field.
- Search for and select "Practitioner A" from the 'Admitting Practitioner' field.
- Search for and select "Practitioner A" from the 'Attending Practitioner' field.
- Select the 'Inpatient/Partial/Day Treatment' tab.
- Select "Unit B" from the 'Unit' field.
- Select "100" from the 'Room' field.
- Select "A" from the 'Bed' field.
- Select any option from the 'Room And Board Billing Code' field and click [Submit].
- Access the 'Admission' form.
- Select the first 'Episode' and click [Edit].
- Validate the 'Program' field contains "Inp. Adult Psych.".
- Select the 'Inpatient/Partial/Day Treatment' tab.
- Validate the 'Unit' field contains "Unit B".
- Validate the 'Room' field contains "100".
- Validate the 'Bed' field contains "A" and click [Discard].
- Click [Open Dashboard] for the new client.
- Validate the 'Client Header' contains the information previously entered during Admission.
|
Topics
• NX
• Admission
• Program Maintenance
• myAvatar/myAvatar NX
|
'Eligibility Response (271)' File Posting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Eligibility Response (271)
- Eligibility Response (271) Report
- Eligibility Inquiry and Response (270/271) Report
Scenario 1: 'Eligibility Response (271)' Form - Verification of 271 Eligibility Response File Posting
Specific Setup:
- Avatar PM Registry Setting 'Enable 270/271 Transaction Sets' must be enabled
- 271 Eligibility Response File configurations must be defined (via Avatar PM 'Guarantors/Payors' form)
- Inbound 271 Eligibility Response file containing one or more valid entries for loading/compilation/posting
Steps
- Open Avatar PM 'Eligibility Response (271)' form (under 'Avatar PM / Billing / Electronic Submission' menu path).
- Select 'Load File' in 'Options' field, and enter 'File Path\Name' value for 271 Eligibility Response file to be loaded.
- Click 'Process File' button to load specified 271 Eligibility Response file.
- Select 'Compile File' in 'Options' field, and select loaded 271 Eligibility Response file to be compiled in 'Select File' field.
- Click 'Process File' button to compile selected 271 Eligibility Response file.
- In 'Eligibility Response (271)' Report results, ensure that one or more valid response entries are compiled and present in report (in 'Response Data' sub-report/section).
- Select 'Post File' in 'Options' field, and select compiled 271 Eligibility Response file to be posted in 'Select File' field.
- Click 'Process File' button to post selected 271 Eligibility Response file.
- In 'Eligibility Response (271)' Report results, ensure that one or more valid response entries are posted and present in report (in 'Response Data' sub-report/section).
- Open Avatar PM 'Eligibility Inquiry and Response (270/271) Report' form (under 'Avatar PM / Billing / Electronic Submission' menu path).
- Enter/select value for 'Client ID', 'Episode Number' and 'Guarantor' criteria fields (as well as 'Service Code' and 'CPT-4 Code' criteria fields where applicable).
- Click 'Display Report' button to view Eligibility Inquiry and Response (270/271) Report results.
- In Eligibility Inquiry and Response (270/271) Report results, ensure that inquiry/response entry/entries is/are present in report for selected Client/Episode/Guarantor (in 'Eligibility Inquiries and Responses (Verified)' sub-report/section).
|
Topics
• Eligibility Response (271)
• NX
|
'Discharge' form - 'Time Verifications' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validating editing 'Discharge' after 'Pre Admission', 'Discharge', and 'Admission' on same date.
Specific Setup:
- Registry Settings: The following registry settings contain a value of 'Y'.
- Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking.
- Avatar PM->Client Management->Movement Options->->->Time Verifications.
- Avatar PM->Client Management->Movement Options->->->Allow Discharge To File/Edit Pre-Admits.
- Client: A:
- Has a 'Pre Admit' record. Note the admission time.
- Was discharged from the Pre Admit' record in the 'Discharge' form on the same date, later than the admission time. Note the discharge time.
- Has an 'Admission' or 'Admission (Outpatient)' record on same date, later than the discharge time.
- Client: B:
- Has a 'Pre Admit' record. Note the admission date and time.
Steps
- Open the existing ‘Discharge’ record for 'Client A'.
- Edit the discharge reason and/or the practitioner.
- Click [Submit].
- The form files successfully.
- Open ‘Discharge for 'Client B'.
- Set the 'Date Of Discharge' and the 'Discharge Time' to the same values noted in 'Setup'.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Discharge Time' to a time that is at least on minute later than the value noted in 'Setup'. Note the value.
- Select all other required or desired fields.
- Click [Submit].
- Open 'Admission' or 'Admission (Outpatient)' for 'Client B' to add a new record.
- Set the 'Preadmit/Admission Date' to the value noted in 'Setup'.
- Set the 'Preadmit/Admission Time' to the value noted in 'Discharge.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Preadmit/Admission Time' to a time that is at least on minute later than the value noted in 'Discharge'.
- Add data to all required or desired fields.
- Click [Submit].
- If desired, change the 'Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking' registry setting to a value of 'N' and repeat the testing.
- The ''Another movement (Preadmit Admission) exists for this date and time' displays' message will not be received.
Scenario 2: Validating editing 'Discharge' after 'Admission' , 'Discharge', and 'Admission' on same date.
Specific Setup:
- Registry Settings: The following registry settings contain a value of 'Y'.
- Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking.
- Avatar PM->Client Management->Movement Options->->->Time Verifications.
- Client: A:
- Has an 'Admission' or ‘Admission (Outpatient)’ record. Note the admission time.
- Was discharged from the above record in the 'Discharge' form on the same date, later than the admission time. Note the discharge time.
- Has another 'Admission' or 'Admission (Outpatient)' record on same date, later than the discharge time.
- Client: B:
- Has an 'Admission' or ‘Admission (Outpatient)’ record. Note the admission date and time.
Steps
- Open the existing ‘Discharge’ record for 'Client A'.
- Edit the discharge reason and/or the practitioner.
- Click [Submit].
- The form files successfully.
- Open ‘Discharge for 'Client B'.
- Set the 'Date Of Discharge' and the 'Discharge Time' to the same values noted in 'Setup'.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Discharge Time' to a time that is at least on minute later than the value noted in 'Setup'. Note the value.
- Select all other required or desired fields.
- Click [Submit].
- Open 'Admission' or 'Admission (Outpatient)' for 'Client B' to add a new record.
- Set the 'Preadmit/Admission Date' to the value noted in 'Setup'.
- Set the 'Preadmit/Admission Time' to the value noted in 'Discharge.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Preadmit/Admission Time' to a time that is at least on minute later than the value noted in 'Discharge'.
- Add data to all required or desired fields.
- Click [Submit].
- If desired, change the 'Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking' registry setting to a value of 'N' and repeat the testing.
- The ''Another movement (Preadmit Admission) exists for this date and time' displays' message will not be received.
|
Topics
• Pre Admit
• Admission (Outpatient)
• Discharge
|
'Client Ledger' Re-Billed Service Display
Scenario 1: 'Client Ledger' - Verification of Service Display for Client Ledger Sorting by Claim
Specific Setup:
- Client record with Client record with re-billed services included in claim(s)
Steps
- Open the Avatar PM/Cal-PM 'Client Ledger' form.
- Enter/select 'Client ID' value for Client Ledger display.
- Select 'Claim' in the 'Claim/Episode/All Episodes' field for limiting Client Ledger display/results to a single claim.
- Select desired claim number for Client Ledger display in 'Claim Number' field, where claim includes re-billed services.
- Select 'Simple' in the 'Ledger Type' field.
- Click 'Process' button.
- In Client Ledger results/display, ensure that re-billed service(s) related to/included in the selected claim are included in display.
|
Topics
• Client Ledger
|
'Compile/Edit/Post/Unpost Roll-Up Services Worklist' - component services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Orders This Episode
- HL7 Connection Monitor
- Launch RxConnect
- Compile Inbound HL7 Charge Batch File
- Post Inbound HL7 Charge Batch File
- Compile/Edit/Post/Unpost Roll-Up Services Worklist
- National Drug Code Reporting
- Rx Summary
- Order Tracking
Scenario 1: NCPDP Roll-Up Billing via the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form- Ensuring excluded component services are not included on the worklist or in National Drug Code Reporting
Specific Setup:
- myAvatar must be configured to communicate with RxConnect via Avatar HL7 and vice versa.
- Avatar HL7 must be installed and configured with an 'ADT-RXCONNECT', 'ORDERS-RXCONNECT', 'BILLING-RXCONNECT' and 'FILLDETAILS-RXCONNECT'.
- The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
- The applications must be configured for NCPDP Billing.
- A client must have an active inpatient episode. (Client A)
- "Client A" must be associated with a NCPDP guarantor in the 'Financial Eligibility' form.
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select "PRILOSEC (OMEPRAZOLE) 20 MG CAPSULE, DELAYED RELEASE ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Capsule" in the 'Dose Unit' field.
- Select "Twice A Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad].
- Search for and select "ADVIL 200 MG TABLET ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Tablet" in the 'Dose Unit' field.
- Select "Every Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad] and [Sign].
- Validate the 'Order grid' contains an order for "ADVIL 200 MG ORAL TABLET 1 Tablet, EVERY DAY" and an order for "PRILOSEC (OMEPRAZOLE) 20 MG ORAL CAPSULE, DELAYED RELEASE 1 Tablet, TWICE A DAY".
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) ORDERS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "ORM^O01" for "Client A".
- Close the report and the form.
- Access the 'Launch RxConnect' form.
- Click [Launch RxConnect].
- Validate that 'RxConnect' is displayed.
- Access 'RxSummary'.
- Find "Client A's" orders for "PRILOSEC 20 MG ORAL CAPSULE, DELAYED RELEASE" and "ADVIL 200 MG TABLET ORAL" and process the orders, which will result in an 'Rx #'s' being displayed for each order.
- Click 'Order Tracking'.
- Select the hospital that is associated with the Avatar application and click [Change and Resume].
- Set the 'Rx #' field to the value for the "PRILOSEC" order and press Enter.
- Validate the 'Order Item(s) - Drug' cell contains "Omeprazole(et PRILOSEC)".
- Validate the 'Order Item(s) - Strength' cell contains "20 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Set the 'Apply On' field to the date that the order was created and a time that is in the evening.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Repeat steps 3j - 3s until the 29th day.
- On the 30th day set the 'Apply On' field to the 30th day and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "PRILOSEC" order.
- Set the 'Rx #' field to the value received for the "ADVIL" order and click [Enter].
- Validate the 'Order Item(s) - Drug' cell contains "Ibuprofen(et IBUPROFEN)".
- Validate the 'Order Item(s) - Strength' cell contains "200 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "1.0000".
- Click [Post].
- Repeat steps 3ae - 3ai through the 30th of the month.
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "ADVIL" order.
- Wait until the files batch, this is done at a specific time each day.
- Once that has been completed access the 'Order Tracking' section and validate that for each 'Rx #' that the administrations were batched.
- Click 'Logout' and close the form.
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) FILL DETAILS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "O01-RDE" for "Client A".
- Select "(Outbound) BILLING-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "P03" for "Client A".
- Close the report and the form.
- Access the 'Compile Inbound HL7 Charge Batch File' form
- Select "Pharmacy" in the 'Compile For Which Charge Type' field.
- Validate a message is displayed stating "The system will now populate those fields for which a default value has been defined for the charge type selected." and click [OK].
- Set the 'Through Date of Service' field to the 30th day of the month and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Post Inbound HL7 Charge Batch File' form.
- Select "Pharmacy" in the 'Charge Type' field.
- Select "Post" in the 'Action' field.
- Select the batch that was just compiled in the 'HL7 Charge Batch File' field.
- Select "Yes, but in the background after posting has finished" in the 'Run Liability Update' field and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form.
- Set the 'Through Date' field to the 30th day of the month.
- Check off "NCPDP ***System Generated***" in the 'Roll-Up Definitions' field.
- Set the 'From Date' field to the first date of the month in which the orders were compiled and posted.
- Click [Compile Worklist].
- Validate a message is displayed stating "Compile complete" and click [OK].
- Click [Run Report].
- Validate that the 'Roll-Up Services Worklist' report is displayed and contains "29.00" under 'Days' and "58.00" under 'Quantity' for the "OMEPRAZOLE" charge code.
- Validate that the charge on the 30th of the month has been excluded from roll-up totals.
- Close the report.
- Select the 'Post Roll-Up Services Worklist' menu item.
- Select the through date with NCPDP rules included in the 'Through Date' field.
- Select any value in the 'Write Off Posting Code' field.
- Click [Post Worklist].
- Validate a 'Post Complete' message is displayed and click [OK] and close the form.
- Access the 'National Drug Code Reporting' form.
- Select "Client A" in the 'Client ID' field.
- Validate the 'Episode Number' field contains "Episode #1".
- Set the 'Service Start Date' field to the first date of the month for the charges that were billed.
- Set the 'Service End Date' field to the last date of the month for the charges that were billed.
- Select the "PRILOSEC (OMEPRAZOLE)" service in the 'Service To Record Information For' field.
- Click [Launch NDC Input].
- Validate that the 'Quantity' field and the 'Medicare Billing Units' field both contain "58".
- Click [Close/Cancel].
- Select the 'Additional Drug Information' section.
- Validate the 'Days Supply' field contains "29".
- Close the form.
Scenario 2: NCPDP Roll-Up Billing via the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form- Ensuring excluded component services are not included on the worklist or in National Drug Code Reporting
Specific Setup:
- myAvatar must be configured to communicate with RxConnect via Avatar HL7 and vice versa.
- Avatar HL7 must be installed and configured with an 'ADT-RXCONNECT', 'ORDERS-RXCONNECT', 'BILLING-RXCONNECT' and 'FILLDETAILS-RXCONNECT'.
- The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
- The applications must be configured for NCPDP Billing.
- A client must have an active inpatient episode. (Client A)
- "Client A" must be associated with a NCPDP guarantor in the 'Financial Eligibility' form.
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select "PRILOSEC (OMEPRAZOLE) 20 MG CAPSULE, DELAYED RELEASE ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Capsule" in the 'Dose Unit' field.
- Select "Twice A Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad].
- Search for and select "ADVIL 200 MG TABLET ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Tablet" in the 'Dose Unit' field.
- Select "Every Day" in the 'Freq' field.
- Set the 'Duration' field to "90" and click [Days].
- Set the 'Days Supply' field to "90".
- Set the 'Start Date' field to a date that is two months in the past and starts on the first of the month.
- Set the 'Start Time' field to "12:00 AM".
- Validate the 'Stop Date' field contains a date that is 90 days in the future of the 'Start Date'.
- Validate the 'Stop Time' field contains a time that is one minute prior than the 'Start Time'.
- Click [Add to Scratchpad] and [Sign].
- Validate the 'Order grid' contains an order for "ADVIL 200 MG ORAL TABLET 1 Tablet, EVERY DAY" and an order for "PRILOSEC (OMEPRAZOLE) 20 MG ORAL CAPSULE, DELAYED RELEASE 1 Tablet, TWICE A DAY".
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) ORDERS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "ORM^O01" for "Client A".
- Close the report and the form.
- Access the 'Launch RxConnect' form.
- Click [Launch RxConnect].
- Validate that 'RxConnect' is displayed.
- Access 'RxSummary'.
- Find "Client A's" orders for "PRILOSEC 20 MG ORAL CAPSULE, DELAYED RELEASE" and "ADVIL 200 MG TABLET ORAL" and process the orders, which will result in an 'Rx #'s' being displayed for each order.
- Click 'Order Tracking'.
- Select the hospital that is associated with the Avatar application and click [Change and Resume].
- Set the 'Rx #' field to the value for the "PRILOSEC" order and press Enter.
- Validate the 'Order Item(s) - Drug' cell contains "Omeprazole(et PRILOSEC)".
- Validate the 'Order Item(s) - Strength' cell contains "20 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Set the 'Apply On' field to the date that the order was created and a time that is in the evening.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- Repeat steps 3j - 3s until the 29th day.
- On the 30th day set the 'Apply On' field to the 30th day and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "0.5000".
- Click [Post].
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "PRILOSEC" order.
- Set the 'Rx #' field to the value received for the "ADVIL" order and click [Enter].
- Validate the 'Order Item(s) - Drug' cell contains "Ibuprofen(et IBUPROFEN)".
- Validate the 'Order Item(s) - Strength' cell contains "200 MG".
- Set the 'Apply On' field to the date that the order was created and a time that is in the morning.
- Set the 'Order Item(s) - Administer' field to "1".
- Click [Calculate Days Supply].
- Validate the 'Order Item(s) - Days Supply' field contains "1.0000".
- Click [Post].
- Repeat steps 3ae - 3ai through the 30th of the month.
- In the 'Tracking Information area, set the 'Start Date' to the first date of the order.
- Validate that the 'Tracking Information' grid and the 'Billing(current)' grid contains the administrations that were done for the "ADVIL" order.
- Wait until the files batch, this is done at a specific time each day.
- Once that has been completed access the 'Order Tracking' section and validate that for each 'Rx #' that the administrations were batched.
- Click 'Logout' and close the form.
- Access the 'HL7 Connection Monitor' form.
- Select "(Outbound) FILL DETAILS-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "O01-RDE" for "Client A".
- Select "(Outbound) BILLING-RXCONNECT" in the 'Select Row' field.
- Set the 'Transaction Log From Date' field to the current date.
- Set the 'Transaction Log Through Date' field to the current date.
- Set the 'Search Pattern 1' field to "Client A's First Name".
- Set the 'Search Pattern 2' field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed and contains two messages with an 'Event Type' of "P03" for "Client A".
- Close the report and the form.
- Access the 'Compile Inbound HL7 Charge Batch File' form
- Select "Pharmacy" in the 'Compile For Which Charge Type' field.
- Validate a message is displayed stating "The system will now populate those fields for which a default value has been defined for the charge type selected." and click [OK].
- Set the 'Through Date of Service' field to the 30th day of the month and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Post Inbound HL7 Charge Batch File' form.
- Select "Pharmacy" in the 'Charge Type' field.
- Select "Post" in the 'Action' field.
- Select the batch that was just compiled in the 'HL7 Charge Batch File' field.
- Select "Yes, but in the background after posting has finished" in the 'Run Liability Update' field and click [Process].
- Validate the 'Inbound HL7 Charge Batch File Details Report' is displayed and contains the charges for the "PRILOSEC (OMEPRAZOLE)" and "ADVIL (IBUPROFEN)" orders.
- Close the report and the form.
- Access the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form.
- Set the 'Through Date' field to the 30th day of the month.
- Check off "NCPDP ***System Generated***" in the 'Roll-Up Definitions' field.
- Set the 'From Date' field to the first date of the month in which the orders were compiled and posted.
- Click [Compile Worklist].
- Validate a message is displayed stating "Compile complete" and click [OK].
- Click [Run Report].
- Validate that the 'Roll-Up Services Worklist' report is displayed and contains "29.00" under 'Days' and "58.00" under 'Quantity' for the "OMEPRAZOLE" charge code.
- Validate that the charge on the 30th of the month has been excluded from roll-up totals.
- Close the report.
- Select the 'Post Roll-Up Services Worklist' menu item.
- Select the through date with NCPDP rules included in the 'Through Date' field.
- Select any value in the 'Write Off Posting Code' field.
- Click [Post Worklist].
- Validate a 'Post Complete' message is displayed and click [OK] and close the form.
- Access the 'National Drug Code Reporting' form.
- Select "Client A" in the 'Client ID' field.
- Validate the 'Episode Number' field contains "Episode #1".
- Set the 'Service Start Date' field to the first date of the month for the charges that were billed.
- Set the 'Service End Date' field to the last date of the month for the charges that were billed.
- Select the "PRILOSEC (OMEPRAZOLE)" service in the 'Service To Record Information For' field.
- Click [Launch NDC Input].
- Validate that the 'Quantity' field and the 'Medicare Billing Units' field both contain "58".
- Click [Close/Cancel].
- Select the 'Additional Drug Information' section.
- Validate the 'Days Supply' field contains "29".
- Close the form.
|
Topics
• Compile/Edit/Post/Unpost Roll-up Services Worklist
• NX
• NCPDP
|
The 'Diagnosis' and 'Enrollment Diagnosis' forms.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Client Diagnosis Web Service - Validating site specific section modeling field - Initially required
Specific Setup:
- An existing client is identified. Note client and episode number.
- A valid ICD-9 code, ICD-9 description, ICD-10 code, ICD-10 description, SNOMED code, SNOMED description and IMO code are identified for web service request.
- Dictionary Update - Input Dictionary Codes section:
- Enter a minimum of two dictionary codes and values. Note all the codes and values added.
- File = Client
- Data Element by number
- Data Element = 31032.1.
- Site Specific Section Modeling - (PATIENT590) Additional Diagnosis Information - 'Prompt Definition' tab:
- The site specific field 'SS Diagnosis Single Select Dictionary 1' is added with following options.
- Set Label to any desired value. Note the label.
- Set the 'Initially Required' to "Yes".
- Set the 'Lock Dictionary' Values to "Yes".
- Diagnosis -'Additional Diagnosis Information' section:
- Make sure the 'SS Diagnosis Single Select Dictionary 1' is added with the same label defined in the above section.
Steps
- Open SoapUI or any other web service tool.
- Use the WEBSVC.Diagnosis - AddClientDiagnosis web service.
- Enter desired SYSTEM CODE, UserName and Password.
- Enter Client ID from the setup section.
- Enter client's episode number in the 'EpisodeNumber' from the setup section.
- Enter desired value in the 'Type Of Diagnosis'. Note the value.
- Enter date of client's episode or after in the 'Date Of Diagnosis'. Note the value.
- Enter desired time in the 'Time Of Diagnosis'. Note the value.
- Enter desired clinician in the 'Diagnosing Clinician'. Note the value.
- Enter desired value in the 'Status' field. Note the value.
- Enter desired value in the 'Bill Order'. Note the value.
- Enter desired value in the 'SSDiagnosisDict1'. Note the value.
- Enter 'ICD9Code' from the setup section.
- Enter 'ICD10Code' from the setup section.
- Enter 'SNOMEDCode' from the setup section.
- Send a request to create a diagnosis record for an existing client.
- Verify the web service files successfully.
- Login to Avatar.
- Open the 'Diagnosis' form.
- Verify the diagnosis record is created for the client as specified in the web service request.
- Select the 'Additional Diagnosis Information' section.
- Verify the new Site Specific Single Select Dictionary field is populated correctly with the value entered through web service request.
- Close the form.
Scenario 2: Modeled forms support 'First Ever Diagnosis', 'Classification', and 'Problem List'
Specific Setup:
- Modeled form with a Diagnosis section and with the following fields added via "Modeling" options.
- Diagnosis mapped from the product Diagnosis form.
- Up to 5 First Ever Diagnosis columns
- Up to 5 Classification columns
- Up to 5 AddToProblemList columns
- Registry Settings that may impact the modeled form are:
- Avatar PM->Client Information->Diagnosis->->->Require Classification.
- Avatar PM->Client Information->Diagnosis->->->Enable Diagnosis Filtering based on Classification. Note that this registry setting can never be disabled once it is enabled.
- Avatar CWS->Problem List->->->->Problem Classification Required.
Steps
- Open the modeled form.
- Complete required fields and go to the "Diagnosis" section.
- Enter a "Diagnosis" of "B20" for "AIDS".
- Set "First Ever Dx" field to any value.
- Select a "Classification".
- Select a "Problem Classification".
- Select "Final" in the "Draft/final" field.
- Click [OK] on the "Selecting "Final" prevents future edits" dialog.
- Click [Submit].
- Access the 'Diagnosis' form.
- Verify that the 'Diagnosis pre-display' is displayed.
- Validate that one row is displayed in the pre-display.
- Select the row and click [Edit].
- Validate that the 'Diagnoses' grid contains a 'Description' of "AIDS" for row 1.
Scenario 3: Diagnoses entered via an Inbound ADT HL7 message
Specific Setup:
- Set the 'Avatar PM->Client Information->Diagnosis->->->Add First Ever Diagnosis Check' registry setting must be set to "1".
- Please log out of the application and log back in after completing the above configuration.
- There must be an Inbound ADT connection for 'ADT-GENERIC'.
- Ensure the 'Program Map' For Processing Inbound ADT' form contains a program map for a 'Receiving Facility (MSH-6.1)' is "98", 'Patient Class (PV1-2.1)' is "I" and the 'Program' is a value other than the one that "Client A" is currently in.
- A client must have an active inpatient episode (Client A).
Steps
- Validate an ADT inbound message was sent for "Client A" that contains an 'ICD10' diagnosis code of "B20".
- Access the 'HL7 Connection Monitor' form.
- Select "ADT-GENERIC" Inbound connection from the 'Select Row' field,
- Click [Show Transaction Log].
- Validate the 'HL7 Inbound Transaction Report' contains an 'Event Type' of "A08".
- Validate the 'HL7 Inbound Transaction Report' contains a 'Filing Status' value of "OK Diagnosis Information - 'Is this the first ever diagnosis?' is missing for row: 1.|".
- Validate the 'HL7 Inbound Transaction Report' contains "Client A's" name in the format of "Last Name^First Name" next to 'Name'.
- Close the report.
- Set the 'Avatar PM->Client Information->Diagnosis->->->Add First Ever Diagnosis Check' registry setting must be set to "2".
- Please log out of the application and log back in.
- Validate an ADT inbound message was sent for "Client A" that contains an 'ICD10' diagnosis code of "B20".
- Access the 'HL7 Connection Monitor' form.
- Select "ADT-GENERIC" Inbound connection from the 'Select Row' field,
- Click [Show Transaction Log].
- Validate the 'HL7 Inbound Transaction Report' contains an 'Event Type' of "A08".
- Validate the 'HL7 Inbound Transaction Report' contains a 'Filing Status' value of "OK".
- Validate the 'HL7 Inbound Transaction Report' contains "Client A's" name in the format of "Last Name^First Name" next to 'Name'.
- Close the report.
- Select "Client A" and access the 'Diagnosis' form.
- Verify that the 'Diagnosis pre-display' is displayed.
- Validate that one row is displayed in the pre-display.
- Select the row and click [Edit].
- Validate that the 'Diagnoses' grid contains a 'Description' of "AIDS" for row 1.
|
Topics
• Web Services
• Diagnosis
• HL7
|
File Import - future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- File Import
- Dynamic Form - Service Maximum Liability Assignment
- Program Maintenance
- Dynamic Form - Edit Service Fee Definition
- Posting/Adjustment Codes Definition
- Avatar_PM_File_Import_Deposit_Entry.rpt
Scenario 1: File Import - Service Guarantor Definitions
Specific Setup:
- Note: This functionality is for any service code type, including CCBHC service codes.
- Please contact your Netsmart representative to enable CCBHC Billing functionality, if desired.
- CCBHC setup has been completed.
- The 'Avatar_PM_File_Import_Record_Layouts' spreadsheet is included in the update zip file to assist in creating the 'Service Guarantor Definitions' file to import.
- Identify an existing service code.
- Create a 'File Import' for the 'Service Guarantor Definition' file type that contains the service code. Note the value of each field included in the file.
Steps
- Open 'File Import'.
- Select Service Guarantor Definitions’ in 'File Type'.
- Load, compile and post the file.
- Open 'Service Fee/Cross Reference Maintenance', 'Guarantor Definitions', and review the imported record in edit mode.
- Validate that all values equal the values in the imported file.
- Click [Guarantor Definitions Report].
- Validate that guarantor information is correct for the service code.
- Close the report.
- Close the form.
Scenario 2: File Import - Compiling/ Posting 'Deposit Entry' file with all the required/optional fields
Specific Setup:
- Registry Setting:
- Set the 'Avatar PM->System Maintenance->File Import->->->Import File Delimiter' registry setting to the desired value.
- Guarantors/Payor:
- An existing guarantor is identified to be assigned to the client. Note the guarantor code/value.
- Program Maintenance:
- Identify an existing program code / value to be used for client's admission.
- Identify the location of the program to be used for Client's admission.
- Admission:
- An inpatient or outpatient client is created using the program identified above or an existing client is identified. Note the Client id/name, admission date/program.
- Financial Eligibility:
- An existing guarantor is assigned to the client. Note the guarantor code/name.
- Service code:
- An existing service code to be used with inpatient/ outpatient program is identified. Note the service code for further validation.
- Posting/Adjustment Code Definition:
- An existing payment, adjustment or transfer code is identified to be used. Note the code and type of the code.
- File Import:
- An import file is created to process the deposit entry. Ensure that the file contains optional fields i.e. Receipt, Check # along with all the required fields. Note the file name / location of the file.
Steps
- Open the 'File Import' form.
- Select the 'Deposit Entry' from the File Type field.
- Upload the file Import file created in the setup section.
- Compile the file.
- Verify the file compiles successfully.
- Post the compiled file.
- Verify the file posted successfully.
- Open the 'Client Ledger' for the client.
- Verify the client ledger displays the deposit entry correctly.
- Click [Close Form].
|
Topics
• File Import
• NX
|
Accounts Receivable Console - Posting/Adjustment Codes Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- AR Console Configuration
- AR Console User Defaults Setup
- Posting/Adjustment Codes Definition
- Guarantors/Payors
- Practitioner Numbers By Guarantor And Program
- Program Maintenance
- Dynamic Form - Edit Service Fee Definition
- System Task Scheduler
- User Definition
Scenario 1: Validate 'Posting Code' availability in 'Post Transaction' pop-up screen.
Specific Setup:
Identify a client with an unpaid claim. Note the claim number, client last name, guarantor and program. The tester has been assigned the corresponding 'Client Last Name Initials to be Worked', 'Guarantor' and 'Program(s)' in 'AR Console User Defaults Setup'. The tester has access to the 'Accounts Receivable Console' widget. The 'System Task Scheduler', 'Auto AR Batch Update' was processed after the above claim was created in billing. Sign out of the system and back in after the 'System Task Scheduler', 'Auto AR Batch Update' has completed. 'Posting/Adjustment Codes Definition' has been used to create 'payment codes', 'adjustment codes' and 'transfer codes'.
Steps
- Open 'Accounts Receivable Console'.
- Enter the 'Claim #'.
- Click [Search].
- Verify that the claim is added to the 'Claims with Outstanding Receivables' grid.
- Select the claim in the 'Claims with Outstanding Receivables' grid.
- Verify that the service(s) display in the 'Claim Service Information' grid.
- Click [Post Transaction].
- Enter the 'Posting Date'.
- Enter the 'Date of Receipt'.
- Note the 'Current Balance'.
- Enter an 'Amount' that will not pay the service in full.
- Enter a question mark in 'Posting Code'.
- Verify that the 'Posting/Adjustment Codes Definitions' display.
- Select a value from the 'Posting/Adjustment Codes Definitions'.
- Note the 'New Balance'.
- Click [New Row].
- Enter an amount equal to the 'New Balance'.
- Enter a question mark in 'Posting Code'.
- Verify that the 'Posting/Adjustment Codes Definitions' display.
- Select a different value from the 'Posting/Adjustment Codes Definitions'.
- Note the 'New Balance' is $0.00.
- Click [Save].
|
Topics
• Accounts Receivable Management
• myAvatar/myAvatar NX
|
Discharge - closing form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validating editing 'Discharge' after 'Pre Admission', 'Discharge', and 'Admission' on same date.
Specific Setup:
- Registry Settings: The following registry settings contain a value of 'Y'.
- Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking.
- Avatar PM->Client Management->Movement Options->->->Allow Discharge To File/Edit Pre-Admits.
- Client: A:
- Has a 'Pre Admit' record. Note the admission time.
- Was discharged from the Pre Admit' record in the 'Discharge' form on the same date, later than the admission time. Note the discharge time.
- Has an 'Admission' or 'Admission (Outpatient)' record on same date, later than the discharge time.
- Client: B:
- Has a 'Pre Admit' record. Note the admission date and time.
Steps
- Open the existing ‘Discharge’ record for 'Client A'.
- Edit the discharge reason and/or the practitioner.
- Click [Submit].
- The form files successfully.
- Open ‘Discharge for 'Client B'.
- Set the 'Date Of Discharge' and the 'Discharge Time' to the same values noted in 'Setup'.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Discharge Time' to a time that is at least on minute later than the value noted in 'Setup'. Note the value.
- Select all other required or desired fields.
- Click [Submit].
- Open 'Admission' or 'Admission (Outpatient)' for 'Client B' to add a new record.
- Set the 'Preadmit/Admission Date' to the value noted in 'Setup'.
- Set the 'Preadmit/Admission Time' to the value noted in 'Discharge.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Preadmit/Admission Time' to a time that is at least on minute later than the value noted in 'Discharge'.
- Add data to all required or desired fields.
- Click [Submit].
- If desired, change the 'Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking' registry setting to a value of 'N' and repeat the testing.
- The ''Another movement (Preadmit Admission) exists for this date and time' displays' message will not be received.
Scenario 2: Validating editing 'Discharge' after 'Admission' , 'Discharge', and 'Admission' on same date.
Specific Setup:
- Registry Settings: The following registry settings contain a value of 'Y'.
- Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking.
- Client: A:
- Has an 'Admission' or ‘Admission (Outpatient)’ record. Note the admission time.
- Was discharged from the above record in the 'Discharge' form on the same date, later than the admission time. Note the discharge time.
- Has another 'Admission' or 'Admission (Outpatient)' record on same date, later than the discharge time.
- Client: B:
- Has an 'Admission' or ‘Admission (Outpatient)’ record. Note the admission date and time.
Steps
- Open the existing ‘Discharge’ record for 'Client A'.
- Edit the discharge reason and/or the practitioner.
- Click [Submit].
- The form files successfully.
- Open ‘Discharge for 'Client B'.
- Set the 'Date Of Discharge' and the 'Discharge Time' to the same values noted in 'Setup'.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Discharge Time' to a time that is at least on minute later than the value noted in 'Setup'. Note the value.
- Select all other required or desired fields.
- Click [Submit].
- Open 'Admission' or 'Admission (Outpatient)' for 'Client B' to add a new record.
- Set the 'Preadmit/Admission Date' to the value noted in 'Setup'.
- Set the 'Preadmit/Admission Time' to the value noted in 'Discharge.
- Validate that the message 'Another movement (Preadmit Admission) exists for this date and time' displays.
- Click [OK].
- Change the 'Preadmit/Admission Time' to a time that is at least on minute later than the value noted in 'Discharge'.
- Add data to all required or desired fields.
- Click [Submit].
- If desired, change the 'Avatar PM->Client Management->Movement Options->->->Duplicate Date/Time Checking' registry setting to a value of 'N' and repeat the testing.
- The ''Another movement (Preadmit Admission) exists for this date and time' displays' message will not be received.
Service Fee/Cross Reference Maintenance - Guarantor Definitions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Service Fee/Cross Reference and Guarantor Definition Export
- File Import
- Dynamic Form - Restore Definition
Scenario 1: File Import - Service Guarantor Definitions - 'Import Process Type' Registry Setting
Specific Setup:
- Registry Settings:
- The 'Avatar PM->System Maintenance->File Import->->->Import Process Type'' has the following values: 'FU&GU'.
- Service Fee/Cross Reference and Guarantor Definition Export has been used to export the 'Guarantor Definition. Select a service code with a definition to update.
- File Import:
- A 'Service Guarantor Definition' file exists to update the guarantor fee for the service code.
Steps
- Open 'File Import'.
- Select 'Service Guarantor Definitions' in 'File Type'.
- Upload/compile/post the 'Service Guarantor Definition' file.
- Open 'Service Fee/Cross Reference Maintenance'.
- Select the 'Guarantor Definitions' section.
- Click [Guarantor Definitions Report].
- Validate that the fee for the service code was updated.
- Close the report.
- Select the 'Restore Definitions' section.
- Click [Restore Maximum Liability Assignment Definition That Existed Prior to Last File Import].
- Select the 'Guarantor Definitions' section.
- Click [Guarantor Definitions Report].
- Validate that the fees were restored.
|
Topics
• Discharge
• NX
• Registry Settings
• Service Fee/Cross Reference Maintenance
• File Import
|
Edit service Information - Enable 'Admission vs. Service Program' Functionality registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Maintenance
- Program Transfer (OutPatient)
- Dynamic Form - Edit Service Information - Select Service(s) to Edit
Scenario 1: Edit Service Program - Editing the service information after program transfer - Enable 'Admission vs. Service Program' Functionality registry setting
Specific Setup:
- Registry Setting:
- The "Enable 'Admission vs. Service Program' Functionality" registry setting is set to 'Y'.
- Program Maintenance:
- Two new outpatient admission programs are created such that there is no overlap of the associated service programs between the two admission programs. Note the admission programs and associated service programs.
- Admission (Outpatient):
- The client is admitted in to the first admission program.
- Client Charge Input:
- A service is rendered to the client under one of the associated service programs. Note the service date and service code.
- Program Transfer (Outpatient):
- The client is transferred in to the second admission program.
Steps
- Open the 'Edit Service Information' form.
- Fill in all required fields.
- Click [Select Service(s) to Edit].
- Verify the 'Select Service(s) to Edit' dialog box launched with all the services rendered to the selected client.
- Select desired service to edit.
- Verify the 'Program' field is populated with the service programs that was associated with the admission program at the time of service creation.
- Submit the form.
- Verify the form submits successfully.
Scenario 2: Edit Service Program - Editing service program to another associated program - Enable 'Admission vs. Service Program' Functionality registry setting
Specific Setup:
- Registry Setting:
- The "Enable 'Admission vs. Service Program' Functionality" registry setting is set to 'Y'.
- Program Maintenance:
- Two new outpatient admission programs are created such that there is no overlap of the associated service programs between the two admission programs. Note the admission programs and associated service programs.
- Admission (Outpatient):
- The client is admitted in to the first admission program.
- Client Charge Input:
- A service is rendered to the client under one of the associated service programs. Note the service date and service code.
Steps
- Open the 'Edit Service Information' form.
- Fill in all required fields.
- Click [Select Service(s) to Edit].
- Verify the 'Select Service(s) to Edit' dialog box launched with all the services rendered to the selected client.
- Select desired service to edit.
- Verify the 'Program' field is populated with the service programs that were associated with the admission program at the time of service creation.
- Change the service program.
- Enter desired practitioner.
- Submit the form.
- Verify the form submits successfully.
|
Topics
• Registry Settings
• Program Maintenance
• Edit Service Information
• Program Transfer
• NX
|
Service Panel Charge Input - Incident-To Practitioner
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Practitioner Enrollment
- User Definition
- Incident-To Practitioner Daily Log
- Dynamic Form - Edit Service Fee Definition
- Service Panel
- Service Panel Charge Input
- SQL Query/Reporting
Scenario 1: Service Panel Charge Input - Filing incident-to practitioner with the panel services - 'Enable Incident-To Practitioner' registry setting is set to "YC"
Specific Setup:
- Registry Setting:
- The 'Enable Incident-To Practitioner' registry setting is set to 'YC'.
- The 'Service Panel Charge Input - Fields To Include' registry setting is set to desired value to add 'Service Start Time' and 'Service End Time' fields to 'Service Panel Charge Input' form.
- Practitioner Enrollment:
- Create a new practitioner or edit an existing practitioner. Note the practitioner id and practitioner name.
- The 'Incident-To Practitioner' field is set to "Yes" for the practitioner identified above.
- Service Code:
- Parent service codes should be defined before they are used in this form. Note the service code.
- Service Fee/Cross Reference:
- The service fee is defined for the service code.
- The 'Incident-To' field is set to Y.
Steps
- Open the 'Incident-To Practitioner Daily Log' form.
- Select the 'Add Daily Log Entry' tab.
- Select the practitioner identified in the setup section. Note the practitioner.
- Select the desired date to 'Date' field. Note the date.
- Select 'Start Time'. Note the time.
- Select the 'End time'. Note the time.
- Select desired 'Location'. Note the location.
- Click [File Entry].
- Validate the 'Information' dialogue contains 'Filed Successfully' message.
- Click [OK].
- Open the 'Service Panel' form.
- Select 'Add' In the 'Add New or Edit Existing Service Panel' field.
- Select an existing service code in the 'Service Code' field (i.e. Service Code 1).
- Enter desired date based on the date defined in the 'Effective Date' field.
- Select 'Yes' in the 'File The Parent Service With This Panel' field.
- Select another existing service code from the 'Select Service Code To Add To Panel' search box (i.e. Service Code 2).
- Click [Add selected Service To Panel].
- Verify the service code selected is displayed in the 'Service Panel' item.
- Submit the form.
- Verify that the form submitted successfully.
- Open the 'Service Panel Charge Input' form.
- Enter desired date in the 'Date Of Service' field.
- Select the client in the 'Client ID' field.
- Enter 'Service Start Time' based on the time range defined for the Incident-To Practitioner in the 'Incident-To Practitioner Daily Log' form.
- Enter 'Service End Time' based on the time range defined for the Incident-To Practitioner in the 'Incident-To Practitioner Daily Log' form.
- Select the 'Panel Description'.
- Select the 'Panel Service(s)'.
- Select the 'Incident-To Practitioner'.
- Verify the panel service files successfully.
- Open the 'Crystal Report' or any other SQL data viewer.
- Query the 'SYSTEM.billing_tx_history' SQL table.
- Verify the Incident To practitioner is filed correctly for the service.
Scenario 2: Service Panel Charge Input - Filing incident-to practitioner with the panel services - 'Enable Incident-To Practitioner' registry setting is set to "Y"
Specific Setup:
- Registry Setting:
- The 'Enable Incident-To Practitioner' registry setting is set to 'Y'.
- The 'Service Panel Charge Input - Fields To Include' registry setting is set to desired value to add 'Service Start Time' and 'Service End Time' fields to 'Service Panel Charge Input' form.
- Practitioner Enrollment:
- Create a new practitioner or edit an existing practitioner. Note the practitioner id and practitioner name.
- The 'Incident-To Practitioner' field is set to "Yes" for the practitioner identified above.
- Service Code:
- Parent service codes should be defined before they are used in this form. Note the service code.
- Service Fee/Cross Reference:
- The service fee is defined for the service code.
- The 'Is This Incident-To Service' field is set to 'Y'.
Steps
- Open the 'Incident-To Practitioner Daily Log' form.
- Select the 'Add Daily Log Entry' tab.
- Select the practitioner identified in the setup section. Note the practitioner.
- Select the desired date to 'Date' field. Note the date.
- Select 'Start Time'. Note the time.
- Select the 'End time'. Note the time.
- Select desired 'Location'. Note the location.
- Click [File Entry].
- Validate the 'Information' dialogue contains 'Filed Successfully' message.
- Click [OK].
- Open the 'Service Panel' form.
- Select 'Add' In the 'Add New or Edit Existing Service Panel' field.
- Select an existing service code in the 'Service Code' field (i.e. Service Code 1).
- Enter desired date based on the date defined in the 'Effective Date' field.
- Select 'Yes' in the 'File The Parent Service With This Panel' field.
- Select another existing service code from the 'Select Service Code To Add To Panel' search box (i.e. Service Code 2).
- Click [Add selected Service To Panel].
- Verify the service code selected is displayed in the 'Service Panel' item.
- Submit the form.
- Verify that the form submitted successfully.
- Open the 'Service Panel Charge Input' form.
- Enter desired date in the 'Date Of Service' field.
- Select the client in the 'Client ID' field.
- Enter 'Service Start Time' based on the time range defined for the Incident-To Practitioner in the 'Incident-To Practitioner Daily Log' form.
- Enter 'Service End Time' based on the time range defined for the Incident-To Practitioner in the 'Incident-To Practitioner Daily Log' form.
- Select the 'Panel Description'.
- Select the 'Panel Service(s)'.
- Select the 'Incident-To Practitioner'.
- Verify the panel service files successfully.
- Open the 'Crystal Report' or any other SQL data viewer.
- Query the 'SYSTEM.billing_tx_history' SQL table.
- Verify the Incident To Practitioner is not filed for the service.
Quick Billing - Add/Edit quick billing batch
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Quick Billing
- Guarantors/Payors
- Quick Billing Rule Definition
- Dynamic Form Compile Complete
Scenario 1: Quick Billing - Validating work screen and 837 report through 'Edit Existing' quick billing batch
Specific Setup:
- Registry Setting:
- The 'Enable New Quick Billing Format' registry setting is enabled.
- Please note: This is a one-time, system-wide registry setting and the associated functionality cannot be disabled once the registry setting is enabled. Once this setting has been enabled, it will no longer be able to be viewed in the 'Registry Settings' form.
- Admission:
- Two outpatient clients are identified. Please note the admission program of the clients.
- Guarantors/Payor:
- An existing guarantor is identified.
- Financial Eligibility:
- Guarantor identified above is assigned to the clients.
- Client Charge Input:
- 1-2 days of professional charges are rendered to the clients. Please note the service codes used during rendering services.
- Client Ledger:
- The charges are distributed to the guarantors assigned to the clients.
- Quick Billing Rule Definition:
- A new quick billing rule is created as follows:
- The admission programs are selected in the 'Program' field.
- An '837 Professional' is selected in the 'Billing Form' field.
- The guarantors assigned to the clients in their financial eligibility are selected in the 'Guarantors' field.
- All required fields are populated.
- The 'Create Interim Billing Batch' field is set to 'Yes'.
Steps
- Open the 'Quick Billing' form.
- Run a new quick billing batch using the rule created in the setup section.
- Use a date range spanning services entered.
- Select 'Create Batch', 'Close Charges', and 'Generate Bills' in the 'Quick Billing Tasks To Execute' field.
- Submit the form.
- Verify that compile completes and the prompt states 'Compile Complete'. A Quick Billing Batch and an Interim Billing Batch will be created.
- Select the 'Edit Existing' option.
- Select the quick bill that was created in previous step.
- Submit the form again.
- Click [OK].
- Select the 'Edit Existing' option.
- Select the quick bill that was created in previous step.
- Click [Print 837 Report].
- Verify the report launched successfully.
- Close the report.
- Click [Launch Workscreen].
- Verify the work screen contains all the clients included in the batch.
- Deselect one client from the 'Client' filter at the top of the work screen.
- Verify the grid does not display the services of that client.
- Select the same client again from the 'Client' filter at the top of the work screen.
- Verify the grid displays the services of that client.
- Save the grid.
- Verify the grid saves successfully.
- Close the form.
Spreadsheet Batch Remittance Posting - Security level of the posting code
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
- User Definition
- Spreadsheet Batch Remittance Posting
- Individual Cash Posting (PM)
- Dynamic Form - Individual Cash Posting - Information
- Dynamic Form - Individual Cash Posting - Alert
- Dynamic Form - Individual Cash Posting - Client
- Spreadsheet Remittance Posting
Scenario 1: Spreadsheet Batch Remittance Posting - Validating security level of the posting code
Specific Setup:
- Posting/Adjustment Codes Definition:
- Identify an existing posting code. Note the code/value of the posting code.
- Security level is set up to desired level. Note the security level of the code.
- User Definition:
- Set the security level of the user to a lower level than the security level set up for the posting code identified.
- Admission:
- An existing client is identified. Note the client ID and client name.
- Financial Eligibility:
- An existing guarantor is assigned to the client. Note the guarantor code and value.
- Client Charge Input:
- 5-6 services are rendered to the client.
- Close Charges:
- The services rendered to the client are closed.
- Client Ledger:
- The services are distributed correctly to the guarantor.
- Create Interim Billing Batch:
- An interim billing batch is created to include client/guarantor and services. Note the interim billing batch number generated and name.
Steps
- Open the 'Spreadsheet Batch Remittance Posting' form.
- Select "Create Batch" in the "Create, Edit Or Delete Remittance Batch" field.
- Enter a description in the “Batch Description” field. Note the batch description.
- Select the interim billing batch created in the setup section in the 'Interim Batch Number' field.
- Enter a date in the “Posting Date” field.
- Enter a date in the “Date Of Receipt” field.
- Select all other fields as required.
- Click the "Launch Work Screen" button.
- Validate the Client, Ep#, Payor, Begin Date/Svc Date, End Date, Total Charges, Liability fields populated correctly based on the client, guarantor and services included in the interim billing batch.
- Validate the 'Payment Code' dropdown field does not contain the payment code created in the 'Posting /Adjustment Code Definition' form.
- Click [Cancel].
- Click [Close Form].
- Open the 'User Definition' form.
- Update the security level of the user so that it is greater than or equal to the security level of the posting code identified above in the setup section.
- Click "Refresh Forms" icon.
- Open the 'Spreadsheet Batch Remittance Posting' form.
- Select "Create Batch" in the "Create, Edit Or Delete Remittance Batch" field.
- Enter a description in the “Batch Description” field. Note the batch description.
- Select the interim billing batch created in the setup section in the 'Interim Batch Number' field.
- Enter a date in the “Posting Date” field.
- Enter a date in the “Date Of Receipt” field.
- Select all other fields as required.
- Click the "Launch Work Screen" button.
- Validate the Client, Ep#, Payor, Begin Date/Svc Date, End Date, Total Charges, Liability fields populated correctly based on the client, guarantor and services included in the interim billing batch.
- Validate the 'Payment Code' dropdown field contains the payment code created in the 'Posting /Adjustment Code Definition' form.
- Select the posting amount/code identified in the setup section.
- Click [Accept].
- Click [Submit].
- Validate the 'Remittance Batch [Batch# created] Posted' message.
- Click [OK].
- Select "No" to form return message.
Scenario 2: Individual Cash Posting - Validating security level of the user based on the security level of the posting code
Specific Setup:
- Posting/Adjustment Codes Definition:
- Identify an existing posting code. Note the code/value of the posting code.
- Security level is set up to desired level. Note the security level of the code.
- User Definition:
- Set the security level of the user to a same level as the security level set up for the posting code identified.
- Admission:
- An existing client is identified. Note the client ID and client name.
- Financial Eligibility:
- An existing guarantor is assigned to the client. Note the guarantor code and value.
- Client Charge Input:
- 5-6 services are rendered to the client.
- Close Charges:
- The services rendered to the client are closed.
- Client Ledger:
- The services are distributed correctly to the guarantor.
- Create Interim Billing Batch:
- An interim billing batch is created to include client/guarantor and services. Note the interim billing batch number generated and name.
Steps
- Open the 'Individual Cash Posting' form.
- Select desired client.
- Click the 'Select the Item(s) to Post Against'.
- Select the desired row.
- Enter 'Posting Date'.
- Enter 'Date of Receipt'.
- Select the desired 'Guarantor'.
- Enter the 'Dollar Amount To Be Posted'.
- Select the payment posting code set up in the setup section.
- Click [Update Temporary Files].
- Click [OK].
- Click [Submit].
- Verify the posting submitted successfully.
Scenario 3: Spreadsheet Remittance Posting - Validating security level of the user based on the security level of the posting code
Specific Setup:
- Posting/Adjustment Codes Definition:
- Identify an existing posting code. Note the code/value of the posting code.
- Security level is set up to desired level. Note the security level of the code.
- User Definition:
- Set the security level of the user to a lower level than the security level set up for the posting code identified.
- Admission:
- An existing client is identified. Note the client ID and client name.
- Financial Eligibility:
- An existing guarantor is assigned to the client. Note the guarantor code and value.
- Client Charge Input:
- 5-6 services are rendered to the client.
- Close Charges:
- The services rendered to the client are closed.
- Client Ledger:
- The services are distributed correctly to the guarantor.
- Create Interim Billing Batch:
- An interim billing batch is created to include client/guarantor and services. Note the interim billing batch number generated and name.
Steps
- Open the 'Spreadsheet Remittance Posting' form.
- Select desired client.
- Enter a date in the “Posting Date” field.
- Enter a date in the “Date Of Receipt” field.
- Select all other fields as required.
- Click the "Launch Work Screen" button.
- Validate the Client, Ep#, Payor, Begin Date/Svc Date, End Date, Total Charges, Liability fields populated correctly based on the client, guarantor and services included in the interim billing batch.
- Validate the 'Payment Code' dropdown field contains the payment code created in the 'Posting /Adjustment Code Definition' form.
- Select the payment code created in the 'Posting /Adjustment Code Definition' form.
- Enter desired amount in the 'Payment Amount' field.
- Click [Accept].
- Click [Submit].
- Verify the error message for the security level.
- Open the 'User Definition' form.
- Update the security level of the user such that it is greater than or equal to the security level of the posting code identified above in the setup section.
- Open the 'Spreadsheet Remittance Posting' form.
- Select desired client.
- Enter a date in the “Posting Date” field.
- Enter a date in the “Date Of Receipt” field.
- Select all other fields as required.
- Click the "Launch Work Screen" button.
- Validate the Client, Ep#, Payor, Begin Date/Svc Date, End Date, Total Charges, Liability fields populated correctly based on the client, guarantor and services included in the interim billing batch.
- Validate the 'Payment Code' dropdown field contains the payment code created in the 'Posting /Adjustment Code Definition' form.
- Select the payment code created in the 'Posting /Adjustment Code Definition' form.
- Enter desired amount in the 'Payment Amount' field.
- Click [Accept].
- Click [Submit].
- Validate the amount posted successfully.
- Click [X].
- Select "No" to form return message.
;
Web Service - Edit Service Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Dynamic Form - Edit Service Information - Select Service(s) to Edit
- SQL Query/Reporting
Scenario 1: Edit Service Information - Editing 'Open' services
Specific Setup:
- Identify an existing client that have at least one existing open service.
Steps
- Open the 'Edit Service Information' form.
- Select the desired client in the 'Client ID' field.
- Select desired episode from the 'Episode Number' field.
- Click [Select Service(s) To Edit].
- Verify the 'Select Service(s) To Edit' dialog is displayed.
- Select desired service from the 'Select Service(s) To Edit' dialog.
- Enter a different value in the 'Duration (Minutes)' field.
- Select a new service code in the 'Service Code' field.
- Click [OK].
- Submit the form.
- Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
- Click [No].
- Query the 'SYSTEM.billing_tx_history' SQL table.
- Validate the 'PATID' column is equal to the correct client id identified in the setup.
- Validate the 'date_of_service' column is equal to correct date of service rendered to the client.
- Validate the 'Service Code' column contains correct service code entered in the 'Edit Service Information' form.
- Validate the 'data_entry_source' column contains 'Edit Service Information'.
Scenario 2: 'Edit Service Information' web service - Editing 'Open' services
Specific Setup:
- Identify an existing client that have at least one existing open service. Note the client id/name, service code and service date.
Steps
- Open the SoapUI or any other web service testing tool.
- Create a web service request to edit the service information.
- Enter same value in the SYSTEMCODE which is used to sign in to Avatar.
- Enter same value in the USERNAME which is used to sign in to Avatar.
- Enter values for all required fields.
- Select desired service from the 'Select Service(s) To Edit' dialog.
- Select a new service code in the 'Service Code' field.
- Submit the request.
- Verify the message: "Edit Service Information web service has been filed successfully."
- Select desired items from the 'Content' checkbox.
- Click [Submit].
- Open the 'Crystal Reports' or any other SQL Data Reporting tool.
- Select the PM namespace.
- Query the 'SYSTEM.billing_tx_history' SQL table.
- Validate the 'PATID' column is equal to the correct client id identified in the setup.
- Validate the 'date_of_service' column is equal to correct date of service rendered to the client.
- Validate the 'Service Code' column contains correct service code entered in the web service request.
- Validate the 'data_entry_source' column contains 'WEBSVC.EditServiceInformation:EditServiceInformationICD10'.
837 Professional - Place of service (CLM-05-01)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Dynamic Form - Edit Service Fee Definition
Scenario 1: 837 Professional - Validating Place of Service Code (2300-CLM-05-1) field for the primary service associated to the add-on service code
Specific Setup:
- Guarantors/Payors:
- A new guarantor is created or an existing guarantor is identified.
- Note the guarantor code/name to be used during creating financial eligibility record for the client.
- Admission:
- The client is admitted to the outpatient program or an existing outpatient client is identified. Note the admission date/program.
- Financial Eligibility:
- The guarantor identified above is assigned to the client.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Dictionary Update:
- File = Client
- Dictionary Element - Location
- Dictionary Code - Desired code that is different than the default location for the admission program
- Dictionary Value - Desired value
- Extended Dictionary Data Element - Place Of Service (837 Electronic Billing)
- Extended Dictionary Value (Single Dictionary) - Desired value
- Service Codes:
- An add-on code is created of desired 'Service Code Type'. Note the code/value.
- A primary service code is created of the desired 'Service Type Code'. Note the code/value.
- Service Fee/Cross Reference Maintenance:
- Fee definitions are created for the service codes and CPT codes are assigned to the service code.
- Client Charge Input:
- A service is rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
- Close Charges:
- Charges are closed.
- Client Ledger:
- Verify the charges are correctly distributed to the desired guarantor, and they are in 'Unbill' status.
- Create Interim Billing Batch:
- A billing batch is created for the client, service and guarantor. Note the batch number to be used during 'Electronic Billing'.
Steps
- Open the 'Electronic Billing' form.
- Compile an 837 professional bill for the interim billing batch created in the setup section.
- Verify the bill compiles successfully.
- Dump the file.
- Review an 837 professional dump file.
- Verify the 'Place of Service Code' at the claim level (2300-CLM-05-1) is based on the location selected for the service.
- Click [X].
- Click [Discard].
Scenario 2: 837 Professional - Validating Place of Service Code (CLM-05-1) field for the service that is not associated to the add-on service code
Specific Setup:
- Guarantors/Payors:
- A new guarantor is created or an existing guarantor is identified.
- Note the guarantor code/name to be used during creating financial eligibility record for the client.
- Admission:
- The client is admitted to the outpatient program or an existing outpatient client is identified. Note the admission date/program.
- Financial Eligibility:
- The guarantor identified above is assigned to the client.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Dictionary Update:
- File = Client
- Dictionary Element - Location
- Dictionary Code - Desired code that is different than the default location for the admission program
- Dictionary Value - Desired value
- Extended Dictionary Data Element - Place Of Service (837 Electronic Billing)
- Extended Dictionary Value (Single Dictionary) - Desired value
- Service Codes:
- An existing service code is identified or a new service code is created of desired 'Service Code Type'. Note the code/value.
- Service Fee/Cross Reference Maintenance:
- Fee definitions is created for the service code and CPT code is assigned to the service code.
- Client Charge Input:
- A service is rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
- Close Charges:
- Charges are closed.
- Client Ledger:
- Verify the charges are correctly distributed to the desired guarantor, and they are in 'Unbill' status.
- Create Interim Billing Batch:
- A billing batch is created for the client, service and guarantor. Note the batch number to be used during 'Electronic Billing'.
Steps
- Open the 'Electronic Billing' form.
- Compile an 837 professional bill for the interim billing batch created in the setup section.
- Verify the bill compiles successfully.
- Dump the file.
- Review an 837 professional dump file.
- Verify the 'Place of Service Code' at the claim level (2300-CLM-05-1) is based on the location selected for the service.
- Click [X].
- Click [Discard].
|
Topics
• NX
• Spreadsheet Batch Remittance Posting
• Spreadsheet Remittance Posting
• Individual Cash Posting
• Edit Service Information
• Web Services
• 837 Professional
|
Client Ledger - 'Claim' Ledger type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
- Individual Cash Posting (PM)
- Dynamic Form - Individual Cash Posting - Information
- Dynamic Form - Individual Cash Posting - Alert
- Dynamic Form - Individual Cash Posting - Client
Scenario 1: Registry Setting Validation - Include Non-Chargeable Leaves in Client Ledger View
Steps
Set the 'Limit Registry Settings to the Following Search Criteria' to "Include Non-Chargeable Leaves in Client". Click [View Registry Settings]. Validate the 'Registry Setting' field contains "Avatar PM->Billing->Client Ledger->->->Include Non-Chargeable Leaves in Client Ledger View". Validate the Registry Setting Details text area contains "[FACILITY SPECIFIC] Selecting 'Y' allows for Leaves defined as non-chargeable to report on the simple view of the Client Ledger. The system will include any '(757) Type of Leave From' value that has the defined extended dictionary element '(10031) Chargeable Leave Y/N' set to 'No' as a line item on the Client Ledger. The claim view will also show all leaves. Please Note: this will add information to the Client Ledger for reporting purposes only. The system will not generate charges for these types of Leaves. Selecting 'N' continues to not report non-chargeable Leaves in the Client Ledger. This is the default behavior of the system." Validate the 'Registry Setting Value' field is equal to "N". Set the 'Registry Setting Value' input box to "1". Validate the Error dialog contains "The selected value is not valid in the current system code for the following reason: Invalid response -- Must be Y or N". Click [OK]. Set the 'Registry Setting Value' input box to "0". Validate the Error dialog contains "The selected value is not valid in the current system code for the following reason: Invalid response -- Must be Y or N". Click [OK]. Set the 'Registry Setting Value' input box to "". Click [Submit]. Validate the Filing Error dialog contains "Filing Error The following fields are missing: Registry Setting Value" Click [OK]. Set the Registry Setting Value input box to "@" Validate the Error dialog contains "The selected value is not valid in the current system code for the following reason: Invalid response -- Must be Y or N". Click [OK]. Set the Registry Setting Value input box to "Y". Click [Submit]. Validate the Filing Results text area contains "Results filing value Y to Avatar PM->Billing->Client Ledger->->->Include Non-Chargeable Leaves in Client Ledger View Successful filing in System Code SBOX. " Click [OK]. Validate the Form Return dialog contains "Form Return Registry Settings has completed. Do you wish to return to form?" Click [No].
Scenario 2: Client Ledger - Validating 'Claim' based crystal reort
Specific Setup:
- Posting/Adjustment Codes Definition:
- Identify an existing payment, adjustment and/or transfer codes. Note the codes/values for further testing.
- Admission:
- A new client is admitted in the inpatient program. Note the client id/name, admission program, admission date.
- Guarantor/Payors:
- An existing guarantor is identified to assign to the client.
- Financial Eligibility:
- The existing guarantor is assigned to the client. Note the Guarantor code/value.
- Service Codes:
- An existing room and board service code is identified to render services to the client. Note the service code.
- Client Charge Input:
- 5-6 days of the room and board services are rendered to the client.
- Close Charges:
- The charges rendered to the client are closed.
Steps
- Open the 'Electronic Billing' form.
- Run an 837 Institutional bill for the client.
- Verify the bill compiles successfully.
- Claim the services.
- Verify the bill compiles successfully.
- Open the 'Client Ledger' form.
- Process the report using 'Claim' ledger type and validate that the claim based report displays all the claim specific information.
- Open the ‘Individual Cash Posting’ form.
- Select the ‘Client’.
- Select desired value in the ‘Post By’ field.
- Click [Select Item(s) To Post Against].
- A grid opens containing a row for all services.
- Select a desired row.
- Click [OK] when all desired rows have been selected.
- Note the ‘Information’ message and the current balance for the guarantor.
- Click [OK].
- Enter desired value in ‘Posting Date’.
- Enter desired value in ‘Date of Receipt’.
- Validate that the ‘Guarantor’ defaulted to the guarantor in the current balance message.
- Enter desired value in ‘Dollar Amount To Be Posted’. Amount entered can be the full amount due or a partial amount due.
- Enter desired value in ‘Posting Code’.
- If desired, enter a value in ‘Check #’.
- Enter desired value in ‘Action For Remaining Balance If Applicable’.
- Click [Update Temporary File].
- If desired, continue to add payment/adjustments/transfers using the steps above for all other services.
- Click [Submit] when all payment/adjustments/transfers have been completed.
- Open ‘Client Ledger’ for the client’.
- Process the report using ‘Simple' ledger type and validate that the payment/adjustments/transfers posted correctly.
- Process the report using ‘Claim' ledger type and validate that the payment/adjustments/transfers posted correctly specific to claim.
- Close the form.
Client Ledger - Leave of absence view in the 'Simple' and 'Claim' crystal report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Leaves
- Posting/Adjustment Codes Definition
- Individual Cash Posting (PM)
- Dynamic Form - Individual Cash Posting - Information
- Dynamic Form - Individual Cash Posting - Alert
- Dynamic Form - Individual Cash Posting - Client
- Discharge
Scenario 1: Client Ledger - Validating leave of absence in the 'Simple' and 'Claim' report - Client with a single episode - Registry setting 'Include Non-Chargeable Leaves in Client Ledger View' = "Y"
Specific Setup:
- Registry Setting:
- The 'Include Non-Chargeable Leaves in Client Ledger View' registry setting is set to "Y".
- Dictionary Update:
- Dictionary = Client
- Data Element = Type of Leave From
- Identify an existing non-billable leave type or create a new dictionary code/value for a non-billable leave type that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘No’. Note the type of leave.
- Identify an existing same day leave type or create a new dictionary code/value for a same day leave that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘No’. Note the type of leave.
- Identify an existing billable leave type or create a new dictionary code/value for a billable leave that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘Yes’. Note the type of leave.
- Guarantor/Payors:
- An existing guarantor is identified to assign to the client.
- Admission:
- A new client is admitted in an inpatient program. Note the client id/name, admission program, admission date.
- Financial Eligibility:
- The existing guarantor is assigned to the client. Note the Guarantor code/value.
- Service Codes:
- An existing service code is identified to render services to the client. Note the service code.
Steps
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting from the admission date.
- Open the 'Leaves' form.
- Place the client on a non-billable leave for desired days after the admission date. Note the date.
- Open the 'Return From Leaves' form.
- Return the client. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting after date of the return.
- Open the 'Leaves' form.
- Place a client on a billable leave for desired days after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client after desired days from the leave start date. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client after date of return.
- Open the 'Leaves' form.
- Place a client on a same day leave after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client on a same day a few hours from the leave start time.
- Open the 'Client Ledger' form for the client.
- Process the 'Simple' ledger for the client.
- Review the report.
- Verify the ledger displays no-billable leaves along with the services rendered to the client in the report and does not display billable and/or same day leave in the report.
- Close the report.
- Process the 'Claim' ledger for the client.
- Verify the ledger displays non-billable leaves, billable leaves and/or same day leave in the report.
- Close the report.
Scenario 2: Client Ledger - Validating 'Claim' based crystal reort
Specific Setup:
- Posting/Adjustment Codes Definition:
- Identify an existing payment, adjustment and/or transfer codes. Note the codes/values for further testing.
- Admission:
- A new client is admitted in the inpatient program. Note the client id/name, admission program, admission date.
- Guarantor/Payors:
- An existing guarantor is identified to assign to the client.
- Financial Eligibility:
- The existing guarantor is assigned to the client. Note the Guarantor code/value.
- Service Codes:
- An existing room and board service code is identified to render services to the client. Note the service code.
- Client Charge Input:
- 5-6 days of the room and board services are rendered to the client.
- Close Charges:
- The charges rendered to the client are closed.
Steps
- Open the 'Electronic Billing' form.
- Run an 837 Institutional bill for the client.
- Verify the bill compiles successfully.
- Claim the services.
- Verify the bill compiles successfully.
- Open the 'Client Ledger' form.
- Process the report using 'Claim' ledger type and validate that the claim based report displays all the claim specific information.
- Open the ‘Individual Cash Posting’ form.
- Select the ‘Client’.
- Select desired value in the ‘Post By’ field.
- Click [Select Item(s) To Post Against].
- A grid opens containing a row for all services.
- Select a desired row.
- Click [OK] when all desired rows have been selected.
- Note the ‘Information’ message and the current balance for the guarantor.
- Click [OK].
- Enter desired value in ‘Posting Date’.
- Enter desired value in ‘Date of Receipt’.
- Validate that the ‘Guarantor’ defaulted to the guarantor in the current balance message.
- Enter desired value in ‘Dollar Amount To Be Posted’. Amount entered can be the full amount due or a partial amount due.
- Enter desired value in ‘Posting Code’.
- If desired, enter a value in ‘Check #’.
- Enter desired value in ‘Action For Remaining Balance If Applicable’.
- Click [Update Temporary File].
- If desired, continue to add payment/adjustments/transfers using the steps above for all other services.
- Click [Submit] when all payment/adjustments/transfers have been completed.
- Open ‘Client Ledger’ for the client’.
- Process the report using ‘Simple' ledger type and validate that the payment/adjustments/transfers posted correctly.
- Process the report using ‘Claim' ledger type and validate that the payment/adjustments/transfers posted correctly specific to claim.
- Close the form.
Scenario 3: Validating leave of absence in the 'Simple' and 'Claim' report - Registry setting 'Include Non-Chargeable Leaves in Client Ledger View' = "N"
Specific Setup:
- Registry Setting:
- The 'Include Non-Chargeable Leaves in Client Ledger View' registry setting is set to "N".
- Dictionary Update:
- Dictionary = Client
- Data Element = Type of Leave From
- Identify an existing non-billable leave type or create a new dictionary code/value for the non-billable leave type that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘No’. Note the type of leave.
- Identify an existing same day leave type or create a new dictionary code/value for the same day leave that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘No’. Note the type of leave.
- Identify an existing billable leave type or create a new dictionary code/value for the billable leave that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘Yes’. Note the type of leave.
- Guarantor/Payors:
- An existing guarantor is identified to assign to the client.
- Admission:
- A new client is admitted in the inpatient program. Note the client id/name, admission program, admission date.
- Financial Eligibility:
- The existing guarantor is assigned to the client. Note the Guarantor code/value.
- Service Codes:
- An existing service code is identified to render services to the client. Note the service code.
Steps
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting from the admission date.
- Open the 'Leaves' form.
- Place the client on a non-billable leave for desired days after the admission date. Note the date.
- Open the 'Return From Leaves' form.
- Return the client. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting after date of the return.
- Open the 'Leaves' form.
- Place the client on a billable leave for desired days after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client after desired days from the leave start date. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client after date of return.
- Open the 'Leaves' form.
- Place the client on a same day leave after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client on a same day after few hours from the leave start time.
- Open the 'Client Ledger' form for the client.
- Process the 'Simple' ledger for the client.
- Review the report.
- Verify the ledger does not include no-billable leaves in the report and does not display billable and/or same day leave in the report.
- Close the report.
- Process the 'Claim' ledger for the client.
- Verify the ledger does not include non-billable leaves, billable leaves and/or same day leave in the report.
- Close the report.
Scenario 4: Client Ledger - Validating leave of absence in the 'Simple' and 'Claim' report - Client with multiple episode - Registry setting 'Include Non-Chargeable Leaves in Client Ledger View' = "Y"
Specific Setup:
- Registry Setting:
- The 'Include Non-Chargeable Leaves in Client Ledger View' registry setting is set to "Y".
- Dictionary Update:
- Dictionary = Client
- Data Element = Type of Leave From
- Identify an existing non-billable leave type or create a new dictionary code/value for the non-billable leave type that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘No’. Note the type of leave.
- Identify an existing same day leave type or create a new dictionary code/value for the same day leave that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘No’. Note the type of leave.
- Identify an existing billable leave type or create a new dictionary code/value for the billable leave that has the defined extended dictionary value for ‘Chargeable Leave Y/N’ set to ‘Yes’. Note the type of leave.
- Guarantor/Payors:
- An existing guarantor is identified to assign to the client.
- Admission:
- A new client is admitted in two inpatient episodes. Note the client id/name, admission program, admission date.
- Financial Eligibility:
- The existing guarantor is assigned to the client. Note the Guarantor code/value.
- Service Codes:
- An existing room and board service code is identified to render services to the client. Note the service code.
Steps
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting from the admission date.
- Open the 'Leaves' form.
- Place the client on a non-billable leave for desired days after the admission date. Note the date.
- Open the 'Return From Leaves' form.
- Return the client. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting after date of the return.
- Open the 'Leaves' form.
- Place the client on a billable leave for desired days after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client after desired days from the leave start date. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client after date of return.
- Open the 'Leaves' form.
- Place the client on a same day leave after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client on a same day after few hours from the leave start time.
- Open the 'Client Ledger' form for the client.
- Process the 'Simple' ledger for the client.
- Review the report.
- Verify the ledger displays no-billable leaves along with the services rendered to the client in the report and does not display billable and/or same day leave in the report.
- Close the report.
- Process the 'Claim' ledger for the client.
- Verify the ledger displays non-billable leaves, billable leaves and/or same day leave in the report.
- Close the report.
- Open the 'Discharge' form.
- Discharge the client. Note the discharge date.
- Open the 'Admission' form for the same client.
- Admit the client in a new inpatient episode.
- Open the 'Financial Eligibility' form.
- Assign an existing guarantor to the second episode of the client. Note the guarantor id/name.
- Open the 'Client Charge Input' form.
- Render three days of the service to the client starting from the admission date.
- Open the 'Leaves' form.
- Place a client on a non-billable leave for desired days after 1 week from the admission date. Note the date.
- Open the 'Return From Leaves' form.
- Return the client. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client starting after date of the return.
- Open the 'Leaves' form.
- Place a client on a billable leave for desired days after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client after desired days from the leave start date. Note the date of return.
- Open the 'Client Charge Input' form.
- Render desired days of the service to the client after date of return.
- Open the 'Leaves' form.
- Place a client on a same day leave after last date of the service. Note the date.
- Open the 'Return From Leaves' form.
- Return the client on a same day after few hours from the leave start time.
- Open the 'Client Ledger' form for the client.
- Process the 'Simple' ledger for the client.
- Review the report.
- Verify the ledger displays no-billable leaves along with the services rendered to the client in the report and does not display billable and/or same day leave in the report.
- Close the report.
- Process the 'Claim' ledger for the client.
- Verify the ledger displays non-billable leaves, billable leaves and/or same day leave in the report.
- Close the report.
|
Topics
• Registry Settings
• Client Ledger
• NX
|
The 'User Permissions for Multiple Iteration Tables' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- User Permissions for Multiple Iteration Tables
- Cross Episode Financial Eligibility
- Family Financial Eligibility
- Managed Care Authorizations
- Managed Care Authorizations By Provider
- User Role Definition
- Change User Role ID
- User Merge
Scenario 1: Validate the 'Enable User Permissions for Multiple Iteration Tables' registry setting
Steps
- Access the 'Registry Settings' form.
- Enter "Enable User Permissions for Multiple Iteration Tables" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Validate the 'Registry Setting' field contains "Avatar PM->System Maintenance->System Definition->->->Enable User Permissions for Multiple Iteration Tables".
- Validate the 'Registry Setting Details' field contains: Selecting "Y" will add the form 'User Permissions for Multiple Iteration Tables'. This form allows users to assign permissions for adding, editing and deleting rows from multiple iteration tables. The following forms will allow user permissions to be set: 'Financial Eligibility' (Guarantor Selection), 'Financial Eligibility' (Customize Plan), 'Cross Episode Financial Eligibility' (Guarantor Selection),'Cross Episode Financial Eligibility' (Customize Plan), 'Family Financial Eligibility' (Guarantor Selection), 'Family Financial Eligibility' (Customize Plan), 'Family Financial Eligibility' (Guarantor Assignment), 'Managed Care Authorizations' (Managed Care Authorization Data), 'Managed Care Authorizations by Provider' (Managed Care Authorizations by Practitioner Data), and 'Family Registration' (Family Members). Selecting "N", will remove this form and all associated logic.
- Validate the default value is "N" in the 'Registry Setting Value' field.
- Enter "Y" in the 'Registry Setting Value' field.
- Click [Submit].
- Access the 'User Definition' form.
- Select the logged in user in the 'Select User' field.
- Select the "Forms and Tables" section.
- Click [Select Forms for User Access].
- Validate the 'User Permissions for Multiple Iteration Tables' form is available under PM and select it.
- Click [OK] and [Submit].
- Click [Refresh Forms].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Validate the form displays.
- Validate the 'User' field is displayed.
- Validate the 'User Role' field is displayed.
- Validate the 'Permissions Table' is displayed.
- Validate the 'Add/Edit/Delete Permission' field is displayed.
- Validate the 'Row Selection' field is displayed.
- Validate the 'Forms' field is displayed.
- Validate the 'Select Permission' field is displayed.
- Validate the 'Update Table' button is displayed.
- Close the form.
- Access the 'Registry Settings' form.
- Enter "Enable User Permissions for Multiple Iteration Tables" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Enter "N" in the 'Registry Setting Value' field.
- Click [Submit].
- Click [Refresh Forms].
- Validate the 'User Permissions for Multiple Iteration Tables' form is no longer available.
Scenario 2: User Permissions for Multiple Iteration Tables (User) - Financial Eligibility
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user is defined (User A) and is currently logged in.
- A client has existing rows in both the "Guarantor Selection" and "Customize Plan" sections of the 'Financial Eligibility' form (Client A).
Steps
Scenario 3: User Permissions for Multiple Iteration Tables (User) - Cross Episode Financial Eligibility
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user is defined (User A) and is currently logged in.
- A client has existing rows in both the "Guarantor Selection" and "Customize Plan" sections of the 'Cross Episode Financial Eligibility' form (Client A).
Steps
Scenario 4: User Permissions for Multiple Iteration Tables (User) - Family Financial Eligibility
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user is defined (User A) and is currently logged in.
- A family is defined in the 'Family Registration' form with family members added (Family A).
- "Family A" has an existing guarantor on file in 'Family Financial Eligibility' with a row defined in the 'Customize Plan' and 'Guarantor Assignment' sections.
Steps
Scenario 5: User Permissions for Multiple Iteration Tables (User) - Managed Care Authorizations
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user is defined (User A) and is currently logged in.
- A client has an existing record in the 'Managed Care Authorization' form with existing rows filed in the 'Managed Care Authorization History' table (Client A).
Steps
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Managed Care Authorizations (Managed Care Authorization Data)" in the 'Forms' field.
- Select "Add" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the permission just filed.
- Close the form.
- Select "Client A" and access the 'Managed Care Authorizations' form.
- Select the "Managed Care Authorization Data" section.
- Validate the ability to add new rows.
- Validate the ability to edit/delete rows added in the current session.
- Select an existing row filed in a previous session and click [Edit Selected Item].
- Validate a message is displayed stating: Cannot edit rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate all fields are disabled and read-only.
- Select an existing row filed in a previous session and click [Delete Selected Item].
- Validate a message is displayed stating: Cannot delete rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK].
- Populate any desired fields and click [Submit].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Edit" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Deselect "Add" in the 'Select Permissions' field.
- Select "Edit" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the updated permission.
- Close the form.
- Select "Client A" and access the 'Managed Care Authorizations' form.
- Select the "Managed Care Authorization Data" section.
- Click [Add New Item].
- Validate a message is displayed stating: Cannot add rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate a row has not been added.
- Select an existing row filed in a previous session and click [Delete Selected Item].
- Validate a message is displayed stating: Cannot delete rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK].
- Select an existing row filed in a previous session and click [Edit Selected Item].
- Update any desired fields and click [Submit].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Edit" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Deselect "Edit" in the 'Select Permissions' field.
- Select "Delete" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the updated permission.
- Close the form.
- Select "Client A" and access the 'Managed Care Authorizations' form.
- Select the "Managed Care Authorization Data" section.
- Click [Add New Item].
- Validate a message is displayed stating: Cannot add rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK].
- Select an existing row filed in a previous session and click [Edit Selected Item].
- Validate a message is displayed stating: Cannot edit rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate all fields are disabled and read-only.
- Select an existing row filed in a previous session and click [Delete Selected Item].
- Validate a message is displayed stating: Are you sure?
- Click [Yes] and validate the row is deleted from the 'Practitioner Authorization Data' table.
- Click [Submit].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Edit" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Deselect "Delete" in the 'Select Permissions' field.
- Select "None" in the 'Select Permissions' field. This means the user will not have permissions to add/edit/delete.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the updated permission.
- Close the form.
- Select "Client A" and access the 'Managed Care Authorizations' form.
- Select the "Managed Care Authorization Data" section.
- Click [Add New Item].
- Validate a message is displayed stating: Cannot add rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate a row has not been added.
- Select an existing row filed in a previous session and click [Edit Selected Item].
- Validate a message is displayed stating: Cannot edit rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate all fields are disabled and read-only.
- Select an existing row filed in a previous session and click [Delete Selected Item].
- Validate a message is displayed stating: Cannot delete rows because the User Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and close the form.
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Edit" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Deselect "None" in the 'Select Permissions' field.
- Select "Add", "Edit", and "Delete" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the updated permission.
- Close the form.
- Select "Client A" and access the 'Managed Care Authorizations' form.
- Select the "Managed Care Authorization Data" section.
- Validate the ability to add new rows and edit/delete new and existing rows.
- Click [Submit].
Scenario 6: User Permissions for Multiple Iteration Tables (User) - Managed Care Authorizations By Provider
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user is defined (User A) and is currently logged in.
- A client has an existing record in the 'Managed Care Authorization By Provider' form with existing rows filed in the 'Practitioner Authorization Data' table (Client A).
Steps
Scenario 7: User Permissions for Multiple Iteration Tables (User) - Family Registration
Scenario 8: User Permissions for Multiple Iteration Tables (User Role) - Financial Eligibility
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user role is defined in 'User Role Definition' (PermissionsROLE is used for testing).
- The logged in user is associated to the "PermissionsROLE" user role.
- A client has existing rows in both the "Guarantor Selection" and "Customize Plan" sections of the 'Financial Eligibility' form (Client A).
Steps
Scenario 9: User Permissions for Multiple Iteration Tables (User Role) - Cross Episode Financial Eligibility
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user role is defined in 'User Role Definition' (PermissionsROLE is used for testing).
- The logged in user is associated to the "PermissionsROLE" user role.
- A client has existing rows in both the "Guarantor Selection" and "Customize Plan" sections of the 'Cross Episode Financial Eligibility' form (Client A).
Steps
Scenario 10: User Permissions for Multiple Iteration Tables (User Role) - Family Financial Eligibility
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user role is defined in 'User Role Definition' (PermissionsROLE is used for testing).
- The logged in user is associated to the "PermissionsROLE" user role.
- A family is defined in the 'Family Registration' form with family members added (Family A).
- "Family A" has an existing guarantor on file in 'Family Financial Eligibility' with a row defined in the 'Customize Plan' and 'Guarantor Assignment' sections.
Steps
Scenario 11: User Permissions for Multiple Iteration Tables (User Role) - Managed Care Authorizations
Scenario 12: User Permissions for Multiple Iteration Tables (User Role) - Managed Care Authorizations By Provider
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user role is defined in 'User Role Definition' (PermissionsROLE is used for testing).
- The logged in user is associated to the "PermissionsROLE" user role.
- A client has an existing record in the 'Managed Care Authorization By Provider' form with existing rows filed in the 'Practitioner Authorization Data' table (Client A).
Steps
Scenario 13: User Permissions for Multiple Iteration Tables (User Role) - Family Registration
Scenario 14: User Permissions for Multiple Iteration Tables - Change User Role ID
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
Steps
- Access the 'User Role Definition' form.
- Enter "PermissionsNEW" in the 'User Role ID' field.
- Populate all required fields.
- Click [Submit] and [No].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "PermissionsNEW" in the 'User Role' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Family Registration (Family Members)" in the 'Forms' field.
- Select "Add" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the permission added.
- Close the form.
- Access the 'Change User Role ID' form.
- Select "PermissionsNEW" in the 'User Role' field.
- Validate the 'Current User Role ID' field contains "PermissionsNEW".
- Enter "PermissionsTEST" in the 'New User Role ID' field.
- Click [Submit].
- Validate a message is displayed stating "Change User Role ID has completed. Do you wish to return to form?"
- Click [No].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Validate the 'User Role' field contains "PermissionsTEST" and no longer contains "PermissionsNEW".
- Select "PermissionsTEST" in the 'User Role' field.
- Validate the 'Permissions Table' contains the permission filed in the previous steps indicating the user role ID has been updated successfully.
- Close the form.
Scenario 15: User Permissions for Multiple Iteration Tables - Change User ID
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
Steps
- Access the 'User Definition' form.
- Enter "TestPermissions1" in the 'User ID' field.
- Enter "Test Permissions 1" in the 'User Description' field.
- Select "Yes" in the 'Is this user a system administrator' field.
- Select "No" in the 'Associate User with a User Role' field.
- Select the "Forms and Tables" section.
- Select the desired system codes in the 'System Code(s)' field.
- Click [Submit] and [No].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "TestPermissions1" in the 'User' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Financial Eligibility (Guarantor Selection)" in the 'Forms' field.
- Select "Add" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the permission added.
- Close the form.
- Access the 'Change User ID' form.
- Select "Test Permissions 1 (TestPermissions1)" in the 'User' field.
- Enter "TestPermissions" in the 'New User ID' field.
- Validate the 'Old User ID' field contains "TestPermissions1".
- Click [Submit].
- Validate a message is displayed stating "Change User ID has completed. Do you wish to return to form?"
- Click [No].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Validate the 'User' field contains "TestPermissions" and no longer contains "TestPermissions1".
- Select "TestPermissions" in the 'User' field.
- Validate the 'Permissions Table' contains the permission filed in the previous steps indicating the user ID has updated successfully.
- Close the form.
Scenario 16: User Permissions for Multiple Iteration Tables - User Merge
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
Steps
- Access the 'User Definition' form.
- Enter "Merge1" in the 'User ID' field.
- Enter "Merge Test 1" in the 'User Description' field.
- Select "Yes" in the 'Is this user a system administrator' field.
- Select "No" in the 'Associate User with a User Role' field.
- Select the "Forms and Tables" section.
- Select the desired system code(s) in the 'System Code(s)' field.
- Click [Submit] and [No].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "Merge1" in the 'User' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Financial Eligibility (Guarantor Selection)' in the 'Forms' field.
- Select "None" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the permission added.
- Close the form.
- Access the 'User Merge' form.
- Select "New" in the 'Merge Into New Or Existing User' field.
- Enter "Merge2" in the 'New User ID' field.
- Enter "Merge Test 2" in the 'New User Description' field.
- Select "Merge Test 1 (Merge1)" in the 'Source User 1' field.
- Click [Submit] and [No].
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Validate the 'User' field contains "Merge2" and no longer contains "Merge1".
- Select "Merge2" in the 'User' field.
- Validate the 'Permissions Table' contains the permission filed in the previous steps indicating the user permissions have been merged successfully.
- Close the form.
Scenario 17: User Permissions for Multiple Iteration Tables - validate the 'mult_iter_permission_user' table
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user is defined and currently logged in (User A).
- "User A" has access to the 'mult_iter_permission_user' table in 'User Definition'.
Steps
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Financial Eligibility (Guarantor Selection)" in the 'Forms' field.
- Select "Add" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the added permission.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Select the PM namespace.
- Create a report using the 'mult_iter_permission_user' table.
- Validate there is a row displayed for the permission added in the previous steps.
- Validate the 'ID' field contains a unique identifier for the user (ex. 98||UserA||1).
- Validate the 'forms' field contains "1".
- Validate the 'forms_value' field contains "Financial Eligibility (Guarantor Selection)".
- Validate the 'status' field contains "1".
- Validate the 'status_value' field contains "Add".
- Validate the 'user' field contains "PermissionsTEST".
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Edit" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Validate "Add" is selected in the 'Select Permissions' field.
- Select "Delete" and "Edit" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the updated permission.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Refresh the report using the 'mult_iter_permission_user' table.
- Validate the permission updated in the previous steps is displayed.
- Validate the 'status' field contains "1&3&2".
- Validate the 'status_value' field contains "Add, Delete, Edit".
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "User A" in the 'User' field.
- Select "Delete" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' no longer contains the permission.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Refresh the report using the 'mult_iter_permission_user' table.
- Validate a row is no longer displayed for the permission since it has been deleted.
- Close the report.
Scenario 18: User Permissions for Multiple Iteration Tables - validate the 'mult_iter_permission_role' table
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user role is defined (PermissionsROLE is used for testing).
- The logged in user is associated to the "PermissionsROLE" user role and has access to the 'mult_iter_permission_role' table in 'User Role Definition'.
Steps
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "PermissionsROLE" in the 'User Role' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Financial Eligibility (Guarantor Selection)" in the 'Forms' field.
- Select "Add" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the added permission.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Select the PM namespace.
- Create a report using the 'mult_iter_permission_role' table.
- Validate there is a row displayed for the permission added in the previous steps.
- Validate the 'ID' field contains a unique identifier for the user role (ex. 98||PermissionsROLE||1).
- Validate the 'forms' field contains "1".
- Validate the 'forms_value' field contains "Financial Eligibility (Guarantor Selection)".
- Validate the 'status' field contains "1".
- Validate the 'status_value' field contains "Add".
- Validate the 'user_roles' field contains "PermissionsROLE".
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "PermissionsROLE" in the 'User Role' field.
- Select "Edit" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Validate "Add" is selected in the 'Select Permissions' field.
- Select "Delete" and "Edit" in the 'Select Permissions' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' contains the updated permission.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Refresh the report using the 'mult_iter_permission_role' table.
- Validate the permission updated in the previous steps is displayed.
- Validate the 'status' field contains "1&2&3".
- Validate the 'status_value' field contains "Add, Edit, Delete".
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "PermissionsROLE" in the 'User Role' field.
- Select "Delete" in the 'Add/Edit/Delete Permission' field.
- Select the permission filed in the previous steps in the 'Row Selection' field.
- Click [Update Table].
- Validate a message is displayed stating "Filed Successfully".
- Click [OK] and validate the 'Permissions Table' no longer contains the permission.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Refresh the report using the 'mult_iter_permission_role' table.
- Validate a row is no longer displayed for the permission since it has been deleted.
- Close the report.
Scenario 19: User Permissions for Multiple Iteration Tables - Validate user permissions override user role permissions when both are defined
Specific Setup:
- The 'Enable User Permissions for Multiple Iteration Tables' registry setting is set to "Y".
- A user role is defined in 'User Role Definition' (PermissionsROLE is used for testing).
- A user is defined in the 'User Definition' form (User A) and is associated to the "PermissionsROLE" user role.
- Must be logged in as "User A".
- A family is defined in the 'Family Registration' form with family members added (Family A).
Steps
- Access the 'User Permissions for Multiple Iteration Tables' form.
- Select "PermissionsROLE" in the 'User Role' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Family Registration (Family Members)" in the 'Forms' field.
- Select "Add" in the 'Select Permission' field.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the permission added for the user role.
- Select "User A" in the 'User' field.
- Select "Add" in the 'Add/Edit/Delete Permission' field.
- Select "Family Registration (Family Members)" in the 'Forms' field.
- Select "None" in the 'Select Permission' field.
- Click [Update Table].
- Validate a message is displayed stating: Filed Successfully!
- Click [OK] and validate the 'Permissions Table' contains the permission added for "User A".
- Close the form.
- Access the 'Family Registration' form for "Family A".
- Select the "Family Members" section.
- Click [Add New Item].
- Validate a message is displayed stating: Cannot add rows because the User Role Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate a row has not been added.
- Select an existing row filed in a previous session and click [Edit Selected Item].
- Validate a message is displayed stating: Cannot edit rows because the User Role Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and validate all fields are disabled and read-only.
- Select an existing row filed in a previous session and click [Delete Selected Item].
- Validate a message is displayed stating: Cannot delete rows because the User Role Permissions does not allow it. Permissions are set in the 'User Permissions for Multiple Iteration Tables' form.
- Click [OK] and close the form.
|
Topics
• Registry Settings
• User Permissions for Multiple Iteration Tables
• Financial Eligibility
• NX
• Managed Care Authorizations
• Family Registration
• Change User Role Id
• Change User ID
• User Merge
• Query/Reporting
|
'Practitioner Enrollment' Electronic Visit Verification Fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Practitioner Enrollment
- Practitioner Enrollment (Brief)
Scenario 1: 'ClinicianServices' Web Service - Verification Of 'putClinicianCreation' Filing
Specific Setup:
- Application utilizing the Avatar PM 'ClinicianServices' web service
Steps
- Using Avatar PM 'ClinicianServices' web service, submit request to 'putClinicianCreation' method to create new Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record), including values for 'StaffEVVID' and 'OfficeLocationID' fields/segments.
- Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm new Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Staff EVV ID' and 'Office Location ID' field values (as well as values assigned for Avatar MSO 'Performing Provider' and 'Performing Provider Registration' practitioner association/link fields if enabled).
Scenario 2: 'ClinicianServices' Web Service - Verification Of 'putClinicianUpdate' Filing
Specific Setup:
- Application utilizing the Avatar PM 'ClinicianServices' web service
Steps
- Using Avatar PM 'ClinicianServices' web service, submit request to 'putClinicianUpdate' method to edit/update Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record if linked), including values for 'StaffEVVID' and 'OfficeLocationID' fields/segments.
- Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including 'Staff EVV ID' and 'Office Location ID' field values.
Scenario 3: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianCreation' Filing
Specific Setup:
- Application utilizing the Avatar PM 'ClinicianServicesV2' web service
Steps
- Using Avatar PM 'ClinicianServicesV2' web service, submit request to 'putClinicianCreation' method to create new Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record), including values for 'StaffEVVID' and 'OfficeLocationID' fields/segments.
- Confirm 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm new Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Staff EVV ID' and 'Office Location ID' field values (as well as values assigned for Avatar MSO 'Performing Provider' and 'Performing Provider Registration' practitioner association/link fields if enabled).
Scenario 4: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianUpdate' Filing
Specific Setup:
- Application utilizing the Avatar PM 'ClinicianServicesV2' web service
Steps
- Using Avatar PM 'ClinicianServicesV2' web service, submit request to 'putClinicianUpdate' method to edit/update Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record if linked), including values for 'StaffEVVID' and 'OfficeLocationID' fields/segments.
- Confirm 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
- Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
- Confirm 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
- Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
- Confirm 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
- Example: " <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including 'Staff EVV ID' and 'Office Location ID' field values.
Scenario 5: 'Practitioner Enrollment' - Form Verification
Specific Setup:
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Practitioner Enrollment' form (under 'Avatar PM / Practitioner / Practitioner Registration' menu path).
- Enter/select existing Practitioner Enrollment record for viewing/update (or click 'New Staff' button for new Practitioner Enrollment entry).
- Ensure new input fields 'Staff EVV ID' and 'Office Location ID' are added to 'Practitioner Enrollment' form (in 'Practitioner Enrollment' first/primary form section).
- Enter value for 'Staff EVV ID' field (up to 30 characters).
- Enter value for 'Office Location ID' field (up to 30 characters).
- Enter/select values for all other form fields as required/desired.
- Click 'Submit' button to file 'Practitioner Enrollment' form/record.
- Re-open Avatar PM 'Practitioner Enrollment' form and select same/previously filed Practitioner Enrollment record for view/update.
- Ensure that previously entered/filed values for 'Staff EVV ID' and 'Office Location ID' fields are present/displayed in form for selected record.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.staff_enrollment_history', ensure that fields 'Staff_EVV_ID' and 'office_location_ID' are available, and contain values filed for 'Staff EVV ID' and 'Office Location ID' (respectively) via Avatar PM 'Practitioner Enrollment' form.
Scenario 6: 'Practitioner Enrollment (Brief)' - Form Verification
Specific Setup:
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Practitioner Enrollment (Brief)' form (under 'Avatar PM / Practitioner / Practitioner Registration' menu path).
- Enter/select existing Practitioner Enrollment record for viewing/update (or click 'New Staff' button for new Practitioner Enrollment entry).
- Ensure new input fields 'Staff EVV ID' and 'Office Location ID' are added to 'Practitioner Enrollment (Brief)' form (in 'Practitioner Enrollment (Brief)' first/primary form section).
- Enter value for 'Staff EVV ID' field (up to 30 characters).
- Enter value for 'Office Location ID' field (up to 30 characters).
- Enter/select values for all other form fields as required/desired.
- Click 'Submit' button to file 'Practitioner Enrollment (Brief)' form/record.
- Re-open Avatar PM 'Practitioner Enrollment (Brief)' form and select same/previously filed Practitioner Enrollment record for view/update.
- Ensure that previously entered/filed values for 'Staff EVV ID' and 'Office Location ID' fields are present/displayed in form for selected record.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.staff_enrollment_history', ensure that fields 'Staff_EVV_ID' and 'office_location_ID' are available, and contain values filed for 'Staff EVV ID' and 'Office Location ID' (respectively) via Avatar PM 'Practitioner Enrollment (Brief)' form.
Scenario 7: 'PractitionerRegister' Web Service - Verification Of 'PractitionerRegister' Filing
Specific Setup:
- Application utilizing the Avatar PM 'PractitionerRegister' web service
Steps
- Using Avatar PM 'PractitionerRegister' web service, submit request to 'PractitionerRegister' method to create new Avatar PM Practitioner Enrollment, including values for 'StaffEVVID' and 'OfficeLocationID' fields/segments.
- Confirm 'PractitionerRegister' web service responds with confirmation data/ID on successful filing of 'PractitionerRegister' method.
- Example:"<Confirmation>Unique ID : 000056</Confirmation>"
- Confirm 'PractitionerRegister' web service responds with confirmation message on successful filing of 'PractitionerRegister' method.
- Example:"<Message>Practitioner Enrollment web service has been filed successfully.</Message>"
- Confirm 'PractitionerRegister' web service responds with successful status value on successful filing of 'PractitionerRegister' method.
- Example:" <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm new Practitioner/Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Staff EVV ID' and 'Office Location ID' field values.
Scenario 8: 'PractitionerRegister' Web Service - Verification Of 'EditPractitionerRegister' Filing
Specific Setup:
- Application utilizing the Avatar PM 'PractitionerRegister' web service
Steps
- Using Avatar PM 'PractitionerRegister' web service, submit request to 'EditPractitionerRegister' method to edit/update Avatar PM Practitioner Enrollment, including values for 'StaffEVVID' and 'OfficeLocationID' fields/segments.
- Confirm 'PractitionerRegister' web service responds with confirmation data/ID on successful filing of 'EditPractitionerRegister' method.
- Example:"<Confirmation>Unique ID : 000056</Confirmation>"
- Confirm 'PractitionerRegister' web service responds with confirmation message on successful filing of 'EditPractitionerRegister' method.
- Example:"<Message>Practitioner Enrollment web service has been filed successfully.</Message>"
- Confirm 'PractitionerRegister' web service responds with successful status value on successful filing of 'EditPractitionerRegister' method.
- Example:" <Status>1</Status>"
- Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
- Confirm Practitioner/Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including 'Staff EVV ID' and 'Office Location ID' field values.
|
Topics
• Practitioner
• Web Services
• Practitioner Enrollment
• NX
|
| |