UKGovcamp and NHS Hack Day: a fortnight of fab

Two great events in two weeks. A proper good start to the year.

On the 18th January 2020, I attended UKGovcamp 20 in London at the Ministry of Justice offices in London. The following weekend on 25th and 26th January, I helped run another NHS Hack Day at Cardiff University. They were both great.

UKGovcamp 20

It was UKGovcamp last weekend (Saturday 18th January), hosted again at the excellent Ministry of Justice offices in London. This was my third UKGovcamp, and many of us will be looking forward to next year’s already.

UKGovcamp is always a nice event. There are many more emphatic adjectives that people could use to describe the event: enlightening! emboldening! refreshing! inspiring! All totally valid. It’s also just really nice, and that’s really why I keep going back.

The effort put in by the organising team is obvious – it’s a confident event, and is slickly run. Being involved in organising events myself (NHS Hack Day and UK Health Camp), I have learned first hand that it is easy to underestimate how much effort it takes to make things look calm.

Amanda Smith was a great host – I was definitely watching and learning. The whole team are supportive of each other and this sets the tone for everyone.

Photo taken from behind the audience at the pitching session at UK Gov Camp. Many audience members have their hands raised to indicate their interest in the pitched session.
Photo by @mattstibbs / CC BY-NC

Every year, there’s an increasingly strong focus on diversity, accessibility, and inclusivity. Irrespective of whether you personally care about these things (although most of the people at UKGovcamp value them highly) – we all feel the benefit of them being such a focus.

I pitched a session, which was a first for me at UKGovcamp. It’s not the first time I’ve had to talk to a room of people, but it still scares me and I get very worked up about it! I’m glad I pitched, though.

It started as a bit of a niche topic, which I was attempting to open out into a discussion that was more widely revelant and applicable to people outside of health. I didn’t quite manage to pitch it like this, but we had a decent number of people in the room and everyone had something to say.

I felt that I was among friends for my session. Though it was niche, the whole room were actively involved in the conversation, and that’s testament to the sort of supportive, inquisitive people that UKGovcamp attracts.

It did make me appreciate the skill in putting together a session pitch that is well thought through, and designed to be inclusive and engaging. It’s certainly not mandatory to have prepared a session, but it can make experience even better for people and those are the sessions which often live on for people after the day.

I’m looking forward to applying for a ticket next year ūüôā


NHS Hack Day #23

The following weekend, I was part of a team running NHS Hack Day #23 in Cardiff. I’ve been involved with NHS Hack Day for a few years now (initially as an attendee, and more recently as an organiser). Anne-Marie Cunningham, a GP and health informatician by day, led the Cardiff event. She’s also a great host.

NHSHD_25Jan_026
Photo by paulclarke.com / CC BY-NC

I love NHS Hack Day ‚ô•ÔłŹ

NHS Hack Day shares many of the values of UKGovcamp (and the community around it). It too is a community event, run by people in the community, for other people in the community. It too is an event that is entirely dependent on the attendees for its success! And it too is an event that is much easier to enjoy when the organisation is calm and clear (which takes a considerable amount of effort to enable).

Cardiff #23 was excellent – maybe one of the best yet. We had over 115 people, 28 initial pitches; 18 projects made it through to the presentation stage at the end.

We live-streamed the presentations on YouTube and had over 20 people watching at one point – this was very encouraging and we will certainly continue to put the effort in to streaming in future.

NHSHD_26Jan_066
Photo by paulclarke.com / CC BY-NC

It also meant we could record the presentations, which are now all published on the NHS Hack Day website. You can also find the videos on the NHS Hack Day YouTube channel.

As always, the results from a little over 12 hours of hacking were amazing. Genuinely impressive. I always get halfway through the presentations and think “I wish people from all over the NHS were watching this right now.”

People might assume that most of the ideas people pitch are from ‘tech bros’ who want to solve the NHS with ‘Uber for dentists’. In our experience this simply isn’t true (well maybe one or two ‘fillings via the blockchain’ pitches) – the overwhelming majority are real problems from real people.

Clinicians present problems they suffer on a daily basis when trying to do their jobs; patients present problems they experience in accessing their own data, or in managing their own care.

Here’s real magic though: often people pitch these problems with relatively low expectations of what will happen. “I’m afraid I can’t really help to build anything – I’m just a clinician” or “I don’t really know how far I can take this problem because I’m really not techy.”

