Skip to end of metadata
Go to start of metadata



  • 2020-06-03 Changes
    • removed QC step from workflow
    • removed transitions from TSC approval to Draft and WG approval

Process

  • Recommend moving away from Confluence form and move to JIRA Issue for submitting PSS
    • Will allow us to populate JIRA based on content to support Consensus Review
    • Will store data in an external DB to JIRA
    • DECISION:  AGREEMENT
  • CREATE PSS
    • PSS created by submitter - Status = Draft
      • Button available = Submit
        • Transition to "WG Approval" Status
      • Sub-tasks will be created for
        • Sponsoring WG
        • Identified Co-Sponsoring WG (others can opt-in during Consensus Review)
        • Management Group - based on products selected in PSS
          • NEED TO REVIEW WHAT THE PRODUCT LIST WILL LOOK LIKE AS PART OF PSS REVIEW 
            • V2 Messages (Administrative) - V2 MG
            • V2 Messages (Clinical) - V2 MG
            • V2 Messages (Departmental) - V2 MG
            • V2 Messages (Infrastructure) - V2 MG
            • FHIR Extensions - FMG
            • FHIR Profiles - FMG
            • FHIR Implementation Guide - FMG
            • FHIR resources - FMG
            • V3 Documents (Administrative e.g SPL) - CDA MG
            • V3 Documents (Clinical) - CDA MG
            • V3 Documents (Knowledge) - CDA MG
        • ARB - if external content > 50% identified
        • Steering Division - based on Sponsoring WG
        • USRSC - if project indicates US Realm
  • WORK GROUP APPROVAL
    • Work Group will review and approve and update sub-task
      • Option = Approve/Reject
      • Status on Sub-task = Approved or Rejected
      • If Approved on sub-task - Status on parent issue transitions to "QC Review CONSENSUS REVIEW"
      • If Rejected on sub-task - Status remains at "Work Group Approval)
      • DECISION: WILL ADD IN SOME VALIDATION FOR PSS CONTENT BEFORE CAN MOVE TO CONSENSUS REVIEW
  • QC REVIEW - 
    • Automatically transitions to Status = QC Review when sub-task for sponsoring WG = Approved
    • Button available - Send to Review and ??
  • CONSENSUS REVIEW
    • Status = Consensus Review on parent issue 
    • SUB-TASK REVIEW
      • Options for groups - Agree, Disagree, Opt-out
        • Status = Agree, Disagree, Opted-out
    • Transitions to Triage, when 1 month has elapsed AND all sub-tasks have status of:
      • "agree"
      • "opted-out" 
      • "approved" (for sponsoring WG only)
    • Emails will be sent to co-chairs, International Council, groups identified in sub-tasks and will be posted on Zulip
  • TRIAGE
    • purpose is to confirm that all comments have been reconciled
    • Status = TRIAGE
    • Button available - Consensus Review and Send to TSC
  • TSC REVIEW
    • Status = TSC Review
    • Buttons = Accept or Reject
    • Final status = Accepted and Rejected

Questions/Decisions

  • Creation of Sub-tasks
    • Options for Products - should we create sub-tasks and assign for each of these? 

      • DECISION - we will review this list and mappings when we review the PSS form
      • Arden Syntax
      • Clinical Information Modeling Initiative
      • Clinical Context Object Workgroup (CCOW)
      • Domain Analysis Model (DAM)
      • Electronic Health Record (EHR) Functional Profile
      • Guidance (e.g. Companion Guide, Cookbook,etc)
      • Logical Model
      • New/modified/HL7 Policy/Procedure/Process
      • New Product Definition
      • New Product Family
      • Non Product Project (Education Marketing, Elect Services, etc)
      • White Paper
      • Creating/Use a tool not listed in HL7 Tooling Inventory
      • V3 Domain Information Model (DIM/DMIM)
      • V3 Foundation - RIM
      • V3 Foundation - Vocab Domains & Value Sets
      • V3 Messages - Administrative
      • V3 Messages - Clinical
      • V3 Messages - Departmental
      • V3 Messages - Infrastructure
      • V3 Rules - GELLO
      • V3 Services - Java Services (ITS Work Group)
      • V3 Services - Web Services (SOA)
  • Do we add all Management Groups, or just those appropriate for products selected?
    • Ask Project Management Council
  • Should there be an option at QC Review to transition back to WG Approval - if there are issues with the PSS?
    • or should it go back to Draft?
    • DECISION:  WILL REMOVE QC STEP AND ADD IN VALIDATION ON JIRA ISSUE TO REQUIRE MANDATORY FIELDS BEFORE IT CAN MOVE TO CONSENSUS REVIEW
      • PROJECT SCOPE, PROJECT NEED, REPOSITORY, SPONSORING WG
      • ADD FIELD TO INCLUDE LINK TO MINUTES WITH WG APPROVAL
    • ADD QC REVIEW AS PART OF CONSENSUS REVIEW PROCESS OTHERWISE
  • Process for Re-Review while in Consensus Review
    • if a group wants substantive changes to a PSS (for example, change to the overall scope, change to the artifacts) - they will add a comment and disagree
      • Sponsoring WG will be notified that a group has "disagreed" and will need to reconcile the feedback
        • Options
          • When change is made to PSS - flag it as substantive - will change any sub-task with a status of other than "Review" back to "Review" and notify those groups to go and re-review PSS
          • When change is made to PSS - rely on Sponsoring WG/project to go to each sub-task where status is not "review" and mark it as "Needs Review"
    • DECISION:  WILL GENERATE AN EMAIL WHEN A CHANGE IS MADE TO EVERYONE, BUT WON'T AUTOMATE THE TRANSITION BACK TO REVIEW
      • CREATE A CHECKLIST FOR REVIEW 
      • WG CO-CHAIRS/PROJECT LEAD WILL FLAG GROUPS IN SUB-TASKS FOR RE-REVIEW AS NEEDED
  • Which Statuses can TSC transition PSS back to when in TSC Approval Stage?
    • Draft
    • WG Approval
    • Consensus Review
    • DECISION:  ONLY SUPPORT TRANSITION TO CONSENSUS REVIEW FROM TSC APPROVAL STAGE
  • Which options should there be in Triage stage?
    • DECISION: Send to TSC and Consensus Review


  • No labels