As a patient, I interact with the NHS in a number of places. But it’s still the same “me”.
I expect my doctors feel that way too.
#Standards: the common rules that mean our digital services can cross primary, secondary and community care.
When you follow standards, you increase the size of your team.
-From @INTEROPenAPI@twitter.com’s #FHIRhack
I keep coming back to this.
It’s insightful and true.
And if they’re mature, open standards with wide adoption— you have a pre-trained workforce to help you solve your problem, too.
Such an inspiring hack day. We definitely need to do more of them! Well done to all who were building prototypes crossing primary/secondary care boundaries. And community care too!
It’s so exciting to see the promise of interoperability brought to actual user needs.
It was great to talk about the #techvision with some of the best product and digital people in the NHS/DHSC family.
Thanks so much for inviting me along!
RT @firstname.lastname@example.org: Another cracking #HealthProductPeople line up. Thank you to @ColinPattinson@twitter.com @email@example.com @mattedgar @hadleybeeman and Kass for talking all things: tech vision, user needs, service manual and evaluating the success of a project.
Stay tuned for the write up!
Sending good wishes for clean data, RESTful APIs and use cases that make life better for users and citizens — to all at #odcamp. Hope it’s a great day!
*(Except for the ridiculous tweets. Those continue regardless. You knew what you were getting into when you followed any one of us...!)
And so, this quarter’s @tag face-to-face draws to a close. Thanks to all who put up with our WebRTC video calls (inevitably at an odd hour for your time zone!), our unnecessarily wordy questions on GitHub, & our endless ridiculous tweets.
Normal service resumes now.*
We are now revisiting...
The CIA Simple Sabotage Field Manual, 1944
...in our @w3ctag meeting.
Day 3 of @w3ctag face-to-face in Paris. Beginning with design reviews:
In our issues review, we looked in depth at the proposal for Decentralized Identifiers.
Our interim comments: https://github.com/w3ctag/design-reviews/issues/216#issuecomment-434349655
We're now reviewing WebRTC transport (ICE - Interactive Connectivity Establishment) and QUIC
with Martin Thomson, who is kind enough to join us from Australia
This is the current draft of the Security and Privacy Questionnaire for spec authors:
Starting day 2 of @tag face-to-face in Paris with @lukOlejnik@twitter.com sharing his proposed edits to the Security and Privacy Questionnaire to help spec authors/designers design safe new web features.
We the @tag are publishing guidelines for creating web platform compatible components.
When you create custom elements, how to make them fit in well with the rest of the platform?
Started today with guest-star (and former @tag member) @firstname.lastname@example.org, to talk about jointly hosting a workshop on content aggregation and the publisher ecosystem with the @email@example.com.
This is something of an office...!
Architect for #openstandards & the Web. Advisor on tech policy. Co-founder of
. Data & security geek. Active in NHS, UK gov and W3C; views mine.
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!