Consent Migration
This process should be run on your SCR go-live day or for existing practices immediately following upgrade to SCR 2.1. The Consent Migration upload sends all patient dissent Read codes stored in Vision 3 to the Spine. It also performs the following changes to the local record:
- Change legacy Read codes to the New Codes.
- For patients with an existing SCR on the Spine, but no consent record locally, Implied Consent 9Ndl. Implied consent for core Summary Care Record dataset upload is added. Note - For patients with 'Dissent' recorded on the Spine but not in Vision 3, no ACS upload is sent. When next selected in Consultation Manager the patient will have an ACS mismatch. This must be resolved to ensure no SCR updates are sent for dissenting patients.
Patients with no existing SCR on the Spine and no consent preference specified by the patient, Vision 3 assumes implied consent. This displays in the local record as "No Preference Expressed". The patients SCR will contain Core data only.
The patients consent is then checked each time the patient is selected in Consultation Manager as part of the patient synchronisation criteria. If the patient has dissented, but there are differences between the spine and the local record, an ACS mismatch message displays and must be resolved.
Patients with the original legacy Read codes for consent, used in the initial version of SCR, are converted to the new codes during the Consent Migration process, the new dissent Read codes are then updated to the ACS.
The details are:
|
Consent Status |
Local Legacy Read Code |
New Read Code following Migration |
|
Legacy Dissent |
93C3. Refused consent for upload to national shar electronic rec |
9Ndo. Express dissent for Summary Care Record dataset upload |
|
Legacy Consent |
93C2. Consent given for upload to national shared electronic rec |
9Ndn. Express consent for core and additional SCR dataset upload |