These are some of the best candidates for successful projects – with these problems, you get a team forming around the actual user with the actual problem. Many might not realise it, but this is basically a dream come true for any product team trying to build something that useful. It’s actually more interesting to join a team where the person hasn’t already solved the problem.

I’m going to write something separate on how NHS Hack Days (and maybe hack events in general) are actually an unintentional ‘neutron star’ of modern product development principles – densely packing, into one weekend, many of the behaviours we spend months trying to enact in our ‘real jobs’.

We’re doing two more NHS Hack Days this year: one in Manchester on 6th/7th June and one in London in the autumn.

There’s a lovely set of photos here taken by Paul Clarke (paulclarke.com). (Separate album for second day).

You can sign-up to the mailing list on http://nhshackday.com/ or follow https://twitter.com/nhshackday for more news about those events.

UK Health Camp is a spin-off from UKGovcamp focused on the health and care sector. You can find out more at https://ukhealthcamp.com or follow https://twitter.com/ukhealthcamp.

You can find out more about UKGovcamp on https:/www.ukgovcamp.com or follow https://twitter.com/ukgovcamp

What a fab fortnight ūüôā

NHS Digital consults the public on data and tech

Recently, NHS Digital has published two public consultations that are of broad public interest and deserving of comprehensive feedback. They are looking to define principles and standards for the use of NHS technology and data.

I’ve summarised and linked to them below in the hope that you will take a bit of time to take part.

Continue reading “NHS Digital consults the public on data and tech”

The Zen of Interoperability

I was having a discussion with a colleague this week about architectural options for some specific interoperability use cases we are tackling.

The conversation touched on implementation choice – how much flexibility should there be in how to approach specific interoperability use cases within the NHS?

I’ve thought about this quite a bit, and struggled with the complexity that “many ways to do the same thing” can introduce. I naturally found myself quoting¬†PEP 20 ‚ÄĒ The Zen of Python | Python.org.

Specifically:

There should be one — and preferably only one — obvious way to do it.

Could this be a reasonable principle for us to take with NHS interoperability?

I wonder if there is a place for “The Zen of NHS Interoperability” – to define some guiding principles for all of us working hard to make interoperability useful for the NHS.

Here is a slightly tongue-in-cheek attempt at a “Zen of NHS Interoperability” ūüôā

The Zen of Interoperability

Elegant is better than messy.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Open is better than controlled.
But controlled is better than proprietary.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you designed it.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Clear Standards are one honking great idea -- let's have more of those!

NHS Hack Day 17 – Manchester

"NHS Public Data" team

I have just spent the weekend at NHS Hack Day in Manchester, hosted by the Co-op in their new tech hub The Federation.

I wrote this blog post with the primary intention of sharing with my colleagues in NHS Digital to hopefully encourage some more people to get involved – but I don’t think there’s anything here that doesn’t apply to everyone.

It was a brilliant weekend, and there was a super mixture of people there – plenty of healthcare professionals, IT¬†professionals, some senior management types (CIOs / CCIOs), general “techies” (professional, aspiring, and amateur), researchers, and¬†a lawyer.

"Mobi-Alert" team

What’s NHS Hack Day like?

For those who aren’t familiar with¬†NHS Hack Day, it goes something like this:

The event runs 9-5 Sat and Sun

Lunch is provided on both days and hot drinks are available throughout.

Saturday morning is spent using coffee to recover from the work week, chatting with people, and pitching ideas.

Pitches are 2 minutes each and you can pitch anything from a solid idea to an open-ended question (this time we even had someone who wanted to create a sci-fi story about healthcare in the year 2100).

Most people are nervous

Some people only decide to pitch an idea whilst watching the other pitches – the team that won last weekend only decided to pitch after getting confidence from the other pitches.

After pitching everyone has some time to go and talk to the pitchers, explore the ideas, and gradually¬†teams are formed around the¬†projects. Sometimes ideas are merged together,¬†sometimes they’re split off into smaller projects.

The rest of Saturday, and most of Sunday is spent working on projects 

Different people work in different ways; some teams like to stick the headphones on and just chip away at a problem and others will spend a lot of time working through problems interactively. 

Sometimes people start building software etc.¬†in the first hour, sometimes people don’t build at all.

On Sunday afternoon teams decide if they would like to present their project to everyone else – and if so submit their projects

This is completely optional, but it feels good and is encouraged – the community is friendly and rarely does a team not present something.

"Trendy" team

