Duplicate Provider Result Tasking

Duplicate Provider Result Tasking

Postby KISMITH » Thu Mar 28, 2013 4:09 pm

We have a provider, let's say Dr. Test that is in the TW provider dictionary. This provider worked at our clinic. Then, left to go work at a hospital that we interface with. Let's say the hospital provider's name is Dr. Test - MPS. In TW provider dictionary would have the following entries:

EntryCode IsInactiveFlag NPI
2076 N 1234567890 This would be Dr. Test
2094 N 1234567890 This would be Dr. Test - MPS

We have to leave both of these active for 90 days in case a result comes back that was ordered before Dr. Test left the clinic. In this case the result should get tasked to the provider code of 2076 (Dr. Test). The script looks for active providers in the TW Provider SQL table based on the NPI. It just returns the top 1. Due to this issue the task goes to the wrong provider (2094 - the new code).

Has anyone encountered this issue? Any suggestions on how to fix this?
KISMITH
 
Posts: 25
Joined: Thu Apr 14, 2011 7:54 am

Re: Duplicate Provider Result Tasking

Postby tsuacci » Thu Apr 04, 2013 10:47 pm

Hi Kim,

One solution that I can think of is to customize the map to force the use of the provider's EntryCode, rather than NPI. Build the mapping customization with a t-table so that you can easily add/delete providers from using the logic.

For example, build a t-table called HospitalCustomProvider with an input of NPI and an output of Provider EntryCode and "C" (to denote the use of the EntryCode) concatenated with a pipe.

Input Output
1234567890 2094|C

In your result mapping, change the ProviderIn logic to lookup the NPI in the HospitalCustomProvider t-table and grab piece one based on pipe ("|"), otherwise use the current NPI mapping. For the ProviderForm field, lookup the NPI in the HospitalCustomProvider t-table and grab piece two based on pipe ("|"), otherwise use the current 'P' mapping.

Now, whenever you receive a result for 1234567890, the FileResult call will file to provider code 2094. After 90 days, or whenever this needs to be removed, simple delete the entry from the t-table and cycle the target system.

If you have any questions about implementing this, fell free to contact me.

Thanks,
Tyler
Tyler Suacci
Consultant
Galen Healthcare Solutions
707.335.4710
tyler.suacci@galenhealthcare.com
tsuacci
 
Posts: 55
Joined: Mon Apr 04, 2011 12:08 pm


Return to Order/Result

Who is online

Users browsing this forum: No registered users and 1 guest

cron