This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

HTA Discussions

From HL7Wiki
Revision as of 16:53, 24 October 2013 by Julie James (talk | contribs) (Created page with "===Discussion between Jim Case and Julie James regarding HTA role in Harmonisation, and HTA process generally=== 22-24 October 2013 Jim: As for the harmonization proposals, I ty...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Discussion between Jim Case and Julie James regarding HTA role in Harmonisation, and HTA process generally

22-24 October 2013

Jim: As for the harmonization proposals, I typically review all of the vocab items that strike my fancy, but am looking at them with more rigor given the opportunity here to move towards the grand plan of using SNOMED CT wherever possible to eliminate the need for HL7 to maintain vocabulary (still just a dream). I noticed this one proposal as a “poster child” for the type of proposal that SHOULD come to the TA and that the TA SHOULD advise harmonization about.

I am not aware of any new documentation for the TA as of yet, although we did talk about what initial organizational documentation is needed (the standard mission and charter, decision-making practices, etc.)

In general, the TA should review every vocab harmonization proposal (how that work is divided will be up to the TA) and each one selected for further review should be evaluated by the TA members in conference calls and a recommendation sent to harmonization in advance of the meeting.

IMHO, every vocab harmonization proposal should have some status recorded by the TA, such as Not Applicable (out of scope for the TA), Reviewed and Declined (reviewed and found to not require a recommendation), Reviewed and Recommended (reviewed and the TA makes a formal recommendation for change to the harmonization process). There are variations on this depending on whether the proposal is realm specific or not.

Julie: Thanks, Jim, that’s very helpful. I for one am particularly hoping that you will stay around as an advisor for some time to come  But it inevitably leads to other questions….who is responsible for getting the TA – us - organised – at least for this coming Harmonisation? Or are we deemed to not have really “got started yet”? Again apologies if all of this was sorted at the get together at the IHTSDO meeting – I was not able to even join by TC for that as I was travelling  and I’ve not seen any notes from that (yet). As well as the documentation you mention, which I’m sure the TA needs, I suggest it may also need some process documentation – these are the main tasks, these are the main things to do in those tasks, and eventually also some documentation about the principles for the decision-making to guide those who come after and to build some “organisational memory”.

Jim: I agree with your other assessments about process. I think when we met at HL7 that was the initial goal, to get some of the processes worked out in more detail. As for this round of harmonization, my opinion is that without the detailed processes some review could be done ad hoc, but nothing in a formal sense. For example, I would think that in the normal process there should be a scheduled meeting of the TA in advance of the harmonization meeting that fits with the harmonization process review (i.e. should the TA meet before or after the harmonization technical review?). It should be a part of the calendar, so the schedule for the meetings would be known far in advance.