Re: How to merge 2 customers into 1?

Hi John,

I've seen this problem and solution in all of the hospitals I've done work for.

The problem is, a patient may be admitted to the hospital without giving or being able to give complete information, so a new record is created in the interests of expediency. Later, more information is obtained, and they are able to match the patient information with a previously existing record in the database. At that point, they are able to merge the records.

And because the capability exists, some admitting personnel apparently think it's easier to simply do a new record than do a search for the existing record. And in fact, privacy issues may have made it seem safer to let someone who's not under pressure to provide patient care take care of the search & merge.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /



On 5/6/2010 5:33 AM, jmckay@xxxxxxxxxxxxxxxx wrote:

First, it all depends ... on the file and record structures. A very simple
solution would be to delete both and start over again.

Second, I would the application system so that this cannot happen again.

Regards.
John McKay,
www.rpglanguage.com



Original Message:
-----------------
From: David FOXWELL David.FOXWELL@xxxxxxxxx
Date: Thu, 6 May 2010 14:16:58 +0200
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: How to merge 2 customers into 1?

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Rory Hewitt

It sounds from the other responses that commitment control
would be the way to go. However, I'd like to know how long
this process has been in place and how often an error occurs.

Rare. The error was related to the EXECUTE problem I posted on midrange-L.
We aren't looking to change anything, I thought that the task must be a
common one and I wanted to read about other shops' implemented solutions.
What does the user do when he realises he created different records for the
same person?