<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Damien Hampton on Medium]]></title>
        <description><![CDATA[Stories by Damien Hampton on Medium]]></description>
        <link>https://medium.com/@damienhampton?source=rss-6951bad2cd9c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UldOPKAUHEbJMSCL5b9zAw.png</url>
            <title>Stories by Damien Hampton on Medium</title>
            <link>https://medium.com/@damienhampton?source=rss-6951bad2cd9c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:57:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damienhampton/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A guide to SRP, Open/Closed, Dependency Injection, Interfaces, Unit Testing and Mocks]]></title>
            <link>https://medium.com/26brains/a-guide-to-srp-open-closed-dependency-injection-interfaces-unit-testing-and-mocks-3b02a47f4196?source=rss-6951bad2cd9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b02a47f4196</guid>
            <dc:creator><![CDATA[Damien Hampton]]></dc:creator>
            <pubDate>Thu, 12 Jan 2017 17:22:39 GMT</pubDate>
            <atom:updated>2017-03-24T09:32:34.136Z</atom:updated>
            <content:encoded><![CDATA[<p>This video is a guide for developers to help them understand what changes need to be made to code to make it testable and sustainable. It uses parts of the SOLID principles to refine an example class.</p><p>Topics covered:</p><ul><li>Single Responsibility Principle (SRP)</li><li>Open/Closed principle</li><li>Dependency Injection</li><li>Interfaces</li><li>Unit Testing</li><li>Mocks</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FgMRPcmZ4BZo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DgMRPcmZ4BZo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgMRPcmZ4BZo%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/33feb203b25d77b126faa46da82d4902/href">https://medium.com/media/33feb203b25d77b126faa46da82d4902/href</a></iframe><p><em>Originally published at </em><a href="https://www.26brains.com/2017/01/a-guide-to-srp-openclosed-dependency-injection-interfaces-unit-testing-and-mocks/"><em>26 Brains</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b02a47f4196" width="1" height="1" alt=""><hr><p><a href="https://medium.com/26brains/a-guide-to-srp-open-closed-dependency-injection-interfaces-unit-testing-and-mocks-3b02a47f4196">A guide to SRP, Open/Closed, Dependency Injection, Interfaces, Unit Testing and Mocks</a> was originally published in <a href="https://medium.com/26brains">26Brains</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Black belt software development]]></title>
            <link>https://medium.com/26brains/black-belt-software-development-bff562678508?source=rss-6951bad2cd9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bff562678508</guid>
            <dc:creator><![CDATA[Damien Hampton]]></dc:creator>
            <pubDate>Mon, 17 Oct 2016 14:21:03 GMT</pubDate>
            <atom:updated>2016-10-17T14:21:03.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7sbnJXo9rMAlfkzk1Le0_Q.png" /></figure><p>The Boss: “This software project has gone £50,000 over budget, it’s 12 weeks late, and I want to know why!”</p><p>“I think we spent too much time thinking about automated testing”, said no team member, ever.</p><p>I’ve been thinking a lot about software development recently — what works and what doesn’t and why is everything so damned hard?!</p><p>I read David Heinemeier Hansson’s <a href="http://david.heinemeierhansson.com/2014/tdd-is-dead-long-live-testing.html">article on the death of TDD</a> and, whilst I think I understand where he is coming from, my concern with his article is that some developers might read it and think that they don’t need to worry about learning things, like testing, that improve the quality of their code.</p><p>Many software developers seem to only know what they learnt at university, which is just not good enough for the modern developer. A developer who has never written a test, has never become comfortable writing tests, is rarely going to be a good thing.</p><p>There are things that software developers can learn from the way karate is taught.</p><p>If you learn karate, you learn basic moves. You learn stances, punches, kicks, blocks, throws. The stances are hard and low and not representative of how one would fight. The basic moves are exaggerated because if you can do the exaggerated moves, you can do the moves better in a more natural fighting stance. The basic moves stretch you to improve your fighting.</p><p>And you repeat them.</p><p>Over and over and over. Building muscle memory. And you think about them. And you meditate over them. And you think about how to apply them to real-world situations.</p><p>I think of software development techniques in the same way. We should practice techniques, we should keep practicing, over and over until it becomes natural. We should think about them, we should meditate over them and think of the best ways to apply them.</p><p>SOLID design principles, unit tests, TDD, BDD and pair programming are all examples of basic techniques that a developer should learn. Knowing these techniques can only make you a better developer, even if you choose not to use them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bff562678508" width="1" height="1" alt=""><hr><p><a href="https://medium.com/26brains/black-belt-software-development-bff562678508">Black belt software development</a> was originally published in <a href="https://medium.com/26brains">26Brains</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Responsibility, accountability and ownership]]></title>
            <link>https://medium.com/26brains/responsibility-accountability-and-ownership-1ef5ded78508?source=rss-6951bad2cd9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ef5ded78508</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Damien Hampton]]></dc:creator>
            <pubDate>Wed, 12 Oct 2016 21:22:45 GMT</pubDate>
            <atom:updated>2018-09-24T06:30:30.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sIoCvgXT8f0u9ZULF1Aabw.jpeg" /></figure><p>We like people who are responsible. It all sounds very grown up.</p><p>Someone who is responsible will get something done, because they are responsible and responsible is good.</p><p>The problem is, things don’t always get done, do they? That thing was needed, the responsible person was supposed to do it, but they didn’t. It’s their fault. They were responsible and they didn’t do that thing.</p><p>It’s all very neat. There was a problem, but we know what the cause was, so it is ok.</p><p>Except it’s not ok. The job still didn’t get done and blaming someone didn’t help, it just allowed others to absolve themselves of responsibility by blaming the person who was responsible.</p><p>Enter accountability.</p><p>I’ve been responsible for things and I’ve been made accountable for things and I didn’t really understand the point. It didn’t make me approach my work differently.</p><p>The thing about accountability is that it is not something for the individual to help them navigate the things for which they are responsible. Accountability is a lever for others to use to ensure that the responsible person is doing their damn job.</p><p>If you are part of a team and a member of the team is accountable for something, YOU have a duty to hold them accountable. It’s your job to make sure that they do the thing for which they are responsible. This is one of the key things about being part of a team. It’s not just about helping each other, it’s also about calling each other out.</p><p>When someone asks you to do something and you then pass that on to someone else, maybe even the person responsible, and then you forget about it, you are part of the problem. That person might not have done the thing needed to be done and the person who made the original request has been let down. And it’s your fault.</p><p>When you take ownership of a problem you become a giant of a person. You become the unsung hero of the story. You take the request, you pass it on, you make sure it gets done and you relay the good news. No-one thanks you for it, but you can rest easy knowing that you have been part of the solution and have done the right thing. Believe me, over time you will reap the benefits, personally and professionally; it’s like compound interest.</p><p>Responsibility, accountability and ownership together are an amazing productivity cocktail — do these things and you will never be out of work. Act responsible, but ignore accountability and ownership and you just become part of the system and part of the problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ef5ded78508" width="1" height="1" alt=""><hr><p><a href="https://medium.com/26brains/responsibility-accountability-and-ownership-1ef5ded78508">Responsibility, accountability and ownership</a> was originally published in <a href="https://medium.com/26brains">26Brains</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Switch]]></title>
            <link>https://medium.com/26brains/the-switch-fcea60805bda?source=rss-6951bad2cd9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcea60805bda</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Damien Hampton]]></dc:creator>
            <pubDate>Tue, 09 Aug 2016 08:04:37 GMT</pubDate>
            <atom:updated>2016-08-09T08:04:37.725Z</atom:updated>
            <content:encoded><![CDATA[<p>My brother bought a Mac when he went to university. Some sort of Performa model, if memory serves me correctly. I would have been about 16 at the time and still using our home PC and playing Doom II. I went to university in 1995, discovered Windows 95, broke it, fixed it and then a friend taught me about hardware and I first built a PC from component parts. It was part of the fun: build the PC, set-up Windows, tweak it to be just how you want it, break it, re-install it.</p><p>I bought my first Mac around 2000, probably running Mac OS9. Curiously, I loved it. No tweaking set-up, no building PCs, just a computer that worked. You could get on with stuff. But there were problems. By the time OS X replaced OS 9, the latter had become tediously buggy. An application crashes and the whole OS crashes — seriously? OS X was new and exciting and also missing a heap of functionality — why can’t I save inline attachments from emails?</p><p>I built another Windows PC after that, in part because I couldn’t afford another Mac. Windows 2000 was also a lot better than Mac OS9. I returned to the Mac family, buying a Macbook Pro, probably around 2007 and I’ve not switched back. Nothing that I’ve seen in newer versions of Windows has compelled me to think switching would be a good idea.</p><p>My first iPhone was the 3G — I think I switched from a Nokia N95 — probably in 2008. If you cannot imagine what that experience was like, it was pretty amazing. The N95 was packed with functionality, it’s just that none of it really worked. The 3G had less stuff but what it did have it used infinitely better. The N95 seemed brilliant until you compared it to an iPhone and then it suddenly seemed like something from the dark ages.</p><p>Since then I’ve had an iPhone 4, 5 and 6. I very briefly switched to a Nexus 5 between the iPhone 5 and 6, in part so I could try out Android and in part so I could sell my 5 before the release of the 6 devalued it. I used the Nexus 5 enough to make a quick judgement that I preferred the iPhone, but no more.</p><p>I recently sold my iPhone 6 in preparation for the release of the 7 and I bought a Nexus 6. I’ve been using the Nexus 6 for just over a week now.</p><p>I’m not sure that I can fairly compare a phone that I’ve used for just over a week to a phone I’ve been using for the last 5 years, but I’m going to try.</p><p>When I tried out the Nexus 5 I made a conscious decision to divorce myself from the Apple ecosystem. I made sure my eBooks were not using iBooks, I switched my photo storage to Flickr, I switched my music to Spotify. Even as an Apple fanboy, I prefer that set-up. Of course, there is a limit to what you can do — I have bought apps in the App Store and I can only get value from those on an iPhone, as the same is true of the Play Store and Android.</p><p>I guess the first thing to note is that if you are wedded to the Apple ecosystem — photos, books, music — well, you are wedded to Apple. If you switch, you’ll experience a lot of pain. Having mitigated the pain, switching from the iPhone 6 to the Nexus 6 was easy.</p><p>I’m still learning about Android and I don’t think I’ll ever be able to give an unbiased view, but I can offer a few thoughts.</p><p>Android is way more flexible than iOS, it is by far and away the biggest difference between the two systems. iOS controls so much of the user experience in comparison to Android. This has pros and cons. iOS requires no customisation from the user. Android can also work without any customisation from the user, but it sure as hell improves if you *do* customise it.</p><p>There is another thing — Android is not necessarily Android. The Nexus 6 runs the stock version of Android. This is the original version of Android as Google intended. It’s also relatively bare. You want app badges? Not so fast… you going to need an app for that. Samsung have customised Android to the way they think it should be, giving a different perspective on the default Android user experience. I’ve not used Samsung devices, so I cannot comment on how good they are, but they get very good reviews.</p><p>A few things I have noted about the Nexus 6 in comparison to the iPhone 6:</p><ul><li>The Nexus 6 gets hot when charging, the iPhone doesn’t</li><li>There is a big difference in charging speed when charging the Nexus 6 over USB vs. plugged into a wall socket — I have not noticed this with the iPhone</li><li>There seems to be a bigger difference between low power use and high power use on the Nexus 6 compared to the iPhone — but I should point out that both drain the battery pretty fast under sustained use</li><li>iOS on the iPhone feels faster than Android on the Nexus 6. It could be the apps, it could be the device, it could be the OS. I don’t know, iOS just seems like a more consistent, fast experience. I should stress that iOS has its moments when it is slow, but it just doesn’t seem that frequent.</li><li>It seems as though the hardware and software on the iPhone work together better that those of the Nexus 6 — the heat, the speed, the power usage all hint at this</li><li>Many apps are very, very similar across iOS and Android</li><li>Some apps are more gesture based on iOS, such as Facebook, versus Android in which it is button (tap) based</li><li>You really can customise a lot about Android and tailor it to how you want it</li><li>Android’s notification system is a lot more sophisticated than that of iOS — but you do have to configure it to get the best out of it</li></ul><p>Coming from iOS, I really like app badges. On Android, there a multitude of ways of doing that. I installed the paid-for version of the Nova launcher, which then gives you even more control over home screens. I changed the grid to a 5 x 6 grid to get even more apps on my home screen. And now I have app badges.</p><p>I know there are better Android devices than the Nexus 6 and part of the reason I bought it was because I wanted to try out a bigger device before opting for an iPhone 7 plus. The Nexus 6 is perhaps a little too big for me, but I do like it.</p><p>Getting app badges made a big difference to my usage — I realise that it is one of the main ways that I know whether something is going on inside an app.</p><p>If you use an iPhone, Apple expect you to use the apps that come with the device and then supplement it with additional apps. If you use an Android device, I think Google expect you to replace some of the apps.</p><p>I have read articles titled “Best camera app for iOS”. Its a bit confusing — best what? What’s wrong with the built in camera app? Why would you change the default camera app? If you use Android, it becomes clear why you would change it. Also, the Nexus 6 camera is poor — again, I know other Android devices have better cameras.</p><p>Google don’t presume to have all the best apps — though some of their apps are awesome: gmail, maps, etc. If you want to change for something else, you are free and almost encouraged to do so. Apple do presume to make the best apps and even if they don’t, they will tell you they do. Google maps? You mean Apple maps, right?</p><p>Before I started using the Nexus 6, I knew that iOS and Android were both awesome. From a technology perspective, I think we are lucky to have such a competitive battle between Apple and Google.</p><p>If I was forced to stick with Android, I could happily use it. But I am not sure whether Android appeals to my desire to tweak and changes things or whether it is meeting a real need. Do the customisations that I can make to Android make me more productive? I’m not sure they do.</p><p>I’ve been lucky that my iPhone has not been bricked by one of the rogue Apple software updates. When I got my Nexus 6, it would not install the Android May patches. I had to scour the internet and then enable debugging and reinstall the OS using the Android ADB application on my Mac — not a process for the non-computer literate.</p><p>I use almost all the same apps between iOS and Android: Spotify, Skype, Flickr, Slack, Trello, BBC News/Sport, Evernote, Facebook, Myfitnesspal, Strava, 1password, Pocket, Google maps, Audible, Guardian, Youtube, eBay and Lovefilm are probably the most prevalent. On iOS I use Safari, on Android I use Chrome. On iOS I use mail, on Android I use Gmail. All are very similar across Android and iOS — there are some differences and I have a few gripes, but I think that is just because I am used to things being a certain way.</p><p>The Nexus 6 is not as good as the iPhone 6, but there are better Android devices than the Nexus 6. I think I am back to where I started — Android and iOS are both awesome operating systems. They work in slightly different ways, iOS requiring little effort, but offering little control. Android requires more effort to get the best out of it, but offers more control.</p><p>I think my perfect device would have the customisation capability of Android with the default quality of iOS, the hardware quality of the iPhone (or maybe Samsung?), the hardware and software integration of the iPhone and a battery that can last a week. And app badges.</p><p>If you buy an iPhone, it will be awesome. If you buy an Android device, it might be awesome, but it might just be very good, depending on which one you pick. If you buy an Android device, you should probably buy it based on the hardware specs — and not using the adage that more is better. Better is better; more is just more. Trust the reviews. You want the best battery life, the best hardware/software integration and the best hardware. The software will be awesome. And even if it isn’t, you can customise it to make it awesome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcea60805bda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/26brains/the-switch-fcea60805bda">The Switch</a> was originally published in <a href="https://medium.com/26brains">26Brains</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In or out of Europe?]]></title>
            <link>https://medium.com/@damienhampton/in-or-out-of-europe-c187e992181a?source=rss-6951bad2cd9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c187e992181a</guid>
            <category><![CDATA[european-union]]></category>
            <category><![CDATA[politics]]></category>
            <dc:creator><![CDATA[Damien Hampton]]></dc:creator>
            <pubDate>Thu, 21 Jan 2016 13:44:14 GMT</pubDate>
            <atom:updated>2016-01-21T13:44:56.462Z</atom:updated>
            <content:encoded><![CDATA[<p>The ‘in’ and ‘out’ camps would have us believe that the referendum on Europe will either save or break Britain. Each side claims that one decision will cripple Britain whilst the other decision will be our salvation. Here are the possibilities:</p><p>1) Both sides are right. In this scenario, whatever the result of the referendum, the UK will simultaneously be saved and destroyed. Clearly, this is nonsense.</p><p>2) One side is right. If one side is right, the result will determine whether the UK is saved or destroyed. This is possible, at least the UK will exist in some stable situation — whether it is good or bad!</p><p>3) Neither side is right. If neither side is right, then we can consider options that do not involve the saviour or destruction of the UK. I’m simplifying a little, but given that most politicians seem to be alike (look at each Government for as far back as you can remember), if one lot is wrong — would it not seem a reasonable baseline to assume both sides are wrong?</p><p>I’m not a politician, nor am I an economist, but I have a hunch, nothing more, that the result of the referendum will have a less catastrophic impact on the UK. I will say now that my personal view is that we should stay in the EU and I will make clear why. But if we leave Europe, I don’t expect civilisation as we know it to end.</p><p>Being part of the EU provides freedom of movement, few trade barriers and access to a wealth of EU resources. Those benefits come with trade-offs, freedom of movement means that the supply of labour from cheaper EU countries lowers wages in the UK — this is not so good for labourers, but a bonus for businesses and/or consumers. Few trade barriers mean that small UK companies have no protection from multi-national companies in other EU countries eating into their market. Access to EU resources is balanced by the eye-watering payments the UK makes to the EU.</p><p>Being in the EU means a more diverse population, benefits for larger businesses who can scale across the continent, lower prices for consumers, lower wages for some workers and a rapid development in technology and industry funded by the EU.</p><p>Conversely, leaving the EU would mean a less diverse population, benefits for smaller business who now have the protection of trade-barriers, higher prices for consumers as import tariffs rise and wages re-balance, higher wages for labourers without the competition of cheap labour and slow development in technology and industry.</p><p>Leaving the EU, would be an isolationist move — we would be doing to the EU, what we tried to stop Scotland doing to the UK. The irony that Scots do not want to leave the EU should not be lost. History is not littered with successful isolationist strategies, but there are negative stories — think the US in the 1930s. Leaving the EU would probably benefit UK businesses and workers in the short and medium term, but on a global scale we would start to lag behind. Our excellence in R&amp;D is not that good that we can do it on our own. Reminiscing about glory days of British industrialisation is not a strategy for future success.</p><p>Staying in the EU means that the UK remains part of a team. A big team in which we are only one player — albeit an important one. Consumers will get a good deal. Big business will continue to be successful and we will have to ensure that they remain accountable. Small businesses will need help to ensure that multi-nationals do not monopolise markets.</p><p>Freedom of movement is an issue but I do not believe it is the epidemic that some would have you believe. There are parts of the UK where the rise in immigration from EU countries has had a marked effect on public services and this needs addressing. Growth in population is only sustainable if combined with the growth in services for that population. Likewise, housing needs addressing. Our country is not bursting at the seams, we have plenty of room. What we need is balance to where people are located — more housing and services that can scale with the population.</p><p>I’ll be voting to stay in the EU because I think it is better in the long-term and I think that the current problems should be fixed rather than used as a reason to back away.</p><p>A final point on the related discussion on European Convention on Human Rights vs. a UK Bill of Rights. I had thought that a bill of rights would be a reasonable choice until I read <a href="http://www.dominicgrieve.org.uk/news/why-human-rights-should-matter-conservatives">this</a> by Dominic Grieve, my local (Conservative) MP. His article changed my mind completely. Despite agreeing on this, I did not vote for Dominic Grieve at the General Election.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c187e992181a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital healthcare — how do you feel?]]></title>
            <link>https://medium.com/@damienhampton/digital-healthcare-how-do-you-feel-12e32a8526ca?source=rss-6951bad2cd9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/12e32a8526ca</guid>
            <category><![CDATA[digital-health]]></category>
            <category><![CDATA[health-technology]]></category>
            <category><![CDATA[nhs]]></category>
            <dc:creator><![CDATA[Damien Hampton]]></dc:creator>
            <pubDate>Mon, 18 Jan 2016 15:32:17 GMT</pubDate>
            <atom:updated>2016-01-18T16:54:09.733Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPqRo_B-xO01OveqYWWZjw.jpeg" /></figure><p>Much has been written about digital healthcare and it often polarises opinion. The two perspectives below highlight opposing views of an increasingly connected healthcare system.</p><h4>Perspective 1: Digital healthcare is a bad idea and has no place in the NHS</h4><p>The last few years have been an onslaught of news and information about digital in healthcare. From online booking, to seeing your medical record, e-prescriptions and online consultations, and sharing data. It’s too much. Digital has its place in home and personal entertainment. Your iPhone is good for phonecalls and text messages, music and games. You can even log your exercise. But it is not a medical device.</p><p>Online booking is great, but it penalises those who don’t have internet access. It is ok to make a few appointments available, but the bulk need to be reserved for those phoning or walking in. Access to medical records is a Government inspired nonsense. Patients don’t want or need access to their record, besides the fact, it is your GP’s record, not yours.</p><p>Personal health records are a bad idea because health data belongs in the hands of professionals not patients. If patients can interfere with medical data, it will put lives at risk.</p><p>Data sharing? Two words: Care (dot) Data. You should be afraid. The Government will sell your medical data to private companies so they can make profits. You data will not be safe. Patients trust their GP to look after their medical data and they are happy with that. Patients do not want anyone else to have access to that data.</p><p>The internet is a fantastic invention, it has given us so much access to information and services. But with those benefits have come risks and problems. Fraud, identity theft, phishing attacks, hacking, to name but a few. Medical data is sensitive and should not be exposed to these risks for the vanity of a few fancy apps. The Government wants to use open source software because it is cheaper, but the most popular open source software specifically designed to make computers safer (OpenSSL) was revealing a huge back door for hackers to exploit — and it wasn’t spotted for over two years! Medical systems should not be connected to the internet because it is not safe.</p><p>Clinicians train for many years to become proficient at what they do. When you have a problem, they can assess you and make a judgement and ensure that you get the correct medication. They are short on time and the last thing they need is you with your Google diagnosis and your fitness tracking results. Let the doctor do their job and you can keep your data for your own time.</p><p>NHS organisations are under financial pressures like never before. They need to save huge amounts of money just to maintain existing levels of care, which are already falling behind demand. You want them to do this and revolutionise who some things work by introducing completely new ways of working? Get real, there is only so much change that can be absorbed at any one time. Maybe come back when the existing crisis is over.</p><p>Simply put, reliance on digital and the internet will cost lives and be a disaster.</p><h4>Perspective 2: Digital healthcare can bring huge benefits to patients and save the NHS</h4><p>The use of the internet, patient’s own devices and more reliance on patient will introduce new problems to the NHS and to healthcare. Hacking is a real problem and it will affect healthcare, only a fool would suggest otherwise. There are many challenges that the introduction of digital to healthcare will bring. But there are a also a huge number of benefits, benefits that we believe outweigh the problems and make a good case for their inclusion.</p><p>The NHS is in trouble. If everything were perfect, there would be no need to suggest making changes. There is a funding crisis, there is a demand crisis, there are individual conditions, such as diabetes, obesity and dementia that present their own crises. When things are not working, you can either do more or less or something or you can do something different. The funding crisis has effectively withdrawn the option to do more of the same. The only viable option is to do something different.</p><p>Some patients are not able to be involved in their own healthcare, they are 100% dependent on other. Some are not interested in being involved in their own healthcare — they think that is a job for their doctor. Some patients are interested though and if we can do more to help this group to help themselves, then there will be proportionally more resources to help those who either can’t help themselves or do not want to. Patients are not stupid — many raise families, hold down jobs and pay bills on time. We can trust them to do more.</p><p>Online and telephone banking has reduced the need for banks to invest in high street branches and has made banking significantly more convenient for those with online accounts. It has probably made some people think more about what they do with their money as they have direct access to their account — what goes in and what goes out. The NHS cannot copy this model in its entirety — it still needs to provide services to those without internet access, with quality matching, or better than, existing services. For those with internet access, there is a possibility that some will become more involved in their healthcare and become more conscious about what decisions they take that impact their health.</p><p>Patients can collect their own data. Smart phones are perfectly good devices on which to collect data. The sophistication of wearables and other connected devices means that so many things can be tracked. Yes, there are concerns about the quality of some of them, but the glacial development pace and expense of existing medical technology is not a practical solution. Quality too late is not better than poor quality on time. Better that we have something that is ‘good enough’ and available now. Is it better that a nurse takes a patient’s blood pressure after they have walked up hill to the surgery or that the patient can simply send the nurse data collect every day for the past 30 days from a wearable device? Which data is likely to be more accurate and useful?</p><p>I would not profess to be an expert on how to run a consultation. At the Modality Partnership, they replaced face to face consultations with telephone consultations. The telephone consultation could take place within an hour of a patient requesting an appointment. The telephone consultation might result in the need for a face to face consultation. Rather than have fixed consultation slots of 10 minutes, GPs worked through the call list with an average call time of 3 mins. Only 30% of patients needed face to face follow up consultations. Modality met their previously unmet demand and also found more time to give to high-risk patients who needed more care. Convenience for patients — consultations where you are, when you want them. Efficiency for the practices. All GP surgeries should do this today.</p><p>Hotels, groceries, movies and many other things can be booked online. It makes sense. It is more convenient for users and cheaper for companies. Some practices offer this service, though in my experience and anecdotally, it is almost always done badly. Services should be available online and they should be implemented by someone that knows what they are doing. Online services should not replace traditional services, they should complement them. Done well, few resources will be needed to provide the traditional services and the traditional services will improve.</p><p>Care.data was a disaster. It was a good idea, excruciatingly badly executed and communicated — the Government failed to help the public understand the purpose of the programme.</p><p>Any system has security flaws and those connected to the internet are no different. Whilst it is true to say that transferring data across the internet brings with it new risks, it should be recognised that the current system is not without problems. We have all read about laptops being left on trains, folders of sensitive papers being left in public places, emails sent to groups exposure personal details. Security knowledge within the NHS, as with many industries is variable at best. Whilst concerns around the use of the internet are valid, they are by no means the biggest concern regarding security. Systems can also be too secure — when data is so secure that those who need access cannot get to it, that is still a risk to lives.</p><p>I want access to my medical record because it is my record. Furthermore, I want to be in control of who has access to my record. I can understand that my GP should have statutory access. But I should be able to consent to paramedics, hospital nurses and doctors, physiotherapists, psychologists have partial or complete access to my record. It should be my choice — it is after all, my data. A GP should have a statutory right to share my data also, if he or she feels that it is necessary to do so. Consent does not have to be complicated. Do I want my physiotherapist to see medical data about my spine whilst they are treating my back? Yes, please. Do I want them to have access to my sexual health records? No, thank you. It is not hard.</p><p>Digital technology and the internet are great tools and can bring enormous benefit to patients and the NHS. Are they the whole solution? No. Are they a key part part of it? Most definitely.</p><h4>My view</h4><p>Whilst I can sympathise with many of the issues that clinicians and staff raise about the use of digital technology and the internet, I cannot help but feel that they are misplaced views. In some cases, people have entrenched views that they are not willing or able to question. In other cases, I think the fear of the unknown and fear of being left behind are contributing factors. I think that more needs to be done to educate staff and clinicians about real risks and benefits of digital technology and set them in context against risks and benefits of current service delivery.</p><p>It is hard to promote a balanced view that says the internet has not had an overall positive impact for consumers on industries that it has touched. I am convinced that healthcare would likewise benefit.</p><p>About the author:</p><p>Damien Hampton is the owner of 26 Brains Ltd, a technology and agile delivery consultancy in Buckinghamshire. Damien has significant experience improving the use of technology within the NHS and healthcare generally.</p><p><a href="https://www.26brains.com/">https://www.26brains.com</a></p><p><em>Originally published at </em><a href="http://roaringux.com/2016/01/18/digital-healthcare-how-do-you-feel/"><em>roaringux.com</em></a><em> on January 18, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e32a8526ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>