Sarah,

 

Not a problem on delay. As for the Git stuff, I am very happy to meet and work through. I think you can definitely do all that and happy to show how I would approach (there’s a couple ways to approach). If you want to try and connect before Monday CDAMG, maybe we can get Git sorted and try to approve at WGM. CDAMG is meeting Monday Q4 and Thursday Q0. Right now, I could do:

 

 

As for #1 and #3, I’ll bring those up today at CDAMG and get some feedback from the group.

 

Cheers,

John

 

 

From: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Sent: Tuesday, May 2, 2023 4:44 PM
To: John D'Amore <johnd@moreinformatics.com>
Cc: cdamg@lists.hl7.org
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Hi John,

 

Sorry, I’ve just been able to get to this again.

 

  1. The changes were done outside of Jira – the CDC NHSN client has their own change request process.
  2. I don’t really understand the Git repo stuff. I am not very good with Git repos, I can do the basics, but beyond that… I’m not even sure how to proceed here.
    1. So with the set up you are proposing, is it possible for me to keep the multiple releases separate on my machine and update them when I need to, like if I need to update a sample file from a previous release, but NOT from a later release, can I just go into a folder on my machine and do that and push it up to Git? And then the implementers can grab that file?
    2. If you look at the link below for the different versions of the IGs that NHSN is using, does that make any difference to your recommendation on how to set up the git folders?
  3. This IG (well the regular HAI version) has been in production for over 10 years. I think that we REALLY don’t want to change the name if at all possible. Changing to “Edition” from “Release” is going to cause major confusion. They are still calling things D (for DSTU!) – see their Guide to CDA versions here: https://www.cdc.gov/nhsn/cdaportal/toolkits/guidetocdaversions.html
    1. I can fix up the cover page
    2. NHSN still has many versions of the IG in production

 

Are you going to be at the WGM next week? Would it be possible to get together to talk/get some help on the Git issue?

 

Thanks,

Sarah

 

Sarah Gaunt (she, her)

Senior Information Analyst

t: +61 410 292 506

Brisbane, Australia (Australian Eastern Standard Time)

 

 

From: John D'Amore <johnd@moreinformatics.com>
Sent: Wednesday, April 26, 2023 6:45 AM
To: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Cc: cdamg@lists.hl7.org
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Sarah,

 

In order of the items:

 

  1. The query you shared is private, but I was able to create a query for the JIRA issues like this:
    1. project = CDA AND Specification ~ "National Healthcare Safety Network (NHSN) Healthcare Associated Infection (HAI) Reports for Long Term Care Facilities (HAI-LTCF-CDA) (CDA)"  ORDER BY created DESC
    2. That returned no unresolved issues, on that query, but I also don’t see your changes listed here in JIRA: https://confluence.hl7.org/display/PHWG/Update%3A+CDA+IG+-+NHSN+Healthcare+Associated+Infection+%28HAI%29+Report+for+Long+Term+Care+Facilities+%28LTCF%29%2C+Release+1%2C+STU+1.1
    3. Were the changes tracked against another specification or just done outside of JIRA?
  2. So I don’t entirely understand the issue. You can “tag” prior releases and also keep all the branches from multiple releases (detailed instructions are here, which I acknowledge you’ve looked at since you commented about in 2022: https://confluence.hl7.org/display/SD/CDA+Github+Repository+Best+Practices). That way you can have all the branches but the latest release should be merged into “main.” If “main” is currently on a prior release which you need to reference, just create a tag (or branch if you prefer) from the current “main” branch and then you can always refer to that after you merge the new branch. HL7 repo consistency helps in the following:
    1. A single repo makes tracking by CMG and HL7 easier than having many repos for each release
    2. A single repo makes change tracking easier than having multiple repositories
    3. Having the “main” (or previously “master”) branch represents the latest and greatest (either a release or work in progress) and is organized with content under “input” folder makes it easier for others to find who are used to HL7 repos

I am happy to jump on a call this week to help fix, but I am not comfortable to say that the checklist criteria are met with the repo the way it is. If the larger group thinks it’s reasonable, then obviously we can proceed, but I think it’s something that could be changed to the standard way without losing any functionality (noting that I may not fully understand all issues, which is where I started).

  1. I agree that the naming conventions have changed. This is being added to the GOM. I think they might already be there…see section 13.03 http://www.hl7.org/documentcenter/public/membership/HL7_Governance_and_Operations_Manual.pdf copied below for convenience (highlighting added)
    1. {Family Name} [R {Release Number}] {Product Type}: {Product Name}, Edition {Edition Number}
    2. There is the possibility to override this but would want to have the group review
    3. In addition, it would be helpful to add the specific version (1.1.1) to the cover page as outlined in the CDA checklist step 2

                                                               i.      Example Cover Page information:
Specification Date: August 2015
Specification Name: HL7 CDA R2 Implementation Guide: Consolidated CDA Templates for Clinical Notes (C-CDA)
Specification Version: 2.1.0.7 August 2022

    1. It sounds like you intend to keep multiple versions open for comment. That’s what you have in JIRA now (both 1.1.1 and 1.1.0) https://github.com/HL7/JIRA-Spec-Artifacts/blob/master/xml/CDA-hailtcfcda.xml but just confirming
  1. It looks like the other changes were done. The ballot and product brief links are on the CDA Management Group approval page, so all set there.

 

Apologies that I lost track of your responses form the 12th! Let me know if you would like to jump on a call or if we should defer until the CDA Management Group reconvenes at next Wednesday (5/3).

 

Cheers,

John

 

 

From: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Sent: Wednesday, April 12, 2023 3:58 PM
To: John D'Amore <johnd@moreinformatics.com>
Cc: cdamg@lists.hl7.org
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Hi John,

 

Thanks for looking at this at such short notice!

 

Notes in red below.

 

Thanks,

Sarah

 

 

Sarah Gaunt (she, her)

Senior Information Analyst

t: +61 410 292 506

Brisbane, Australia (Australian Eastern Standard Time)

 

 

From: John D'Amore <johnd@moreinformatics.com>
Sent: Thursday, April 13, 2023 3:00 AM
To: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Cc: cdamg@lists.hl7.org
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Notes on CDA review (from checklist)

 

Two unresolved JIRA. One is motioned and marked Persuasive. Are you deferring these changes? SG: Those unresolved Jiras are for a different IG.  This is the HAI LTC IG (they are very similar names!). Try this query: https://jira.hl7.org/issues/?filter=18511&jql=project%20%3D%20%22CDA%20Specification%20Feedback%22%20AND%20Specification%20%3D%20%22National%20Healthcare%20Safety%20Network%20(NHSN)%20Healthcare%20Associated%20Infection%20(HAI)%20Reports%20for%20Long%20Term%20Care%20Facilities%20(HAI-LTCF-CDA)%20(CDA)%20%5BCDA-hailtcfcda%5D%22

 

 

Your github does not follow naming conventions. Discuss with CDA MG https://github.com/HL7/CDAR2_IG_HAI_LTCF_R1_D1/

 

https://github.com/HL7/CDAR2_IG_HAI_LTCF_R1_D1

Should have an input folder with your content. You need to merge your branch CDA-hai-ltcf-1.1.1 into master likely SG: We really need to keep the branches separate. NHSN provides support for each distinct version of the IG – and also updates the files over time. I’d really prefer not to merge if I don’t have to. My preference would be to have totally separate repos for each release, but that isn’t the pattern specified by CDA MG. Not sure how to proceed with this one.

 

 

Name change

Current: HL7 CDA® R2 Implementation Guide: National Healthcare Safety Network (NHSN) Healthcare Associated Infection (HAI) Reports for Long Term Care Facilities (HAI-LTCF-CDA), Release 1, STU 1.1 - US Realm

Should be: HL7 CDA® R2 Implementation Guide: National Healthcare Safety Network (NHSN) Healthcare Associated Infection (HAI) Reports for Long Term Care Facilities (HAI-LTCF-CDA), Edition 1, STU 1.1 - US Realm SG: Was not aware of the Edition thing. This is not really aligned with all the past releases. Where is this documented – I totally missed it. Do we HAVE to follow this? The product brief here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=546 says “Release” not “Edition” and this is an update to Release 1, not Edition 1.

 

In your Footer, I think “April 2023” is more consistent than “April 2023 Update” SG: Will update

 

Your document Volume 2 still says Volume 1 in the title SG: Great catch, will update

 

Can you provide the ballot information? Didn’t see that but we track on approval log. SG: This was balloted back in 2019 Sept (http://www.hl7.org/ctl.cfm?action=ballots.tallydetail&ballot_id=1775&ballot_cycle_id=550&ballot_voter_id=14672). The unballoted update (dot release) information is here (link plus others at the start of this email thread): https://confluence.hl7.org/display/PHWG/Update%3A+CDA+IG+-+NHSN+Healthcare+Associated+Infection+%28HAI%29+Report+for+Long+Term+Care+Facilities+%28LTCF%29%2C+Release+1%2C+STU+1.1

 

 

Cheers,

John

 

 

From: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Sent: Wednesday, April 12, 2023 2:12 AM
To: Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>
Cc: cmg_inbox@hl7.org; Anne Wizauer (HL7) <anne@hl7.org>; Dave Hamill (HL7) <dhamill@hl7.org>
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Sorry guys – I’m late doing the checklist.

 

It’s here: https://confluence.hl7.org/display/PHWG/2023-04+HAI+LTC+CDA+Publication+Request+Checklist

 

Sarah Gaunt (she, her)

Senior Information Analyst

t: +61 410 292 506

Brisbane, Australia (Australian Eastern Standard Time)

 

 

From: Sarah Gaunt
Sent: Thursday, March 30, 2023 7:13 AM
To: Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>
Cc: cmg_inbox@hl7.org; Anne Wizauer (HL7) <anne@hl7.org>; Dave Hamill (HL7) <dhamill@hl7.org>
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Thank you! I 100% forgot to do it yesterday…

 

Sarah Gaunt (she, her)

Senior Information Analyst

t: +61 410 292 506

Brisbane, Australia (Australian Eastern Standard Time)

 

 

From: Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>
Sent: Thursday, March 30, 2023 4:17 AM
To: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Cc: cmg_inbox@hl7.org; Anne Wizauer (HL7) <anne@hl7.org>; Dave Hamill (HL7) <dhamill@hl7.org>
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Hi Sarah,

 

CMG is planning on tenatively putting the NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1 dot release on the Agenda for April 12th. Our meeting is from 1-2:30 pm ET.

 

If you can complete the checklist by EOD, April 6th, this will give the co-chairs enough time to do their review prior to the call April 12th call.

Let us know if you have any time restrictions.

 

Thanks!

Zabrina

 

 

From: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Sent: Tuesday, March 28, 2023 4:39 PM
To: Yan Heras <yan.heras@optimumehealth.com>; Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>; 'Dave Carlson' <dcarlson@mieweb.com>
Cc: 'Anne Wizauer (HL7)' <anne@hl7.org>; 'Dave Hamill (HL7)' <dhamill@hl7.org>
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Thanks! Will do the checklist today and let you know where it is when I’m finished. 😊

 

Sarah Gaunt (she, her)

Senior Information Analyst

t: +61 410 292 506

Brisbane, Australia (Australian Eastern Standard Time)

 

 

From: Yan Heras <yan.heras@optimumehealth.com>
Sent: Wednesday, March 29, 2023 2:02 AM
To: Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>; 'Dave Carlson' <dcarlson@mieweb.com>; Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Cc: 'Anne Wizauer (HL7)' <anne@hl7.org>; 'Dave Hamill (HL7)' <dhamill@hl7.org>
Subject: RE: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Thanks Zabrina.

 

From: Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>
Sent: Tuesday, March 28, 2023 5:16 AM
To: 'Dave Carlson' <dcarlson@mieweb.com>; Yan Heras <yan.heras@optimumehealth.com>; Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Cc: Anne Wizauer (HL7) <anne@hl7.org>; Dave Hamill (HL7) <dhamill@hl7.org>
Subject: FW: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

 

Hi Dave and Yan,

 

Both Anne and Dave H are out of the office through March 29th, I’ll go ahead and add this topic as a “user submitted” topic for us to discuss tomorrow.

 

@Sarah Gaunt – no need to attend tomorrow.  Let us know when you complete the checklist.

 

We will follow up with you after our call.

 

Thanks!

 

Zabrina

 

 

 

From: Zabrina Gonzaga
Sent: Tuesday, March 28, 2023 7:48 AM
To: Anne Wizauer (HL7) <anne@hl7.org>; 'Dave Carlson' <dcarlson@mieweb.com>; Yan Heras <yan.heras@optimumehealth.com>; Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Cc: Dave Hamill (HL7) <dhamill@hl7.org>
Subject: FW: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Anne,

 

Would you mind adding this to the agenda ?

 

Dave Carslon, Yan – perhaps we can put aside 2-3 minutes just to discuss this tomorrow as to when we can bring this to CMG for a vote/eVote?  Then, we can get back to Sarah on timing.

 

@Sarah Gaunt – do you have a deadline you are trying to meet?

 

Thanks!

Zabrina

 

 

 

 

From: Sarah Gaunt <sarah.gaunt@lantanagroup.com>
Sent: Tuesday, March 28, 2023 12:20 AM
To: Lisa Nelson <lnelson@max.md>; Zabrina Gonzaga <zabrina.gonzaga@lantanagroup.com>; 'Yan Heras' <yan.heras@optimumehealth.com>; 'Michaelsen, Linda J' <linda.michaelsen@optum.com>; 'Dave Carlson' <dcarlson@mieweb.com>; 'John D'Amore' <jdamore@diameterhealth.com>; 'Didi Davis' <ddavis@sequoiaproject.org>; brett@waveoneassociates.com; 'Raychelle Fernandez' <raychelle@dynamichealthit.com>; giorgio.cangioli@gmail.com; emma.jones@emiadvisors.net
Subject: CDA Mgmt Group Agenda (eVote?) Request: NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1

 

Hi all,

 

Could we get on the next CDA Management Group agenda (or the next eVote?) to seek approval for Publication of the NHSN Healthcare Associated Infection (HAI) Report for Long Term Care Facilities (LTCF), Release 1, STU 1.1 dot release (it has been through the un-balloted STU IG update process):

 

 

Can you let me know which date we can get on the agenda and I will plan to attend (or let me know if it’s just an eVote).

 

Let me know if you need any more information.

 

Thanks,

Sarah

 

Sarah Gaunt (she, her)

t: +61 410 292 506

Brisbane, Australia (Australian Eastern Standard Time)