Web Service - WEBSVC.AppointmentScheduling.CLS
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- SOAPUI - AppointmentSchedulingV2
- Client Ledger
- SOAPUI - AddAppointment
Scenario 1: Client Charge Input - Validate the 'FileClientChargeInputICD10' web service for the quoted character
Specific Setup:
- Guarantors/Payors:
- An existing guarantor is identified to be used. Note the guarantor code/name.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the ' Service Codes' form.
- Admission:
- An existing client is identified or a new client is admitted. Note client id, admission program, admission date.
- Financial Eligibility:
- A guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
Steps
- Open SoapUI or any other web service tool.
- Set up the 'FileClientChargeInputICD10' method of the 'ClientChargeInput' web service.
- Create a new Client Charge Input request for a desired client by specifying the Date of Service, ClientID, Episode Number, diagnosis information and service code within quotes.
- Verify the web service displays error message: The following fields are invalid : Service Code : Invalid Service code : "[SERVICE CODE]".
- Remove the quotes from the 'ServiceCode' item of the web service request.
- File the request again.
- Verify the web service files successfully and displays confirmation message: "Client Charge Input web service has been filed successfully."
- Login to Avatar.
- Open the 'Client Ledger' form.
- Select desired client.
- Select desired episode.
- Select desired ledger type.
- Click [Process]
- Verify the service details are correct as filed via web service request.
- Click [Submit].
- Click [No].
Scenario 2: Appointment Scheduling Web Services - Validating 'AddAppointment' method for the quoted characters
Specific Setup:
- Practitioner Enrollment:
- An existing practitioner is identified. Note practitioner code/name.
- Staff Members Hours and Exceptions:
- The practitioner identified above is defined with hours and exception. Note the hours and exception. Note the site code/name for the practitioner.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the 'Service Codes' form.
- Admission:
- An existing client is identified or a new client is admitted. Note client id, admission program, admission date.
Steps
- Access SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by entering desired value to the 'Date of appointment', 'ClientID', 'Episode Number','Start/End time','service code' and 'ApptNotes' fields. Please note: The value in the 'ApptNote' field is within quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ApptNote' field is without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ServiceCode' field is within quotes.
- Verify the webservice returns error about invalid service code.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ServiceCode' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Location' field is within quotes.
- Verify the webservice returns error about invalid Location.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Location' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value from the 'ClientID' field is within quotes.
- Verify the webservice returns error about invalid ClientID.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ClientID' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Program' field is within quotes.
- Verify the webservice returns error about invalid Program.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Program' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Episode' field is within quotes.
- Verify the webservice returns error about invalid Episode.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Episode' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Site' field is within quotes.
- Verify the webservice returns error about invalid Site.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Site' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ApptStartTime' field is within quotes.
- Verify the webservice returns error about invalid ApptStartTime.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ApptStartTime' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ApptEndTime' field is within quotes.
- Verify the webservice returns error about invalid ApptEndTime.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ApptEndTime' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
Scenario 3: Client Charge Input - Validate the 'FileClientChargeInputICD10' web service for the quoted character
Specific Setup:
- Guarantors/Payors:
- An existing guarantor is identified to be used. Note the guarantor code/name.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the ' Service Codes' form.
- Admission:
- An existing client is identified or a new client is admitted. Note client id, admission program, admission date.
- Financial Eligibility:
- A guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
Steps
- Open SoapUI or any other web service tool.
- Set up the 'FileClientChargeInputICD10' method of the 'ClientChargeInput' web service.
- Create a new Client Charge Input request for a desired client by specifying the Date of Service, ClientID, Episode Number, diagnosis information and service code within quotes.
- Verify the web service displays error message: The following fields are invalid : Service Code : Invalid Service code : "[SERVICE CODE]".
- Remove the quotes from the 'ServiceCode' item of the web service request.
- File the request again.
- Verify the web service files successfully and displays confirmation message: "Client Charge Input web service has been filed successfully."
- Login to Avatar.
- Open the 'Client Ledger' form.
- Select desired client.
- Select desired episode.
- Select desired ledger type.
- Click [Process]
- Verify the service details are correct as filed via web service request.
- Click [Submit].
- Click [No].
Scenario 4: Appointment Scheduling Web Services - Validating 'AddAppointment' method for the quoted characters
Specific Setup:
- Practitioner Enrollment:
- An existing practitioner is identified. Note practitioner code/name.
- Staff Members Hours and Exceptions:
- The practitioner identified above is defined with hours and exception. Note the hours and exception. Note the site code/name for the practitioner.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the 'Service Codes' form.
- Admission:
- An existing client is identified or a new client is admitted. Note client id, admission program, admission date.
Steps
- Access SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by entering desired value to the 'Date of appointment', 'ClientID', 'Episode Number','Start/End time','service code' and 'ApptNotes' fields. Please note: The value in the 'ApptNote' field is within quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ApptNote' field is without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ServiceCode' field is within quotes.
- Verify the webservice returns error about invalid service code.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ServiceCode' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Location' field is within quotes.
- Verify the webservice returns error about invalid Location.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Location' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value from the 'ClientID' field is within quotes.
- Verify the webservice returns error about invalid ClientID.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ClientID' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Program' field is within quotes.
- Verify the webservice returns error about invalid Program.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Program' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Episode' field is within quotes.
- Verify the webservice returns error about invalid Episode.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Episode' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'Site' field is within quotes.
- Verify the webservice returns error about invalid Site.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'Site' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ApptStartTime' field is within quotes.
- Verify the webservice returns error about invalid ApptStartTime.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ApptStartTime' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
- Go back to SOAPUI or any other web service tool.
- File the 'AddAppointment' method of the Appointment Scheduling web service for a desired client by specifying the different Appointment Date or different Start/End time, ClientID, Episode Number, service code and 'ApptNotes' fields. Please note: The value in the 'ApptEndTime' field is within quotes.
- Verify the webservice returns error about invalid ApptEndTime.
- Go back to 'AddAppointment' request for of the Appointment Scheduling web service.
- Enter desired value in the 'ApptEndTime' field without quotes.
- Verify the webservice files successfully.
- Login to myAvatar.
- Open the 'Scheduling Calendar' form.
- Verify that the appointment is on the calendar and the appointment details are correct as filed from the web service.
|
Topics
• Client Charge Input
• Web Services
• Add New Appointment
|
File Import - CPT Code Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- CPT Code Definition (PM)
- Crystal Report Viewer
Scenario 1: Cal-PM - File Import - CPT Code Definition - Add / Edit
Specific Setup:
- Registry setting:
- Set Import File Delimiter = desired vale, noting the value.
- File Import:
- A 'CPT Code Description' file type is added to the File Import.
- Import a file to add new CPT code.
- Import a file to edit above CPT code.
Steps
- Open the "File Import" form.
- Select the "CPT Code Description" in the 'File Type' field.
- Select "Upload New File" in the 'Action' field.
- Click [Process Action].
- Select the "File A".
- Select "Compile/Validate File" in the 'Action' field.
- Select the "File A" in the 'Files(s)' field.
- Click [Process Action].
- Validate an Information message is displayed stating: Compiled
- Click [OK].
- Select "Print File" in the 'Action' field.
- Select the "File A" in the 'Files(s)' field.
- Click [Process Action].
- Validate the Report Viewer displays the contents of the file.
- Click [Close Report].
- Select "Post File" in the 'Action' field.
- Click [Process Action].
- Select the "File A".
- Validate an Information message is displayed stating: Posted.
- Click [OK] and close the form.
- Open the "CPT Code Definition" form.
- Click [Edit].
- Validate the form is filed with the data based on the uploaded file.
- Close the form.
- Follow steps 1-24 for Edit CPT Code File Import.
|
Topics
• File Import
|
Financial Eligibility - Policy Number Override section
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission (Outpatient)
- Diagnosis
- Fast Financial Eligibility
- Guarantors/Payors
- Financial Eligibility
- Client Charge Input
- Client Ledger
- Create Interim Billing Batch File
- Electronic Billing
Scenario 1: Fast Financial Eligibility - Add/Edit record
Specific Setup:
- Client is admitted and has no 'Fast Financial Eligibility', 'Family Financial Eligibility', 'Financial Eligibility', or 'Cross Episode Financial Eligibility' records.
- An active 'Guarantors/Payors' exists.
Steps
- Open 'Fast Financial Eligibility'.
- Add the eligibility record and submit the form.
- Open 'Fast Financial Eligibility'.
- Edit the eligibility record and submit the form.
- Open 'Fast Financial Eligibility'.
- Verify that the edited information displays correctly.
Scenario 2: Cal-PM - Financial Eligibility - Policy Number Override - Subscriber Client Index Number
Specific Setup:
- Registry Setting:
- Set Add Policy Number Override = Y.
- Allow Policy Number By Date Sort = Y.
- Enable MHSA/DIG Data Collection Fields = Y.
- Guarantor/Program Billing Defaults:
- Set Override Policy Number With CIN # = Y in 837P and 837I sections.
- Client A:
- Financial Eligibility:
- Enter the 'Subscriber Policy number in the 'Guarantor Selection' section. Note the value.
- Enter 'Subscriber Client Index Number' in the 'Guarantor Selection' section. Note the value.
- Enter 'Subscriber Client Index Number' in the 'Policy Number Override' section. Note the value.
- Enter 'Policy Number' in the 'Policy Number Override' section. Note the value.
- Has unclaimed services, for different/same service codes, that can be billed on the 837 Professional.
- Use 'Client Ledger' to note the service codes, dates of service, financial class, and guarantor.
- Client has an active diagnosis record.
- Create Interim Batch.
- Close the charges using 'Close Charges'.
- Client B:
- Financial Eligibility:
- Enter the 'Subscriber Policy number in the 'Guarantor Selection' section. Note the value.
- Enter 'Subscriber Client Index Number' in the 'Guarantor Selection' section. Note the value.
- Enter 'Subscriber Client Index Number' in the 'Policy Number Override' section. Note the value.
- Enter 'Policy Number' in the 'Policy Number Override' section. Note the value.
- Has unclaimed services, for different/same service codes, that can be billed on the 837 Institutional.
- Use 'Client Ledger' to note the service codes, dates of service, financial class, and guarantor.
- Client has an active diagnosis record.
- Create Interim Batch.
- Close the charges using 'Close Charges'.
Steps
- Open 'Electronic Billing'.
- Create an 837 Professional for Client A.
- Review the dump file to verify.
- Open dump file and validate the subscriber client index number contains the value in the 'Policy Number 'Override' section.
- Close the report.
- Create an 837 Institutional for Client B.
- Review the dump file to verify.
- Open dump file and validate the subscriber client index number contains the value in the 'Policy Number 'Override' section.
- Close the report.
- Close the form.
Guarantor/Program Billing Defaults
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission (Outpatient)
- Diagnosis
- Financial Eligibility
- Client Charge Input
- Client Ledger
- Create Interim Billing Batch File
- Electronic Billing
- File Import
- File Import - Compile/Post Report
- Crystal Report Viewer
Scenario 1: Validate 'Guarantor Program Billing Defaults', 'Sort Claims by Month' = Yes.
Specific Setup:
- Client A:
- Has unbilled, closed, services for a two-month date range. Tester knows the date range, guarantor, financial class of the guarantor and the program.
- The 'Guarantor/Program Billing Defaults' template used to bill the services has a value of 'Yes' in 'Sort Claims by Month' in the 837 Professional and/or 837 Institutional sections.
Steps
- Open 'Electronic Billing'.
- Create a bill for the services entering both months of service in the billing date range.
- Review the dump file.
- Validate that the client has two CLM segments.
- Validate that the service DTP segments after the first CLM segment are for the first month of service.
- Validate that the service DTP segments after the second CLM segment are for the second month of service.
- Click [X].
- Click [X].
Scenario 2: Validate 'Guarantor Program Billing Defaults', 'Sort Claims by Month' = No.
Specific Setup:
- Client A:
- Has unbilled, closed, services for a two-month date range. Tester knows the date range, guarantor, financial class of the guarantor and the program.
- The 'Guarantor/Program Billing Defaults' template used to bill the services has a value of 'Yes' in 'Sort Claims by Month' in the 837 Professional and/or 837 Institutional section.
Steps
- Open 'Electronic Billing'.
- Create a bill for the services entering both months of service in the billing date range.
- Review the dump file.
- Validate that the client has only one CLM segment.
- Validate that the service DTP segments after the first CLM segment are for both months of service.
- Click [X].
- Click [X].
Scenario 3: 'File Import' - Verification of 'Guarantor/Program Billing Defaults Template' Import (Avatar Cal-PM)
Specific Setup:
- Avatar Cal-PM 'Guarantor/Program Billing Defaults' Import File containing one or more valid import rows for 837 Professional information:
- 'Rendering Provider Entity Type Qualifier (2310B/2420A-NM1-02)' field/segment 127
- 'Rendering Provider Last Or Organization Name (2310B/2420A-NM1-03)' field/segment 128
- 'Rendering Provider First Name (2310B/2420A-NM1-04)' field/segment 129
- 'Rendering Provider Middle Name (2310B/2420A-NM1-05)' field/segment 130
- 'Rendering Provider Name Suffix (2310B/2420A-NM1-07)' field/segment 131
- 'Rendering Provider Identification Code Qualifier (2310B/2420A-NM1-08)' field/segment 132
- 'Rendering Provider Identification Code (2310B/2420A-NM1-09)' field/segment 133
- 'Rendering Provider Taxonomy Code (2310B/2420A-PRV-03)' field/segment 134
- 'Rendering Provider Reference Identification Qualifier (2310B/2420A-REF-01)' field/segment 135
- 'Rendering Provider Reference Identification (2310B/2420A-REF-01)' field/segment 136
- 'Rendering Provider Reference Identification Qualifier-2 (2310B/2420A-REF-01)' field/segment 137
- 'Rendering Provider Identification Code-2 (2310B/2420A-REF-02)' field/segment 138
- 'Specify How Rendering Provider Information Should Be Populated' field/segment 139
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar Cal-PM 'File Import' form.
- Select File Type 'Guarantor/Program Billing Defaults'.
- Select 'Upload New File' in 'Action' field and Click 'Process Action' button.
- Select Avatar Cal-PM 'Guarantor/Program Billing Defaults' import file including value for one or more of the following 837 Professional fields/segments and click 'Open' button:
- Select 'Compile/Validate File' in 'Action' field.
- Select loaded 'Guarantor/Program Billing Defaults' import file and click 'Process Action' button.
- Ensure that 'Compile/Validate File' action completes, and message 'Compiled' or '(File Name) contains one or more errors. These errors can be reviewed using 'Print Errors' action' is displayed.
- Click 'OK' button.
- Select 'Print File' in 'Action' field to view successfully compiled import data; Select compiled import file and click 'Process Action' button.
- In 'Guarantor/Program Billing Defaults' File Import Report, ensure that all valid import row(s) are included in report with segment/value details.
- Select 'Post File' in 'Action' field to post successfully compiled import data; Select compiled import file and click 'Process Action' button.
- Ensure that 'Compile/Validate File' action completes, and message 'Posted' and/or 'The selected file contains one or more lines with compilation errors. Only those lines without compilation errors will be posted' is displayed.
- Open Avatar Cal-PM 'Guarantor/Program Billing Defaults' form.
- Select 'Edit Template' in 'Action' field and select imported Guarantor/Program Billing Defaults template for review/edit.
- Navigate to '837 Professional' section of form.
- Ensure that imported values for 837 Professional Rendering Provider (2310B/2420A) fields noted above are present for selected template.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar Cal-PM SQL table 'SYSTEM.file_import_gpbd_p837', ensure that new row is filed in table for each successfully compiled/posted import row, including values for following fields:
- 'rendering_entity_code'/'rendering_entity_value'
- 'rendering_first_name'
- 'rendering_last_org_name'
- 'rendering_middle_name'
- 'rendering_suffix'
- 'rendering_id_qual_code'/'rendering_id_qual_value'
- 'rendering_id'
- 'rendering_taxonomy'
- 'rendering_ref_qual_code'/'rendering_ref_qual_value'
- 'rendering_ref_id'
- 'rendering_ref_qual2_code'/'rendering_ref_qual2_value'
- 'rendering_ref_id2'
- 'use_rnd_if_notfound_code'/'use_rnd_if_notfound_value'
For Avatar Cal-PM 'Guarantor/Program Billing Defaults - 837 Professional' format/layout, please refer to 'Avatar_Cal-PM_File_Import_Record_Layouts.xls' document included with update.
|
Topics
• Financial Eligibility
• NX
• 837 Professional
• 837 Institutional
• Guarantor/Program Billing Defaults
• File Import
|
Cal-OMS
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Maintenance
- Admission (Outpatient)
- Cal-OMS Submission
- Crystal Report Viewer
- Dynamic Form - Cal-OMS File Submission
Scenario 1: 'Cal-OMS Admission' - Form Verification
Specific Setup:
- Avatar Cal-PM Registry Setting 'Do Not Allow User To Continue Filing With Errors' may optionally be enabled/disabled
- Client record eligible for Cal-OMS Admission record entry/edit
Steps
- Open Avatar Cal-PM 'Cal-OMS Admission' form.
- Select client/episode for Cal-OMS Admission entry (or select existing Cal-OMS Admission record for view/edit).
- Enter all required and desired data on the form.
- File the form.
- Return to the form and choose the admission record to Edit.
- Validate that all the filed data for the fields exist.
- Close form.
- Compile/ Print and Submit(Create File) the admission using the "Cal-OMS Submission" form.
Cal-OMS
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Cal-OMS Admission Web Service
Scenario 1: Cal-OMS Admission Web Service - Verification of Web Service Filing
Specific Setup:
- Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC').
- Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y').
- Application utilizing the Avatar Cal-PM 'Cal-OMS Admission' web service (including Netsmart ProviderConnect).
- One or more client(s) with episodes eligible for 'Cal-OMS Admission' record filing.
- Crystal Reports or other SQL reporting tool.
Steps
- Using the 'Cal-OMS Admission' web service (and/or 'Cal-OMS Admission V2' web service), submit request to 'FileCalOMSAdmission' method to create or update Cal-OMS Admission record.
- Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAdmission' method.
- Example:"<Confirmation>ClientID:111||EP:1||UniqueID:OMA.001</Confirmation>"
- Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSAdmission' method.
- Example:"<Message>Cal-OMS Admission web service has been filed successfully.</Message>"
- Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSAdmission' method.
- Example:"<Status>1</Status>"
- Open Avatar Cal-PM 'Cal-OMS Admission' form and select client/episode/Cal-OMS Admission record filed via web service for view/update.
- Confirm Cal-OMS Admission record is created/updated in Avatar Cal-PM, with values/data submitted via web service, including the following fields:
- 'Record To Be Submitted'
- 'Ethnicity'
- 'What is your Principal Source of Referral?'
- 'Primary Drug Route of Administration'
- 'Secondary Drug Route of Administration'
- 'Which of the following medication is prescribed as part of treatment?'
- 'Current Living Arrangements'
- 'Race 1'
- 'Race 2'
- 'Race 3'
- 'Race 4'
- 'Race 5'
- Open Crystal Reports or other SQL reporting tool.
- In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_admission', ensure data values are filed/present for all fields as filed via web service, including LA-Specific field values noted above.
|
Topics
• Cal-OMS
• NX
• Web Services
|
Avatar Cal-PM 'Cal-OMS Administrative Discharge' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Cal-OMS Administrative Discharge
Scenario 1: 'Cal-OMS Administrative Discharge' - Form Verification
Specific Setup:
- Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' may optionally be enabled (value 'Y' or 'YC') or disabled (value 'N')
- One or more client(s) with episodes eligible for 'Cal-OMS Admission'/Cal-OMS Administrative Discharge' entry
- One or more client(s) with existing 'Cal-OMS Admission' record eligible for 'Cal-OMS Administrative Discharge' entry
Steps
- Open Avatar Cal-PM 'Cal-OMS Administrative Discharge' form.
- Select Client ID and Cal-OMS Admission record/episode for Cal-OMS Administrative Discharge record entry/edit.
- In 'Cal-OMS Administrative Discharge' form, ensure that 'Discharge Process Date' field is present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is enabled; ensure that 'Discharge Process Date' field is not present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is disabled.
- Enter/select values for all 'Cal-OMS Administrative Discharge' form fields as required/desired, including value for 'Discharge Process Date' field if enabled/present in form.
- Click 'Submit' button to file 'Cal-OMS Administrative Discharge' form/record.
- Re-open 'Cal-OMS Administrative Discharge' form, selecting same Client ID and Cal-OMS Admission/episode where Cal-OMS Discharge record previously filed.
- Ensure values for all 'Cal-OMS Administrative Discharge' form fields are present where previously entered/filed, including value for 'Discharge Process Date' field if enabled/present in form.
|
Topics
• Registry Settings
• Cal-OMS
• NX
|
Cal-PM CarePOV system - Selecting client
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Internal Test Only
|
Topics
• Client Search
|
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Avatar NX Report Viewer
- Service Fee/Cross Reference Maintenance
- Service Codes
- Product Updates (PM)
Scenario 1: File Import - 'Service Fee/Cross Reference' file type
Specific Setup:
- The registry setting 'Import File Delimiter' is enabled with desired value.
- An existing service code is identified. Note the service code.
- File Import:
- File 1: A 'Service Fee/Cross Reference Maintenance' import file is created for the service code and contains a leading $ sign in the 'Fee' field. Note the value of each field included in the file. Note the file name.
- File 2: A 'Service Fee/Cross Reference Maintenance' import file is created for the service code and contains only the amount in the 'Fee' field. Note the value of each field included in the file. Note the file name.
Steps
- Open the 'File Import' form.
- Select the 'Service Fee/Cross Reference Maintenance' from the 'File Type' field.
- Upload File 1.
- Compile the file.
- Verify the information message: "File [File Name] contains one or more errors. These errors can be reviewed using 'Print Errors' action".
- Click [OK] button.
- Select the 'Print Errors' option.
- Review the error report.
- Verify the report displays the error: 'Invalid numeric format'.
- Click [X].
- Upload File 2.
- Compile the file.
- Verify the information message: 'Compiled'.
- Click [OK].
- Post File 2.
- Verify the file posted successfully.
- Open the 'Service Fee/Cross Reference Maintenance' form.
- Edit the service code mentioned in the file import file.
- Enter the 'From Date' same as the date entered in the file import file.
- Verify the fee of the service displays correctly as entered in File 2.
- Click [Close Form].
|
Topics
• Service Fee/Cross Reference Maintenance
• File Import
|
274 Provider Directory - SQL Tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- 274 - Provider Directory Definition
Scenario 1: 274 - Provider Directory Definition - Site Definition
Specific Setup:
- Tester has been given access to the ‘274 - Provider Directory Definition’ form in ‘User Definition’ under ‘Avatar PM / System Maintenance / System Definition / Health Care Provider Directory (274)’.
Steps
- Open ‘274 - Provider Directory Definition’.
- Select the 'Site Definition’ section.
- Validate that ‘Add or Edit Site’ is the only required field on the form.
- Select ‘Add’ in ‘Add or Edit Site’.
- Validate that ‘Site or Location of Service Name (2100A-NM1-03)', ‘Provider Group’ and ‘Active’ are now required fields.
- Click [X].
- Open 'Site Specific Section Modeling' for Avatar PM.
- Select 'TABLE27400 (274 - Provider Directory Definition) Site Definition’ in 'Site Specific Selection'.
- Click [OK].
- Select the ‘Site Specific Section’ option.
- Click on row ‘60’ in ‘Prompt Order’.
- Click [Edit Selected Item].
- Validate that ‘Label’ is disabled and contains ‘Facility ID (2140DA-REF-02)’.
- Validate that ‘Initially Enabled’ = ‘Yes’.
- Validate that ‘Initially Required’ = 'No'.
- Select ‘Yes’ in ‘Initially Required’.
- As desired, set other ‘Prompt Order’ rows to a value of ‘Yes’ in ‘Initially Required’. Note the values of the other fields, specifically the ‘Label’.
- Click [Submit].
- Click ‘Refresh Forms’ icon.
- Open ‘274 - Provider Directory Definition’.
- Select the ‘Site Definition’ section.
- Validate that ‘Facility ID (2140DA-REF-02)’ is required.
- Validate that all other rows that were updated to be required display as required. The 'Label' that was noted is the field name.
- Add desired data to the form.
- Click [File Site Details].
- Select the filed Site and validate that the data displays correctly.
- If desired, create additional desired ‘Site Definitions’ and file them.
- Click [X].
- Open ‘274 - Provider Directory Definition’.
- Select the 'Site Definition’ section.
- Select any site and validate that the filed data displays correctly.
- Click [X].
Scenario 2: 274 - Provider Directory Definition - Provider Definition
Specific Setup:
- Tester has been given access to the ‘274 - Provider Directory Definition’ form in ‘User Definition’ under ‘Avatar PM / System Maintenance / System Definition / Health Care Provider Directory (274)’.
- 274 Provider Directory Definition:
- A minimum of one 'Group Definition' exists.
- A minimum of one 'Site Definition' exists.
Steps
- Open ‘274 - Provider Directory Definition’.
- Validate that the form opened to the ‘Group Definition’ section.
- Select the ‘Provider Definition’ section.
- Validate that ‘Provider’ is the only required field on the form.
- Select a ‘Provider’.
- Validate that ‘Associated Site’ and ‘Active’ are now required fields.
- Click [X].
- Open 'Site Specific Section Modeling' for Avatar PM.
- Select 'TABLE27400 (274 = Provider Directory Definition) Provider Definition’ in 'Site Specific Selection'.
- Click [OK].
- Select ‘Site Specific Section’ option.
- Click on row ‘84’ in ‘Prompt Order’.
- Click [Edit Selected Item].
- Validate that ‘Label’ is disabled and contains ‘Provider Identifier - Secondary (2140EA-REF-02)’.
- Validate that ‘Initially Enabled’ = ‘Yes’.
- Validate that ‘Initially Required’ = 'No'.
- Select ‘Yes’ in ‘Initially Required’.
- As desired, set other ‘Prompt Order’ rows to a value of ‘Yes’ in ‘Initially Required’. Note the values of the other fields, specifically the ‘Label’.
- Click [Submit].
- Click ‘Refresh Forms’ icon.
- Open ‘274 - Provider Directory Definition’.
- Select the ‘Provider Definition’ section.
- Validate that ‘Provider Identifier - Secondary (2140EA-REF-02)’ is now required.
- Validate that all other rows that were updated to be required display as required. The 'Label' that was noted is the field name.
- Add desired data to the form.
- Click [File Provider Details].
- Select the same provider and site.
- Validate that the submitted date displays correctly.
- Select the ‘Provider’ that was submitted in ‘Provider’.
- Select a new value in ‘Associated Site’.
- Validate that a ‘Provider-Site Records On File’ item displays the message ‘Record to default Information From’ and contains a drop down list of ‘Sites’.
- Select a site and click [OK].
- Validate that the data defaulted into the fields.
- Click [File Provider Details].
- Create additional desired ‘Provider Definitions’ for the same provider for another site and then inactivate the provider in one of the three sites. The provider will not display in the submission for the inactive site.
- Create additional desired ‘Provider Definitions’.
- Click [X].
- Open ‘274 - Provider Directory Definition’.
- Select the ‘Provider Definition’ section.
- Select the desired provider and site.
- Validate that the submitted date displays correctly.
- Click [X].
274 Provider Directory - Update Class Mapping/Submission File Logic/File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- 274 - Provider Directory Submission
- Crystal Report Viewer
- 274 - Provider Directory Definition
Scenario 1: 274 - Provider Directory Submission - form validation
Specific Setup:
- An output directory has been defined in ‘Facility Defaults’ field ‘Output Path On Server For State Reporting Files’.
Steps
- Open ‘274 - Provider Directory Submission’.
- Validate that the ‘Options’, ‘Reporting Period (MM/YY)’, and ‘File Description’ fields are required.
- Select ‘Compile File’ in ‘Options’.
- Enter the desired value in ‘Reporting Period (MM/YY)’.
- Enter the desired value in ‘File Description’.
- Click [Process File].
- The ‘Health Care Provider Directory’ report will open. The report can contain the following links: ‘274 Submission’, ‘Required Data Missing/Invalid - Directory Defaults’, ‘Required Data Missing/Invalid - Group’, ‘Required Data Missing/Invalid – Site’, ‘‘Required Data Missing/Invalid – Provider’, and ‘‘Required Data Missing/Invalid – Other’.
- Click on the link for any ‘Required Data Missing/Invalid’ links and review the data in the sub report. Correct the data as desired.
- Click on the link for ‘274 Submission’ and review the data in the report. Providers will not display for the sites in which they are inactive.
- Close the report.
- Select ‘Dump File’ in ‘Options’.
- Validate that ‘Select File’ in now required.
- Select the file compiled above in ‘Select File’.
- Click [Process File].
- The ‘Health Care Provider Directory’ report will open and display the data that will be included in the dump file.
- Close the report.
- Select ‘Create File On Server For Submission’ in ‘Options’.
- Select the file compiled above in ‘Select File’.
- Click [Process File].
- The ‘Create File’ item is received with the message ‘Process Completed’.
- Click [OK].
- Select ‘Run Report’ Select ‘Create File On Server For Submission’ in ‘Options’.
- Select the file compiled above in ‘Select File’.
- Click [Process File].
- The ‘Health Care Provider Directory’ report will open and contain the same links the previously opened.
- Close the report.
- ‘Options’ contains ‘Delete File’. If deleting a file is desired, select ‘Delete File’.
- Select the file compiled above in ‘Select File’.
- Click [Process File].
- Close the form.
Scenario 2: 274 - Provider Directory Definition - Site Definition
Specific Setup:
- Tester has been given access to the ‘274 - Provider Directory Definition’ form in ‘User Definition’ under ‘Avatar PM / System Maintenance / System Definition / Health Care Provider Directory (274)’.
Steps
- Open ‘274 - Provider Directory Definition’.
- Select the 'Site Definition’ section.
- Validate that ‘Add or Edit Site’ is the only required field on the form.
- Select ‘Add’ in ‘Add or Edit Site’.
- Validate that ‘Site or Location of Service Name (2100A-NM1-03)', ‘Provider Group’ and ‘Active’ are now required fields.
- Click [X].
- Open 'Site Specific Section Modeling' for Avatar PM.
- Select 'TABLE27400 (274 - Provider Directory Definition) Site Definition’ in 'Site Specific Selection'.
- Click [OK].
- Select the ‘Site Specific Section’ option.
- Click on row ‘60’ in ‘Prompt Order’.
- Click [Edit Selected Item].
- Validate that ‘Label’ is disabled and contains ‘Facility ID (2140DA-REF-02)’.
- Validate that ‘Initially Enabled’ = ‘Yes’.
- Validate that ‘Initially Required’ = 'No'.
- Select ‘Yes’ in ‘Initially Required’.
- As desired, set other ‘Prompt Order’ rows to a value of ‘Yes’ in ‘Initially Required’. Note the values of the other fields, specifically the ‘Label’.
- Click [Submit].
- Click ‘Refresh Forms’ icon.
- Open ‘274 - Provider Directory Definition’.
- Select the ‘Site Definition’ section.
- Validate that ‘Facility ID (2140DA-REF-02)’ is required.
- Validate that all other rows that were updated to be required display as required. The 'Label' that was noted is the field name.
- Add desired data to the form.
- Click [File Site Details].
- Select the filed Site and validate that the data displays correctly.
- If desired, create additional desired ‘Site Definitions’ and file them.
- Click [X].
- Open ‘274 - Provider Directory Definition’.
- Select the 'Site Definition’ section.
- Select any site and validate that the filed data displays correctly.
- Click [X].
|
Topics
• 274 - Provider Directory
|
Envelope import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Envelope Export (PM)
- Form Designer (PM)
Scenario 1: Envelope Export/Import - 'Include Form Design Changes' in the file set to "Y"
Specific Setup:
- Have a modeled form [FormA], contained in [EnvelopeA], that will be used to make form designer changes
Steps
- Open the 'Form Designer' form.
- Select [FormA] from the 'Forms' field.
- Make any type of form designer change in the section [FDchange1]. For example, a field is moved to different location.
- Save the changes and exit the form.
- Navigate to form "Envelope Export".
- Select [EnvelopeA].
- In the "Include Form Design Changes? field, select "Yes".
- Click [Begin Export].
- Validate export is completed successfully. [ExportA].
- Open the 'Form Designer' form.
- Select [FormA] from the 'Forms' field.
- Make another form designer change in the section [FDchange2].
- Save the changes and exit the form.
- Open [FormA].
- Validate [FDchange1] and [FDchange2] are both present in the form.
- Open form "Envelope Import".
- Click [Select Envelope For Import].
- Navigate the location of [ExportA].
- Select the file.
- Select radio button "Overwrite Existing".
- In the "Include Form Design Changes? field, select "Yes". [Note: "Yes" implies that any form designer changes contained in the import file, 'will' be imported and/or overwrite any existing changes already made on the form].
- Click [Begin Import Scan].
- Validate there are no errors/warnings found within the import file scan results.
- Click [Begin Import].
- Validate import is completed successfully.
- Open [FormA].
- Select [SectionA].
- Validate [FDchange1] is present on the form.
- Validate [FDchange2] is not present on the form.
Quick billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Quick Billing
- Guarantors/Payors
- Admission (Outpatient)
- Financial Eligibility
- Diagnosis
- Client Ledger
- Quick Billing Rule Definition
- Crystal Report Viewer
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.
|
Topics
• Envelope Import
• Quick Billing
• Quick Billing Rule Definition
|
837 Billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- Dictionary Update (PM)
- Service Fee/Cross Reference Maintenance
- Admission (Outpatient)
- Diagnosis
- Financial Eligibility
- Program Maintenance
- Client Charge Input
- Client Ledger
- Electronic Billing
- Individual Cash Posting (PM)
- Product Updates (PM)
Internal Test Only
|
Topics
• 837 Professional
• NX
• State Forms
|
File Import - Client charge input
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Ledger
- File Import
- Crystal Report Viewer
- Service Fee/Cross Reference Maintenance
- Admission (Outpatient)
- Dictionary Update (PM)
- Financial Eligibility
- Client Charge Input
- Diagnosis
- Electronic Billing
- Create Interim Billing Batch File
Scenario 1: File Import - Render service to the client using multiple add-on codes
Specific Setup:
- The following registry setting has a value of 'Y': Avatar PM->System Maintenance->Service Code Maintenance->->->Enable Multiple Add-On Code Per Primary Code Functionality.
- Dictionary Update has been used to update 'Other Tabled File, 291, Service Code Type' to have a value of 'Yes' in the extended dictionary 'Allow Multiple Add-On Code Definition' for all dictionary codes.
- A 'Service Code' identified with a 'Service Code Category' of 'Primary Code' has at least two values selected in 'Select Multiple Add-On Code'.
- An outpatient client is identified. Note the program. The client has an active diagnosis record, and an active financial eligibility record, noting the financial class.
- A 'Client Charge Input', 'File Import' file has been created import the primary service and add-on services.
Steps
- Open the 'File Import' form.
- Select the 'Client Charge Input' from the 'File Type' field.
- Upload the 'Multiple Add-Ons' file created in the setup section.
- Compile the file.
- Verify the information message : 'Compiled'.
- Click [OK].
- Post the file.
- Verify the file posted successfully.
- Close the form.
- Open the Client Ledger.
- Validate the Primary service code display with Multiple Add-on codes.
Scenario 2: 837 Professional billilng when 'Enable Multiple Add-On Code Per Primary Code Functionality' = Y.
Specific Setup:
- The following registry setting has a value of 'Y': Avatar PM->System Maintenance->Service Code Maintenance->->->Enable Multiple Add-On Code Per Primary Code Functionality.
- Dictionary Update has been used to update 'Other Tabled File, 291, Service Code Type' to have a value of 'Yes' in the extended dictionary 'Allow Multiple Add-On Code Definition' for all dictionary codes.
- A 'Service Code' identified with a 'Service Code Category' of 'Primary Code' has at least two values selected in 'Select Multiple Add-On Code'.
- An outpatient client is identified. Note the program. The client has an active diagnosis record, and an active financial eligibility record, noting the financial class.
- A service has been created for the above 'Service Code'. Note the date of service. The service has been closed.
- Use 'Client Ledger' to note the fee for the 'Service Code' and for each 'Add-On Code'. Note the total fee.
Steps
- Open 'Electronic Billing'.
- Create an '837 Professional' bill for the service.
- Review the dump file to validate that the amount in the 'CLM' is equal to the total fee and that the amounts in the 'SV1' segments is equal to the total fee.
- Close the dump file.
- Close the form.
- Query the SYSTEM.billing_tx_master table. Locate the 'Service Code' selected in Setup.
- Validate that the 'multi_addon_svc_code' displays all add-on service code numbers selected in the primary service code.
- Validate that the 'multi_addon_svc_value' displays all add-on service code descriptions selected in the primary service code.
|
Topics
• Client Charge Input
• File Import
• 837 Professional
|
| |