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

US Core is spelled "US Core" and "USCore" throughout the implementation guide.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US QI Core (FHIR)
    • current
    • Clinical Quality Information
    • (many)
    • Hide

      USCore appears in the following areas and needs to be changed to US Core:

      QI-Core Profile page - section 2.1 

      • The following table lists the QI-Core profiles that are part of the IG, which USCore profile they are derived from, if any, and the underlying FHIR resources:
      • and in the table header as USCore Profile
      • Section 2.2 Referencing QI-Core Profiles text "There are a number of QI-Core profiles inherit directly from US Core profiles, if any, or other FHIR resources (i.e. US Core Implantable Device Profile, FHIR Vital Signs, US Core Smoking Status etc.) and the underlying Reference elements can address the US Core or FHIR profiles for the items referenced. For any other references to base FHIR resources or not formally defined in a QI-Core Profile, the referenced resource SHALL be a QI-Core Profile if a QI-Core Profile exists for the resource type. For example, USCore Smoking Status references US Core Patient profile, the reference to Patient SHALL be a valid QI-Core Patient."

      The following uses of USCore (no space) are appropriate -

      Section 3.1.2 Extension use is appropriate since it references the slice: define TestSlices: [USCoreBloodPressure] BP

      It also appears and is appropriate in QDM-to-QI-Core Mapping section 9.4 AllergyIntolerance.code map to USCoreAllergySubstance because it references a string

      {}It also appears and is appropriate in{{ QDM-to-QI-Core Mapping section 9.12.5 Encounter.code Uses extensible binding to value set: USCoreEncounterType }}because it references a link

      Show
      USCore appears in the following areas and needs to be changed to US Core: QI-Core Profile page - section 2.1  The following table lists the QI-Core profiles that are part of the IG, which USCore profile they are derived from, if any, and the underlying FHIR resources: and in the table header as USCore Profile Section 2.2 Referencing QI-Core Profiles text "There are a number of QI-Core profiles inherit directly from US Core profiles, if any, or other FHIR resources (i.e. US Core Implantable Device Profile, FHIR Vital Signs, US Core Smoking Status etc.) and the underlying Reference elements can address the US Core or FHIR profiles for the items referenced. For any other references to base FHIR resources or not formally defined in a QI-Core Profile, the referenced resource SHALL be a QI-Core Profile if a QI-Core Profile exists for the resource type. For example, USCore Smoking Status references US Core Patient profile, the reference to Patient SHALL be a valid QI-Core Patient." The following uses of USCore (no space) are appropriate - Section 3.1.2 Extension use is appropriate since it references the slice: define TestSlices: [USCoreBloodPressure] BP It also appears and is appropriate in QDM-to-QI-Core Mapping section 9.4 AllergyIntolerance.code map to USCoreAllergySubstance because it references a string { } It also appears and is appropriate in {{ QDM-to-QI-Core Mapping section 9.12.5 Encounter.code Uses extensible binding to value set: USCoreEncounterType  }} because it references a link
    • Floyd Eisenberg/Michelle Dardis: 24-0-1
    • Correction
    • Non-substantive

    Description

      US Core is spelled "US Core" and "USCore" throughout the implementation guide. Submitting ticket so there may be a review of when these variations are appropriate versus when they should be changed.

      Attachments

        Activity

          People

            jen_seeman Jennifer Seeman
            ericamartin Erica Martin
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: