@ianmcnicoll |
The Usability Problem Pt 1: What the EMR Market Can Learn From Twitter http://t.co/9TkkYL5u #Handihealth #NHShackday >> in spades(Thu, 07 Jun 2012 16:07:35 +0100) |
@HANDIhealth |
Are standards a barrier to innovation? Join us tonight to discuss. Follow the #handihealth hashtag between 8-9pm(Thu, 07 Jun 2012 18:34:44 +0100) |
@HANDIhealth |
60 mins until we begin our #handihealth chat tonight. Join us at 8pm to discuss ?Standards are a barrier to innovation?(Thu, 07 Jun 2012 19:03:42 +0100) |
@Time4Recovery |
Personal Health Record app underscores importance of using patient friendly medical terms http://t.co/FDPxeP4a #mapsandapps #handihealth (Thu, 07 Jun 2012 19:18:15 +0100) |
@HANDIhealth |
10 mins until we start the #handihealth chat. This week?s topic is ?Standards are a barrier to innovation: Discuss? Join us at 8(Thu, 07 Jun 2012 19:51:33 +0100) |
@HANDIhealth |
Evening all and welcome to tonight?s #handihealth chat #handihealth (Thu, 07 Jun 2012 20:01:18 +0100) |
@HANDIhealth |
Tonight’s topic is Standards are a barrier to innovation: Discuss #handihealth (Thu, 07 Jun 2012 20:02:00 +0100) |
@hildegardfranke |
#handihealth Evening all(Thu, 07 Jun 2012 20:02:16 +0100) |
@HANDIhealth |
Hi @hildegardfranke #handihealth (Thu, 07 Jun 2012 20:03:17 +0100) |
@robdykedotcom |
Shared this xkcd cartoon thousands of times http://t.co/XTok7TIF #handihealth (Thu, 07 Jun 2012 20:03:19 +0100) |
@mrcthompson |
@robdykedotcom love it! #handihealth I recall seeing this in one of the presenters slides at the newcastle event. so true(Thu, 07 Jun 2012 20:04:52 +0100) |
@HANDIhealth |
Who else do have tonight? @ianmcnicoll ? #handihealth (Thu, 07 Jun 2012 20:05:50 +0100) |
@ianmcnicoll |
#handihealth Hi all(Thu, 07 Jun 2012 20:06:10 +0100) |
@HANDIhealth |
RT @robdykedotcom : Shared this xkcd cartoon thousands of times http://t.co/de9ayrPq #handihealth (Thu, 07 Jun 2012 20:06:42 +0100) |
@wylpf |
So what exactly do we mean by Standards in this context? #handihealth (Thu, 07 Jun 2012 20:06:46 +0100) |
@HANDIhealth |
Good evening. Shall we start by clarifying what we mean by standards? #handihealth (Thu, 07 Jun 2012 20:07:13 +0100) |
@hildegardfranke |
#handihealth we should probably narrow the statement a bit to say ‘imposed top down standards are a barrier to innovation’?(Thu, 07 Jun 2012 20:07:25 +0100) |
@mrcthompson |
Are we talking about Health Information / Data Standards? #handihealth (Thu, 07 Jun 2012 20:08:57 +0100) |
@HANDIhealth |
@ianmcnicoll mentioned “top down stds can inhibit, emergent standards by consensus should not if done right” can you elaborate? #handihealth (Thu, 07 Jun 2012 20:10:20 +0100) |
@wylpf |
@hildegardfranke wouldn’t always agree with that. Knowing what to aim for by using a standard can be helpful #handihealth (Thu, 07 Jun 2012 20:10:54 +0100) |
@mrcthompson |
RT @robdykedotcom : Shared this xkcd cartoon thousands of times http://t.co/XTok7TIF #handihealth (Thu, 07 Jun 2012 20:12:36 +0100) |
@ianmcnicoll |
#handihealth . If standards dev is agile and responsive + allows extensions, it should be poss to allow innovation. Kinda how web stds work(Thu, 07 Jun 2012 20:12:51 +0100) |
@hildegardfranke |
@wylpf #handihealth I believe there is a difference between knowing what to aim for and having to comply with a standard imposed from above(Thu, 07 Jun 2012 20:13:00 +0100) |
@ianmcnicoll |
#handihealth the challege is on managing innovation and local variation whilst maintaining the best community consensus. Needs communication(Thu, 07 Jun 2012 20:14:33 +0100) |
@HANDIhealth |
are there any models that can be learned from? #handihealth (Thu, 07 Jun 2012 20:15:23 +0100) |
@ianmcnicoll |
#handihealth Managing clinical content stds as small, agile, rapidly iterated components (like apps) is the best approach. ‘Archetypes'(Thu, 07 Jun 2012 20:17:34 +0100) |
@HANDIhealth |
RT @ianmcnicoll : Managing clinical content stds as small, agile, rapidly iterated components (like apps) is the best approach.. #handihealth (Thu, 07 Jun 2012 20:18:59 +0100) |
@wylpf |
@HANDIhealth @ianmcnicoll Are we talking the terminology standards here or messaging / storage standards? #handihealth (Thu, 07 Jun 2012 20:20:36 +0100) |
@Time4Recovery |
RT @robdykedotcom : Shared this xkcd cartoon thousands of times http://t.co/XTok7TIF #handihealth (Thu, 07 Jun 2012 20:21:51 +0100) |
@ianmcnicoll |
#handihealth Terminology + content structure standards e.g. Allergy, Blood pressure. Not persistence though good if they can be(Thu, 07 Jun 2012 20:22:56 +0100) |
@ianmcnicoll |
#handihealth . Messaging std clearly necessary between business prtnrs but not essential to terminology / content stds.(Thu, 07 Jun 2012 20:24:46 +0100) |
@ianmcnicoll |
#handihealth technical interoperability is easy bit, and messaging is not a good way of definig semantics.(Thu, 07 Jun 2012 20:26:01 +0100) |
@wylpf |
@ianmcnicoll hmm, I think a stable terminology standard (if its a good one) is better than an ever changing standard #handihealth (Thu, 07 Jun 2012 20:27:36 +0100) |
@hildegardfranke |
@wylpf #handihealth what do you mean by a ‘stable terminology standard’?(Thu, 07 Jun 2012 20:28:58 +0100) |
@robdykedotcom |
RT @ianmcnicoll : #handihealth technical interoperability is easy bit, and messaging is not a good way of definig semantics.(Thu, 07 Jun 2012 20:30:01 +0100) |
@ianmcnicoll |
#handihealth eHealth stds are never stable, change inevitable. Agree we need as much stability as poss in both terminology/structure but ..(Thu, 07 Jun 2012 20:30:31 +0100) |
@wylpf |
@hildegardfranke one who’s structure (but not necessarily content) is relatively fixed for example #handihealth (Thu, 07 Jun 2012 20:31:04 +0100) |
@robdykedotcom |
stds add value and lower barriers to development and innovation; and I like the way they stack up http://t.co/Mliw0B1o #handihealth (Thu, 07 Jun 2012 20:31:36 +0100) |
@ianmcnicoll |
#handihealth “Innovation eats standards for breakfast” to borrow a phrase.(Thu, 07 Jun 2012 20:31:53 +0100) |
@wylpf |
@ianmcnicoll very true, but innovation can break interoperability #handihealth (Thu, 07 Jun 2012 20:34:22 +0100) |
@ianmcnicoll |
#handihealth OSI model works well for tech stds. Not so well for clinical content stds which r social constructs and need negotiated(Thu, 07 Jun 2012 20:34:26 +0100) |
@hildegardfranke |
@wylpf #handihealth still not sure what you mean – can you give an example?(Thu, 07 Jun 2012 20:34:48 +0100) |
@wylpf |
@ianmcnicoll a lot of recent app innovation is built using existing standards but only interoperable with itself #handihealth (Thu, 07 Jun 2012 20:35:02 +0100) |
@HANDIhealth |
RT @ianmcnicoll : #handihealth technical interoperability is easy bit, and messaging is not a good way of definig semantics. #handihealth (Thu, 07 Jun 2012 20:36:14 +0100) |
@ianmcnicoll |
#handihealth @wylpf Absolutely agree. Apps will create silos but I think the right approach can help devs build shared content models(Thu, 07 Jun 2012 20:37:33 +0100) |
@wylpf |
@hildegardfranke for example the drugs standard dm+d has been stable in terms of model since 2006 #handihealth (Thu, 07 Jun 2012 20:38:04 +0100) |
@robdykedotcom |
@wylpf @ianmcnicoll I’m happy with that; 3rd pty stuff (ESB, ETL, other middleware magic) fixes broken #interoperability #handihealth (Thu, 07 Jun 2012 20:38:55 +0100) |
@ianmcnicoll |
#handihealth We think that #openEHR has cracked this problem of distributed content stds development, using web tools(Thu, 07 Jun 2012 20:39:03 +0100) |
@wylpf |
@ianmcnicoll here’s hoping! Depends whether interoperability is a requirement out of the box, if not, silo apps are worth doinf #handihealth (Thu, 07 Jun 2012 20:39:15 +0100) |
@wylpf |
@hildegardfranke implementers like dm+d as they know the model and that its not likely to change #handihealth (Thu, 07 Jun 2012 20:39:50 +0100) |
@ianmcnicoll |
#handihealth Yup dm+d is a good example of a sensible std to represent meds and allergy agents inside a medication or allergy structure.(Thu, 07 Jun 2012 20:40:12 +0100) |
@ianmcnicoll |
#handihealth was at a meeting in Edinb. yesterday where exactly that was agreed with Allergy structure based on GP2GP archetype + dm+d(Thu, 07 Jun 2012 20:41:18 +0100) |
@HANDIhealth |
RT @ianmcnicoll : We think that #openEHR has cracked this problem of distributed content stds development, using web tools #handihealth (Thu, 07 Jun 2012 20:41:27 +0100) |
@ianmcnicoll |
#handihealth dm+d also adopted as standard medication terminology (UK wide? ) but no common med structures yet.(Thu, 07 Jun 2012 20:43:05 +0100) |
@griffglen |
#handihealth I suggested last week that loads of innovation might also be a barrier to the adoption of standards(Thu, 07 Jun 2012 20:43:34 +0100) |
@robdykedotcom |
Designing digital public services: where we went wrong http://t.co/Tfbck3x4 via @guardian #handihealth great reflective piece(Thu, 07 Jun 2012 20:44:03 +0100) |
@hildegardfranke |
@wylpf #handihealth yes, agree that dm+d is useful to implementers as a terminology standard(Thu, 07 Jun 2012 20:44:27 +0100) |
@robdykedotcom |
#handihealth – last tweet not ‘on topic’, sorry(Thu, 07 Jun 2012 20:44:42 +0100) |
@griffglen |
@HANDIhealth @ianmcnicoll what does open EHR directly compete with in the stds domain? #handihealth (Thu, 07 Jun 2012 20:44:45 +0100) |
@HANDIhealth |
RT @robdykedotcom : Designing digital public services: where we went wrong http://t.co/GRy4ORZy @guardian great reflective piece #handihealth (Thu, 07 Jun 2012 20:46:02 +0100) |
@wylpf |
@ianmcnicoll there are some standards around electronic prescriptions but different in England/Wales/Scotland etc 😦 #handihealth (Thu, 07 Jun 2012 20:46:21 +0100) |
@hildegardfranke |
@wylpf #handihealth exactly – and that’s the implementers nightmare(Thu, 07 Jun 2012 20:47:09 +0100) |
@ianmcnicoll |
#handihealth Traditionally #openEHR competes w HL7v3 and 13606 but times are changing as v3 not delivering as hoped http://t.co/vf4xBpUd (Thu, 07 Jun 2012 20:48:50 +0100) |
@wylpf |
@hildegardfranke yup, you’re someone like Boots or Lloyds and you want to have one system across all sites…very hard to do! #handihealth (Thu, 07 Jun 2012 20:50:19 +0100) |
@griffglen |
@robdykedotcom #handihealth – good example of where a leader (Robert Metcalfe) encouraged vendors to club together 3Com Xerox and Banyan(Thu, 07 Jun 2012 20:50:38 +0100) |
@ianmcnicoll |
#handihealth yes – at least 8 different ways of expressing GP medication. That was reason for Meds stds workshop http://t.co/FWiSlHgI (Thu, 07 Jun 2012 20:53:13 +0100) |
@hildegardfranke |
@wylpf #handihealth no, not 1 system, but an agreed way of expressing the same thing (e.g. prescribed medication) so it can be shared(Thu, 07 Jun 2012 20:53:26 +0100) |
@HANDIhealth |
RT @ianmcnicoll : Traditionly #openEHR competes w HL7v3 & 13606 but time changing v3 nt delivering as hoped http://t.co/qwrJtHGN #handihealth (Thu, 07 Jun 2012 20:55:07 +0100) |
@wylpf |
@hildegardfranke sorry didn’t mean a single system across all, just say Boots using one system in all Boots stores #handihealth (Thu, 07 Jun 2012 20:56:01 +0100) |
@wylpf |
@hildegardfranke agree with not having a *single* system for everyone to use! #handihealth (Thu, 07 Jun 2012 20:56:29 +0100) |
@griffglen |
@HANDIhealth @ianmcnicoll #handihealth as a subset or superset – which way round? would the HL7 community see it that way too?(Thu, 07 Jun 2012 20:57:11 +0100) |
@hildegardfranke |
@griffglen #handihealth subset or superset of what?(Thu, 07 Jun 2012 20:57:49 +0100) |
@ianmcnicoll |
#handihealth Hl7 community agreed that v3 is complex and not working – latest have thing is #FHIR http://t.co/wgI3dDaP more like archetypes(Thu, 07 Jun 2012 21:01:18 +0100) |
@wylpf |
@ianmcnicoll going for the 80/20 split in terms of coverage. Probably a wise idea #handihealth (Thu, 07 Jun 2012 21:03:02 +0100) |
@griffglen |
@hildegardfranke #handihealth where is the overlap? are stds interchangeable? therefore interoperable(Thu, 07 Jun 2012 21:03:43 +0100) |
@mrcthompson |
it was suggested at last chat that #handihealth provide a resource to educate on stds. I would love to see a concise overview of the stds.(Thu, 07 Jun 2012 21:04:26 +0100) |
@HANDIhealth |
We’ve ran over a little on time tonight..& still lots to talk about. Shall we decide on next weeks topic over the coming week? #handihealth (Thu, 07 Jun 2012 21:05:28 +0100) |
@hildegardfranke |
RT @ianmcnicoll : @griffglen #openEHR archetypes are maiximally modelled so usually a superset of HL7 content and transformable #handihealth (Thu, 07 Jun 2012 21:06:35 +0100) |
@griffglen |
@hildegardfranke @ianmcnicoll #handihealth thks- my last tweet should have said operable rather than interoperable(Thu, 07 Jun 2012 21:08:58 +0100) |
@ianmcnicoll |
@mrcthompson #handihealth ‘concise’ guide to ehelth stds might be tricky!! but I will give it a go. So many to choose from :-)(Thu, 07 Jun 2012 21:09:46 +0100) |
@hildegardfranke |
RT @ianmcnicoll : @HANDIhealth I think leave choice of topic unless anyone has a good suggestion now #handihealth (Thu, 07 Jun 2012 21:11:22 +0100) |
@HANDIhealth |
OK, we can tweet for suggestions during the week… in the meantime, thanks everyone for taking part! #handihealth (Thu, 07 Jun 2012 21:14:16 +0100) |
@robdykedotcom |
@mrcthompson I don’t have a cartoon for ‘a concise view of stds’ #handihealth (Thu, 07 Jun 2012 21:14:23 +0100) |
@mrcthompson |
@robdykedotcom OK that can be my job – I’ll have a think 😉 #handihealth (Thu, 07 Jun 2012 21:14:53 +0100) |
@ianmcnicoll |
@robdykedotcom @mrcthompson Sadly I probably do 😦 #handihealth (Thu, 07 Jun 2012 21:15:08 +0100) |
@hildegardfranke |
#handihealth ciao everyone(Thu, 07 Jun 2012 21:15:08 +0100) |
@ianmcnicoll |
#handihealth Bye all, Thanks Chris(Thu, 07 Jun 2012 21:15:48 +0100) |
@mrcthompson |
Goodnight all. Thanks. #handihealth (Thu, 07 Jun 2012 21:16:57 +0100) |
@HANDIhealth |
RT @ianmcnicoll : Hl7 community agreed that v3 is complex & nt working latest thing – #FHIR http://t.co/kxqAt7Jw like archetypes #handihealth (Thu, 07 Jun 2012 21:20:27 +0100) |
@griffglen |
@HANDIhealth @ianmcnicoll #handihealth interesting site – an ad hoc harley award sounds like it might be worth having(Thu, 07 Jun 2012 21:29:00 +0100) |
@curtomil |
RT @ianmcnicoll : #handihealth Managing clinical content stds as small, agile, rapidly iterated components (like apps) is the best approach. ‘Archetypes'(Thu, 07 Jun 2012 22:31:36 +0100) |
@mrcthompson |
Looking for geeks who love the NHS http://t.co/QOOYaJjX #nhshd #handihealth (Thu, 07 Jun 2012 23:09:12 +0100) |
@ppazos |
RT @ianmcnicoll : #handihealth Traditionally #openEHR competes w HL7v3 and 13606 but times are changing as v3 not delivering as hoped http://t.co/vf4xBpUd (Fri, 08 Jun 2012 07:27:15 +0100) |
@claireOT |
Next up, the #handihealth guys, Tweetchats thurs 8-9pm, great people doing great stuff @HANDIhealth @WoodcoteEwan @robdykedotcom (Fri, 08 Jun 2012 08:24:13 +0100) |
@carlplant |
RT @HANDIhealth : http://t.co/3aTh0FrP To help someone stay independent longer #rallyroundme looks interesting #handihealth #careapps #digihealthcon #nhshd (Fri, 08 Jun 2012 08:43:44 +0100) |
@skoba |
RT @ianmcnicoll : #handihealth Hl7 community agreed that v3 is complex and not working – latest have thing is #FHIR http://t.co/wgI3dDaP more like archetypes(Fri, 08 Jun 2012 12:41:10 +0100) |
@skoba |
with openness. RT @ianmcnicoll : #handihealth #openEHR has cracked this problem of distributed content stds development, using web tools(Fri, 08 Jun 2012 12:43:05 +0100) |
@twhicher |
RT @ianmcnicoll : #handihealth Managing clinical content stds as small, agile, rapidly iterated components (like apps) is the best approach. ‘Archetypes'(Fri, 08 Jun 2012 15:22:09 +0100) |