FHIR Chat · Task force vs. work group · patient empowerment

Stream: patient empowerment

Topic: Task force vs. work group


view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 19:47):

Apparently the board didn't get this on their agenda. My leaning is to proceed with registering as a work group and see how the process goes. So I guess we now do beat the bushes. @Grahame Grieve is this an appropriate time to make a post on #Announcements and reach out to the co-chair list? We're looking for several more members to sponsor and one more to act as a co-chair.

view this post on Zulip Grahame Grieve (Jul 30 2019 at 19:48):

board discussion was relatively opposed to making it a WG, and rather it be a taskforce. I don't think it matters either way for what we're proposing. Austin suggested yesterday to make a TSC chartered task force, and we (Wayne, Austin and I) are looking into that

view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 19:53):

Task force has no ability to be responsible for content, has no authority to sponsor or co-sponsor projects. I think that's problematic

view this post on Zulip Grahame Grieve (Jul 30 2019 at 19:54):

what content is envisaged?

view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 20:01):

They would presumably have ownership of a few pages in the FHIR core specification. They might also own informative specs governing behavior for patient-facing apps

view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 20:02):

US Realm is the only task force we have that can actually do anything - and the fact that it's a taskforce and not a WG often acts as handcuffs that get in the way. That doesn't seem like a wise way to start out.

view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 20:02):

US Realm needs to have 'tight-ish' rules around who gets a say. But it's not obvious that the same holds for Patient.

view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 20:03):

If we can find the members to qualify as an official work group, that seems the most useful thing to do/be

view this post on Zulip Grahame Grieve (Jul 30 2019 at 20:07):

making it a task force doesn't preclude it becoming a WG in the long term but it does get things going quickly. Which is better than getting mired in counter-productive procedural arguments that don't relate to anything of interest to this group

view this post on Zulip Lloyd McKenzie (Jul 30 2019 at 20:17):

If it starts as a task force, the hurdle to becoming a full work group becomes steeper. Rather than just being evaluated on its merits as an application to form a new work group, there's now a question of transformation - and a need to answer questions around pressing needs for change. I don't understand why we feel a task force is going to be faster. And I don't really understand the push-back against it being a work group.

view this post on Zulip Virginia Lorenzi (Jul 31 2019 at 14:55):

1) Workgroups under OSSD do not need to ballot. 2) I could easily see this group being added on PSSes for other WGs!
Great examples might include Privacy/Consent ballots, patient generated data. 3) , care planning (patient driven), symptom reporting... 3) There are numerous developers and researchers that are working on solving their own health issue so its really not strange at all. We have sick faculty at Columbia that are basically devoting their work to helping patients like them. I would expect that if you get patients together they will invent something to ballot . 4) Lloyd is right - we want this to work. So whatever vehicle is able to connect that patient energy and leadership we should tap it. The patient advocate community is a strong one that is full of energy and some group like this at HL7 can be the conduit to that community. And may help us focus on our mission. To build community we need to connect communities right?

view this post on Zulip Virginia Lorenzi (Jul 31 2019 at 15:02):

They would presumably have ownership of a few pages in the FHIR core specification. They might also own informative specs governing behavior for patient-facing apps

@Lloyd McKenzie don't mean to distract from your point but wanted to give a plug for the CARIN Code of Conduct - https://www.carinalliance.com/our-work/trust-framework-and-code-of-conduct/ (which took a long time to develop with numerous stakeholders) - is addresses some recommended behavior for apps.
although who knows maybe it will need a maintenance home in HL7 like many other great things created outside and maybe that will help in serve its purpose! (@Ryan Howells ) (@Mark Scrimshire ) Could in fact be one of the first "products"


Last updated: Apr 12 2022 at 19:14 UTC