‪There were loads of other amazing innovations — see @amCunningham’s thread for more — and it was challenging indeed to pick winners.‬

Thanks to the organisers and volunteers, and to all those who hacked. Your creativity & skills are inspiring!



‪— and used SVG from KML files to create a map at the top of each card, representing the area.‬

‪We were particularly impressed with the volume of work they accomplished in just two days, and their ability to communicate complicated subjects (the various things that make CAMHS services successful or challenged, and how each region compares to others) in a fun and engaging way. ‬


‪Honourable mention: NHS Top Trumps‬

‪The team dynamically generated top trumps cards reflecting child and adolescent mental health statistics from each local authority.‬

‪They used python for the data wrangling and to create the cards, pushed the data into CSV where they could manage it, —‬


‪— including with a video from the clinician that the patient could examine at home. ‬

‪The app then produced a PDF that could be emailed to patient or clinician, and they aimed to remove thousands of kilogrammes of paper from the system.‬


‪3rd prize: Consent reimagined‬

‪They created a web app to let patient and clinician electronically build a customised consent form, for a patient to understand risk in and agree to a procedure.‬

‪The app had interfaces for the clinician to customise the content for the patient, and for the patient to review it —‬


‪They used a variety of data sources, actually built an API during the weekend for their welsh data (done by a remote participant, but still), created something with practical uses for patients, and provided us with a great illustration for why it’s useful to expose more operational data through APIs‬


‪2nd Prize: Alexa skills on NHS data‬

‪This team created Alexa skills so a patient could ask their Amazon Alexa questions like “What is the wait time at Bryn Beryl Hospital?”, “How much would a prescription cost me?” “What is car parking like at Addenbrooke’s hospital?” and “What is the rating of Kings College Hospital?”‬


‪Then they built the back-end on a vehicle-delivery-problem algorithm, to create sensible routes and direct the most appropriate porter to collect an urgent specimen — and an app to show each porter where they were needed next.‬

Elegant, self-contained problem with a clear user need and a clinical benefit, and massive work by the team this wknd.


‪1st prize: Porteroo‬

Rather than porters rushing round to get/deliver routine collections of blood & specimens, this team created a sign for each collection pt, with a “if urgent, scan this QR-code” to send the specific specimen into the urgent queue.


‪Today’s @nhshackday@twitter.com was our ecosystem at its best: clinicians, entrepreneurs, carers, patients, and developers all setting themselves a user need and building a prototype to fix it.‬

And it was a great honour (and great fun) to judge with @wendyclar@twitter.com and @GillianLeng@twitter.com


@r4vi 🤣 I love that you’ve taken the time to do that. Thank you. :)

‪Jobs: My team needs a new executive assistant!‬
‪Feeling up for a new challenge?‬


Today's @tag meeting (& incidentally, 6am feels much less early in June!):

• PointerEvent extension, to follow the path of a mouse/pointer's motion, like for a drawing app
(See left pane in the image)


‪Not only is this a reusable set of code & architectural work, & should save £ + unlock their data more quickly…‬

The repo’s README also includes some of my favourite words:

“ROQR is very much a work in progress and will keep evolving.”

Good work @YHCareRecord!


‪This is so much fun to see. @YHCareRecord wanted to make it easy for data providers (hospitals/system suppliers/etc) to provide them access to a precise set of data.‬

So they put together plans/code for an open source FHIR server (“ROQR”), so the data providers can use that.


RT @mr_indisingh@twitter.com is championing the move to publishing out code in the open as we develop & LHCRs putting this into action. @YHCareRecord@twitter.com github.com/nhsx/open-source-fh

‪We started the NHS app with lots of user research to meet lots of user needs.‬

‪But since we can’t meet every need for every kind of patient — we’ll keep it thin & expose the APIs, so charities & innovators can create apps for other patient journeys.‬

‪@matthewsgould@twitter.com’s first blog post for :‬


I blogged: to explain why now, why ethics when we're a technical group, and how this fits into our broader @w3ctag work.

Our ethics drive the architecture of the web:


Harassment, disinformation, filter bubbles, algorithmic bias in feeds and ranking...

The web we all create has massive ethical implications. As spec authors, we have a responsibility to consider them.

Our new finding:

@W3CTAG Ethical Web Principles


Show more

For people involved in the activities of the World Wide Web Consortium (W3C), in Working Groups or Community Groups, and people who follow the work of the W3C. Run on a volunteer basis by Sandro Hawke and others, NOT the W3C systems team, and NOT supported by W3C. Uses the W3C Code of Ethics and Professional Conduct. A place to talk online about the things you would talk about in a meeting, or at a meal with your group. We plan to have a relay-bot soon, so don't feel like you need an account here to be a member of this online community. Please post things you think the W3C community might find interesting!