Site Specific Section Modeling - Fast Service Entry Submission
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- Admission (Outpatient)
- Diagnosis
- Dynamic Form - Pre-Display Confirmation
- Financial Eligibility
- CPT Code Definition (PM)
- CPT Code Definition (MSO)
- Revenue Code Definition (PM)
- Revenue Code Definition (MSO)
- Service Codes
- Plan Definition
- Funding Source Registration
- Applying Contracting Provider
- Provider Fee Definition
- Registry Settings (PM)
- MSO to Parent System Integration Mapping
- Claim Processing (CMS 1500)
- Close Batch
- Dynamic Form - Site Specific Section Modeling (CWS)
- Site Specific Section Modeling (MSO)
- Fast Service Entry
Scenario 1: 'Claim Processing...' forms and functions - Verification of 'Explanation Of Coverage' value for 'Pended' Service Authorization, and verifying new batch not created when batch is closed
Specific Setup:
- Client record with Service Authorization(s) where 'Current Authorization Status' value is 'Pending'
- One or more claim(s)/service(s) for adjudication where 'Pending' status Service Authorization is selected/associated to service
Steps
- Open Avatar MSO 'Claim Processing...' form ('Claim Processing (CMS 1500)', 'Claim Processing (UB-04)' and/or 'Fast Service Entry' forms).
- Select claims processing batch for service entry/edit.
- Open existing claim or create new claim for service entry/edit.
- Set value for 'Member Name or ID' and 'Provider' in claim level section (if adding new claim/services).
- Navigate to 'Service Detail' section of form.
- Click 'Add New Item' button (or select existing service and click 'Edit Selected Item' button).
- Enter/select 'Date of Service', 'Procedure Code', 'Total Charge' and 'Service Units' field values.
- Click 'Display Valid Authorizations' button and select Service Authorization (or directly enter value in 'Authorization Number' field).
- In case where 'Current Authorization Status' value is 'Pending' for selected/associated Service Authorization record - ensure that 'Claim Status' value is set to 'Pending' for service.
- In case where 'Current Authorization Status' value is 'Pending' for selected/associated Service Authorization record - ensure that 'Explanation Of Coverage' field for service includes value 'The service was pended for the following reason: Authorization is pending'.
- Click [Enter Third Party Adjudication Data].
- Create a new row with desired data, and if desired click [View] and create a new row with desired data. Save the rows.
- Click [Submit].
- Close the batch and validate that a new pended batch is created.
- Repeat steps 1-12 and validate that the ‘Third Party Adjudication Data’ was copied forward.
- Click [Submit].
- Close the batch and validate that a new pended batch is created.
- Repeat steps 1-12 and validate that the ‘Third Party Adjudication Data’ was copied forward.
Scenario 2: Avatar MSO 'Site Specific Section Modeling' - 'Fast Service Entry Submission' - opening prompt section.
Specific Setup:
- Site Specific Section Modeling for MSO:
- Select the ‘MSOBAT185SUBMISSION (Fast Service Entry Submission) Fast Service Detail’ item in the dropdown list.
- Click [OK].
- Select ‘Prompt Definition’ section.
- If desired, add a new prompt and customize the label or customize the label of an existing prompt.
- Click [Submit].
- Refresh the forms.
Steps
- Open ‘Fast Service Entry’.
- Select the ‘Fast Service Detail’ section.
- Validate that the prompt that was added or changed exists on the form.
- Close the form.
- Open ‘Site Specific Section Modeling’ for MSO.
- Select the ‘MSOBAT185OVERRIDE (Fast Service Entry) Fast Service Detail’ item in the dropdown list.
- Click [OK].
- Select ‘Prompt Definition’ section.
- Validate that the prompt added or changed in Setup displays in the table.
- Select the prompt and click [Delete Selected Item].
- Click [Yes] on the ‘Confirm’ message.
- Click [Submit].
- Refresh the forms.
- Open ‘Fast Service Entry’.
- Select the ‘Fast Service Detail’ section.
- Validate that the prompt does not exist.
Claim Processing - Third Party Adjudication Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- Admission (Outpatient)
- Diagnosis
- Dynamic Form - Pre-Display Confirmation
- Financial Eligibility
- CPT Code Definition (PM)
- CPT Code Definition (MSO)
- Revenue Code Definition (PM)
- Revenue Code Definition (MSO)
- Service Codes
- Plan Definition
- Funding Source Registration
- Applying Contracting Provider
- Provider Fee Definition
- Registry Settings (PM)
- MSO to Parent System Integration Mapping
- Claim Processing (CMS 1500)
- Close Batch
- Dynamic Form - Site Specific Section Modeling (CWS)
- Site Specific Section Modeling (MSO)
- Fast Service Entry
Scenario 1: 'Claim Processing...' forms and functions - Verification of 'Explanation Of Coverage' value for 'Pended' Service Authorization, and verifying new batch not created when batch is closed
Specific Setup:
- Client record with Service Authorization(s) where 'Current Authorization Status' value is 'Pending'
- One or more claim(s)/service(s) for adjudication where 'Pending' status Service Authorization is selected/associated to service
Steps
- Open Avatar MSO 'Claim Processing...' form ('Claim Processing (CMS 1500)', 'Claim Processing (UB-04)' and/or 'Fast Service Entry' forms).
- Select claims processing batch for service entry/edit.
- Open existing claim or create new claim for service entry/edit.
- Set value for 'Member Name or ID' and 'Provider' in claim level section (if adding new claim/services).
- Navigate to 'Service Detail' section of form.
- Click 'Add New Item' button (or select existing service and click 'Edit Selected Item' button).
- Enter/select 'Date of Service', 'Procedure Code', 'Total Charge' and 'Service Units' field values.
- Click 'Display Valid Authorizations' button and select Service Authorization (or directly enter value in 'Authorization Number' field).
- In case where 'Current Authorization Status' value is 'Pending' for selected/associated Service Authorization record - ensure that 'Claim Status' value is set to 'Pending' for service.
- In case where 'Current Authorization Status' value is 'Pending' for selected/associated Service Authorization record - ensure that 'Explanation Of Coverage' field for service includes value 'The service was pended for the following reason: Authorization is pending'.
- Click [Enter Third Party Adjudication Data].
- Create a new row with desired data, and if desired click [View] and create a new row with desired data. Save the rows.
- Click [Submit].
- Close the batch and validate that a new pended batch is created.
- Repeat steps 1-12 and validate that the ‘Third Party Adjudication Data’ was copied forward.
- Click [Submit].
- Close the batch and validate that a new pended batch is created.
- Repeat steps 1-12 and validate that the ‘Third Party Adjudication Data’ was copied forward.
Scenario 2: Avatar MSO 'Site Specific Section Modeling' - 'Fast Service Entry Submission' - opening prompt section.
Specific Setup:
- Site Specific Section Modeling for MSO:
- Select the ‘MSOBAT185SUBMISSION (Fast Service Entry Submission) Fast Service Detail’ item in the dropdown list.
- Click [OK].
- Select ‘Prompt Definition’ section.
- If desired, add a new prompt and customize the label or customize the label of an existing prompt.
- Click [Submit].
- Refresh the forms.
Steps
- Open ‘Fast Service Entry’.
- Select the ‘Fast Service Detail’ section.
- Validate that the prompt that was added or changed exists on the form.
- Close the form.
- Open ‘Site Specific Section Modeling’ for MSO.
- Select the ‘MSOBAT185OVERRIDE (Fast Service Entry) Fast Service Detail’ item in the dropdown list.
- Click [OK].
- Select ‘Prompt Definition’ section.
- Validate that the prompt added or changed in Setup displays in the table.
- Select the prompt and click [Delete Selected Item].
- Click [Yes] on the ‘Confirm’ message.
- Click [Submit].
- Refresh the forms.
- Open ‘Fast Service Entry’.
- Select the ‘Fast Service Detail’ section.
- Validate that the prompt does not exist.
|
Topics
• Claims Processing
• Service Authorizations
• Site Specific Section Modeling
• NX
|
'Provider File Attach' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'Provider File Attach' - Form Verification
Specific Setup:
- Document Management Configuration must be defined for Cache Server or Perceptive (via Avatar PM / RADplus Utilities 'Document Management Defaults' form)
- Dictionary Codes may optionally be defined for 'Other Tabled Files' Data Element '(70007) Document Type' (via Avatar MSO 'Dictionary Update' form)
- One or more .PDF (Adobe Portable Document Format) and/or .TIF (Tagged Image File Format) files for Provider File Attach upload/storage
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar MSO 'Provider File Attach' form (under 'Avatar MSO / Provider Management' menu).
- Enter/select 'Member ID' value.
- Enter/select 'Provider' value.
- In 'File Type' field, ensure the following selections are available:
- 'Authorization' (will link File Attachment to a specific Avatar MSO Service Authorization record for selected Provider)
- 'Provider' (will link File Attachment to selected Provider)
- 'Other' (will link File Attachment to selected Provider)
- Select 'File Type' value.
- If 'Authorization' is selected in 'File Type' field, ensure that 'Authorization' selection field is enabled, and includes only Avatar MSO Service Authorization records for selected Provider; select 'Authorization' field if applicable.
- Select 'Document Type' value (optional field).
- Enter 'Comments' value if desired (optional field).
- Click 'Upload File' button, and select file for Provider Attachment upload/storage.
- On completion of File Attachment upload, ensure 'File Name' field is populated with uploaded file name.
- Click 'Store File' field to store File Attachment in Avatar MSO; ensure user is presented with confirmation dialog noting 'File successfully created'.
- Click 'OK' button to return to 'Provider File Attach' form.
- Select 'File Type' value for previously uploaded/stored File Attachment.
- Ensure uploaded/stored File Attachment files are listed/available for selection in the 'Existing Files' field; select file in 'Existing Files' field.
- Ensure that 'Comment History' field displays entered/updated 'Comments' field entries for selected file (with username and date/timestamp associated to each 'Comments' entry).
- Example:
- "Comment 1 AVATAR USERNAME 1 2022-04-21 04:19PM"
- Enter additional/new 'Comments' field data for selected File Attachment.
- Click 'Update Comments' button to store additional/new 'Comments' field data for selected File Attachment; ensure user is presented with confirmation dialog noting 'Comments Successfully updated'.
- Click 'OK' button to return to 'Provider File Attach' form.
- Select 'File Type' value for previously uploaded/stored File Attachment.
- Select uploaded/stored File Attachment in 'Existing Files' field.
- Ensure that 'Comment History' field displays all previously entered/updated 'Comments' field entries for selected file (with username and date/timestamp associated to each 'Comments' entry).
- Example:
- "Comment 2 AVATAR USERNAME 2 2022-04-22 01:35PM / Comment 1 AVATAR USERNAME 1 2022-04-21 04:19PM"
- Select 'File Type' value.
- Click 'Upload File' button, and select file for Provider Attachment upload/storage - selecting file with same name as previously uploaded/stored File Attachment.
- If file with same name as previously uploaded/stored File Attachment (for same Member ID/client) is selected, ensure user is presented with error dialog noting 'File already exists on the server' on clicking 'Store File' button (and File Attachment is disallowed).
- Select 'File Type' value for previously uploaded/stored File Attachment.
- Select uploaded/stored File Attachment file in 'Existing Files' field.
- Click 'Delete File' button to delete File Attachment.
- Ensure user is presented with Delete File confirmation dialog noting 'Are you sure you want to delete this file?'; click 'Yes' button to confirm file deletion.
- Ensure user is presented with Delete File confirmation dialog noting 'File deleted successfully'; click 'OK' button to return to 'Provider File Attach' form.
- Select 'File Type' value for previously uploaded/stored File Attachment.
- Ensure deleted File Attachment files are not listed/not available for selection in the 'Existing Files' field.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar MSO SQL table 'SYSTEM.file_attach_object', ensure that all uploaded/stored File Attachment files are present in SQL table data (one row per File Attachment).
- In Avatar MSO SQL table 'SYSTEM.file_attach_comments', ensure that all entered/updated 'Comments' field entries for File Attachment are present in SQL table data (one row per 'Comments' entry for File Attachment).
Avatar MSO 'Provider File Attach' Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- View Definition
- NX View Definition
- Provider File Attach
- Provider File Attach Widget
Scenario 1: 'Provider File Attach' Widget - Widget Display Verification
Specific Setup:
- Document Management Configuration must be defined for Cache Server or Perceptive (via Avatar PM / RADplus Utilities 'Document Management Defaults' form)
- 'Provider File Attach' Widget must be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
- One or more .PDF (Adobe Portable Document Format) and/or .TIF (Tagged Image File Format) files uploaded/stored via Avatar MSO 'Provider File Attach' form
Steps
- Open 'View Definition' form (under 'Avatar PM / RADplus Utilities / Widget Management' menu).
- Click 'Select View' button and select View Definition for update (or select 'Add New View' for new View Definition entry).
- Click 'Launch View Designer' button.
- In 'View Definition' form View Designer, ensure that Avatar MSO 'Provider File Attach' Widget is available for assignment (under 'Client' category).
- Select/add Avatar MSO 'Provider File Attach' Widget to View; click 'Submit' button to save View Designer layout, and click 'Submit' button to file 'View Definition' form.
- Navigate/select Home View, Chart View or Client Dashboard View where Avatar MSO 'Provider File Attach' Widget is assigned/present.
- Ensure that the 'Provider File Attach' Widget displays all uploaded/stored File Attachment files for selected/currently active Member ID/Client (one row in Widget display per File Attachment).
- Ensure that the 'Provider File Attach' Widget includes the following columns/information for each File Attachment row for selected/currently active Member ID/Client:
- 'View' button
- This button will open the selected .PDF or .TIF File Attachment file in the Console Widget Viewer
- 'Provider' display
- 'Document Name' display
- 'Date' display
- 'Authorization Number' display
- If applicable/value present, otherwise blank
- 'Document Type' display
- If applicable/value present, otherwise 'No Entry'
Scenario 2: 'Provider File Attach' Widget - Verification of File Attachment Display in 'Console Widget Viewer'
Specific Setup:
- Avatar PM/RADplus Registry Setting 'Enable Console Widgets/Views' must be enabled
- Document Management Configuration must be defined for Cache Server or Perceptive (via Avatar PM / RADplus Utilities 'Document Management Defaults' form)
- Avatar MSO 'Provider File Attach' Widget must be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
- Avatar NX/myAvatar 'Console Widget Viewer' must be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
- One or more .PDF (Adobe Portable Document Format) and/or .TIF (Tagged Image File Format) files uploaded/stored via Avatar MSO 'Provider File Attach' form
Steps
- Navigate/select Home View, Chart View or Client Dashboard View where Avatar MSO 'Provider File Attach' Widget and Avatar NX/myAvatar 'Console Widget Viewer' are assigned/present.
- Ensure that the 'Provider File Attach' Widget displays all uploaded/stored File Attachment files for selected/currently active Member ID/Client (one row in Widget display per File Attachment).
- Click 'View' button in 'Provider File Attach' Widget to view selected File Attachment.
- Ensure that selected .PDF or .TIF File Attachment image is opened for display in Avatar NX/myAvatar 'Console Widget Viewer'.
- Ensure multiple File Attachments may be opened/displayed in Avatar NX/myAvatar 'Console Widget Viewer' from 'Provider File Attach' Widget simultaneously.
- Ensure File Attachment images may be closed within Avatar NX/myAvatar 'Console Widget Viewer' (by closing individual files/tabs within viewer, or use of the 'Close All' button).
|
Topics
• NX
• Provider File Attach
• Widgets
• Console Widget
|
Avatar MSO 'Claim Acknowledgement (277CA) File' Form/Function
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Claim Acknowledgement (277CA) File
- Import/Export File Configuration
- Claim Processing Automation
- 837 Health Care Claim Professional
- 837 Health Care Claim Institutional
Scenario 1: 'Claim Acknowledgement (277CA) File' - Verification of Claim Acknowledgement File Creation
Specific Setup:
- File path for 277CA Claim Acknowledgement file creation must be defined in the 'Output Directory' field for system (via Avatar MSO 'Set System Defaults' or 'Import/Export File Configuration' form)
- Avatar MSO Claims Processing Batch(es) may optionally be set to automatically close following 837 posting (via Avatar 'Claim Processing Automation' form)
- 277CA Claim Acknowledgment file may optionally be enabled for automatic generation (via Avatar MSO 'Import/Export File Configuration' form)
- 837 Professional and/or Institutional format inbound file(s) for compilation/posting, including one or more 'Pending' Claim Status service(s)
Steps
- Using Avatar MSO '837 Health Care Claim Professional' and/or '837 Health Care Claim Institutional' forms (or via Avatar MSO automated 837 file processing), load/compile/post inbound 837 file(s) containing one or more valid claim(s) where Claim Status for one or more service(s) is 'Pending'.
- Avatar MSO Claims Processing batch(es) created via inbound 837 file posting may be 'Open' or 'Closed' status, including batches closed automatically via 'Claim Processing Automation' functionality.
- Open the Avatar MSO 'Claim Acknowledgement (277CA) File' form.
- 277CA file generation/content review may also be confirmed directly in system output directory where automatic 277CA file generation is enabled.
- Select 'Create File On Server' in 'Options' field.
- Select 'Submission Type' field value ('Institutional' or 'Professional').
- Select 837 file for Claim Acknowledgement (277CA) file creation.
- Click 'Process' button.
- Ensure that for selected 837 file, Claim Acknowledgement (277CA) file is created on server in defined directory.
- This may be confirmed via the 'Claim Acknowledgement (277CA) File' form 'Run Report' or 'Dump File' options, and/or by reviewing files in 277CA output directory.
- Select 'Dump File' in 'Options' field.
- Select 'Submission Type' field value ('Institutional' or 'Professional').
- Select 837 file for Claim Acknowledgement (277CA) file review.
- Click 'Process' button.
- In 277CA Claim Acknowledgement file(s) for successfully posted 837 Professional and/or Institutional inbound claims including one or more 'Pending' Claim Status service(s), ensure that claim/service(s) is/are reported with 'Accepted' status (including case where 837 Claims Processing batch containing 'Pending' status service is automatically closed following 837 posting).
- Examples:
- 'STC*A2:20**WQ*180~'
- 'STC*A2:20*20220516*WQ*60~'
- 277CA file content review may also be confirmed directly in system output directory by opening/reviewing file(s).
|
Topics
• 837 Health Care Claim Professional
• Claims Processing
• 837 Health Care Claim Institutional
|
| |