Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-40195

Need to create actual CLDs for value sets

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • Human Services Directory (FHIR)
    • 1.0.0-ballot
    • Human and Social Services
    • STU
    • Human Service Category VS
      Human Service Type VS
    • Hide

       __ 211 LA has not yet reached agreement with HL7, so the 211 LA taxonomy will be removed from this version (STU 1) of the IG and will not be referenced in either the code systems and value sets. Instead, the IG will create a new value set including a subset of codes from the Plannet HealthcareServiceCategoryCS (http://hl7.org/fhir/us/davinci-pdex-plan-net/CodeSystem/HealthcareServiceCategoryCS)  for use with HealthcareService.category  and from the code system  ServiceType (http://terminology.hl7.org/CodeSystem/service-type) in THO for use with HealthcareService.type. Each value set will apply example bindings to these value sets. CLDs will appropriately be created to reflect the subset of example codes for each value set.

       

      Value Set CLDs in the HSD HealthcareService profile (category and type) will be updated to only include the open-source (Creative Commons License) Open Eligibility taxonomy for human and social services instead of including value sets derived from the 211 LA due because the MOU between HL7 & LA 211 organization allowing HL7 to reference 211 LA in HL7 specifications cannot be reached.

      However, if the proposed resolution to FHIR-40366 - HealthcareService category and type bindings – should extend plan-net bindings (https://jira.hl7.org/browse/FHIR-40366) is voted down (negative), and the work group votes to Brian Handspicker's recommendation (documented in comments entered on 7/3 to FHIR-40366 (only include the Plan Net value sets with example bindings in a new HealthcareService profile that is not derived from Plan Net), the value set CLDs will include ONLY PlanNet codes currently depicted in the PlanNet Provider Directory IG (minus the 'Other' code in the HealthcareService.category value set) along with example bindings). 

       

      Show
       __ 211 LA has not yet reached agreement with HL7, so the 211 LA taxonomy will be removed from this version (STU 1) of the IG and will not be referenced in either the code systems and value sets. Instead, the IG will create a new value set including a subset of codes from the Plannet HealthcareServiceCategoryCS ( http://hl7.org/fhir/us/davinci-pdex-plan-net/CodeSystem/HealthcareServiceCategoryCS )  for use with HealthcareService.category  and from the code system  ServiceType ( http://terminology.hl7.org/CodeSystem/service-type ) in THO for use with HealthcareService.type. Each value set will apply  example  bindings to these value sets. CLDs will appropriately be created to reflect the subset of example codes for each value set.   Value Set CLDs in the HSD HealthcareService profile (category and type) will be updated to only include the open-source (Creative Commons License) Open Eligibility taxonomy for human and social services instead of including value sets derived from the 211 LA due because the MOU between HL7 & LA 211 organization allowing HL7 to reference 211 LA in HL7 specifications cannot be reached. However, if the proposed resolution to FHIR-40366 - HealthcareService category and type bindings – should extend plan-net bindings ( https://jira.hl7.org/browse/FHIR-40366 ) is voted down (negative), and the work group votes to Brian Handspicker's recommendation (documented in comments entered on 7/3 to FHIR-40366 (only include the Plan Net value sets with example bindings in a new HealthcareService profile that is not derived from Plan Net), the value set CLDs will include ONLY PlanNet codes currently depicted in the PlanNet Provider Directory IG (minus the 'Other' code in the HealthcareService.category value set) along with example bindings).    
    • Serafina Versaggi / Sean Muir : 26 - 0 - 0
    • Correction
    • Compatible, substantive

      Once actual proper 211LA code system resource is available, the CLD of these value sets needs to be created. 

      1. If the needed codes are available to the publisher, the CLD should use FHIR filters and access the code system for thee expansion
      2. If the codes are NOT available, the value set should use the rulesText extension to describe the script a user would follow to obtain the value set expansion needed, assuming the user will have obtained access the the code system.

            Unassigned Unassigned
            Rob_McClure Rob McClure
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: