Description
The program RNJOIN00 merges patients who have been entered twice in thesystem with their institution master records, cases, insurancerelationships, and risk factors.

Precondition
Enter the institution and patients that are to be merged in theselection screen. You can also search for a specific patient using thepossible entries pushbutton (F4).
You can simulate the merging function by setting the Test Modeindicator. In this case, no changes are made to the database. When youwant to execute the function in an update run, the system informs youthat you are in test mode. If you want to execute the function in testmode, please set the corresponding indicator.
Normally, you can only merge patients who do not have any open orcleared items in Financial Accounting. This restriction applies to thepatient who is deactivated as a result of being merged. If you also wantto merge patients with cleared items, deselect Include Cleared Items
. This can, however, result in the following situations in thesubsequent processing:
For the active patient, the system now contains invoices that refer to acustomer that is no longer used. If you cancel the original invoice, thesystem also makes a posting to the original customer. If you then renewthe billing run for the case, the system carries out billing for thecustomer of the current patient. The postings are distributed to twocustomers and the balance of each individual customer is inconsistent.
Possible procedure:
Lock the customer in Financial Accounting for postings. This preventspostings inadvertently being made to the original customer. If suchactions as described in the above example should become necessary, youcan temporarily unlock the customer, make the postings, and then makeany necessary transfer postings in Financial Accounting.

Output
The data of the two patients is listed side by side in an overviewbefore the patients are merged. This information includes the name andaddress of the patients, the institution master records (if you have setclient-wide patient identification in your system), the cases, theinsurance relationships and the risk factors. You can then merge thepatients by choosing the Merge function.
The two patient numbers are displayed again in the Patient Mergedialog box for you to check. Here, you can choose which patient is toremain active in the system and which one is to be deactivated. Thesystem outputs an error message if the patients you have chosen cannotbe merged. This is usually due to open or cleared items (if you haveselected the Include Cleared Items indicator) in FinancialAccounting.
You now execute the Merge function a second time and an overviewof the data for the patient who remains active is displayed. You canthen merge the two patients with the Merge function. An errormessage is issued if you have selected Test Mode on the selectionscreen.
Once they have been merged, the cases of the inactive patient areassigned to the active patient. The institution master records,insurance relationship proposal pool, and risk information are alsocopied.
The patient who is deactivated is canceled when the patients are merged.
Particularities of procedure concerning self-payer customer:
If the patient who remains active has a self-payer insurancerelationship with customer in the insurance relationship proposal pool,this customer is retained. If the patient who remains active does nothave self-payer insurance relationship nor a corresponding customer, thesystem copies the information from the patient to be canceled.

• Scenario 1

Patient 1 (remains active): SP IR with customer 123
Patient 2: SP IR with customer 456
In accordance with the previous logic, the system no longer uses thecustomer 456 in the insurance relationship after the patients have beenmerged.

• Scenario 2

Patient 1 (remains active): no SP IR
Patient 2: SP IR with customer 456
Previously the system issued the error message First create aself-payer IR for patient 1. When you merge the patients, the systemnow creates a new entry for a self-payer insurance relationship withcustomer 456 in the insurance relationship proposal pool.

• Scenario 3

Patient 1 (remains active): SP IR without customer
Patient 2: SP IR with customer 456
When you merge the patients, the system copies the customer 456 into theself-payer insurance relationship of patient 1.