XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • Cross Paradigm Gender Harmony - Sex and Gender Representation (OTHER)
    • 1.0.0-ballot
    • Terminology Infrastructure
    • Home
    • 1.4.1
    • Hide

      Improved the readability with the following md structure:

       
      This guide builds upon the prior GH logical model by providing HL7 product family specific additions that define how to send the information noted above in:

              1. FHIR
                The FHIR core additions needed to support the GH model *are not* defined in this guide, instead they are found in the R5 FHIR Core ballot.

      This gender harmony guide contains:
      1. Informative description of the FHIR additions
      2. A discussion of design decisions that led to the chosen approach
      3. A discussion of how to "pre-adopt" the R5 extensions into implementations prior versions of FHIR
      4. Detailed FHIR examples based upon a common set of uses cases

              1. V2
                The new V2 segments needed to support the GH model are not defined in this guide, instead they are found in the V2.9.1 ballot.

      This gender harmony guide contains:
      1. Informative description of the V2 segment additions
      2. A discussion of design decisions that led to the chosen approach
      3. A discussion of how to "pre-adopt" the new v2.9.1 segments into implementations using prior version of V2
      4. Detailed V2 examples based upon a common set of uses cases

              1. CDA
                The new CDA entry templates needed to support the GH model *are not* defined within this guide.

      This gender harmony guide contains:
      1. The STU definition of entry templates to be used for the in-scope items noted above.
      2. A discussion of design decisions that led to the chosen approach
      3. A discussion of how to include the new entry templates into current CDA-based implementations, including C-CDA
      4. Detailed CDA examples based upon a common set of uses cases

              1. Terminology artifacts
                No terminology artifacts are defined in this guide.

      1. Value sets and code systems needed for these artifacts *are not* defined in this guide, instead they are defined in the FHIR R5 ballot and are used consistently across all product families.
      1. Given the constraint in CDA to not include null-flavor codes within the "clinical content" value sets, the CDA entry templates bind to value sets that do not contain null-value concepts. Those "core" value sets are then used to create the complete value set used in FHIR

      Show
      Improved the readability with the following md structure:   This guide builds upon the prior GH logical model by providing HL7 product family specific additions that define how to send the information noted above in: FHIR The FHIR core additions needed to support the GH model * are not * defined in this guide, instead they are found in the R5 FHIR Core ballot. This gender harmony guide contains: 1. Informative description of the FHIR additions 2. A discussion of design decisions that led to the chosen approach 3. A discussion of how to "pre-adopt" the R5 extensions into implementations prior versions of FHIR 4. Detailed FHIR examples based upon a common set of uses cases V2 The new V2 segments needed to support the GH model are not defined in this guide , instead they are found in the V2.9.1 ballot. This gender harmony guide contains: 1. Informative description of the V2 segment additions 2. A discussion of design decisions that led to the chosen approach 3. A discussion of how to "pre-adopt" the new v2.9.1 segments into implementations using prior version of V2 4. Detailed V2 examples based upon a common set of uses cases CDA The new CDA entry templates needed to support the GH model * are not * defined within this guide. This gender harmony guide contains: 1. The STU definition of entry templates to be used for the in-scope items noted above. 2. A discussion of design decisions that led to the chosen approach 3. A discussion of how to include the new entry templates into current CDA-based implementations, including C-CDA 4. Detailed CDA examples based upon a common set of uses cases Terminology artifacts No terminology artifacts are defined in this guide. 1. Value sets and code systems needed for these artifacts * are not * defined in this guide, instead they are defined in the FHIR R5 ballot and are used consistently across all product families. 1. Given the constraint in CDA to not include null-flavor codes within the "clinical content" value sets, the CDA entry templates bind to value sets that do not contain null-value concepts. Those "core" value sets are then used to create the complete value set used in FHIR
    • Davera G / Carmela C : 12-0-0
    • Clarification
    • Compatible, substantive
    • Yes
    • current

      The numbering at the level (see existing wording samples) below the standards names in this section seems odd. Suggest removing and making paragraph text.

      Existing Wording:

      1. The FHIR core additions/new V2 segments/CDA entry templates...
      2. This guide contains…
      1. Informative…

      Proposed Wording:

      The FHIR core additions…
      This guide contains…
      1. Informative….

      (Comment 4 - imported by: Lloyd McKenzie)

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: