Ballot processes: Grahame reports that on Thursday, he became aware of a FHIR ballot that he was unaware of that was supposed to be published on Github (CDS Hooks). Paul notes it wasn't publishing that was approved, it was balloting that was approved. Grahame clarifies that you have to publish something to go to ballot. Need to determine if you can ballot on Github. The other problem is there is no copyright agreement with Boston Children's on CDS Hooks. Grahame has asked the NIB approval process to be modified to let the product director know about the NIBs. Will discuss publishing to Github at a later date. Paul notes that the PSS did not mention joint copyright so we should get that amended. Grahame notes this project will generate 3 or 4 ballot items, so perhaps that should also be included in the PSS. Paul: Appeared to be an omnibus PSS that would liaise with CDS Hooks. If you have IP or external arrangements, it should be called out in its own PSS. Timelines were also vague. Brian Pech notes that Lorraine Constable has been coming to EST calls for the last couple weeks to talk about the use of Github with CIMI. From an EST standpoint it's fine to talk about in terms of process. Grahame: 3 different ways you can use Github - 1) to manage source and content, 2) to publish content for discussion, and 3) for having the discussion. In FHIR we have quite a lot of content on Github but anything relating to ballot content has to be on HL7-managed Github. HQ has a process for keeping up with stuff in HL7 Github and making a synced copy in case of Github failure. Brian: The discussion at EST has been primarily related to non-FHIR material but there was brief discussion about FHIR material that needs to move to the HL7 Github.

Second issue is that the CDS Hooks guys (including Josh) would like to manage the ballot discussion on Github. Josh explains the benefits of doing so. It would be okay for STU ballots but Normative would require a GOM change. TSC would have to approve for STU. Will be asking TSC to approve for future ballots. Also need to discuss the potential of Jira.

ACTION: Anne to add to next week - discussion on publishing ballot content on Github

ACTION: Josh and Grahame to determine requirements for proposal to manage balloting on Github. Need to be sure everyone can participate, that there are continuity arrangements, that we know what the process will look like.