TARGET Update for February 2006 |
|
Update Archives |
Client CombineThe client combine function is now available in TARGET. This function allows you to merge client records so that information that was erroneously entered as belonging to two clients can be combined into one, accurate client record. For Example: An assessment is entered for “Joe S. Client”. An admission is entered for “Joe Some Client”. Since the name information is different TARGET views this as two separate clients and when you search for “Joe Client” both names show up. To avoid confusion as well as for accurate record keeping you might consider combining these client records. To Use the Client Combine Function:
All of the information for client 2 is now listed under client 1. If there was a reason why the clients could not be combined then that will be displayed and the merge will not take place. Very Important Questions to Ask: Can I reverse the process if I make a mistake?
What information is combined?
We have more than one branch. What if the client is listed incorrectly at more than one location?
I have a client that is listed incorrectly five or six times. What do I do about combining them?
I am getting an error message. How come it is not working? Like everything else in life there are some rules. Here are the rules for the Client Combine function:
What is happening behind the scenes? In TARGET all events are linked to a client by a “client identifier”. You can view this identifier at the bottom of the Client Master screen. What the Client Combine function does is replace all the instances of the identifier for client 1 with the identifier for client 2. All milestones and activities are therefore now associated with client 2. Client 1 should no longer appear in your searches. I thought of some more questions. Where do I turn for help?
DowntimeThe TARGET system is typically not be available the last weekend of each month from 5:00 p.m. Friday, through 8:00 a.m. Monday. The dates for this month are: February 24th thru the 27th. |
| Modified:
April 03, 2009 Privacy Notice |

