| 85 | |
| 86 | == Duplicate Enrollments |
| 87 | |
| 88 | As of version 1.1.1 the Ice Messaging module: |
| 89 | |
| 90 | - Checks to see if a patient already exists within CiviCRM. |
| 91 | - If they do the new GENVASC enrollment will be associated with the existing patient. |
| 92 | - If the patient already has an existing GENVASC enrollment, the new enrollment will have **the same GPT number as the existing enrollment** and will have a status of **excluded**. |
| 93 | |
| 94 | == Address uploading |
| 95 | |
| 96 | As of version 1.2 the Ice Messaging module: |
| 97 | |
| 98 | - Uploads the address details from the PMI into CiviCRM. |
| 99 | - If there is an existing address in CiviCRM, the user gets to choose between the existing address and the PMI address. |
| 100 | - The post code of the chosen address will be used to populate the post code custom field on the GENVASC study recruitment record. |
| 101 | |
| 102 | === Work Instructions |
| 103 | |
| 104 | - If the patient does not exist in the PMI or their address is different from the one on the GENVASC consent form, the details from the consent form should be used to update Patient Centre. The PMI details on the ICE message can be updated by clicking the ''refresh'' button. |
| 105 | - The PMI look up only shops the patients main address. It is possible that the address on the consent form is in Patient Centre as a ''postal address'' - for example, if the patient lives abroad but is staying long term in the UK. In these situations: |
| 106 | 1. Process the ICE message using the PMI address. |
| 107 | 1. Add the address on the consent form to the patient's record in Civi and mark this address as the ''main address''. |
| 108 | 1. Update the post code custom field in their GENVASC enrollment to be the post code from the consent form. |