Review the table below for availability listed below.
Reserve a time by entering your Work Group the table below. All times are in ET.
New to GoToMeeting? Get the app now and be ready when your first meeting starts: https://global.gotomeeting.com/install/229338669
Tuesday, October 20 1:00 pm
|Payer/Provider Information Exchange||invite sent|
|Tuesday, October 20 3:00 pm||CBCP||invite sent|
|Thursday, October 22 2:00 pm||Public Health||invite sent|
|Monday, October 26 1:00 pm||Pharmacy||invite sent|
|Monday, October 26 3:00 pm||Mobile Health|
Confirmed by MH
|Wednesday, October 28 10:00 am||Imaging Integration||invite sent|
|Friday, October 30 11:00 am||Security WG||invite sent|
|Friday, October 30 4:00 pm||Clinical Quality Information (CQI)||invite sent|
|Monday, November 2 1:00 pm||Clinical Genomics||invite sent|
|Thursday November 12 2:00 pm||CIC at Business meeting||need to reschedule|
|Friday, November 20 11:00 am|
|Friday, November 20 4:00 pm|
** If none of the above times will accommodate your workgroup, please contact firstname.lastname@example.org.
Template for _readme :
Migration to JIRA for capture of specification feedback and comments
The current process to capture comments on specifications varies between product families. In order to standardize how comments are captured across HL7, we will be moving to the use of JIRA. A JIRA Specification Feedback Project has been created for each of the Product Families – CDA, V2 and FHIR. Feedback for other products and specifications such as V3, EHR-S, DAMS, etc. will be assigned to a separate project labelled “Other”.
These Specification Feedback Projects have been set up at jira.hl7.org. FHIR was previously migrated to JIRA for specification feedback, so many of you will already have experience with it. The new projects will have the same look-and-feel and workflow as the FHIR Specification Project.
What does this mean for your Work Group?
The first step for migrating to JIRA is to set up each specification in JIRA to record comments. This includes specifications under development, Active STU specifications currently available for commenting and Expired STU Specifications with incomplete reconciliation of comments. There is no need to create a specification within a project for specifications that are retired, withdrawn or inactive.
- Documentation for this step can be found on Confluence: https://confluence.hl7.org/display/HL7/Configuring+Specification+Feedback
The initial set up of Active STU specifications and Expired STU specifications with ongoing comment reconciliation has been completed or is in progress as follows:
- The CDA Product Management Group is working with Work Groups who have sponsored the creation of a CDA IG to complete this work and will reach out to you to confirm a time for this step
- The V2 Product Management Group has set up the V2 base specifications as well as Active STU Specifications
- Active STU Specifications not part of a Product Family will be set up by HQ
Tasks for Work Groups to complete related to specifications – please notify Melva Peters (email@example.com) for the following:
- Expired STU specification with incomplete reconciliation that should be migrated to JIRA (http://www.hl7.org/dstucomments/index_expired.cfm)
- Specification that is not listed in the “Specification” drop down in the relevant JIRA project
Going forward, the set up and management of specifications in JIRA will be the responsibility of the Co-Chairs of the Sponsoring Work Group and may be delegated to the Project Team. Once JIRA Specification Feedback is rolled out, you will manage all specification comments in JIRA. For more information on managing feedback in JIRA: Managing Specification Feedback
What does this mean for commenters?
Once the specification exists in the JIRA project, comments that you wish to make on the specification will be entered into JIRA. You must register as a user on HL7’s Confluence and Jira systems - if you already have an account in Confluence, this step is not necessary. If you try to enter a comment on a specification and find that it is not in the dropdown, email firstname.lastname@example.org who will notify the Work Group.
You can find more information about how to comment in Confluence: Specification Feedback and in these short videos:
Does this change how comments are made on HL7 Ballots?
For now, no changes will occur with the HL7 ballot process. You will continue to gather comments in spreadsheets as part of a ballot. As with the FHIR Specification Feedback process, submitters may add their comments for specifications that are part of the ballot in JIRA (assuming the specification exists in JIRA), but they must also submit a spreadsheet that references the JIRA issue.
If spreadsheets are submitted, at the conclusion of a ballot, co-chairs will be responsible for consolidating feedback into a single Excel spreadsheet, ‘cleaning’ that spreadsheet to meet Jira import rules and then importing the feedback into Jira prior to reconciliation. See Confluence for more information on how to complete this process: Importing ballot results from spreadsheets. In the short term, help for preparing spreadsheets for import can be requested via Confluence:https://confluence.hl7.org/display/HL7/Request+Help+Uploading+Ballot+Spreadsheets
Reconciliation of ballot comments will be done in JIRA once the spreadsheets have been imported.
How will the migration to JIRA Specification Feedback occur?
The migration will occur in the following phases:
- Implementation of Specification Feedback Projects in JIRA is targeted to begin the week of October 19th
- Work Groups can begin to use JIRA for capturing feedback on specifications as early as October 19th assuming the specification has been created in the relevant project.
- The CDA Management Group will work with Work Groups to complete the addition of specifications into JIRA over a six-week period starting the week of October 19th – as the review is completed, specifications will be migrated to JIRA
- Comments for active STU specifications will be migrated from the STU comments page to JIRA once the specifications have been added – this work will be completed by HQ. Commenting on the STU Comment page will be turned off once this is complete.
- Comments for expired STU specifications that have not completed reconciliation will be migrated as Work Groups confirm the specifications that need to migrate.
- The use of Gforge for entering Trackers will be discontinued as of December 1, 2020
Summary of Activities
Target Completion Date
Begin to use JIRA to record comments and feedback for specifications
October 19, 2020 (for specifications that are in JIRA)
Set up Specifications for V2 and Other Specifications
November 15, 2020
Identify Expired STU Specifications (with comments) to be migrated to JIRA
November 15, 2020
Review documentation on the use of JIRA
December 1, 2020
Work with CDA Management Group to complete review of Specifications to be added
WG Co-Chairs (CDA Management Group will reach out to impacted WGs)
December 1, 2020
Identify missing Specifications that should be added to JIRA
December 1, 2020