Versions Compared

Old Version 8

changes.mady.by.user Carmela A. Couderc

Saved on

compared with

New Version Current

changes.mady.by.user Carmela A. Couderc

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. COMPANION SLIDE DECK that aligns with outline.  August2021_CodeSystemIdentifierBoF.pptx   September BoF Poll Questions.pptx


  1. Purpose of Webinar/Background - Why are we presenting this material
    1. The Art of Vocabulary in Implementation Guides, Profiles or Resources
      1. CodeSystem   (cc: go find official definitions)
        1. Internal
        2. External
      2. ValueSet
      3. Concepts  (this will not be discussed)
      4. Concept Map (this will not be discussed)
      5. Not talking about binding strength (there will be a separate webinar)
    2. Acronyms - Define
      1. UTG, THO, UP, HSRC, HTA
        1. UTG is the project initiated to get us to a new process
    1. UTG 
      1. Remind people of UTG, why it was created, when it was announced, when it went live, etc.
        1. Problem it was designed to solve
          1. Fragmented sources of terminology content, difficult to discover
          2. Terminology review (harmonization) bound to ballot cycle (V3, CDA)
          3. Minimal FHIR terminology review outside of ballot comments
            1. Dependent on ballot commenters, some of whom do not review terminology artifacts
        2. Shifting responsibility to IG authors/team, sponsoring work groups
          1. Contact voters, etc.
          2. Unfortunately not streamlined at this point
          3. Provide a reference to the V3 harmonization process which was replaced by UTG
        3. Solution 
          1. PSS approved 2016
          2. ONC funded
          3. Create a consensus, continual process to manage terminology change
            1. UP JIRA project
            2. Point to the documentation (submitters, reviewers, approvers)
              1. Note the videos are out of date 
          4. Create THO to be the single source of truth for HL7 terminology  
            1. Imported V2, CoreMIF, some of FHIR terminology 
              1. FHIR Structural/ballot bound terminology is not in THO (provide an example)
                1. Required bindings to code datatype elements
        4. Benefits
          1. Most HL7 terminology in one place   (moon or mars landing) 
            1. IG authors, implementers have one place to go to find terminology 
            2. Connectathon for terminology, test it out, community consensus
              1. 7/19/2021: can't remember the point of this bullet, ask Frank and Mary Kay
            3. Saves time (reduce duplicative work/code systems), saves aggravation, enhance relationships with external code system owners, IP respect
            4. Unify terminology process across all product families
            5. Unify content (ObservationInterpretation)
            6. Exposing stale content that should be updated or replaced or retired
          2. Move terminology review earlier in the process, collaborative, get community feedback, crowd sourcing
            1. PresentOnAdmission
          3. Moving forward - prevent chaos - not attempting to fix existing situation
            1. However, in some cases, work groups and Accelerators are fixing what needs to be fixed
          4. Changing CodeSystem identifiers **
            1. Enable change management-
              1. change is inevitable -
              2. minimize impact
              3. Provide an example of name changes, url changes (UCUM?) 
              4. NamingSystem clearly documents CodeSystem identifiers, their life cycle, and important metadata
        5. What THO IS NOT!
          1. Not a terminology server 
            1. The THO Code Systems contents are in tx.fhir.org
              1. We have to ask GG to confirm what from THO is in tx.fhir.org. Ted Kleinmight know
            2. Optionally THO Code Systems in the CI build may be in tx.fhir.org
          2. Does not make CodeSystem version information available (internal and external) (check - need to be careful with an example) (can't look up a CPT code from 2 years ago)
        6. Example from MK - demonstrating where example codes are used 
          1. http://hl7.org/fhir/ValueSet/claim-careteamrole   - all codes drawn from ClaimCareTeamRoleCodes
            1. http://terminology.hl7.org/CodeSystem/claimcareteamrole
            2. Example codes, clearly noted. Used in multiple IGs.  
            3. Ended up in the CARIN-BB IG as the codes to use
              1. http://hl7.org/fhir/us/carin-bb/ValueSet/C4BBClaimInstitutionalCareTeamRole   
                1. bound with required binding strength to EOB role code
                2. http://hl7.org/fhir/us/carin-bb/STU1/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html
          2. Second example?
    2. CodeSystem Types
      1. External:
        1. Content is managed by some organization other than HL7
        2. Follows HTA process (see previous webinar/education session)
        3. Example: SNOMED CT, LOINC, CPT, HCPCS 
      2. Internal: 
        1. Content is managed by HL7 
        2. UTG, THO, Specification
        3. Two types of internal code systems
          1. Codes whose change management is bound to ballot cycle (aka structural codes, ballot bound codes)
            1. Status
          2. Codes whose change management is not bound to ballot cycle
            1. ObservationInterpretation
      3. Example
        1. Do we need to describe Example Code System
          1. Why create?
            1. FHIR core spec requirements (can't reference proprietary codes)
            2. No known code system covers the domain
            3. Provides guidance to implementers
          2. Expectations for use
            1. Example codes that will never and should never be used in a production system
            2. Example codes that may be used in a production system 
    3. Using CodeSystems
      1. You need to reference coded concepts in your IG/resource/profile
        1. Most likely need to reference a CodeSystem
        2. Look for a source for your concepts  (define concept & code, and the difference)
      2. Preference: Use a CodeSystem where the CodeSystem identifier is in THO 
        1. Exception: Codes whose change management is bound to ballot cycle (aka structural codes, ballot bound codes)
        2. Use the identifier as defined in THO
          1. Check published version and CI build
      3.  If you can't use a CodeSystem where the identifier is in THO, (walk through the flow chart)
        1. External:
          1. HTA process
            1. Acknowledge we're in a transition phase 
            2. Timing is critical, start the process as soon as you are sure you will use concepts from an external code system 
              1. Pull in suggested process places for the HTA process
            3. Must engage HTA to obtain a url/identifier for an external code system - do not make one up 
              1. JIRA, and email? 
              2. HTA process overview
                1. Contact the owner
                2. If no response after X days/weeks, assign an identifier/url
                3. Supply metadata, create an HTA page, establish the CodeSystem identifier and metadata in THO
            4. temporary url assignment  
        2. Internal
          1. terminology.hl7.org - engage with the UTG Process
            1. Before ballot: Identifier/NamingSystem in THO (UTG process - pending Code System notification)
              1. Pro-forma code system request
            2. Before publish: Content in THO, UTG request 
        3. Example
          1. last resort
      4. When in doubt - 
        1. What do you do? Who do you call? UTG ticket; contact Vocab Co-chairs  Zulip Terminology Track
    4. Benefits 
      1. All HL7 terminology in place   (moon or mars landing) 
        1. IG authors, implementers have one place to go to find terminology 
        2. Connectathon for terminology, test it out, community consensus
        3. Saves time (reduce duplicative work/code systems), saves aggravation, enhance relationships with external code system owners, IP respect
      2.  Move terminology review earlier in the process, collaborative, get community feedback, crowd sourcing
      3. Notify community
      4. Encourage people to sign up for JIRA notifications (not sure this is a smooth process now -  would have to sign up for notifications) 
      5. Moving forward - prevent chaos - not attempting to fix existing mess
        1. Fixing only what absolutely needs to be fixed
      6. Changing CodeSystem identifiers **
        1. Enable change management-
          1. change is inevitable -
          2. minimize impact
          3. Provide an example of name changes, url changes (UCUM?) 
          4. NamingSystem clearly documents CodeSystem identifiers, their life cycle, and important metadata
    5. Identifier Systems
      1. Removed from the FHIR spec in R5 
        1. https://www.hl7.org/fhir/identifier-registry.html
      2. Brought into the UTG process
      3. In THO
      4. Examples: Social Security Number, Driver's License Numbers, 
      5. HTA is not going to manage the process for assigning identifiers for identifier systems
        1. This may become part of the TSMG responsibilities?
      6. Will be removed from the FHIR specification
      7. Straighten out the IdentifierSystems, define them, 
      8. https://www.hl7.org/fhir/v2/0203/index.html#SB   
        1. is being used as the system value for an identifier (are these identifier systems?)
    6. Value Sets
      1. terminology.hl7.org 
    7. Plug for the UTG education materials, join the meetings
      1. Other misc. documentation
      2. How to make sure people move forward with the right stuff, rather than copying incorrect stuff from prior publications? (e.g. NUBC PresentOnAdmission)  
      3. Reporting issues:  UTG, waiting for input status.  (we would need to create a dashboard.....)
    8. Review FHIR Code System page Policy for terminology in FHIR IGs  
      1. This info has a slightly different topic than the CodeSystem identifier focus for this team - 
  2. Polls during the webinar
    1. Before and after 
      1. What is THO, 
      2. Where do you request a CodeSystem identifer for an external code system 
      3. When did the UTG project start? 
      4. Who worked on the UTG project
  3. Incorporate this material into the FHIR certification


  1. COMPANION SLIDE DECK that aligns with outline.  August2021_CodeSystemIdentifierBoF.pptx


  1. Purpose of Webinar/Background - Why are we presenting this material
    1. The Art of Vocabulary in Implementation Guides, Profiles or Resources
      1. CodeSystem   (cc: go find official definitions)
        1. Internal
        2. External
      2. ValueSet
      3. Concepts  (this will not be discussed)
      4. Concept Map (this will not be discussed)
      5. Not talking about binding strength (there will be a separate webinar)
    2. Acronyms - Define
      1. UTG, THO, UP, HSRC, HTA
        1. UTG is the project initiated to get us to a new process
    1. UTG 
      1. Remind people of UTG, why it was created, when it was announced, when it went live, etc.
        1. Problem it was designed to solve
          1. Fragmented sources of terminology content, difficult to discover
          2. Terminology review (harmonization) bound to ballot cycle (V3, CDA)
          3. Minimal FHIR terminology review outside of ballot comments
            1. Dependent on ballot commenters, some of whom do not review terminology artifacts
        2. Shifting responsibility to IG authors/team, sponsoring work groups
          1. Contact voters, etc.
          2. Unfortunately not streamlined at this point
          3. Provide a reference to the V3 harmonization process which was replaced by UTG
        3. Solution 
          1. PSS approved 2016
          2. ONC funded
          3. Create a consensus, continual process to manage terminology change
            1. UP JIRA project
            2. Point to the documentation (submitters, reviewers, approvers)
              1. Note the videos are out of date 
          4. Create THO to be the single source of truth for HL7 terminology  
            1. Imported V2, CoreMIF, some of FHIR terminology 
              1. FHIR Structural/ballot bound terminology is not in THO (provide an example)
                1. Required bindings to code datatype elements
        4. Benefits
          1. Most HL7 terminology in one place   (moon or mars landing) 
            1. IG authors, implementers have one place to go to find terminology 
            2. Connectathon for terminology, test it out, community consensus
              1. 7/19/2021: can't remember the point of this bullet, ask Frank and Mary Kay
            3. Saves time (reduce duplicative work/code systems), saves aggravation, enhance relationships with external code system owners, IP respect
            4. Unify terminology process across all product families
            5. Unify content (ObservationInterpretation)
            6. Exposing stale content that should be updated or replaced or retired
          2. Move terminology review earlier in the process, collaborative, get community feedback, crowd sourcing
            1. PresentOnAdmission
          3. Moving forward - prevent chaos - not attempting to fix existing situation
            1. However, in some cases, work groups and Accelerators are fixing what needs to be fixed
          4. Changing CodeSystem identifiers **
            1. Enable change management-
              1. change is inevitable -
              2. minimize impact
              3. Provide an example of name changes, url changes (UCUM?) 
              4. NamingSystem clearly documents CodeSystem identifiers, their life cycle, and important metadata
        5. What THO IS NOT!
          1. Not a terminology server 
            1. The THO Code Systems contents are in tx.fhir.org
              1. We have to ask GG to confirm what from THO is in tx.fhir.org. Ted Kleinmight know
            2. Optionally THO Code Systems in the CI build may be in tx.fhir.org
          2. Does not make CodeSystem version information available (internal and external) (check - need to be careful with an example) (can't look up a CPT code from 2 years ago)
        6. Example from MK - demonstrating where example codes are used 
          1. http://hl7.org/fhir/ValueSet/claim-careteamrole   - all codes drawn from ClaimCareTeamRoleCodes
            1. http://terminology.hl7.org/CodeSystem/claimcareteamrole
            2. Example codes, clearly noted. Used in multiple IGs.  
            3. Ended up in the CARIN-BB IG as the codes to use
              1. http://hl7.org/fhir/us/carin-bb/ValueSet/C4BBClaimInstitutionalCareTeamRole   
                1. bound with required binding strength to EOB role code
                2. http://hl7.org/fhir/us/carin-bb/STU1/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html
          2. Second example?
    2. CodeSystem Types
      1. External:
        1. Content is managed by some organization other than HL7
        2. Follows HTA process (see previous webinar/education session)
        3. Example: SNOMED CT, LOINC, CPT, HCPCS 
      2. Internal: 
        1. Content is managed by HL7 
        2. UTG, THO, Specification
        3. Two types of internal code systems
          1. Codes whose change management is bound to ballot cycle (aka structural codes, ballot bound codes)
            1. Status
          2. Codes whose change management is not bound to ballot cycle
            1. ObservationInterpretation
      3. Example
        1. Do we need to describe Example Code System
          1. Why create?
            1. FHIR core spec requirements (can't reference proprietary codes)
            2. No known code system covers the domain
            3. Provides guidance to implementers
          2. Expectations for use
            1. Example codes that will never and should never be used in a production system
            2. Example codes that may be used in a production system 
    3. Using CodeSystems
      1. You need to reference coded concepts in your IG/resource/profile
        1. Most likely need to reference a CodeSystem
        2. Look for a source for your concepts  (define concept & code, and the difference)
      2. Preference: Use a CodeSystem where the CodeSystem identifier is in THO 
        1. Exception: Codes whose change management is bound to ballot cycle (aka structural codes, ballot bound codes)
        2. Use the identifier as defined in THO
          1. Check published version and CI build
      3.  If you can't use a CodeSystem where the identifier is in THO, (walk through the flow chart)
        1. External:
          1. HTA process
            1. Acknowledge we're in a transition phase 
            2. Timing is critical, start the process as soon as you are sure you will use concepts from an external code system 
              1. Pull in suggested process places for the HTA process
            3. Must engage HTA to obtain a url/identifier for an external code system - do not make one up 
              1. JIRA, and email? 
              2. HTA process overview
                1. Contact the owner
                2. If no response after X days/weeks, assign an identifier/url
                3. Supply metadata, create an HTA page, establish the CodeSystem identifier and metadata in THO
            4. temporary url assignment  
        2. Internal
          1. terminology.hl7.org - engage with the UTG Process
            1. Before ballot: Identifier/NamingSystem in THO (UTG process - pending Code System notification)
              1. Pro-forma code system request
            2. Before publish: Content in THO, UTG request 
        3. Example
          1. last resort
      4. When in doubt - 
        1. What do you do? Who do you call? UTG ticket; contact Vocab Co-chairs  Zulip Terminology Track
    4. Benefits 
      1. All HL7 terminology in place   (moon or mars landing) 
        1. IG authors, implementers have one place to go to find terminology 
        2. Connectathon for terminology, test it out, community consensus
        3. Saves time (reduce duplicative work/code systems), saves aggravation, enhance relationships with external code system owners, IP respect
      2.  Move terminology review earlier in the process, collaborative, get community feedback, crowd sourcing
      3. Notify community
      4. Encourage people to sign up for JIRA notifications (not sure this is a smooth process now -  would have to sign up for notifications) 
      5. Moving forward - prevent chaos - not attempting to fix existing mess
        1. Fixing only what absolutely needs to be fixed
      6. Changing CodeSystem identifiers **
        1. Enable change management-
          1. change is inevitable -
          2. minimize impact
          3. Provide an example of name changes, url changes (UCUM?) 
          4. NamingSystem clearly documents CodeSystem identifiers, their life cycle, and important metadata
    5. Identifier Systems
      1. Removed from the FHIR spec in R5 
        1. https://www.hl7.org/fhir/identifier-registry.html
      2. Brought into the UTG process
      3. In THO
      4. Examples: Social Security Number, Driver's License Numbers, 
      5. HTA is not going to manage the process for assigning identifiers for identifier systems
        1. This may become part of the TSMG responsibilities?
      6. Will be removed from the FHIR specification
      7. Straighten out the IdentifierSystems, define them, 
      8. https://www.hl7.org/fhir/v2/0203/index.html#SB   
        1. is being used as the system value for an identifier (are these identifier systems?)
    6. Value Sets
      1. terminology.hl7.org 
    7. Plug for the UTG education materials, join the meetings
      1. Other misc. documentation
      2. How to make sure people move forward with the right stuff, rather than copying incorrect stuff from prior publications? (e.g. NUBC PresentOnAdmission)  
      3. Reporting issues:  UTG, waiting for input status.  (we would need to create a dashboard.....)
    8. Review FHIR Code System page Policy for terminology in FHIR IGs  
      1. This info has a slightly different topic than the CodeSystem identifier focus for this team - 
  2. Polls during the webinar
    1. Before and after 
      1. What is THO, 
      2. Where do you request a CodeSystem identifer for an external code system 
      3. When did the UTG project start? 
      4. Who worked on the UTG project
  3. Incorporate this material into the FHIR certification


  1. COMPANION SLIDE DECK that aligns with outline.  August2021_CodeSystemIdentifierBoF.pptx


  1. Purpose of Webinar/Background - Why are we presenting this material
    1. The Art of Vocabulary in Implementation Guides, Profiles or Resources
      1. CodeSystem   (cc: go find official definitions)
        1. Internal
        2. External
      2. ValueSet
      3. Concepts  (this will not be discussed)
      4. Concept Map (this will not be discussed)
      5. Not talking about binding strength (there will be a separate webinar)
    2. Acronyms - Define
      1. UTG, THO, UP, HSRC, HTA
        1. UTG is the project initiated to get us to a new process
    1. UTG 
      1. Remind people of UTG, why it was created, when it was announced, when it went live, etc.
        1. Problem it was designed to solve
          1. Fragmented sources of terminology content, difficult to discover
          2. Terminology review (harmonization) bound to ballot cycle (V3, CDA)
          3. Minimal FHIR terminology review outside of ballot comments
            1. Dependent on ballot commenters, some of whom do not review terminology artifacts
        2. Shifting responsibility to IG authors/team, sponsoring work groups
          1. Contact voters, etc.
          2. Unfortunately not streamlined at this point
          3. Provide a reference to the V3 harmonization process which was replaced by UTG
        3. Solution 
          1. PSS approved 2016
          2. ONC funded
          3. Create a consensus, continual process to manage terminology change
            1. UP JIRA project
            2. Point to the documentation (submitters, reviewers, approvers)
              1. Note the videos are out of date 
          4. Create THO to be the single source of truth for HL7 terminology  
            1. Imported V2, CoreMIF, some of FHIR terminology 
              1. FHIR Structural/ballot bound terminology is not in THO (provide an example)
                1. Required bindings to code datatype elements
        4. Benefits
          1. Most HL7 terminology in one place   (moon or mars landing) 
            1. IG authors, implementers have one place to go to find terminology 
            2. Connectathon for terminology, test it out, community consensus
              1. 7/19/2021: can't remember the point of this bullet, ask Frank and Mary Kay
            3. Saves time (reduce duplicative work/code systems), saves aggravation, enhance relationships with external code system owners, IP respect
            4. Unify terminology process across all product families
            5. Unify content (ObservationInterpretation)
            6. Exposing stale content that should be updated or replaced or retired
          2. Move terminology review earlier in the process, collaborative, get community feedback, crowd sourcing
            1. PresentOnAdmission
          3. Moving forward - prevent chaos - not attempting to fix existing situation
            1. However, in some cases, work groups and Accelerators are fixing what needs to be fixed
          4. Changing CodeSystem identifiers **
            1. Enable change management-
              1. change is inevitable -
              2. minimize impact
              3. Provide an example of name changes, url changes (UCUM?) 
              4. NamingSystem clearly documents CodeSystem identifiers, their life cycle, and important metadata
        5. What THO IS NOT!
          1. Not a terminology server 
            1. The THO Code Systems contents are in tx.fhir.org
              1. We have to ask GG to confirm what from THO is in tx.fhir.org. Ted Kleinmight know
            2. Optionally THO Code Systems in the CI build may be in tx.fhir.org
          2. Does not make CodeSystem version information available (internal and external) (check - need to be careful with an example) (can't look up a CPT code from 2 years ago)
        6. Example from MK - demonstrating where example codes are used 
          1. http://hl7.org/fhir/ValueSet/claim-careteamrole   - all codes drawn from ClaimCareTeamRoleCodes
            1. http://terminology.hl7.org/CodeSystem/claimcareteamrole
            2. Example codes, clearly noted. Used in multiple IGs.  
            3. Ended up in the CARIN-BB IG as the codes to use
              1. http://hl7.org/fhir/us/carin-bb/ValueSet/C4BBClaimInstitutionalCareTeamRole   
                1. bound with required binding strength to EOB role code
                2. http://hl7.org/fhir/us/carin-bb/STU1/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html
          2. Second example?
    2. CodeSystem Types
      1. External:
        1. Content is managed by some organization other than HL7
        2. Follows HTA process (see previous webinar/education session)
        3. Example: SNOMED CT, LOINC, CPT, HCPCS 
      2. Internal: 
        1. Content is managed by HL7 
        2. UTG, THO, Specification
        3. Two types of internal code systems
          1. Codes whose change management is bound to ballot cycle (aka structural codes, ballot bound codes)
            1. Status
          2. Codes whose change management is not bound to ballot cycle
            1. ObservationInterpretation
      3. Example
        1. Do we need to describe Example Code System
          1. Why create?
            1. FHIR core spec requirements (can't reference proprietary codes)
            2. No known code system covers the domain
            3. Provides guidance to implementers
          2. Expectations for use
            1. Example codes that will never and should never be used in a production system
            2. Example codes that may be used in a production system 
    3. Using CodeSystems
      1. You need to reference coded concepts in your IG/resource/profile
        1. Most likely need to reference a CodeSystem
        2. Look for a source for your concepts  (define concept & code, and the difference)
      2. Preference: Use a CodeSystem where the CodeSystem identifier is in THO 
        1. Exception: Codes whose change management is bound to ballot cycle (aka structural codes, ballot bound codes)
        2. Use the identifier as defined in THO
          1. Check published version and CI build
      3.  If you can't use a CodeSystem where the identifier is in THO, (walk through the flow chart)
        1. External:
          1. HTA process
            1. Acknowledge we're in a transition phase 
            2. Timing is critical, start the process as soon as you are sure you will use concepts from an external code system 
              1. Pull in suggested process places for the HTA process
            3. Must engage HTA to obtain a url/identifier for an external code system - do not make one up 
              1. JIRA, and email? 
              2. HTA process overview
                1. Contact the owner
                2. If no response after X days/weeks, assign an identifier/url
                3. Supply metadata, create an HTA page, establish the CodeSystem identifier and metadata in THO
            4. temporary url assignment  
        2. Internal
          1. terminology.hl7.org - engage with the UTG Process
            1. Before ballot: Identifier/NamingSystem in THO (UTG process - pending Code System notification)
              1. Pro-forma code system request
            2. Before publish: Content in THO, UTG request 
        3. Example
          1. last resort
      4. When in doubt - 
        1. What do you do? Who do you call? UTG ticket; contact Vocab Co-chairs  Zulip Terminology Track
    4. Benefits 
      1. All HL7 terminology in place   (moon or mars landing) 
        1. IG authors, implementers have one place to go to find terminology 
        2. Connectathon for terminology, test it out, community consensus
        3. Saves time (reduce duplicative work/code systems), saves aggravation, enhance relationships with external code system owners, IP respect
      2.  Move terminology review earlier in the process, collaborative, get community feedback, crowd sourcing
      3. Notify community
      4. Encourage people to sign up for JIRA notifications (not sure this is a smooth process now -  would have to sign up for notifications) 
      5. Moving forward - prevent chaos - not attempting to fix existing mess
        1. Fixing only what absolutely needs to be fixed
      6. Changing CodeSystem identifiers **
        1. Enable change management-
          1. change is inevitable -
          2. minimize impact
          3. Provide an example of name changes, url changes (UCUM?) 
          4. NamingSystem clearly documents CodeSystem identifiers, their life cycle, and important metadata
    5. Identifier Systems
      1. Removed from the FHIR spec in R5 
        1. https://www.hl7.org/fhir/identifier-registry.html
      2. Brought into the UTG process
      3. In THO
      4. Examples: Social Security Number, Driver's License Numbers, 
      5. HTA is not going to manage the process for assigning identifiers for identifier systems
        1. This may become part of the TSMG responsibilities?
      6. Will be removed from the FHIR specification
      7. Straighten out the IdentifierSystems, define them, 
      8. https://www.hl7.org/fhir/v2/0203/index.html#SB   
        1. is being used as the system value for an identifier (are these identifier systems?)
    6. Value Sets
      1. terminology.hl7.org 
    7. Plug for the UTG education materials, join the meetings
      1. Other misc. documentation
      2. How to make sure people move forward with the right stuff, rather than copying incorrect stuff from prior publications? (e.g. NUBC PresentOnAdmission)  
      3. Reporting issues:  UTG, waiting for input status.  (we would need to create a dashboard.....)
    8. Review FHIR Code System page Policy for terminology in FHIR IGs  
      1. This info has a slightly different topic than the CodeSystem identifier focus for this team - 
  2. Polls during the webinar
    1. Before and after 
      1. What is THO, 
      2. Where do you request a CodeSystem identifer for an external code system 
      3. When did the UTG project start? 
      4. Who worked on the UTG project
  3. Incorporate this material into the FHIR certification