Requirement Constraints

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 16 August 2013

Maintaining Patient Insurance

Posted on 00:56 by Unknown

How patient insurances are maintained  in the EMR/PMS software's ?

Today, software's are maintaining the patient insurance in difference ways. Each method has its own cons and pros. I will list those methods which i found in my past experience.

Before getting into detail, let us see the terms "Primary",  Secondary, Tertiary and 4th Insurance". In some software, instead of calling 4th Insurance, they will call as Quaternary Insurance.

Actually, there is no defined process or method to identify which is patient primary insurance , and which is patient secondary insurance, and so on. For more details, please download this article and you will know how it has been identified. Since there is no defined way, most of the time, reception people will enter the secondary insurance information into primary and vice versa. That's the reason, all the software's providing swapping option for the insurance

And also, we should know how secondary insurance billed and get paid. Please download this document to know more on that.

Now let us see how software's are maintaining the patient insurance.

Method 1:
Maintain 2 or 4 insurance at the Patient Level

Here you can always maintain 2 or 4 insurance at active state. Give important to the word "Active" here. But, HIPAA EDI 837 Transaction allow up to  11 insurance.  So what happens, at one point of time, the existing insurance get expired and patient got new insurance ? Well, you cannot remove  that insurance from the system it because it is tightly linked to Billing (Claims) Module. So only the option is to de activate the existing primary insurance and add new insurance in the active state as primary Insurance.

The advantages in this method is : Insurance are maintained only at one place i.e. at the patient level. So any changes done here, it will impact all the claims linked to that.  This might be useful when there is error in the data entry and after the correction, they want to re submit all the claims linked to that insurance.

And also, at one point of time, there will be huge number in the inactive state, and no idea which claims are linked to that.

But what happen, if the patient is coming for two different visit types : For example, you may have a patient that is being treated for injuries sustained   from an auto accident that is covered under one insurance policy; yet that same patient may receive treatment during the same visit for a condition    unrelated to the auto accident where a different policy may be billed. So in this case, you need to maintain two primary insurance dependent on the visit type.In the above method, it is not possible, so that is one of the disadvantage.


Method : 2

Another way is to clone the patient demographics insurance while claim is created and therein after maintain the copy of all insurance at the claim  level. 
 
In this method, initially, the insurance are maintained at the patient level. But when the claim is created, software will take a copy of all insurance and will maintain along with part of the claim details. So here, after the claim is created, the insurance at the patient level is plugged off and will not have tightly linked with the claim. If any error in the policy details, of course, first we should correct at the claim level and then at the patient level for error free future claims.

if the patient is coming for two different visit types, then we can easily handle here because, we need to change only at the claim level.

Method 3:

And final method is patient case. This method not only to maintain the insurance, but it can also provide a template kind of stuff to create same  kind of claim data for the same patient again  and again to save the time.

In order understand, simply you can think patient case is nothing but to maintain group of insurances.  Let us see detail now.

What will be in the patient case. ?

1. Patient case is by patient
2. Software allows to create N number of patient cases for each patient.
3. The following details will be maintained at the patient case

  • Referring Physician
  • ICDs and CPTs
  • Insurance (Here you can define upto 11 Insurance)
  • Insurance Authorization information for each insurance if available
  • ICDs and CPTs
  • For hospital type of visits, maintain different dates such as admitted date, discharge date, accident date, etc..

Creating individual cases for why a patient is being seen by a provider simplifies the selection of insurance policies and the order in  which two or more insurance plans may be billed for various types of treatment and conditions. For example, you may have a patient that is being    treated for injuries sustained from an auto accident that is covered under one insurance policy; yet that same patient may receive treatment during   the same visit for a condition unrelated to the auto accident where a different policy may be billed.
 
Creating individual cases for patient treatment also simplifies how paperwork and claims are processed when a case involves an attorney lien or    Workers' Comp claim. For example, you could have an existing patient that has been previously seen for an illness; and later sustains an injury at his    place of employment that may involve a worker's comp claim. How claims are handled for each of these two cases is quite different. In a situation like    this, you would simply locate the existing patient record; and then create a new case for that patient that covers treatment for his injury.

In this method, we can maintain different set of primary, secondary, etc. depending upon the visit types. And also, collecting insurance from the patient is handled by the front desk people and creating the claim for the visit handled by the back office people. So there is no idea for the billing people which insurance has to select on the claim, because they may not aware what is the purpose of the visit.

If we maintain case, then it is job of the front desk to select the case at the appointment level or at the check in level. Then this will be helpful for the billing team to generate the claim for the insurance for the selected case and send to the insurance company.

Happy Insurance Maintaining !!!!!!

Welcome to the Most challenging part of the Medical Billing !!!!

Interested to see some sample screen shots for Patient case ? Here you go.

        

