Chemist + Druggist recently published an article written by Healthcare Regulatory Lawyer, Susan Hunneyball.
In the article, Susan discusses the legal implications that need to be considered before giving pharmacists read-write access to patient records.
Read the full article below.
Giving pharmacists read-write access to patient records is an obvious next step, but there are legal implications that need to be considered beforehand, says Susan Hunneyball
“Inadequate records are a risk to everyone,” said Nigel Clarke, outgoing chairman of the General Pharmaceutical Council (GPhC), at the Pharmacy Show before urging the case for pharmacists to have read-write access to medical records.
The suggestion that pharmacists should have the ability to record in medical records (“write access”) has been a recurring theme in the last decade. On April 1, 2016 pharmacists were given read access to summary care records (SCR); this access is now part and parcel of the pharmacist role. In 2020, a requirement for consistent and reliable access was rolled out by amendment to the Terms of Service, and during the pandemic there was an expansion of the information that could be added to the SCR.
Before write access can be implemented, much needs to be put in place. From a legal point of view, first the terms have to be defined. The Specialist Pharmacy Service has commented, when talking about retention of patient records, that “the definition of the ‘patient medical record’ is unclear”. Read access was given for SCR only. There needs to be a decision on whether write access will be implemented for SCR only, SCR with additional information or shared care records across the board.
Changes to legislation may depend on the model adopted, but at the very least they will involve amending the NHS (Pharmaceutical and Local Pharmaceutical Services) Regulations 2013 to update the Terms of Service.
Professional conduct and standards will have to reflect the expanded responsibilities. There are already standards for those using records (for example the new version of the NHS Records Management Code of Practice 2021 was published last month), but will the GPhC follow the General Medical Council (GMC) and the Nursing and Midwifery Council (NMC) and issue specific standards on recording information?
The importance of contemporaneous records was recently highlighted in a challenge to the suspension of the registration of a cosmetic surgeon, where it was clarified that the first step in determining the facts of a case is to establish what contemporaneous records say before considering the evidence from a witness.
Clarification on information governance issues would be required and building patient trust to obtain informed consent would be important.
From a legal point of view access is, of course, not without its problems. Professional regulation cases seem to fall into situations where pharmacists should have looked at the records, but didn’t (eg out of hours dosage and strength issues) and where pharmacists shouldn’t have looked at records, but did (eg Data protection or information governance issues). There are also potential liability issues if the records are considered, but the information in them is not used appropriately. Liability and professional concerns will, of course, became greater with additional access. The GMC regularly scrutinises inadequate and inaccurate record keeping.
As pharmacists’ clinical role develops further and prescribing rights become widespread, the question of pharmacists having write access to medical records is an important one. It could be said that this is an inevitable next step, but before that happens there needs to be a conversation about the legal small print.
Healthcare Regulatory Lawyer
D.D: 01483 366064
Tel: 01483 451900
Email: susan@gordonsols.co.uk
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
ypsession | 1 month | Yumpu sets this cookie to store a unique ID string for each chatbox session. This allows website support to see previous issues and reconnect with the previous supporter. |
yumpu_slc | 7 days | Yumpu sets this cookie to determine the preferred language and country setting of the visitor. This allows the website to show content most relevant to that region and language. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_ga_6K1Y9P2WGY | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gat_gtag_UA_133165545_1 | 1 minute | Set by Google to distinguish users. |
_gat_UA-* | 1 minute | Google Analytics sets this cookie for user behaviour tracking. |
_gat_UA-133165545-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies store information about how the user uses the website to present them with relevant ads according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
AVPUID | 1 year | No description available. |
SESSION | session | Description is currently not available. |
ypsitetrack | 1 year | Description is currently not available. |