At about 15:30 everyone gets together and watches presentations

Each team gets 3 minutes to present their work, and 2 minutes to answer questions.

I’m always amazed at what people have managed to prepare¬†– last weekend we had a Fresh Prince¬†rap from one team, and a promotional video from another…

I had several conversations with people where they were not sure where they were expected to be in terms of progress at various points through the event. Superbly, there is no right answer.

The presentations are one of the most enjoyable bits for me Рand last weekend had me smiling throughout every single presentation. There were so many great ideas, and every team had something interesting to show.

Teams will present anything from some paper mockups and a bit of narrative through to a fully working product with audience participation Рit is dependent on the type of project, the team, and how good people are at getting up on Sundays mornings.

IMG_0030

After presentations, there is a short period of evaluation where either a panel of invited judges, or the community, will vote for the top three projects – and those teams are given some prizes

We tried a new approach to voting this time where the community was given 3 votes each to vote for the three projects they were most excited by. We trusted the community to not vote for themselves, and to only vote three times – this simply doesn’t need policing.

People then help put the borrowed space back to how it was found, and head home feeling enthused ūüôā¬†

The last 30 mins is spent clearing up, saying goodbye, exchanging contact details, plotting world domination, and just generally wrapping up an enjoyable weekend.

170716-DSCF2913.JPG

Why should I care?

If you’re thinking “well I’m sure you all had fun, but does this matter to me?”, here are a few of my thoughts:

There is absolutely no ‘right skill set’

In fact I shouldn’t need to explain that diversity always wins and this certainly includes diversity of skills.¬†¬†The¬†best outputs come from the teams with the most diversity, and there is no buzz quite like¬†building something with a diverse team of techies, healthcare professionals, artists,¬†and users.

On our team, we were all learners in one way or another so a large amount of our time was spent pairing, learning, explaining, and discovering Рthis is just as rewarding as having something shiny to present the end of it.

This type of event is unconstrained thinking at its absolute best

As an embittered and tiring NHS technology person, I go to these events to recharge my batteries. This kind of community is not subject to the organisational, political, and learned behavioural constraints that many of us are.

It’s incredibly rare¬†that¬†a¬†pitch is binned¬†because “we’ll never get it through the¬†<insert your favourite bureaucratic restriction here>¬†process” – people are there to busk and solve problems. The concept of a political mandate, or a¬†4:1¬†return on investment¬†simply isn’t important here.

The ideas and outputs from these events are a map for the future

Maps are so useful – we are all pretty convinced of the benefit of roadmaps, and visions, and Google maps.

The ideas at these events give us a clue about what is around the corner for NHS technology. Many people at these events are recently qualified healthcare professionals, or are maybe only involved with NHS technology as users and see this as an opportunity to have a voice.

The things they want, and¬†expect,¬†are clues – to what we should be thinking about, to where we should be going, and to where we’re falling short.

It helps prove that the centre can engage, listen and help

Do not read subtext into this – I am¬†not saying “NHS England / NHS Digital never engage with the community”.

But it should not raise eyebrows at these events when one says that they work for NHS Digital, or NHS England – people are, but shouldn’t be, pleasantly surprised.

Last weekend I think I counted the number of attendees from NHS England / NHS Digital on one hand – I’d love to see this go onto two hands.

People are enthused to see us there, and actually we can be really helpful as¬†guides, navigators, and mentors. It encourages innovators just to know that we’ve considered it of value to take time to be there.

It’s not just about AI and mobile apps – people solve fundamental¬†problems too

One of my favourite projects from last week: FastPass. A team of seasoned IT support professionals who were determined to sort out the drag of password resets Рboth for support staff and users. They built a working system for self-service password resets and they intend to take it forward within their local NHS trust.

My team tackled the challenge of collecting timely feedback from users of NHS services at a scale that would produce enough data to be significant.

Real problems, not flashy, that could genuinely make stuff better.

IMG_0025

In conclusion

Next time there’s an NHS Hack Day near you, try and get along – if only for one day.

If you don’t like it then fair enough.

But you might do, and you might find it leads to you bringing a better, more energised self back into work the following Monday Рand that can only be a good thing for your own organisation, and the NHS.

Visit http://nhshackday.com/ for more information, or follow @NHSHackDay on Twitter.

If you are interested, and would like to ask some questions feel free to drop me an email at matt@stibbsy.co.uk or @mattstibbs on Twitter¬†– I’d be really happy to tell you more.

