Tag: data science

  • A quick sketch of consciousness

    Last weekend I was flicking through some TWIML AI podcasts, something I haven’t done since the Covid-19 pandemic kicked and I got busy with  other things. Spoiled for choice as ever, I opted to listen to Sam Charrington’s  interview with Yoshua Bengio.

    It doesn’t need me to tell you that Bengio is something of a legend, one of the world’s leading AI researchers; but what’s great about this interview is the succinctness with which Bengio brings together some of the major strands in contemporary thought about consciousness and the mind in a way that I have been trying and failing to do myself, or at least failing to do with any kind of clarity that I was able to communicate.

    The strands I’m talking about are those characterised by the work of Geoffrey Hinton (deep learning), Daniel Kahneman (System 1 & System 2 thinking), and Judea Pearl (causal inference), .

    I’m not going to give a potted summary of the work in question; the principles of deep learning as developed by Hinton and colleagues are well known enough now; Kahneman’s work with Andreas Tversky won him the Nobel prize in Economics and his book Thinking Fast & Slow was an international bestseller, and I wrote about Pearl’s work in this blog  last year.

    What’s so cool about the TWIML interview with Bengio is that after listening to it I was suddenly felt able to reconcile all these insights into different mental mechanisms into what at least seems like a coherent whole, bound together by Bengio’s insights about working memory and attention, which I already knew was something that he and others (Hinton too, I think) have been working on.

    I sat right down and sketched out this diagram to explain it to myself, and I thought I’d share it hear and ask for comments:

    My quick sketch of consiousness, pace Yoshua Bengio, Geoffrey Hinton, Judea Pearl & Daniel Kahneman

    My quick sketch of consiousness, pace Yoshua Bengio, Geoffrey Hinton, Judea Pearl & Daniel Kahneman

    Now doubt some of this confuses more than it simplifies, but once I’ve had more time to consider it and had some feedback I’ll see if I can improve it and maybe write something a little more detailed about what I’m trying to get it here, in case it isn’t actually as obvious as I’m intending it to be!Now doubt some of this confuses more than it simplifies, but once I’ve had more time to consider it and had some feedback I’ll see if I can improve it and maybe write something a little more detailed about what I’m trying to get it here, in case it isn’t actually as obvious as I’m intending it to be!

  • Why AI is not AI until it wonders why

    Reflections on Judea Pearl’s science of causal reasoning

    Dr. Mark Freestone lecturing on the Alan Turing stage at CogX19.

    Dr. Mark Freestone lecturing on the Alan Turing stage at CogX19.

    Back in June I was lucky enough to attend (indeed, exhibit at) this year’s  CogX Festival of AI and Emerging Technology  in London. It’s a fantastic event stuffed full of fascinating presentations— I urge you to come next year if you can — but of all the great talks I saw and encounters I had, one in particular stood out enough to make me want to sit down and write a blog post about it.

    The presentation in question was by  Dr. Mark Freestone. Freestone is a Senior Lecturer in the Centre for Psychiatry at the Wolfson Institute for Preventive Medicine; he’s also an Alan Turing fellow. What he had to say chimed powerfully with the contents of a book I’d read just a few weeks before, and which for my money sits alongside  Daniel Kahneman’s “Thinking, Fast and Slow”  as one of the books of the decade.

    This was  Judea Pearl’s “The Book of Why”  (co-written with Dana Mackenzie), which is about cause and effect in statistics. As a student of philosophy and psychology and a part-time data scientist I’ve spent a fair chunk of my intellectual life pondering these things, which is why I picked it up and read it in the first place. And what a revelation it proved to be.

    A historical timeline info board about the importance of Judah Pearl and Bayesian networks in the history of AI, from the “AI: More than Human” exhibition at London’s Barbican Centre, August 2019

    A historical timeline info board about the importance of Judah Pearl and Bayesian networks in the history of AI, from the “AI: More than Human” exhibition at London’s Barbican Centre, August 2019

    Statistics tells us an enormous amount about the world, and now — thanks to analytical techniques of various flavours (from logistical regression to neural nets)— we’re baking statistical analysis at scale into the extraordinary data structures we’ve been building since the invention of the micro-processor and, more recently, the Internet.

    We’ve now, with our usual hubris (and usual slavish adherence to the dictates of marketing), decided to call this development  artificial intelligence, despite the fact that it’s not really intelligence at all but is, rather, pattern recognition and statistical analysis.

    I don’t mean to demean the achievements that have been made in these sectors. But when compared to the processes at work in human or animal brains, they are akin to those at the “automated function” end — object persistence or facial recognition in vision, for example. Closer, therefore, to sensory perception than to the abstract cortical processing and decision-making that we generally refer to as “intelligence” (unless you work in marketing).

    As every statistician knows, you see, “correlation is not causation.” But as Pearl points out in “The Book of Why”:

    >
    Unfortunately, statistics has fetishized this commonsense observation. It tells us that correlation is not causation, but it does not tell us what causation is…. Student [of statistics] are not allowed to say that X is the cause of Y — only that X & Y are “related” or “associated”.
    — Judea Pearl, “The Book of Why”

    Even more than that, statisticians have maintained for decades that correlation was enough, that causation was either unfathomable or not required. So perhaps it’s no surprise that, as the crowning achievement of the discipline that has produced it, correlation is what the current crop of AI technology does, and does very well indeed.

    This is fine if we want an  AI  to tell an image of a dog from an image of a cat; to recognise a face or a voice or a word or a cancer cell in the midst of healthy tissue; to calculate routes and identify cars and pedestrians; even to work at how to win at video games. Iterated pattern recognition of labelled data with backward propagation for error correction bolstered by a range of other techniques to simulate the contributions of human memory or the layering function of the mammalian visual cortex can handle all of this admirably. If you ally the techniques to more traditional AI techniques like decision trees and other higher order logics, you can start beating grandmasters at chess or Go and start building (or attempting to build) self-driving cars.

    The trouble starts when we want to ask why something happened or predict what  might happen if  in systems as unconfined and messy as the untrammelled physical world rather than in closed and rule-bound environments such as a Go board or the neatly laid out traffic grid of the average mid-Western US town. Observational data sets of the kind used to train neural networks in pattern recognition do not contain the answers to these kinds of questions, you see (q.v. “correlation is not causation”). When it comes to causal or predictive questions (predictive in the sense of predicting the future, rather than predicting the likelihood of a classification), “data are profoundly dumb”.

    In other words, in the realm of actual thinking, rather than the processing that our visual cortices perform on the patterns of light that play across our retinae, these processes do not replicate what is going on in our heads. We do not use correlation to work out what might happen next. It’s part of the toolkit we might deploy, but it isn’t by any stretch the core mechanic of how we think.

    When it comes to figuring out causation, we instead use scenarios and counterfactuals. We use fictions, not facts (a point that appeals to the  novelist in me, as you might well guess). These fictions have their basis in fact (well, most of the time), but even so they are built on relatively few immediate data points. They are instead largely constructed from multiple reconstituted examples from our experience — what we call “common sense”. They also inherently probabilistic — something they have in common with correlation. What they don’t share with correlation, however, is the ability “to predict the effects of an intervention without actually enacting it,” as Pearl puts it in his book.

    Well, I hear you say, doesn’t AlphaGo do exactly that? And the answer is, no, it does not. AlphaGo enacts millions of virtual scenarios along multiple forking paths of action to produce highly complex statistical analyses of possible outcomes, which are then encoded into the weights of its deep neural nets. This is incredibly effective and even capable of producing previously unappreciated insight into Go’s game mechanic (AlphaGo’s now famous move 37 and, subsequently, Sedol’s move 78). And it may even be, in the broadest sense, akin to what Lee Sedol himself is doing when he’s playing Go. But it’s not what Lee Sedol is doing when he’s trying to work out what he should buy his daughter for her birthday.

    When Lee Sedol does that, he is spinning up various counterfactual scenarios involving various versions of his daughter and himself, various gift options, and a whole range of family scenarios possibly stretching well into the future, scenarios that “reflect the very structure of [his] world model.” None of these scenarios will have happened in the past, and none of them will happen in the future, but he will make a choice dependent on whichever of them conforms most closely with his world model. And then, when he sees his daughter’s (and his wife’s) reaction to the gift, he’ll perhaps embellish his world model according to the difference between his prediction and the perceived reality, thus deploying a training set, not of AlphaGo’s millions of examples, but of just one.

    What’s strange about this is that the empirical observation can never fully confirm or refute the counterfactual. And yet counterfactuals are the primary tools we have for guiding our journey through the world in a cybernetic fashion, and thus are “the building blocks of moral behaviour as well as scientific thought.”

    Current  AI  does not benefit from this mode of human thought. The importance of Pearl’s work, as encapsulated in “The Book of Why”, is that over the last three decades he has developed a method, a “causal calculus”, to enable the “algorithmization of counterfactuals”, and thus make them available to use by thinking machines.

    What is causal calculus? In essence, it’s a way of modelling the probability (P) of an event (L) happening if an action (X) takes place, while taking into account both mediating variables (so enabling the calculus to model of indirect as well as direct relationships between action and outcome) and influencing variables (so enabling the calculus to quantify and/or isolate other factors that may confuse, complexify or obscure the key relationship being interrogated much as the paragon of this form, the randomised control trial, seeks to do).

    Pearl and his collaborators have developed a visual vernacular for mapping the causal relationships between these various elements for any given situation. These causal graphs in turn allows the construction of counterfactuals: how the mapped causal calculus if an influencing variable impinged on this node instead of that node, or if a mediating relationship should turn out to be reciprocal instead of just one way, for example. Once the pathways have been mapped, it then becomes possible to take data generated in one scenario and test its validity or plausibility in another, apparently comparable, scenario.

    This is much more than a Bayesian prior, though priors play an important role in estimating the initial conditions for any given do-calculus, as Pearl terms his graphs. But the do-calculus itself goes far beyond Bayesian techniques in its power and implications as it compartmentalises and tracks conditions that comprise the system under study, rather than taken a global probability snapshot at a given stage and feeding it back into the evolving prediction calculation. (For a nice summary of the technique — and a second recommendation of the book — check out  this Medium post  by data scientist Ken Tsui).

    As you’d expect, in “The Book of Why” Pearl gives plenty of good toy examples of the do-calculus; what’s particularly interesting about these is the way that even a very simple causal graphs with only five or six nodes can help unpick incredibly thorny issues like the demonstration of causal relationship between smoking and lung cancer, or the comparative impacts of nature and nuture on personality.

    It’s in these test cases, too, that we are able to see the profound impact of this approach on the entire discipline of statistics. It means no less than:

    >
    the mantra “Correlation does not imply causation” should give way to “Some correlations do imply causation.”
    — Judea Pearl, “The Book of Why”

    The do-calculus is the technique that allows us — or our computers — to interrogate situations and their counterfactuals to work out which correlations those are.

    Dr. Freestone continues his lecture at CogX19, with an example of a full causal graph.

    Dr. Freestone continues his lecture at CogX19, with an example of a full causal graph.

    So now, I hope, it should be apparent why Mark Freestone’s talk at CogX 2019 excited me so much. It was the first example I’d come across since reading Pearl’s book of someone applying the do-calculus in the wild. As you can see from the photograph above, the causal graph of actions, outcomes, influences and mediators gets pretty crazy pretty fast when you’re trying to understand cause and effect in a situation as complex as the development of risk models for prediction and management of violence in mental health services (the focus of Freestone’s study).

    The approach is also already beginning to make an impact on robotics. Start-up  Realtime Robotics  is making great progress on enabling interactive movement in machines by using  counterfactual causal models, creating a specialised processor and scripting language (Indigolog) specifically to enable it. DeepMind has been mucking about in this area too, as you’d expect. Check out some of their research findings  here.

    I don’t pretend to be an expert in the do-calculus by any stretch. I’m writing this post partly to celebrate Pearl’s work, partly to tell you that it’s worthy of your attention if you haven’t come across it before, and partly to help me explain it to myself. To really grasp it I need to reread the whole book then start working through some trial examples; if I manage to get round to this while trying to close  Hospify’s seed round (which is keeping me pretty busy), I’ll let you know.

    In the meantime, do go and read “The Book of Why” for yourself. I promise you it’s worth it.

  • What AI wants

    A review of “Architects of Intelligence” by Martin Ford (Packt, 2018)

    Towards the end of last year I was sent a review copy of a new book on AI. I read it over Christmas, and since it was pretty good I thought I’d do a little review of it here, as I’ve been pretty busy managing a growth spurt at  Hospify  lately, and haven’t published on my Medium blog for a while.

    The book is called “Architects of Intelligence: The Truth about AI from the people Building It”, and as the title suggests it’s a collection of interviews, conducted by  Martin Ford, whose recent book “Rise of the Robots” (which I haven’t read) won various plaudits including Financial Times Business book of the year.

    When I received the book, I have to confess wasn’t overwhelmed with enthusiasm. I read a fair number of AI newsletters and listen to quite a few AI podcasts (TWIML AI  is my favourite — shout out to Sam Charrington), and glancing through the list of interviewees it felt a bit like a collection of musings by the usual suspects — Yoshua Bengio, Geoffrey Hinton, Yann LeCun Demis Hassabis, Ray Kurzweil, Gary Marcus, Andrew Ng, Jeff Dean et al. While this is undoubtedly a list of extremely smart people, all of whom have excelled in their fields and have an enormous amounts to say, I did feel like I’ve already read or listened to plenty of interviews with all of them, and wondered what another set of “in conversation” transcripts could add. After all, AI is a technical field, and there’s a point at which general discussion about it loses its charm, and what you want from practitioners is a deeper dive into the nuts and bolts of the techniques involved (one of the things TWIML AI strives for, and often achieves), rather than yet another overview of the landscape.

    However, as I worked my way through the 23 interviews in the book, it became apparent that Ford was doing something quite interesting. The big news in AI at the moment is of course the advances made in deep learning by many of the luminaries listed above — Bengio, Hinton, Hassabis, Ng, LeCun in particular. Ford groups these guys in the first half of the collection, interspersing them with philosophical covering fire from the likes of Nick Bostrom and Ray Kurzweil, the latter making the core point in his interview that “connectionism can emulate a rule-based approach, [but] a rule-based system really cannot emulate a connectionist system, so the converse statement is not the case.”

    This is all great as far as it goes. Don’t get me wrong. I love deep learning. I first came across Hinton’s work (with Rumelhart and McClelland) in connectionism (i.e. deep learning and neural nets) as a post-grad back in 1992, and it blew my mind. I think that the work that’s been in recent years to implement it has been amazing, and it doesn’t need me to tell you that it’s been so transformative for computing in that it has re-energised the whole industry. I’ve even coded some deep learning projects  of my own.

    At the same time, however, as a philosophy and neurophysiology student, and I was (and remain) sceptical of claims that deep learning neural nets, which really only approximate how we think the brain works in the vaguest sense, are all there is to intelligence. After all, intelligence is not just about learning. It’s also about wanting. The philosopher I loved best as a post-grad was Gilles Deleuze, who described the abstract processes that underpin life (and thus intelligence) as “desiring machines”. Deep learning captures the machinic aspect of this tuple as well as any process we’ve been able to instantiate on a computer. What it doesn’t capture is the “desiring”. So far, that bit — the bit that the system wants, the thing that justifies its existence, causes it to act, and assesses its outcomes — is still provided — at every juncture — by the human beings that build the system. Until the machine takes over at least some aspect of that, “artificial intelligence” will remain a misnomer. What we’ll have, as we have now, is “augmented intelligence” or, “machine learning”, the term I prefer.

    This niggle is the point at which “Architects of Intelligence” starts to gain purchase and subsequently gets really interesting. Ford has grouped the sceptics (by which I mean those who believe, as I do, that this is more than a niggle, but the whole crux of the problem), so just when you think the argument is done the voices of dissent begin to surface. The psychologist & technologist Gary Marcus is kind of their cheerleader, but there are many other folk here with strong hands on experience, particularly in robotics — Rana El Kaliouby, Rodney Brooks, Cynthia Breazeal, Joshua Tenenbaum — who point out, repeatedly and convincingly, the hard truth that deep learning, while being fantastic for pulling patterns out of vast data mines and finding signal in noise way beyond human abilities, is just not well-suited to generalising from smaller sample sizes. In the world of textual, voice or image analysis this isn’t a problem, at least not now we have the vast resources of the global internet to throw at it. But once you get out of server farms and into the physical world it’s a showstopper, as generalisation from small sample sizes is the way in which genuinely (as opposed to artificially) intelligent agents are able to extrapolate a desire-driven route through a world about which, in fact, they know very little.

    The conceptual covering fire in this second half of the book is provided by Judea Pearl, who like Hinton was inspired by the work of David Rumelhart, and like Kurzweil has genuinely technical chops, but who provides some serious insights into the nature of probability and causal modelling (and thus desire, to continue with my earlier terminology), demonstrating a philosophical depth well beyond the somewhat excitable futurist extrapolations of his counterparts in the first half the book.

    Ford summarises the point perfectly: “causation can never be learned from data alone.” In statistics, this is almost a cliché. “Causation is not correlation” is a phrase statisticians regularly repeat to each other (and their students) to remind themselves of the importance of not reading too much into raw data. But the cliché, as clichés so often are, is a flag pinned on the site of a profound truth. Not only is not causation not correlation, but they are entirely different beasts, one of which — any quantum physicist will tell you — we can only barely claim to understand. To quote Pearl:

    >
    A child learns causal structure by playful manipulation, and this is how a scientist learns causal structure — playful manipulation. But we have to have the abilities and the template to store what we learn from this playful manipulation so we can use it, test it and change it. […] That is the first thing that we have to learn; we have to program computers to accommodate and manage that template.
    — Judea Pearl

    Neural nets take sample sizes of thousands or millions, and discover patterns in the data. Humans take a sample size of one and generalise patterns from that seed. This is the difference between learning and intelligence. We’ve built machines that exhibit the former. We’re a very long way from building them to exhibit the latter.

    If you stick with it through all of its 500 or so pages, therefore (and I suggest that you do, and that you read the interviews sequentially), I think you’ll find as I did that far from being an ad hoc round up of the self-aggrandising thoughts of the current crop of machine learning geniuses, “Architects of Intelligence” is in fact a very dense and complete overview of the field and a great map of both its achievements and its very real challenges.

    While it doesn’t have much technical detail, what it does have is genuine philosophical and conceptual nuance, and I came away from reading it assured of what I’ve been feeling for some time — that artificial general intelligence is much further off that many would have us believe, but that far from being a disappointment this in fact means is that the current excitement around deep learning is only the first in many such similar flowerings that are going to keep humanity busily engaged for the next few centuries at least, as we edge our way towards an increasingly profound understanding of what it means to build a mind.

  • The intersection of art and science

    Very pleased to see my piece about my experiences on the Springboard Data Science Career Track Course — and the impact of digital on the art/science divide — go live on the Springboard blog, complete with portrait by Sean Geer.

    You can read the piece here.

    Big thanks to all at Springboard, especially Raj, Kane, Jan Zikeš, Janet, Adenika and Julia for all your support throughout the program (and the edit process!); and thank you also to Tabitha Goldstaub from CognitionX for turning me onto the course in the first place. It was an amazing experience, and anyone who’s familiar with the work we’re now doing at Hospify can easily see how transformative it proved to be.

  • Eating data science for breakfast

    I got up nice and early this morning to chair a data science and data protection breakfast in Soho. Nothing like a sprinkling of support vector machines on your granola and a couple of slices of regulation on the side to get you going on a Friday.

    The event was organised by data strategists the Ammonite Group, and it was Chatham House rules so I can’t be too specific about who was there or what was said. But a really interesting collection of data scientists from various different industries including publishing, motor, gambling as well as straight up tech were in the house, so it was an interesting discussion.

    While each of us was grappling with very different data problems, it was fascinating to discover how united we were by the questions we were asking about the ways in which big data and machine learning models were going to be affected by the arrival of GDPR.

    My own company,  Hospify — which provides compliant messaging for healthcare — is very much predicated on the existence of this piece of legislation. We’re all about making sure that the kind of things we’ve seen happen to people’s Facebook data as a result of the Cambridge Analytica debacle doesn’t happen to their medical data too.

    Handling data in a compliant way is Hospify’s stock-in-trade, but like other businesses we’re looking to wring value from that data for our users by using the latest machine learning tools. The trouble is, the compliance part of the equation makes that very difficult for us to do.

    Machine learning technology — which, beneath all the hype about AI amounts to adding a layer of robust feature recognition (and associated transformations) to the compute stack — is arriving just at the moment that the world is waking up to the ways in which the great open data experiment is making us all very vulnerable to whole new kinds of attack.

    Cybersecurity, however, is just one of the challenges we face. As we know at Hospify, things can be highly secure and still not be compliant, as compliance deals with a whole raft of requirements from data storage, consumer opt-in, subject data access requests and the right to be forgotten, all of which can be problematic for a business at the best of times, let alone when the data concerned have been passed through a machine-learning model.

    And that’s before we even get to the right to explanation. There are already conflicting interpretations about what this even means. If you’ve been turned down for insurance because of a decision that was made by an algorithm, what does having a right to know how that decision was made amount to? Should you be given access to every weight in the matrix of a multilayer neural net, which would not only be hard to deliver but also pretty much meaningless? Or do you just have the right to be told the methodologies involved? And if so, which ones, and to what extent?

    On top of this, the amount of data that the digital operations side of any business needs to retain in order to properly do its job is increasing all the time. User profiles, mobile apps, metrics from IoT devices, APIs and analytics of all kinds are moving beyond the realm of the human and into that of the algorithmic just by dint of the sheer volume of information they generate.

    Equally, and driven by smaller chips, better batteries, the need to remove data bottlenecks, and the security risks inherent in putting any information in transit, more processing power is moving out of the cloud and back towards the edges of the network. This creates challenges of its own around tracking, implementation and security, and is something that I personally am particularly interested in.

    This morning’s conversation ranged across all these topics, and generated useful insights into quite a few of them. As a group we felt that a lot of the demand for “right to explanation” could be satisfied by demonstrating best practice in data collection and pre-processing, and that unpicking actual models might be much less necessary than it initially appears to be.

    Where that wouldn’t be sufficient, there were some innovative suggestions for using input-output correlations to give a very human level of insight into decisions around individual cases. Keeping clear separation, when possible, between customer data and transaction data was another top tip; it was also salutary to hear the extent to which the group felt that the third-party data market was already disappearing.

    One particularly thorny area concerned the tension between the regulatory need to identify problematic customer behaviour in certain sectors, and the need to exercise the right to be forgotten. Another red flag was raised about the dangers of introducing bias into data sets via hidden correlations in otherwise innocuous-data sources — questionnaires, for example, whose question sets inadvertently encourage particular types of answer, or put off particular categories of person. As a former psychology student, I’m very familiar with this particular species of difficulty, and know well how tough it can be to eradicate it.

    Another spectre that loomed over the meeting was the feeling that different pieces of legislation often contradicted one another, making it impossible to be sure that you were complying with everything. We talked a lot about how transparency of process and clear opt-outs/opt-ins for users and consumers would help mitigate the chances of falling foul of many of the new rules, but that in quite a lot of situations best practice wouldn’t really be established until after GDPR was in place and some edge cases had been tested in the courts.

    One question we did settle though, before we went out separate ways: whoever had final sign-off on the GDPR, they probably weren’t a data scientist!

  • Move Slow and Fix Things

    Hospify — the compliant chat and data company I founded with two surgeons four years ago, in anticipation of the current storm over widespread data abuse

    Hospify — the compliant chat and data company I founded with two surgeons four years ago, in anticipation of the current storm over widespread data abuse

    I’ve been meaning to blog about my role as CEO of  Hospify for a while now, and the events of the last week or two have convinced me that now’s the time to do it. The exposé of the data abuse conducted by Cambridge Analytica, and its impact on the business models underpinning Facebook in particular but also Google, YouTube and many other digital businesses have underlined the reasons that we founded company in the first place.

    I’m often asked what a journalist is doing running a health chat company, and the Cambridge Analytica story allows me to answer that question very neatly. Besides being a writer, I’d always had a strong interest in technology and like many proto-geeks of my generation did a lot of coding as a teenager thanks to the advent of home computers like the ZX81 and BBC Micro.

    I got my first career break — an editorial position on Wired UK back in the mid-nineties — by combining these two interests, and although my career has ranged fairly widely since, these two things have always remained close to the heart of everything I’ve done.

    After Wired I worked at the BBC for a period, building an early social network based around a TV drama. When that project was killed by the September 11th attacks (long story) I migrated to the Telegraph, where I looked after, by turns, online digital development, online video, and the Telegraph Weekly World Edition newspaper — for which I also built a social network, this time for British Expats.

    My proudest moment at the Telegraph Weekly was producing this: a front page that The Atlantic and The Huffington Post deemed “the greatest newspaper front page ever”

    My proudest moment at the Telegraph Weekly was producing this: a front page that The Atlantic and The Huffington Post deemed “the greatest newspaper front page ever”

    My career has, therefore, always been about both content and its expression, “expression” at this particular period in history meaning the internet, the web, social media, and — latterly — mobile, which combines all these things in the almost magical devices that billions of us carry with us everywhere, all the time, and use to mediate all aspects of our lives.

    I was at the Telegraph long enough to earn a coveted window seat, and when I looked out of that window what I saw was Google, whose offices were right across the street from mine. Because every time I looked at my computer I saw Google too, it followed that I should spend quite a bit of time in those offices, which I did, generally discussing the finer details of Search Engine Optimisation (SEO), then in its infancy but still of considerable importance to a newspaper group.

    While the Telegraph initially did well out of the web, as time went by that success began to wane. This was partly as the result of poor strategic decisions by senior management (don’t get me started), but also because the media as a whole and newspapers in particular were being reconfigured by the exponential expansion of Google, Facebook and others, especially as the world began the shift from the desktop to the phone.


    The Block — a valiant attempt to build a social network around a TV drama four years before Facebook (and decent broadband penetration). Set in a 1 kilometre-high tower, the project was shelved by the BBC in the wake of the 9/11 attacks.

    Sitting in that window seat between 2009 and 2012, it became ever more apparent to me that content was becoming increasingly commodified and that I should put more focus on the expression side of my equation if I wanted to stay remotely relevant. It also became clear to me that this data pact that consumers — and, indeed, the newspapers, themselves — were making with the new tech giants by handing over detailed information about their personalities and habits in return for “free” online services was deeply problematic, not least because of the effect it was having on the economics of my own industry, which I witnessed in a very literal way as month after month more of the excellent journalists who sat all around me got laid off. But it was a new world, everyone wanted to try it out for size, and the services were so good that no one really seemed to care.

    Still, I felt that change was coming one way or another, so when the cutbacks reduced my own team to the point where I felt we could no longer put out a quality product, I left the Telegraph to focus more on online video. When that didn’t work out (another long story) I was contacted by two surgeons, one of whom I’d known since university, and ask to bring my media tech experience to bear on an idea they’d had for improving comms in health.

    I didn’t know too much about healthcare as an industry, but my undergrad degree was in experimental psychology and I’d just spent a decade helping my father through an extended battle with chronic lymphatic leukaemia, so the area wasn’t completely alien to me. I did some research and it was soon obvious to me that not only could the kind of consumer messaging and social media tools provided by the likes of Facebook and the companies it had acquired — notably WhatsApp and Instagram — make a huge difference to efficiency in the provision of healthcare, but that here was an area where, however blasé they were in other areas of their lives, people really would care about what happened to their data.

    I therefore threw my lot in with the surgeons, Neville Dastur and Charles Nduka. We talked to the Information Commissioner’s Office, looked at the data protection legislation in health, did a lot of market testing, reviewed the General Data Protection Regulation that was due to come down the line from Europe (and is due to arrive on May 25th), and built a service with an innovative, data compliant architecture for handling chat and data that provided both with best practice, transparency and simplicity for users and employers — without being funded by sharing personal information or serving ads.

    For much of the three years it took us to do this, most people we spoke to told us we were wasting our time, that the service wasn’t necessary, that people didn’t care, that the big companies would surely beat us to it. But our service went live in the Apple and Android app stores in February, and a few weeks later we’ve seen $50bn wiped off the value of Facebook as the extent of the data misuse enabled by its service has become incontrovertibly obvious to everyone.

    In the meantime, Hospify is being all but overwhelmed with enquiries from clinicians, Trusts, unions and chief information officers, app downloads are increasing every day, and several of the big companies that were perceived as such a threat are now instead in the midst of legal, political and cultural firestorms over the chaos that their lax attitudes to handling data have ignited.

    Into this mess rides GDPR, which is looking extraordinarily relevant all of a sudden. It’s true, of course, that regulation doesn’t change things on its own. The Equal Pay Act of 1970 years ago demonstrates that. It’s only now that the #metoo movement has amplified the frustration of women sufficiently (thanks to social media for once acting in the way it was supposed to) that we’re seeing companies opening up their books on the gender pay gap, and change is actually starting to happen.

    So it goes with data privacy. GDPR on its own could easily be in large part ignored. But when week after week we’re hearing about the awful implications of not taking due care over data, revelations that are coming out as a result of the tireless work of reporters such as the Guardian’s Carole Cadwalladr, who I’m proud to say that I know from my time as journalist (and who deserves to pick up a slew of awards for her efforts), we’re seeing not just regulatory change, but culture change too. And the combination is all but unstoppable.

    We are therefore, I believe, about to enter a new era of data compliance. It’s the era we built Hospify for. Yes, it’s taken a while, but good things take time. Unlike Mark Zuckerberg, who extolled his team to move fast and break things until, alas, they ended up breaking democracy, Hospify’s approach is somewhat more measured. “Move slow and fix things” pretty much sums it up. This is not advertising we’re talking about. It’s health. Mistakes have very real consequences, for very real people. You can’t muck about it with it. It really is life and death.

    So join us! Change will ultimately only come if you, the user, demand it, and choose the tools that help you to enact it. Be the change you want to see in the world, as we have tried to do. Hospify is just one of many other great tools coming through that put data compliance and privacy at the heart of everything they do. Seek them out, use them, tell your friends about them. Because information might want to be free — to quote the Wired axiom from my old dotcom days — but as is now abundantly clear, someone always ends up paying.