- Created by Shawna Crawford, last modified on Apr 13, 2016
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
The order in which elements are configured is vital for a successful and complete implementation. Some elements are common and must be configured before other elements. These recommendations have taken these elements into consideration. Some elements must be configured before you can enter charges while other elements must be configured before you can enter payments. Elements are coded based on what they control in Connect Back Office and Connect Reportal, and are listed in the order in which they must be configured. Refer to the key to determine what they control.
Some elements are optional and only need to be configured if these functions are used in your business practices. These elements are identified individually.
Before implementing security in your Connect platform, enter a ticket through the Support Center to request the instructions on changing the default system administrator password.
Use the following table as a guideline for configuring the elements for your billing system. The elements are listed in the order they should be configured:
Element | What to Configure | ||
---|---|---|---|
These elements control the security function for users and roles. Before working with any application in the Connect platform, you must establish your administrator and other users. Users can also be assigned specific roles, which control what the user can do or see in Connect applications. Configure roles for functions in other Connect applications. Create user accounts and assign the roles to user accounts. | |||
Add all facilities where services are provided, including hospitals, pain clinics, medical offices and others. Facilities are affiliated with the practice in the practice configuration. | |||
Add all providers with whom you do business, both rendering and referring, for example, physicians, CRNAs, physician assistants, anesthesia assistants and SRNAs. Providers are affiliated with the practice in the practice configuration. | |||
Configure the concurrency schemes for anesthesia procedures. Concurrency schemes are assigned at the plan configuration. All concurrency schemes must be configured before configuring payers and plans unless you plan to use the Default Concurrency Scheme. | |||
Add the financial classes for reporting purposes in the plan configuration. | |||
Configure all payers that you contract to do business with. Payers are associated to fee schedules in the practice configuration. All payers must be added before you can configure a fee schedule. | |||
Configure all plans you currently send claims to. Plans are associated to fee schedules in the practice configuration. All plans must be configured before you can configure a fee schedule. | |||
Add external collection agencies. For each practice, assign the external collection agencies and configure the external collection rules. If you do not use external collection agencies, skip this configuration. | |||
Add all practices you bill medical services for. This configuration includes demographic information on the practice, affiliated facilities and providers, fee schedules (billing and expected), group NPI numbers assignments and rules for generating statements and activating guarantor and insurance collections.
Statements must be configured before entering payments in Back Office. | |||
Add adjustment and denial code rules for handling group and reason codes in Back Office. Denial Management must be configured before entering payments in Back Office. If you do not use denial management, skip this configuration. | |||
Create a procedure category that can be imported into a fee schedule in the practice configuration. A procedure category is a group of two or more procedure codes related by similar procedures or by types of service, for example, obstetrics, acute pain or pain management. Procedure Categories are also used as a filter for reporting purposes in Reportal. If you do not group procedures by categories, skip this configuration. | |||
Create collection letter layouts for the collection letters you use for guarantor and insurance collections in Back Office. Collection letters must be configured before using collections in Back Office. If you are not using internal collections, skip this configuration. | |||
Add case reporting types as categories for grouping like cases in charge entry of Back Office for reporting purposes. Case Reporting Types must be configured before entering charges in Back Office. If you do not group cases for reporting purposes, skip this configuration. | |||
Add mappings of CPT code to ASA codes for associating anesthesia codes to a CPT code not normally associated with anesthesia. When a mapped code is used on a case, the associated ASA code is listed with the CPT code so that anesthesia specifics can be entered on the case. If you are using the standard ASA code mappings, skip this configuration. | |||
Add all EDC interface configurations for electronic data capture from a hospital download. The EDC interface configuration includes the data mappings from the EDC file to the elements affiliated with the practice. This configuration ensures the data from the hospital download is mapped correctly to the case in Back Office to eliminate duplicate data entry on cases. All facilities in the EDC file must be mapped in the EDC interface configuration; otherwise, the EDC file cannot be mapped into Back Office. EDC Interface Configuration must be completed before importing files from a hospital and importing the file into a case in Back Office. If you are not using electronic data capture, skip this configuration. |
Search this documentation
- No labels