Appointment booking in Urgent Care

Introduction

This is a collection of my thoughts about the challenge of improving appointment booking within the urgent and emergency care sector. It has a fairly technical focus and may well lack context for people not so familiar with the field.

I also want to explicitly acknowledge that this post does not examine user needs in detail as it was originally intended to support technical consideration – it doesn’t replace or negate the need for properly understanding the needs of users both professional (within the NHS) and public (users of the NHS).

Some background

Out of hours care has always had the concept of appointment booking for patients that need contact with a clinician from an out of hours service – this could be a face-to-face appointment at a local out of hours centre, or an appointment for a telephone consultation with a clinician (although this tended to happen less).

Prior to the introduction of NHS 111, out of hours care was generally provided locally (i.e. a patient would contact an out of hours service local to their area), and so booking of appointments was handled internally within the same organisation or with local arrangements between specific nearby services.  In the majority of cases the transactions would all happen within the same IT system.

NHS Direct was a service that operated at national scale, but they did not offer appointments for patients; you would either receive a callback from a nurse, or NHS Direct would pass your details through to your local out of hours service which would then make contact with you.

With the introduction of NHS 111 in 2013, urgent care in England moved to a ‘national service delivered locally’ model. This model made use of national telephony infrastructure to route telephone calls to 111 through to different call centres around the country. In the vast majority of cases, 95% of 111 calls would be routed to a NHS 111 call centre close to the location of the caller using either an approximation of the landline location, or an approximation of a mobile phone using mobile mast triangulation.

Call demand on NHS 111 is incredibly ‘peaky’ – you can see this from the openly available monthly datasets that are published by NHS England. Particularly busy times for urgent & emergency care are long weekends (e.g. bank holidays), Easter, and Christmas / New Year – this is a well understood demand pattern in the NHS.

The challenging aspect of these few ‘super peaks’, however, is that they are several order of magnitudes larger that the regular weekly peaks (which general happen on Saturday mornings around 09:00 to 11:00). In terms of managing and planning for demand, this poses an immense challenge for services for whom simply ‘getting all of your staff in’ isn’t guaranteed to cover it.

An advantage of the national telephony approach is that it allows NHS 111 to distribute incoming calls flexibly across the country – this provides significant contingency for a range of situations (be it a particularly high demand in a particular region, or maybe a significant incident inhibiting the ability of a particular region to handle the local demand).

How does this relate to appointment booking though?

One impact of moving to the national service model is that it introduced a separation between the services handling telephone calls, and the services providing the appointment-based care to patients; in most situations this means separate IT systems are used too.

NHS 111 has been making good use of nationally-standard interoperability since its inception – this allows services to provide safe clinical handover of a patient between services (i.e. an NHS 111 service handing a patient over to an out of hours service so that they can provide further clinical care), however to this date there is no national standard defined for appointment transactions.

The supplier market responded to the gap by building appointment booking interoperability solutions for their customers which augmented the existing nationally-defined clinical handover interoperability – these solutions fill an important gap and several years on these solutions are used fairly widely both within the urgent care sector (e.g. between NHS 111 call centres and other urgent care services) and more recently between urgent care and general practice (GP surgeries).

Existing capabilities

The existing proprietary solutions are already becoming more widely deployed, and will continue to be deployed more and more as the urgent care system moves towards its aspiration of facilitating appointment booking into services for all patients (see the Next Steps on the Five Year Forward View or my precis of the urgent care specific elements of the FYFV). Given the relatively short timescale of the FYFV aspirations, and the fact that we don’t yet have a broad enough, nationally-defined standard for appointment booking interoperability using proprietary solutions in the short term remains a valid option.

There are some limitations to the existing proprietary solutions, and there is a common list of issues and gaps that service providers have started to identify. Some of the limitations are with the implementations themselves often relating to them being specific to individual IT systems (this is understandable in where solutions have been driven by the competitive market and have grown organically), other issues are related to the fact that there is some coordination needed across different services and regions which cannot realistically be provided by market-led proprietary point solutions.

Implementation of proprietary solutions could also increase the implementation cost in the long-run as it generally involves licensing on usage which attracts a cost to the users. There is also a coordination overhead that comes with the rollout of any proprietary point solutions. Having said that, the ROI is still considered to be favourable for investing in these existing capabilities in order to move interoperability between services on from where it is now.

