Medicare Direct Entry workflow
When using Medicare Direct Entry (MDE)
Medicare Direct Entry (MDE) is a separate contractual add-on that allows a site to check eligibilty, transmit claims, and check claim status directly with the Medicare Fiscal Intermediary Standard System (FISS). Also called MDE. as part of your claim processing, there is no
workflow difference in how your claims are prepared on your HIS. The remaining
workflow steps are not very different from the standard product workflow.
You submit claims to Assurance; then correct errors and validate claims until errors are resolved; and then, you or the system sends the claims to the Medicare system.
The difference lies in the tools used to validate and send claims.
1. Submit claims
Submit Medicare claims in a standard UB claim submission file. During the process of validating and saving the claim, a bridge routine checks each claim for Direct Entry criteria such as the payer and claim type. The system sets the Direct flag on claims that meet the requirements. A Medicare Direct claim is validated against payer edits and saved in the database as an unreleased claim, either rejected or accepted. You can open these claims and correct the errors just as you do with other claims.
2. Check eligibility, check edits, and send claims
You can automate the work to check eligibility, check Medicare front-end edits, and send accepted claims. To automate the eligibility checks, you can activate them to run during bridging (claim submission) in the eligibility profile. To automate other work, create a scheduled Direct Entry auto list that contains modules for DE Check Edits and DE Send Claims processes. Schedule it to start about 10 minutes after your FI's connection window opens for the day. You can also add the Check Eligibility process to your scheduled auto list, if you need an additional check. Within the auto modules, use a filter that targets all unreleased Medicare Direct claims for the eligibility and edit check processes. Use a filter that targets all unreleased Medicare Direct claims with an accepted or warned status for the DE Send Claims process.
The direct claims that pass all checks will be accepted by Medicare and automatically become released claims. The key is the sequence of events. Check Eligibility and Check Edits must run before Send Claims.
3. Fix the errors
After Medicare accepts the clean MDE claims, you are dealing only with those Direct claims that contain Medicare errors or payer errors. When all the Medicare errors have been fixed, check Mark Direct Errors Worked. This lets other users know that the Medicare errors have been fixed and are just waiting to be rechecked. Fix the payer errors.
4. Recheck eligibility and edits, then send claims again
After the claims are as clean as possible, recheck the eligibility and
front-end edits before sending the accepted and warned claims to Medicare.
You can automate the recheck with an auto list.
5. Fix claims
As claims are processed, they can be opened, reviewed for errors, and corrected.
If, at this point, you
want to see a Medicare Reason Code for a troublesome error, accept
the claim despite the remaining errors by selecting the Accept
Claim with Errors checkbox in the top right corner of the UB claim
tab. This action marks the claim with an accepted status. Even though
errors remain on the claim, the system can now send it to the Medicare
FISS with no further work. The troublesome data will be evaluated
by Medicare. If the data does not meet Medicare's requirements, the
claim becomes an RTP claim and Medicare returns a
reason code to explain the issue.
6. Send claims
Schedule an auto list for the DE Send Claims process, and set it to run toward the end of your day inside the FI's window of availability. This will send the last of your accepted MDE claims for the day.
7. Check status
Set up a scheduled auto list that uses the DE Check Status auto module. Use a saved filter that gets Direct Entry claims that were released yesterday or two days ago. This process returns Medicare adjudication information on each claim. If the claim is a paid claim, the payment is saved and matched to the claim, available for review from the claim's Payer Activity tab. If the claim contained errors, the reason code is returned to the claim and added to the claim's status history. To find rejected or denied claims, look for released Direct Entry claims with a Local Status Code of 990. To find claims returned to the provider, look for released Direct Entry claims with a Local Status Code of 991.
That's the basic workflow!
- When checking status, add the auto modules you use to create secondary claims from matched remits. If Check Status finds a payment on the claim and returns enough information to create a secondary claim, the secondary will be created.
- If incomplete or disrupted jobs are common, create a scheduled auto list to do catch-up jobs.
- If you send Medicare claims through two FIs, you do not need double sets of filters and automated modules or lists. The claims are automatically grouped by FI and number of claims as the Direct Entry feature begins to run.