Eligibility can be submitted in Revenue Cycle using both person and encounter-level conversations with checks occurring automatically through batch Cerner Millennium Operations jobs or manual submission. In any instance, the responses can be seen using the Insurances or Insurances with Profiles tables.
Each table has dedicated columns, which can display the status of an eligibility submission. The following columns can be used to reference eligibility status:
For additional details about managing insurances in Revenue Cycle, see Working With Registration Conversations: Insurance Management.
Regardless of whether the transaction was submitted manually or automatically, the transaction flow for sending and receiving is the same. In both scenarios, the patient and encounter information is retrieved and the ANSI 270 eligibility request transaction is created and sent to Transaction Services. From there, the transaction goes to the clearinghouse and then to the payer. The payer processes the transaction and creates an ANSI 271 eligibility response, which is sent back through the clearinghouse to transaction services. This entire process takes anywhere from a few seconds to several minutes, depending on the availability of the payer’s eligibility systems.
If the patient or subscriber's Name on File with Payer values are populated in the conversation, the system sends an outbound 270 transaction with those values to the payer. If these values are left blank, the current name of the subscriber on the health plan, as well as the patient's name, is sent to the payer in the eligibility request.
Eligibility transactions can be submitted to the payer through four methods:
Automated submission is accomplished through a Cerner Millennium Operations job, an automated process that selects multiple future appointments and submits each eligibility request as an individual real time transaction for each patient.
The function of the eligibility Operations job is to submit eligibility for created encounters, whether for all active insurances associated with an appointment, or for the primary insurance associated with an appointment.
This job typically runs between 2 a.m. and 4 a.m. An encounter must be created before an eligibility request can be sent to the payer. Creating an encounter and submitting eligibility 48 hours in advance allows you to work the eligibility queue and verify that patients coming in for services have active benefits. For example, Facility ABC automatically submits eligibility through an Operations job for all active insurances associated with an appointment two days before the appointment.
Transactions sent by this Operations job are displayed as sent by a generated domain user.
Right-click on the Insurance table to access the following options:
When you select Eligibility Details, a Previous Transaction option is also displayed.
This option is also available using the context menu command when you select a health plan.
See Overview of Common Financial Clearance View Previous Transactions for more information about using previous transactions with Common Financial Clearance Medical Eligibility .
With Medical Eligibility, you can view all past transactions for a specific payer and alternate payer. You can still select Eligibility Details to view the most recent Medical Eligibility response, as well as any alternate payer info and the Transaction History table.
Manual submission is processed through both Add and Modify Encounter and Person conversations. Submission of eligibility also includes opportunities to submit eligibility through the patient check-in process and through patient tracking. Eligibility and benefit information is stored with the encounter, so the encounter must exist before you can check a patient’s eligibility.
Complete the following steps to manually submit an eligibility transaction to the payer:
The transaction is submitted to the payer immediately, and when the response is received, the screen automatically is refreshed and details for the eligibility and benefits are displayed. When transactions are manually submitted, a response is polled for two minutes. During that time the submission is put in a Pending status and the Submit Eligibility option is disabled. Keep the patient record open and the eligibility and benefit information for the patient is automatically displayed.
Right-click on the Insurance table to access the following options:
The Submit Eligibility with Options workflow allows you to submit eligibility with a service type up front from a context menu command.
You can select the following options to submit with service types up front:
Once the dialog box opens, you can select from the following options:
The Override Cached Response option is available only to clients who use Medical Eligibility in Revenue Cycle.
All above options can be used independently of each other. If you only need to submit for a coverage date, you can select the coverage dates with which you want to submit, no other options, and select OK .
When you select Eligibility Details, a Previous Transaction option is also displayed.
This option is also available using the context menu command when you select a health plan.
See Overview of Common Financial Clearance View Previous Transactions for more information about using previous transactions with Common Financial Clearance Medical Eligibility .
With Medical Eligibility, you can view all past transactions for a specific payer and alternate payer. You can still select Eligibility Details to view the most recent Medical Eligibility response, as well as any alternate payer info and the Transaction History table.
Eligibility submissions through the Appointments perspective are at the patient level.
Complete the following steps to submit eligibility in the Appointments perspective:
Right-click on the Insurance table to access the following options:
The Submit Eligibility with Options workflow allows you to submit eligibility with a service type up front from a context menu command.
You can select the following options to submit with service types up front:
Once the dialog box opens, you can select from the following options:
The Override Cached Response option is available only to clients who use Medical Eligibility in Revenue Cycle.
All above options can be used independently of each other. If you only need to submit for a coverage date, you can select the coverage dates with which you want to submit, no other options, and select OK .
When you select Eligibility Details, a Previous Transaction option is also displayed.
This option is also available using the context menu command when you select a health plan.
See Overview of Common Financial Clearance View Previous Transactions for more information about using previous transactions with Common Financial Clearance Medical Eligibility .
With Medical Eligibility, you can view all past transactions for a specific payer and alternate payer. You can still select Eligibility Details to view the most recent Medical Eligibility response, as well as any alternate payer info and the Transaction History table.
If using the eligibility queue to follow up on incomplete eligibility transactions, encounters can be manually resubmitted from within the queue. Right-click a specific encounter and select one of the following options related to eligibility:
Right-click on the Insurance table to access the following options:
The Submit Eligibility with Options workflow allows you to submit eligibility with a service type up front from a context menu command.
You can select the following options to submit with service types up front:
Once the dialog box opens, you can select from the following options:
The Override Cached Response option is available only to clients who use Medical Eligibility in Revenue Cycle.
All above options can be used independently of each other. If you only need to submit for a coverage date, you can select the coverage dates with which you want to submit, no other options, and select OK .
When you select Eligibility Details, a Previous Transaction option is also displayed.
This option is also available using the context menu command when you select a health plan.
See Overview of Common Financial Clearance View Previous Transactions for more information about using previous transactions with Common Financial Clearance Medical Eligibility .
With Medical Eligibility, you can view all past transactions for a specific payer and alternate payer. You can still select Eligibility Details to view the most recent Medical Eligibility response, as well as any alternate payer info and the Transaction History table.
Alternate payer functionality is not supported with Common Financial Clearance Eligibility.
To support alternate payers, you can submit an eligibility request to two payers simultaneously. This functionality can be used in the situation where a patient may be eligible for Medicare or Medicaid but also has a Managed Medicare or Managed Medicaid policy through a commercial payer. Complete the following steps to submit an eligibility request to an alternate payer in addition to the primary payer :
The following columns can also be added to Insurance Tables to view Alternate Eligibility information:
Right-click on the Insurance table to access the following options:
The Submit Eligibility with Options workflow allows you to submit eligibility with a service type up front from a context menu command.
You can select the following options to submit with service types up front:
Once the dialog box opens, you can select from the following options:
The Override Cached Response option is available only to clients who use Medical Eligibility in Revenue Cycle.
All above options can be used independently of each other. If you only need to submit for a coverage date, you can select the coverage dates with which you want to submit, no other options, and select OK .
When you select Eligibility Details, a Previous Transaction option is also displayed.
This option is also available using the context menu command when you select a health plan.
See Overview of Common Financial Clearance View Previous Transactions for more information about using previous transactions with Common Financial Clearance Medical Eligibility .
With Medical Eligibility, you can view all past transactions for a specific payer and alternate payer. You can still select Eligibility Details to view the most recent Medical Eligibility response, as well as any alternate payer info and the Transaction History table.
Once eligibility has been submitted, the response can be reviewed by selecting the Eligibility Details button on the appropriate table.
Two eligibility detail windows may be available:
Complete the following steps to view coverage status information:
The Historical Response alert is only displayed if you enable the Historical Processing option in the associated domain. If this option is disabled, the Historical Response alert is not displayed.
The Verify Status field for the health plan is automatically updated to Verified if the eligibility status comes back as Active or Yes Follow Up if the eligibility status comes back as Inactive, No Coverage, or Payer Rejection. The following additional values are available for the Verify Status field and can be manually selected by a user after eligibility is checked on the health plan.
Complete the following steps to view patient or subscriber information:
Complete the following steps to select and view benefit information:
Complete the following steps to manually add a benefit:
In the Common Financial Clearance interface, if any differences exist between the information submitted in the request and the information the payer has on file, a discrepancy alert is displayed. Information contained in Cerner Millennium i s displayed in the Current row, while the response from the payer is displayed in the Response row.
Complete the following steps to view and update discrepancies:
If patient demographic discrepancies are accepted back from the eligibility response, those values are copied into the Patient on File with Payer fields and used on subsequent eligibility inquiries. If Cerner Patient Accounting (CPA) is used for Patient Accounting, the Patient on File with Payer fields are not used on the claim. If your site uses RevElateis used for Patient Accounting , the Patient on File with Payer fields are used on the claim to minimize claim rejections. See Understand Insurance Information Between Cerner Millennium and Soarian Financials for additional information.
The Additional Payer/Plan window is currently available only to sites using the Blaze Rules Development Tool (BRDT) in RevElate.
Facilities using the Blaze Rules Development Tool (BRDT) in RevElate can add new health plans to patients based on the initial eligibility response.
Once the health plan has been added to the encounter, sites should run eligibility to verify the patient's plan coverage. This can be done automatically or as part of a workflow established to manually verify. See Overview of Automatically Adding a Health Plan or Accepting a Health Plan Discrepancy in Revenue Cycle for additional details.
Complete the following steps to review messages and alerts:
Complete the following steps to review the support information:
You can use verifications fields as a way to inform the user if eligibility was viewed and ran successfully.
In this workflow, the request is submitted using an Operations job, and the eligibility response is returned. The verification status and corresponding fields are initially blank, and the verification status is not automatically set when the response is returned. The response is added to an unverified work queue until a user views it in Edit mode.
In this workflow, the user manually submits the eligibility request, and a response is returned. The verification fields are initially blank. When the user selects Eligibility Details, the verification status is automatically set to Verified or Follow Up in the following scenarios:
When the verification status is valued, the following fields are also valued:
When the verification status fields are valued and eligibility is run again, t he verification status, verify date, verify source, and verify personnel values are updated only if the value for verification status was originally Follow Up and the new value is Verified.
Otherwise, the verification status fields are not automatically updated.
The verification status is not automatically set if the response returned is an error or if the eligibility response is viewed in View Only mode.
In the Medical Eligibility interface, you can see the service types that were sent on the eligibility request in the Service Type column on the Transaction History table.
The service types can also be seen to the right of the Filters check box in the eligibility response.
See the Filters subsection of the Details section below for more information.
The top portion of this view includes a list of all the submission dates for this encounter. The bottom section provides the detailed information of what was returned for each of the submissions. Select a row in the top portion. The details related to that submission are displayed in the Details view in the lower portion of the screen.
The following columns are displayed in the top section:
Filters
Filters can be used to limit the results displayed to only those relevant to the current visit. The following filters are available:
Selecting any filter values causes the filters indicator to be selected. The specific filters selected are displayed to the right of the Filters check box. You can deselect the filters indicator for all values to be displayed.
Columns
Information in the eligibility transaction returned from the payer is displayed in the Details view columns and includes:
If an icon is displayed in the Comment column, select the icon to view the actual comment in the comment area below the Detail View table.
The Eligibility Details window provides the following information in the response:
The third view is Text view. The actual message returned from the eligibility transaction submission is displayed in this view. Press CTRL+F to search for text in this view.
HDX eligibility services use the industry-standard Accredited Standards Committee X12 (ASC X12) 270/271 transaction to communicate with payers. Although a standard format, important response information may be either hard to find or cryptic in nature. Payer-specific rule-based messages elevate important data and simplify complex response information. HDX writes and maintains rules using proprietary algorithms that evaluate payer-specific response data and produce the rule results that qualify. HDX can sequence these rules to display as the first benefits if the source does not have a specific means of displaying the rule results.
Rules-based messages benefits:
This functionality is generally available with the Cerner Millennium 2015.01.25 Service Release .
Task 130240 (RUN RevenueCycle Registration - Ability to accept demographic differences from the Eligibility Details dialog) is required to accept demographic updates.
Demographic and health plan information such as name, address, member number, and group number are displayed with the insurance verification response. Cerner eligibility checking compares that information with what is stored in Cerner Millennium for the patient .
With HDX Transaction Services, if any differences exist between the information submitted in the request and the information the payer has on file, an Insurance Demographics Differences alert is displayed. Select View to open the Demographic Differences dialog box. Information contained in Cerner Millennium is displayed in the Millennium column, while the response from the payer is displayed in the Insurance Response column. To update Cerner Millennium with the data received from the payer, select the corresponding Approve check box.
The following data is updated in the corresponding On File with Payer prompts in Cerner Millennium :
The following data is updated in the corresponding person-level prompts:
The following data is updated on the corresponding person-level or encounter-level prompts based on whether the submission was done at the person or encounter level:
The Update option is not available when a dependent's information is sent to the payer in the 270 transaction, but not returned in the 271 transaction.
The demographic differences are only compared with the patient's Cerner Millennium information. If the patient is a dependent, the demographic differences are for the dependent and not the subscriber.
For home address differences, you can add the address as a new address or modify the existing address stored in Cerner Millennium . The Add option sets the end-effective date on the current address and adds a new address to the database. The Modify option updates the existing address in the database and does not add a new address entry.
Select Confirm to write the selected demographic differences to the database and update the Eligibility Details view with the new information. Select Cancel to discard the changes and not make any updates.
You can use verifications fields as a way to inform the user if eligibility was viewed and ran successfully.
Verification fields can be configured in the following ways:
With this method, the request is submitted using an Operations job, and the verification fields are blank (verification status, verify date, verify source, verify personnel). When the eligibility response is returned, the verification status is automatically set to Verified or Follow Up in the following scenarios:
When the verification status is valued, the following fields are also valued:
When eligibility has been run and verification fields are valued, and the eligibility request is submitted for a second time using an Operations job, eligibility response is returned. The verification status, verify date, verify source, and verify personnel are updated if the value for verification status is different from the first response. I f the verification status is determined to be the same, none of the verification fields are automatically updated.
With this method, the user submits the request manually, and the verification fields are blank (verification status, verify date, verify source, and verify personnel. The verification status is automatically set to Verified or Follow Up in the following scenarios:
When the verification status is valued, the following fields are also valued:
When the verification status fields are valued and eligibility is run again, t he verification status, verify date, verify source, and verify personnel values are updated only if the value for verification status was originally Follow Up and the new value is Verified.
Otherwise, the verification status fields are not automatically updated.
Verify status is not populated for a transaction that results in an error. No value set in the Verify Status field is equal to not verified.
Once Eligibility is returned, all benefits will automatically post to the Insurance Benefit table in Revenue Cycle.
Complete the following steps to manually add a benefit:
When you submit an eligibility request for all health plans, the system checks for a cached response. If a cached response exists for any of the health plans, the following message is displayed: One or more health plans has a cached eligibility response. Are you sure you want to submit a new transaction for those health plans that have a cached eligibility response? Select Yes to submit a new eligibility request for all health plans and override any existing cached responses. Select No to submit a new eligibility request for all health plans that do not have a cached response and to return the cached response for all health plans that have a cached response.
Caching is configurable through a service request to the Cerner Transaction Services team. The option to use a cached response only exists when the previous eligibility request returned an Active response.
The eligibility queue tracks all the transactions. Multiple filters are available for the queue and the default display shows the transactions with a status of In Error. From the queue, you can resubmit the transaction and access the visit so you can see all the information and track the status as you are working with the transaction.