Existing interfaces generally provide the ability to query slots of a destination service, pick an empty slot for a patient, and book an appointment into that slot. In some cases it is possible to change or cancel that appointment whilst still within the initial booking journey. Some systems have integrated the appointment booking transaction into the wider urgent care workflow, linking the appointment directly to the clinical handover (using the CDA documents that are sent between services). The official Integrated Urgent Care CDA messages have a section that allows systems to embed appointment reference details for the purpose of linking up with appointments within their system. There is a mixture of business rules applied by the various systems involved that guide how appointments can / can’t be booked, and what data items are required to do so. Some suppliers have attempted to build on top of existing proprietary solutions to avoid further divergence but this does mean building on top of existing limitations as well.

The biggest gaps are currently:

a) a lack of clearly defined appointment booking workflow that can be applied consistently across all services

b) a lack of an appointment repository / index that allows services to easily find out if and where a patient already has an appointment booked

c) a lack of business rules around how appointment booking should be handled when happening across regional borders (introduces financial, political, and accountability challenges)

So what comes next?

System suppliers and service providers alike have asked for standardisation of the appointment booking specification for urgent care and emergency care (note specification covers both an API specification and the associated business processes that support it).

There are a number of benefits from standardising the specification:

  • it will reduce the implementation cost for both system suppliers and service providers through use of configuration over installation, and less variability related to the IT systems in use;
  • it will introduce consistency of workflow across services and therefore ultimately improve consistency of experience for the users of the services (i.e. patients)

What about the existing systems like eRS and GP Connect?

System suppliers have been very clear that in order to realise the benefits of standardising the interoperability for appointment booking it is important that we don’t simply introduce YAAS (yet another appointments system). In particular alignment with the existing GP Connect work is preferred.

The key is in the user needs and the fact that nothing exists currently to meet all of the user needs in urgent and emergency care.

A drastic over-simplification of the use cases in urgent and emergency care appointment booking is:

  1. An urgent / emergency care service booking an appointment into general practice (a patient’s GP surgery)
  2. An urgent / emergency care service booking an appointment into another urgent / emergency care service

GP Connect is currently focused on enabling the first of these: booking an appointment into general practice (and specifically only the IT system suppliers that are part of the national GPSoC framework) – it therefore could help to meet some of our user needs in urgent and emergency care, but not all of them.

The e-Referrals Service (eRS) (formerly known as Choose and Book) currently targets a different set of needs: primarily referral from primary care into elective care* services (e.g. your GP referring you to a specialist in a hospital). The sort of workflows that support eRS use cases are quite different to what we need in urgent and emergency care with a key example being the respective definitions of an urgent appointment: in elective care this means 2 weeks, in urgent & emergency care this might mean within 1 hour.

In both cases there are IT systems in urgent and emergency care that do not already have integration with either GP Connect or eRS. This does not mean that neither can be of use, but it does mean that neither can provide what is needed in the current form.

Some specifics

The following notes were made whilst summarising some key characteristics of appointment booking in urgent & emergency care – they are highly likely missing context and are not exhaustive…

Appointment types (e.g. routine, urgent, 1 slot 1 patient, 1 slot many patients, not date/time bound, etc.)

Urgent care appointments are generally specific time-based slots i.e. come to x place at 20:30. In most cases a single patient will be booked into a single as would happen at a GP surgery, but busier or higher acuity services may utilise group slots i.e. come to x place at 16:00 and you will be seen around that time – this helps manage high demand and the general challenge of keeping to specific appointment times in dynamic services such as healthcare.

The urgency of an appointment tends to be denoted by the ‘disposition’ – a term which represents the concept of a timeframe within which the patient needs to be seen (e.g. must be seen within 6 hours) combined with the general type of care the patient requires (e.g. see a clinician, see a dentist, see a pharmacist). When a disposition is derived for a patient the ‘timer is started’ with regards to the timeframe.

As mentioned above, there will be variety in the types of appointment patients require e.g. it might be with a mental health specialist, with a nurse, they might need a clinician who specifically can prescribe medication, they might need to see an emergency dentist.

There is a mixed model of how this is provided: some service providers will supply several types of appointment, whereas other specialist providers might only supply one type (e.g. an emergency dental provider might only supply emergency dental appointments).

Slot management (publishing, synchronisation, ownership, etc.)

