Handling medications in clinical medicine is difficult. One of the easy wins for information technology in medicine is electronic prescribing. Our colleagues in general practice have had such systems for many years but those of us working in hospitals have lagged behind.
In hospital, many of us prescribe on paper prescriptions – sometimes I use a proper prescription when I am starting a drug that is hospital-only – on most occasions, hospital doctors now write a GP communication note or simply add the recommendation to a clinical letter.
There is tremendous value in electronic prescribing. It is one of the quick-wins for information technology in healthcare. There are many advantages.
Advantages of keeping track of medications electronically
For me, keeping track of patients is critical. If you are non-medical, you might think that once you are under ongoing follow-up with a hospital doctor, there is some automatic system to let us know that you missed your last appointment or that your appointment was cancelled. In fact, you’d assume we also had a system to track your diagnoses so that we could potentially find all of our patients with, say, Parkinson’s disease. Sadly, this isn’t common; the way many clinicians handle this is to keep a spreadsheet with names and diagnoses or use something like the British Neurological Surveillance Unit (BNSU) to report rare cases seen.
I have a number of patients with a range of disorders on high-dose corticosteroids. Similarly, I have patients on other immunotherapy drugs (e.g. methotrexate) for whom I need to know that their blood monitoring is performed appropriately and that their blood indices are stable. For me, knowing a) who those patients are and b) when I last saw them, are critical for patient-safety. Too often, we avoid disaster simply through good fortune rather than any systematic approach to patient safety.
The PatientCare web application
Here in Cardiff, we now use a patient electronic health record system to track all such diagnostic, treatment, interventional and outcome data. I have been developing it since 2009 and we now have over 15,000 patients recorded. It is accessed across Wales, mainly for neurological diseases, but we also track a number of rare diseases. Many of these rare disorders are rare individually, but collectively, they are common! There is a sophisticated access-control mechanism into which groups of patients and groups of clinical staff are linked by virtue of clinical services or research projects, so that access is limited to the group of patients to which you are responsible.
Topics to be covered in future blog posts are information governance and how to implement SNOMED-CT. Both difficult but both solved!
Electronic prescribing and the NHS
To start thinking about electronic prescribing and recording of current and past medication, I suggest you first have a look at the NHS DM&D (dictionary of medicines and devices) and a good look at the implementation guidance. There are a number of complexities. In hospital, we are encouraged to prescribe using generic drug names rather than branded drug names. This means that “prescribing” is a distinct process to dispensing. In hospital, the dispensing is performing by a nurse on the ward and a pharmacist for outpatients. Dispensing turns the generic prescription into an appropriate formulation. There are a number of issues to consider during dispensing including differences between formulations (actual medicinal products – AMPs) and issues of cost. Most hospital doctors are not used to selecting appropriate formulations and instead prescribe by generic drug name and dose. A general practitioner prescribes using products. For more information on this,
For example, a hospital doctor may prescribe “ramipril 7.5mg od”. This means the patient should receive 7.5mg of this drug once per day.
A general practitioner would prescribe “ramipril 5mg 1 tablet od” and “ramipril 2.5mg 1 tablet od”.
There are additional complexities. For instance, some hospital clinicians wish to prescribe by product because of differences between formulations. For example, many of us who work with patients with epilepsy prescribe “epilim chrono”. While the active ingredient is sodium valproate, different products may vary in terms of bioavailability / absorption and so we would not want our patient’s medications to be swapped around – imagine a situation in which a generic formulation is substituted in a patient who is seizure free and the substitution results in a seizure when the patient is driving!
Another issue is that medication data is already held in general practitioner systems and so it should be possible to import that list of current and past medications into hospital systems automatically. Having different implementations / models of electronic prescribing in primary and secondary care complicates such automatic import and export of medications.
The NHS DM&D implementation guidance suggests a 3-step prescribing process for each drug. Step 1 is specifying the drug and the route (e.g. oral, inhaled, intravenous). Step 2 involves reviewing the rules for that specific drug and step 3 involves identifying appropriate sub-types of that medication for safe prescribing.
As you might imagine, this is quite an involved and potentially time-consuming process. However, prescribing is potentially dangerous and should be performed with caution and careful consideration. However, different degrees of rigour are required depending on whether the electronic record is acting as a prescription or simply an electronic record of what the patient is taking or an advice letter.
For example, in outpatient clinic, most clinicians will want to quickly record the current and past medications so that we can easily answer questions like “Which anticonvulsant therapies have we already tried in this patient?”. As such, the strict rigour of an electronic prescribing system can be relaxed depending on use-case.
I’ve implemented a system to rapidly enter an existing list of medications and make changes to that medication list. See PatientCare medication entry and Advanced medication entry for two video demonstrations. Here we enter a list of medications which are automatically mapped into SNOMED-CT DM&D drugs. There is a semantic understanding for drugs so that programmatically, we can tell whether a patient is on a thiazide diuretic or anticonvulsant – ie. this is not simply a free-text list! In addition, there is dose equivalence so that the system recognises that 1000mg is the same as 1g etc. Once the list is edited, the software calculates the changes – drugs changed, started, stopped etc. and then applies those changes to the longitudinal record of medication so that there is a complete list of all current and past medications that have been used.
There is a balance of speed and efficiency for expert users and hand-holding for beginners. As such, there is an older pick-list based system which allows users to add drugs manually using drop-downs controls. However, expert users should be allowed to follow a more efficient process.
This balance requires careful planning to ensure process safety and yet remain quick and usable in a busy outpatient clinic or in the assessment unit.
Not only do I now record diagnostic information for my patients (SNOMED-CT coding) but it is now feasible to record all current and past treatments. Such information is very helpful for a range of conditions including Parkinson’s disease and epilepsy.
In addition, because the software recognises that some drugs are unchanged, some have been stopped and some have been started, we can now automatically generate summary reports of encounters. This results in a huge reduction in administrative support requirements as rather than dictating medication changes, the computer does it automatically and in a well-presented summary.
I’ve just released the new version of the PatientCare application that contains this new medication functionality – this is available across NHS Wales. It is much better to have a rapid development lifecycle in which one gets early feedback on design, reviews early implementations and we iterate rapidly. By rapidly, I mean going from initial plans to mock-ups to an early version to this current (“finished”?) version within 3 weeks. I’m looking forward to more feedback from our other users.