...
The patient record continues to exist and existing data is retained.
New data can continue to flow from anywhere to PKB (via HL7/REST/UIthe UI or an integration)
The patient can continue to access data and edit their own data (, including privacy labels)
The patient If the patient has an email address, they will continue to receive email notifications when their data is updated (if an email address is recorded)
There is absolutely no sharing of data between teams
The patient record is not accessible to new teams (including via Break the glass)
The patient is removed from all teams and the , individual professionals, and carers that they were sharing with.
The patient is no longer searchable at the team level (, but is searchable at the org organisation level)
In the organisation patient search list, the action ‘Add to my team’ underneath the patient name is no longer visible and is replaced with the message 'Sharing disabled'. The actions to reset password or remind to register remain.
Clicking the patient's name from the patient search takes you to the 'Team data view' of the patient’s record in the usual way. This means professionals can access the record but will only see data added by their own team. Data They will not see data added by the patient, users outside the team or from hospital feeds will be hidden.
No notifications are sent to the professionals to notify them of sharing becoming disabled.
All carers are removed from sharing - and no notification is notifications are sent about this. The patient continues to have access to people they care for.
All tabs under the Sharing page (except Friends and family sub tab) will only show the message 'Sharing has been disabled. For further details please contact the Privacy Officer'.
Action buttons no longer applicable will display the following warning message 'Sharing has been disabled. For further details please contact the Privacy Officer.'
A notification email is sent to the patient for confirmation (notification only, no action required)to confirm that sharing has been disabled or enabled:
Dear [patient name]
This is confirmation that sharing has been [disabled/enabled] on your Patients Know Best record by the privacy officer [privacy officer name] from [organisation name] as of [date of action].
...
Patients Know Best Help Team
No automatic reversibility (i.e. if patient re-enables sharing they If sharing is re-enabled for the patient, they will need to be manually re-added to teams and add their carers back manually)Patient should
The patient can still be able to be added as a carer, ask for access to a record and access the people they care for.
...
Via the User Interface - when 'Invite / add Add patient' button is used by coordinator or professional, the user will receive notification an alert on screen: 'Could not invite this patient as sharing is disabled'.
Via HL7 - you will not be able to add patients with sharing disabled to teams via hl7 HL7 using a ZTM segment in an A28 message.
You will not be able to add or update a patient’s consent to teams via REST if sharing is disabled.
Via CSV upload - Error information is returned if a record fails to be created. The bulk upload report will give the message 'Could not invite this patient as sharing is disabled'
What access is there via HL7 and REST?
All REST read access - will be disabled - , including BTG break the glass access
For all All APIs return the generic message 'Sharing disabled'
Write access for HL7/REST will continue.
...
Organisations can continue to post messages (encounters)
Professionals can no longer initiate new message threads or consultations.
Patients can no longer initiate new message threads, consultations or start discussions on data-points.
...
Is there an effect on custom integration flows (EMIS, NCRAS etc.)?
No changes as these These integration flows are write only, so they are unaffected by sharing disabled