All existing models within urgent care use real-time slot queries to get availability of appointments. At the busiest periods even this can result in appointments becoming unavailable between the initial search and confirming it with the patient – this is not unlike the high-demand ticket-booking scenario. Demand on services can fluctuate rapidly, and services maintain the ultimate control over the appointments they are making available; it is not unheard of for a service to remove some availability when they see an influx of patients to prevent running over-capacity.

Ultimately the services providing the slots have ownership over what they do and don’t make available – there are some political complications if the service providers are contracted to provide a certain number of appointments for instance, but this is a separate detail.

Services will sometimes make slots available for certain types of patient, and have to manage their slot allocation carefully so as to avoid using all slots within the first hour of opening – they have an obligation to continue to provide a service during the out of hours period and so they have to apply demand predictions and spread their slot availability out. This can be done by restricting certain slots for patients with certain clinical urgency, and spreading these through the schedule (e.g. reserve a % of slots every hour that can only be booked into for patients with a urgency of < 1 hour). Another method of controlling demand is to use the disposition timeframe to filter the time range for appointments e.g. if a patient needs to be seen within 6 hours, don’t show slots sooner than 2 hours away. Obviously some serious thought has to be put into how this is all filtered and as to how they make sure they are providing an acceptable service for patients.

Who can do what? (professionals and patients)

Patients do not currently have any access to their own appointment information in urgent care, and there is no existing facility for patients to book appointments directly without first speaking to a member of staff within a service such as NHS 111.

The permission to book appointments does not tend to be restricted at an individual user level – at this point in time it is more about inter-organisational agreements i.e. can X NHS 111 call centre appointments into Y urgent treatment centre.

Generally if someone is able to deal with a patient on the phone, they will be able to take the patient through the full journey including booking them an appointment at another service. On a technical level, API authentication tends to happen at the organisational level with the authentication and authorisation of individual users remaining the responsibility of the respective systems – it is rare that Jackie Jones from Townsville NHS 111 call centre is specifically given authorised to book an appointment into Townsville Urgent Treatment Centre.

Slot mapping/semantics (e.g. slot = service, or slot = care role, or slot = name clinician, etc.)

This varies depending on the scheduling models that systems implement, and to a certain extent does it matter? Ultimately, though, slots are made available by services, and may be restricted by the type of care provided and restricted by certain patient criteria i.e. only patients who have received a certain disposition can book this slot.

There is no significant precedence of slots being at named clinician level within urgent care as staff are much more ephemeral than in other services, and encounters with urgent care by definition are not the start of an ongoing long-term relationship between the patient and service.

Managing appointments (booking, cancelling, rescheduling, recording attendance, etc.)

Proprietary solutions currently provide Book and limited Cancel / Reschedule functionality.

Cancel / Reschedule is limited because this can only really be done during the initial call with the patient i.e. if the patient changes their mind before the telephone call is completed.

None of the existing proprietary solutions support Cancel / Reschedule after the initial call has completed, and this is one of the big workflow challenges for us: how do we identify that an appointment has previously been booked for a patient if they are to call back to NHS 111 at some point after their original call. In particular considering the notes above regarding distribution of telephone calls nationally there is no guarantee that a patient will speak to the same call centre, let alone same operator, if they call back to NHS 111.

Any national approach will need to provide interoperability and operational workflows that support these missing bits.

Access to the booking system(s)

Patients do not currently have access to the appointment booking systems in urgent care.

Existing proprietary interoperability is all system-to-system  Рthere are no publicly-available or open APIs for third-parties to easily consume.

Monitoring/Analytics/Reporting (e.g. DNAs, unused slots, etc.)

All handled locally by system, nothing centralised at the moment. Being able to look at how appointments are utilised across the urgent care system would be a good thing to tackle, providing it isn’t at the expense of the patient experience and operational workflows.

From a data perspective, it should be possible to get decent activity information about appointment booking without requiring patient-identifiable data – this will need looking at in more detail.

 

* Elective care is pre-arranged, non-emergency care, including scheduled operations. It is provided by medical specialists in a hospital or another care setting. You will usually be referred by your GP.

Referrals vs Transfer of Care

What is the difference between a ‘Referral’ and a ‘Transfer of Care’?

The phrases “Transfer of Care” and “Referral” are used frequently, all over the NHS and they feature especially often when talking about interoperability between IT systems.

Sometimes the two concepts are conflated and the terms used interchangeably; they both involve passing the responsibility of care for a patient to someone else but the nature of the responsibility and the way it is resolved is different.

Here is an attempt at describing the difference between the two:

Referral

