Difference between revisions of "2017-10-30 TSC Call Agenda"
Jump to navigation
Jump to search
Anne wizauer (talk | contribs) |
Anne wizauer (talk | contribs) |
||
(11 intermediate revisions by the same user not shown) | |||
Line 30: | Line 30: | ||
|colspan="2"|Chair/CTO ||colspan="2"|ArB ||colspan="2"|International Affiliate Rep ||colspan="2"|Ad-Hoc | |colspan="2"|Chair/CTO ||colspan="2"|ArB ||colspan="2"|International Affiliate Rep ||colspan="2"|Ad-Hoc | ||
|- | |- | ||
− | | | + | |x||Ken McCaslin||x||Tony Julian||x|| Jean Duteau||x||Freida Hall, GOM Expert |
|- | |- | ||
− | | | + | |x||Wayne Kubick ||x||Lorraine Constable||x|| Giorgio Cangioli||.|| |
|- | |- | ||
|colspan="2" align="center" style="background:#f0f0f0;"|Domain Experts | |colspan="2" align="center" style="background:#f0f0f0;"|Domain Experts | ||
Line 39: | Line 39: | ||
|colspan="2" align="center" style="background:#f0f0f0;"|Technical and Support Services | |colspan="2" align="center" style="background:#f0f0f0;"|Technical and Support Services | ||
|- | |- | ||
− | | | + | |x||Melva Peters||.||Russ Hamm||x||Calvin Beebe||.||Andy Stechishin |
|- | |- | ||
− | | | + | |x||John Roberts||x||Paul Knapp||x||Austin Kreisler||Regrets||Sandra Stuart |
|- | |- | ||
− | | | + | |x||Floyd Eisenberg, Co-chair Elect||. || ||.||Mary Kay McDaniel, Co-chair Elect||.|| |
|- | |- | ||
|colspan="2" align="center" style="background:#f0f0f0;"|''ex officio'' | |colspan="2" align="center" style="background:#f0f0f0;"|''ex officio'' | ||
Line 50: | Line 50: | ||
|colspan="2" align="center" style="background:#f0f0f0;"|HL7 Staff | |colspan="2" align="center" style="background:#f0f0f0;"|HL7 Staff | ||
|- | |- | ||
− | |.||Pat Van Dyke (HL7 Chair) w/vote|| | + | |.||Pat Van Dyke (HL7 Chair) w/vote||x||Hans Buitendijk ||.||''obs1''||x||Anne Wizauer |
|- | |- | ||
|.||Chuck Jaffe (CEO) <s> vote</s>||.||.||.||''obs2''||.|| | |.||Chuck Jaffe (CEO) <s> vote</s>||.||.||.||''obs2''||.|| | ||
Line 70: | Line 70: | ||
##Approve Minutes of [[2017-10-23 TSC Call Agenda]] | ##Approve Minutes of [[2017-10-23 TSC Call Agenda]] | ||
#Review [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=494 action items] – | #Review [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=494 action items] – | ||
− | #Approval items from last | + | ##Austin to draft communication to WGs giving them clarification and instructions on how to handle ballot reconciliation using the language currently in the GOM and HL7 ER |
+ | ##Publication request template | ||
+ | ##*Freida to forward discrepancy between 13.02.07 and 13.02.07.02 to the GOC for review | ||
+ | ##**Freida is working on this with the GOC; has submitted the change request which is now under discussion | ||
+ | ##Anne to post a link to January minutes regarding Withdrawal process | ||
+ | ##*Link to minutes available [http://hl7tsc.org/wiki/index.php?title=2017-01-14_TSC_WGM_Agenda here] | ||
+ | ##Wayne to determine what the ONC needs in terms of trial period being open or not in terms of items cited in government regulation. | ||
+ | #Approval items from previous weeks with followup: | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14039/15819/HL7_Publication_Request_Template_2016May-BRR%20SPL%20R8.docx Normative Publication Request] by the BR&R WG of the DESD for ''HL7 Version 3 Standard: Structured Product Labeling Release 8'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1314 Project Insight 1314] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14039&start=0 TSC Tracker 14039] | ||
+ | ##*'''Referred by Freida:''' Needs date/URL of WG approval minutes, date on which final material was sent to HQ, and response to if substantive changes were made since last ballot. They also probably need to at least update the existing product brief re: what changed in the last ballot. | ||
+ | ##**Anne to resend request copying Melva and John | ||
+ | ##***'''Update: Resent request; no response as of yet.''' | ||
#Approval items for this week: | #Approval items for this week: | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14106/15865/HL7_Publication_Request_FHIR_Quality_QI_Core_PID-1125_2017Sep-01%205%201.docx STU Publication Request] by the CQI WG of the DESD for ''HL7 FHIR Profile: Quality, Release 1 - US Realm'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1125 Project Insight 1125] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14106&start=0 TSC Tracker 14106]'' | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14107/15861/eCR%20FHIR%20HL7%20Project%20Scope%20Statement%20v2017%209%2021%2017%20V5%201.docx Project Approval Request] by the Public Health WG of the DESD for ''FHIR Electronic Case Reporting (eCR)'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1366 Project Insight 1366] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14107&start=0 TSC Tracker 14107] | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14108/15862/CCRF%20DAM%20Publication_Request%202.docx Informative Publication Request] by the CIC WG of the DESD for ''HL7 Domain Analysis Model: Common Clinical Registry Framework, Release 1'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1271 Project Insight 1271] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14108&start=0 TSC Tracker 14108] | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14110/15864/HL7_Structured%20Form%20Definition%20Document_Extension_Request_2017October.docx STU Extension Request] by the Structured Docs WG of the SS-SD for ''HL7 Implementation Guide for CDA® Release 2: Questionnaire Form Definition Document, Release 1'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=335 Project Insight 335] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14110&start=0 TSC Tracker 14110] for 12 months. | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14109/15863/HL7_Questionnaire%20Response%20Document_Extension_Request_2017October.docx STU Extension Request] by the Structured Docs WG of the SSD-SD for ''HL7 Implementation Guide for CDA® Release 2: Questionnaire Response Document, Release 1'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=336 Project Insight 336] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14109&start=0 TSC Tracker 14109] for 12 months. | ||
#Discussion topics: | #Discussion topics: | ||
+ | ##Continued review of requested GOM changes for the next update cycle (Freida/Hans) | ||
+ | ##Review of Withdrawal Process | ||
+ | ##*Withdrawal form [http://www.hl7.org/permalink/?WithdrawANS here] | ||
+ | ##[http://wiki.hl7.org/images/f/f1/Life_Cycle_GovernanceSGB20171011final.docx Product Life Cycle Management Strategy] from SGB - Paul/Austin | ||
+ | ##Revised [http://hl7tsc.org/wiki/images/f/fe/SGB_Mission_and_Charter_TSC_v1_2.docx SGB Mission and Charter] and [http://hl7tsc.org/wiki/images/0/09/Generic-Product-Family-Mission_20171018SGB.docx boilerplate Mission and Charter] - Paul/Austin | ||
+ | ##Essentialism | ||
<!-- #WGM Planning - --> | <!-- #WGM Planning - --> | ||
#[http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=313 Open Issues List]/Parking Lot | #[http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=313 Open Issues List]/Parking Lot | ||
===Minutes=== | ===Minutes=== | ||
− | ''' | + | #Housekeeping |
− | + | ##Introduction of visitors (including declaration of interests) | |
+ | ##Agenda review and approval - | ||
+ | ##*No additions | ||
+ | ##Approve Minutes of [[2017-10-23 TSC Call Agenda]] | ||
+ | ##*Approved via general consent | ||
+ | #Review [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=494 action items] – | ||
+ | ##Austin to draft communication to WGs giving them clarification and instructions on how to handle ballot reconciliation using the language currently in the GOM and HL7 ER | ||
+ | ##*Add for next week | ||
+ | ##Publication request template | ||
+ | ##*Freida to forward discrepancy between 13.02.07 and 13.02.07.02 to the GOC for review | ||
+ | ##**Freida is working on this with the GOC; has submitted the change request which is now under discussion | ||
+ | ##Anne to post a link to January minutes regarding Withdrawal process | ||
+ | ##*Link to minutes available [http://hl7tsc.org/wiki/index.php?title=2017-01-14_TSC_WGM_Agenda here] | ||
+ | ##Wayne to determine what the ONC needs in terms of trial period being open or not in terms of items cited in government regulation. | ||
+ | ##*Complete | ||
+ | #Approval items from previous weeks with followup: | ||
+ | ##[https://gforge.hl7.org/gf/download/trackeritem/14039/15819/HL7_Publication_Request_Template_2016May-BRR%20SPL%20R8.docx Normative Publication Request] by the BR&R WG of the DESD for ''HL7 Version 3 Standard: Structured Product Labeling Release 8'' at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1314 Project Insight 1314] and [https://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=14039&start=0 TSC Tracker 14039] | ||
+ | ##*'''Referred by Freida:''' Needs date/URL of WG approval minutes, date on which final material was sent to HQ, and response to if substantive changes were made since last ballot. They also probably need to at least update the existing product brief re: what changed in the last ballot. | ||
+ | ##**Anne to resend request copying Melva and John | ||
+ | ##***'''Update: Resent request; no response as of yet.''' | ||
+ | ##****MOTION that, in the absence of feedback from the WG, we reject the publication request because of the missing information identified by the TSC: Austin/Melva | ||
+ | ##****VOTE: All in favor | ||
+ | #Discussion topics: | ||
+ | ##Continued review of requested GOM changes for the next update cycle (Freida/Hans) | ||
+ | ##*Last week, the question came up regarding clarifying the language in the GOM on extensions. As GOC started to look at that request, there were several areas of ambiguity, including whether the extensions were additive to the end of the trial period or the start, as well as how long the combination of extensions between TSC and EC can be - is it perpetuity? The other question was the underlying problem of extending the trial period, but is it really the trial we need to extend, or the publication? Do we really need to extend the trial period to be referenced in regulation? | ||
+ | ##*Lorraine: There are cases in which we really want to extend the trial period because we need the comment/update loop to keep going. Wayne: Did confirm with ONC that there are no regulatory requirements that apply as far as they're concerned - they just want something that can be referenced. It doesn't need to be normative and doesn't necessarily need to be in an STU trial period before going to Normative, as long as ONC can reference it. | ||
+ | ##*Hans: Given that info, we need to clarify the lengths of the extensions. Ken: Freida is going to provide an update to the GOM that she will submit to GOC saying we want the STU period to be 1-2 years initially, and then the TSC can extend up to five years from the end of the original STU period. Wayne: There are at least two different types of STU periods - one where comments are being actively collected and one where it's in a more mature state. This regulatory case where we're not going to update it - we're using STU as a convenience to keep it out there, but it's not a real trial use period. Discussion over if we should differentiate and how. Expired STUs are still on the main standards grid, but not on the STU page. | ||
+ | ##**ACTION: EST to review expired STUs not appearing on STU page as they do on the main standards grid. | ||
+ | ##*Freida: So TSC can initially approve 1-2 years for STU. Then can extend up to five years past - i.e., for 6-7 years total publication. Hans: So instead of 1-2 years it should say 1 or 2 years on the GOM update. The GOM also currently says that the TSC cannot provide a trial period for more than 5 years from the original publication date, so this would need to be updated to say 7 years. Freida: I thought we wanted TSC to be permitted to do up to 7 years, and after that, EC would have to do any further extensions. Ken: That is correct. Discussion over next steps. | ||
+ | ##**ACTION: Freida to update the language and bring back to TSC for review | ||
+ | ##*Lorraine notes that ARB will be updating the information in the GOM regarding being on ARB. | ||
+ | ##**ACTION: Add ARB GOM change to January TSC agenda | ||
+ | ##Review of Withdrawal Process | ||
+ | ##*Withdrawal form [http://www.hl7.org/permalink/?WithdrawANS here] | ||
+ | ##**Issue is there is no current step to outline the mechanism for the collection of comments. Discussion over where comments should be collected. Lorraine notes there are 5 different ways we currently collect comments. Wayne states there are even more than that. Ken asks what the target mechanism should be. Needs to be a step in here for the WG to choose where the comments will be collected. | ||
+ | ##***ACTION: Anne to add line "Feedback collection mechanism" - describe the means by which you'll collect comments on this withdrawal and provide link. | ||
+ | ##***ACTION: Anne to delete Gforge from tracker section and state "tracking number assigned and tracking system used." | ||
+ | ##***ACTION: EST to evaluate comment collection mechanisms | ||
+ | ##[http://wiki.hl7.org/images/f/f1/Life_Cycle_GovernanceSGB20171011final.docx Product Life Cycle Management Strategy] from SGB - Paul/Austin | ||
+ | ##*Group reviews. Discussion over if it should be mandatory for the first 5 groups and optional for the remainder? And how would TSC monitor? Ken asks if this has to come to the TSC? Austin states yes, because the management groups report to the TSC. Lorraine states we should cut off the affected groups to those that are formalized. Could recommend best practices but not make it mandatory. Ken would suggest that you're going to be part of HL7, you need to understand and follow the expectations as part of the HL7 product family. Calvin: TSC is the de facto product management group for anything that doesn't a formal family management group. Lorraine: This is asking the families to formalize and document, which is beyond what we've done in the TSC. Paul: It may be that it should apply to niche products as well, such as SPL. Ken: Perhaps we say unless otherwise directed by the TSC, this process should be followed. Lorraine: For the things that don't have a management group, who are we asking to do it? Is it us as TSC? Or the sponsoring WG of the specification? Who is mandated to do this? Calvin: It seems like it would have to be the primary WG on a product by product basis. Austin feels that we make it mandatory for the formal management groups and make it a best practice for others. Group agrees. | ||
+ | ##**ACTION: SGB to review comments on 2017-11-08 call. Need to remove individual products, groups that haven't been stood up yet, and add best practice language for non-product management groups. | ||
+ | ##**ACTION: Add review of remainder of document to homework and further discussion | ||
+ | ##Revised [http://hl7tsc.org/wiki/images/f/fe/SGB_Mission_and_Charter_TSC_v1_2.docx SGB Mission and Charter] and [http://hl7tsc.org/wiki/images/0/09/Generic-Product-Family-Mission_20171018SGB.docx boilerplate Mission and Charter] - Paul/Austin | ||
+ | ##*Add to next week | ||
+ | ##Essentialism | ||
+ | ##*Add to next week | ||
===Next Steps=== | ===Next Steps=== | ||
Line 87: | Line 154: | ||
|- | |- | ||
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/> | |colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/> | ||
− | *[[2017- | + | *[[2017-11-06 TSC Call Agenda]]. |
|} | |} | ||
© 2017 Health Level Seven® International. All rights reserved. | © 2017 Health Level Seven® International. All rights reserved. |
Latest revision as of 14:32, 3 November 2017
TSC Agenda/Minutes
Meeting Info/Attendees
Standing Conference Calls
TSC will hold a Conference Call at 11AM Eastern time, each Monday except during scheduled face-to-face Working Group Meetings unless otherwise noted at TSC_Minutes_and_Agendas.
- GoToMeeting at https://global.gotomeeting.com/join/426505829 using VOIP
- For those without access to microphone/speakers:
- US: +1 (224)501-3318
- Canada: +1 (647)497-9379
- Italy: +39 0 230 57 81 80
- Access Code: 426-505-829
- GoToMeeting ID: 426-505-829
HL7 TSC Meeting Minutes Location: GoToMeeting ID: 426-505-829 |
Date: 2017-MM-DD Time: 11:00 AM U.S. Eastern | |
Facilitator: Ken McCaslin | Note taker(s): Anne Wizauer |
Quorum = chair + 5 including 2 SD represented | yes/no | ||||||
Chair/CTO | ArB | International Affiliate Rep | Ad-Hoc | ||||
x | Ken McCaslin | x | Tony Julian | x | Jean Duteau | x | Freida Hall, GOM Expert |
x | Wayne Kubick | x | Lorraine Constable | x | Giorgio Cangioli | . | |
Domain Experts | Foundation and Technology | Structure and Semantic Design | Technical and Support Services | ||||
x | Melva Peters | . | Russ Hamm | x | Calvin Beebe | . | Andy Stechishin |
x | John Roberts | x | Paul Knapp | x | Austin Kreisler | Regrets | Sandra Stuart |
x | Floyd Eisenberg, Co-chair Elect | . | . | Mary Kay McDaniel, Co-chair Elect | . | ||
ex officio | Invited Guests | Observers | HL7 Staff | ||||
. | Pat Van Dyke (HL7 Chair) w/vote | x | Hans Buitendijk | . | obs1 | x | Anne Wizauer |
. | Chuck Jaffe (CEO) |
. | . | . | obs2 | . |
|
. | . | . | . | . | |||
Agenda
- Housekeeping
- Introduction of visitors (including declaration of interests)
- Agenda review and approval -
- Approve Minutes of 2017-10-23 TSC Call Agenda
- Review action items –
- Austin to draft communication to WGs giving them clarification and instructions on how to handle ballot reconciliation using the language currently in the GOM and HL7 ER
- Publication request template
- Freida to forward discrepancy between 13.02.07 and 13.02.07.02 to the GOC for review
- Freida is working on this with the GOC; has submitted the change request which is now under discussion
- Freida to forward discrepancy between 13.02.07 and 13.02.07.02 to the GOC for review
- Anne to post a link to January minutes regarding Withdrawal process
- Link to minutes available here
- Wayne to determine what the ONC needs in terms of trial period being open or not in terms of items cited in government regulation.
- Approval items from previous weeks with followup:
- Normative Publication Request by the BR&R WG of the DESD for HL7 Version 3 Standard: Structured Product Labeling Release 8 at Project Insight 1314 and TSC Tracker 14039
- Referred by Freida: Needs date/URL of WG approval minutes, date on which final material was sent to HQ, and response to if substantive changes were made since last ballot. They also probably need to at least update the existing product brief re: what changed in the last ballot.
- Anne to resend request copying Melva and John
- Update: Resent request; no response as of yet.
- Anne to resend request copying Melva and John
- Referred by Freida: Needs date/URL of WG approval minutes, date on which final material was sent to HQ, and response to if substantive changes were made since last ballot. They also probably need to at least update the existing product brief re: what changed in the last ballot.
- Normative Publication Request by the BR&R WG of the DESD for HL7 Version 3 Standard: Structured Product Labeling Release 8 at Project Insight 1314 and TSC Tracker 14039
- Approval items for this week:
- STU Publication Request by the CQI WG of the DESD for HL7 FHIR Profile: Quality, Release 1 - US Realm at Project Insight 1125 and TSC Tracker 14106
- Project Approval Request by the Public Health WG of the DESD for FHIR Electronic Case Reporting (eCR) at Project Insight 1366 and TSC Tracker 14107
- Informative Publication Request by the CIC WG of the DESD for HL7 Domain Analysis Model: Common Clinical Registry Framework, Release 1 at Project Insight 1271 and TSC Tracker 14108
- STU Extension Request by the Structured Docs WG of the SS-SD for HL7 Implementation Guide for CDA® Release 2: Questionnaire Form Definition Document, Release 1 at Project Insight 335 and TSC Tracker 14110 for 12 months.
- STU Extension Request by the Structured Docs WG of the SSD-SD for HL7 Implementation Guide for CDA® Release 2: Questionnaire Response Document, Release 1 at Project Insight 336 and TSC Tracker 14109 for 12 months.
- Discussion topics:
- Continued review of requested GOM changes for the next update cycle (Freida/Hans)
- Review of Withdrawal Process
- Withdrawal form here
- Product Life Cycle Management Strategy from SGB - Paul/Austin
- Revised SGB Mission and Charter and boilerplate Mission and Charter - Paul/Austin
- Essentialism
- Open Issues List/Parking Lot
Minutes
- Housekeeping
- Introduction of visitors (including declaration of interests)
- Agenda review and approval -
- No additions
- Approve Minutes of 2017-10-23 TSC Call Agenda
- Approved via general consent
- Review action items –
- Austin to draft communication to WGs giving them clarification and instructions on how to handle ballot reconciliation using the language currently in the GOM and HL7 ER
- Add for next week
- Publication request template
- Freida to forward discrepancy between 13.02.07 and 13.02.07.02 to the GOC for review
- Freida is working on this with the GOC; has submitted the change request which is now under discussion
- Freida to forward discrepancy between 13.02.07 and 13.02.07.02 to the GOC for review
- Anne to post a link to January minutes regarding Withdrawal process
- Link to minutes available here
- Wayne to determine what the ONC needs in terms of trial period being open or not in terms of items cited in government regulation.
- Complete
- Austin to draft communication to WGs giving them clarification and instructions on how to handle ballot reconciliation using the language currently in the GOM and HL7 ER
- Approval items from previous weeks with followup:
- Normative Publication Request by the BR&R WG of the DESD for HL7 Version 3 Standard: Structured Product Labeling Release 8 at Project Insight 1314 and TSC Tracker 14039
- Referred by Freida: Needs date/URL of WG approval minutes, date on which final material was sent to HQ, and response to if substantive changes were made since last ballot. They also probably need to at least update the existing product brief re: what changed in the last ballot.
- Anne to resend request copying Melva and John
- Update: Resent request; no response as of yet.
- MOTION that, in the absence of feedback from the WG, we reject the publication request because of the missing information identified by the TSC: Austin/Melva
- VOTE: All in favor
- Update: Resent request; no response as of yet.
- Anne to resend request copying Melva and John
- Referred by Freida: Needs date/URL of WG approval minutes, date on which final material was sent to HQ, and response to if substantive changes were made since last ballot. They also probably need to at least update the existing product brief re: what changed in the last ballot.
- Normative Publication Request by the BR&R WG of the DESD for HL7 Version 3 Standard: Structured Product Labeling Release 8 at Project Insight 1314 and TSC Tracker 14039
- Discussion topics:
- Continued review of requested GOM changes for the next update cycle (Freida/Hans)
- Last week, the question came up regarding clarifying the language in the GOM on extensions. As GOC started to look at that request, there were several areas of ambiguity, including whether the extensions were additive to the end of the trial period or the start, as well as how long the combination of extensions between TSC and EC can be - is it perpetuity? The other question was the underlying problem of extending the trial period, but is it really the trial we need to extend, or the publication? Do we really need to extend the trial period to be referenced in regulation?
- Lorraine: There are cases in which we really want to extend the trial period because we need the comment/update loop to keep going. Wayne: Did confirm with ONC that there are no regulatory requirements that apply as far as they're concerned - they just want something that can be referenced. It doesn't need to be normative and doesn't necessarily need to be in an STU trial period before going to Normative, as long as ONC can reference it.
- Hans: Given that info, we need to clarify the lengths of the extensions. Ken: Freida is going to provide an update to the GOM that she will submit to GOC saying we want the STU period to be 1-2 years initially, and then the TSC can extend up to five years from the end of the original STU period. Wayne: There are at least two different types of STU periods - one where comments are being actively collected and one where it's in a more mature state. This regulatory case where we're not going to update it - we're using STU as a convenience to keep it out there, but it's not a real trial use period. Discussion over if we should differentiate and how. Expired STUs are still on the main standards grid, but not on the STU page.
- ACTION: EST to review expired STUs not appearing on STU page as they do on the main standards grid.
- Freida: So TSC can initially approve 1-2 years for STU. Then can extend up to five years past - i.e., for 6-7 years total publication. Hans: So instead of 1-2 years it should say 1 or 2 years on the GOM update. The GOM also currently says that the TSC cannot provide a trial period for more than 5 years from the original publication date, so this would need to be updated to say 7 years. Freida: I thought we wanted TSC to be permitted to do up to 7 years, and after that, EC would have to do any further extensions. Ken: That is correct. Discussion over next steps.
- ACTION: Freida to update the language and bring back to TSC for review
- Lorraine notes that ARB will be updating the information in the GOM regarding being on ARB.
- ACTION: Add ARB GOM change to January TSC agenda
- Review of Withdrawal Process
- Withdrawal form here
- Issue is there is no current step to outline the mechanism for the collection of comments. Discussion over where comments should be collected. Lorraine notes there are 5 different ways we currently collect comments. Wayne states there are even more than that. Ken asks what the target mechanism should be. Needs to be a step in here for the WG to choose where the comments will be collected.
- ACTION: Anne to add line "Feedback collection mechanism" - describe the means by which you'll collect comments on this withdrawal and provide link.
- ACTION: Anne to delete Gforge from tracker section and state "tracking number assigned and tracking system used."
- ACTION: EST to evaluate comment collection mechanisms
- Issue is there is no current step to outline the mechanism for the collection of comments. Discussion over where comments should be collected. Lorraine notes there are 5 different ways we currently collect comments. Wayne states there are even more than that. Ken asks what the target mechanism should be. Needs to be a step in here for the WG to choose where the comments will be collected.
- Withdrawal form here
- Product Life Cycle Management Strategy from SGB - Paul/Austin
- Group reviews. Discussion over if it should be mandatory for the first 5 groups and optional for the remainder? And how would TSC monitor? Ken asks if this has to come to the TSC? Austin states yes, because the management groups report to the TSC. Lorraine states we should cut off the affected groups to those that are formalized. Could recommend best practices but not make it mandatory. Ken would suggest that you're going to be part of HL7, you need to understand and follow the expectations as part of the HL7 product family. Calvin: TSC is the de facto product management group for anything that doesn't a formal family management group. Lorraine: This is asking the families to formalize and document, which is beyond what we've done in the TSC. Paul: It may be that it should apply to niche products as well, such as SPL. Ken: Perhaps we say unless otherwise directed by the TSC, this process should be followed. Lorraine: For the things that don't have a management group, who are we asking to do it? Is it us as TSC? Or the sponsoring WG of the specification? Who is mandated to do this? Calvin: It seems like it would have to be the primary WG on a product by product basis. Austin feels that we make it mandatory for the formal management groups and make it a best practice for others. Group agrees.
- ACTION: SGB to review comments on 2017-11-08 call. Need to remove individual products, groups that haven't been stood up yet, and add best practice language for non-product management groups.
- ACTION: Add review of remainder of document to homework and further discussion
- Group reviews. Discussion over if it should be mandatory for the first 5 groups and optional for the remainder? And how would TSC monitor? Ken asks if this has to come to the TSC? Austin states yes, because the management groups report to the TSC. Lorraine states we should cut off the affected groups to those that are formalized. Could recommend best practices but not make it mandatory. Ken would suggest that you're going to be part of HL7, you need to understand and follow the expectations as part of the HL7 product family. Calvin: TSC is the de facto product management group for anything that doesn't a formal family management group. Lorraine: This is asking the families to formalize and document, which is beyond what we've done in the TSC. Paul: It may be that it should apply to niche products as well, such as SPL. Ken: Perhaps we say unless otherwise directed by the TSC, this process should be followed. Lorraine: For the things that don't have a management group, who are we asking to do it? Is it us as TSC? Or the sponsoring WG of the specification? Who is mandated to do this? Calvin: It seems like it would have to be the primary WG on a product by product basis. Austin feels that we make it mandatory for the formal management groups and make it a best practice for others. Group agrees.
- Revised SGB Mission and Charter and boilerplate Mission and Charter - Paul/Austin
- Add to next week
- Essentialism
- Add to next week
- Continued review of requested GOM changes for the next update cycle (Freida/Hans)
Next Steps
Actions (Include Owner, Action Item, and due date)
| |||
Next Meeting/Preliminary Agenda Items |
© 2017 Health Level Seven® International. All rights reserved.