Questions or feedback are always welcome. You can email me at vbsenthilinnet@gmail.com. You can hire me as consultant for EMR/PMS Domain and Web development on EMR/PMS Product!
Email ThisBlogThis!Share to XShare to Facebook
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • ZK Example for inline Editing with Add New and Delete
    I am quite impressed on this demo from ZK . But adding new record and delete existing record is missing as part of typical CRUD. So i thoug...
  • EDI 5010 Documentation 837 Professional - Loop 2010BB Payer Name
    2010BB Payer Name          In this loop, all the information will be taken from Insurance master screen. Take a look of our sample screen...
  • EDI 5010 Documentation–837 - BHT - Beginning of Hierarchical Transaction
    BHT – Beginning of Hierarchical Transaction Loop Seg ID Segment Name Format Length Ref# Req Value   BHT Beginning of Hier...
  • Hibernate Validator Example 2
    In this example, we will see some more validation constraints such as @email, @past, @length, etc. And also we will also define custom error...
  • ZK Passing Parameter between two files using MVVM–Part 1
    Overview This is the first series of articles about Passing parameter between two zul files using MVVM Design pattern .This article will fo...
  • MVVM Command annotation and Notify change example
    Here is an example, how to pass parameter on a zul through MVVM Command binding annotation. ZK URL http://books.zkoss.org/wiki/ZK%20Develo...
  • History of Present Illness
    HPI - One of the main component of Clinical History. What is an HPI ? The history of present illness (HPI) is a chronological description...
  • Patient Demographics
    Patient browse (search) is the key element for any EMR / PMS Software. In my past 15 years experience, i involved more than 5 times in desig...
  • ViewModel Class Java Annotation @Init, @NotifyChange, @Command
    In following sections we'll list all syntaxes that can be used in implementing a ViewModel and applying ZK bind annotation. The ZK binde...
  • Good Website Design Links
    Form Design Label Placement in Forms International Address Fields in Web Forms 40 Eye-Catching Registration Pages blog-comment-form-...

Categories

  • Billing Process
  • C Workbook
  • C++ Workbook
  • Eclipse Tips
  • EDI 5010
  • EMR Appointment Features
  • EMR Labs Stuff
  • EMR PMS Links
  • EMR Use cases
  • EMR Vital Sign
  • Good Website Design
  • Hibernate Criteria Queries
  • Hibernate Introduction
  • Hibernate Introduction Setup
  • Hibernate Mapping
  • Hibernate POC
  • Hibernate Validator
  • Hibernate–Java Environment setup
  • HPI
  • Java
  • Maven
  • MU Certification
  • NPI
  • PQRS
  • Practice Management System
  • Spring Security
  • Tech Links
  • Today Tech Stuff
  • zk
  • ZK Hibernate
  • ZK 5 Databinding
  • ZK Application
  • ZK Calling Another ZUL
  • ZK CheckBox
  • ZK CreateComponents
  • ZK CSS
  • ZK extended Components
  • ZK Foreach
  • ZK Forum Posts
  • ZK Framework
  • ZK Hibernate Setup
  • ZK ID Space
  • ZK Include
  • ZK Installation
  • ZK iReport
  • ZK Layout
  • ZK Listitem Pagination
  • ZK Message Box
  • ZK MVC
  • ZK MVC Combox Box
  • ZK MVC CRUD Examples
  • ZK MVC Listbox
  • ZK MVVM
  • ZK MVVM Combo
  • ZK MVVM CRUD
  • ZK MVVM ListBox
  • ZK Spring
  • ZK TextBox

Blog Archive

  • ▼  2013 (105)
    • ►  December (3)
    • ►  September (7)
    • ▼  August (13)
      • HL7 Parsing–My Own Parser
      • ZK Dropupload example
      • Hibernate Custom validator to validate Multiple em...
      • ZK List box inline Editing with Add New and Delete...
      • ZK Example for inline Editing with Add New and Delete
      • Patient Demographics and Patient cases
      • How to get Current Date and Time and store in the ...
      • Maintaining Patient Insurance
      • EDI Transactions
      • Health care Coding system
      • ZK upload PDF to server and show in the screen us...
      • ZK Quick InputBox
      • HL7 Parsing
    • ►  July (1)
    • ►  June (11)
    • ►  May (3)
    • ►  April (14)
    • ►  March (19)
    • ►  February (21)
    • ►  January (13)
  • ►  2012 (177)
    • ►  December (1)
    • ►  November (13)
    • ►  October (19)
    • ►  September (24)
    • ►  August (26)
    • ►  July (6)
    • ►  June (37)
    • ►  May (30)
    • ►  April (16)
    • ►  March (1)
    • ►  January (4)
  • ►  2011 (5)
    • ►  December (1)
    • ►  November (1)
    • ►  July (1)
    • ►  June (1)
    • ►  April (1)
  • ►  2010 (1)
    • ►  September (1)
Powered by Blogger.

About Me

Unknown
View my complete profile