A referral is a request made by one clinician or organisation to another clinician or organisation for them to take responsibility for part of a patient’s care.

This part responsibility might be for a specific problem the patient has, or for a particular activity (e.g. medical imaging and other diagnostic tests) to assist the GP with further diagnosis.

The referral, and therefore the responsibility, will often have a defined end point – for example until a particular activity has been completed (or ‘discharged’), or until a particular problem has been resolved. In other cases it might be an ongoing responsibility – for instance management of a Long Term Condition.

Example

A patient has visited their GP because with a painful back. The GP feels that they may need some further investigations, for example an MRI scan, to find out what is going on.

The GP makes a referral for the patient to the radiology department at the local hospital asking that they use medical imaging to help diagnose the patient’s back problems. The patient is told that the referral has been made and to wait to be contacted by the hospital.

The patient receives an appointment from the radiology department. They attend the appointment and the appropriate scans are taken of their back.

The consultant radiologist then produces a report describing the results of the scan which is sent back to the GP who made the referral. This particular referral is then completed and responsibility for the next steps are back with the patient’s GP.

 

Transfer of Care

A ‘Transfer of Care’ is where a clinician or organisation passes the overall responsibility for a patient’s care to another clinician or organisation.

This is often related to a patient moving to a different stage in an overall pathway of care, or to a change in their condition which requires a different type or level of care.

Example

A patient is feeling unwell on a Saturday evening, and calls NHS 111 to get some help. They have a conversation with a nurse who feels that they really need to see an out of hours doctor in their area.

The nurse takes some more details from the patient and searches for an out of hours service near to the patient. He finds an appropriate service and advises the patient that he will arrange for them to see a doctor within the next 4 hours.

Once all confirmed, he initiates a transfer of care from NHS 111 through to the out of hours service, sending all of the details he has recorded about the patient through to the out of hours service.

The out of hours service accepts the transfer of care and is now responsible for the ongoing care of that patient.

The nurse in the NHS 111 service is no longer responsible for that patient’s ongoing care, and moves on to look a new patient.

 

Is this right? Views and comments welcome.

NHS Hack Day 16 – London

Last weekend was the 13th NHS Hack Day¬†(#nhshd)¬†–¬†superbly¬†organised and hosted in London by Helen Jackson (@DeckOfPandas)¬†¬†– and the 2nd #nhshd¬†that I’ve attended.

My¬†first #nhshd¬†was in Manchester last year where a small group of us¬†hacked¬†an idea to help medical students get access to more hands-on learning opportunities – we called it¬†SLOT (Supervised Learning Opportunities by Text). We¬†agreed¬†to¬†continue with¬†the project on after the hack day and we’ve just started a trial at¬†Western General Hospital in Edinburgh – we’re keeping our fingers crossed that we get some interesting results.

There have been several blogs published since last week¬†describing what it’s like to attend a NHS Hack Day and I think they’ve done a pretty good job – so I’m going to avoid repeating the same¬†things and¬†link to a few of them instead:

http://www.drgrimes.co.uk/?p=206

http://itsuite.it.brighton.ac.uk/rlr17/blog/?p=215

http://openhealthcare.org.uk/blog/2016/05/20/nhs-hack-day-13/

There were many excellent ideas pitches and I was really encouraged by the number of ideas that were focused on making a tangible change to the way and ease with which people can do their work.

I arrived with¬†no preconceptions about the type of idea I would work on – only that I would actively avoid anything that was focused around sending people text messages (I’ve hacked around this a few times now).

I was particularly excited by a couple of the ideas:

  • The first was an¬†idea¬†to hack a real anaesthetic machine (brought to the venue) to get data from it directly and do useful things with it –¬†we were told that currently information is normally transcribed manually from the machine to¬†the patient records.
  • The second was an idea to hack¬†an easily-deployable¬†patient observation system which can be used¬†in the field during health emergencies where you don’t have reliable power¬†and¬†connectivity – the example¬†used¬†was the Ebola virus epidemic in West Africa where using paper to record observations was both impractical and an infection risk.

The idea that I was ultimately drawn to was from Adhiraj who is a consultant child and adolescent psychiatrist working in London. He described a frustrating situation faced by clinicians working in mental health all over the country. We ended up prototyping a solution to help locate available mental health beds, and automate the process of requesting and accepting referrals.

We managed to demonstrate a working prototype by the end, and were lucky enough to be placed in the top three by the judges! A very satisfying end to the weekend ūüôā