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

Align with USCDI v3 Pregnancy Status

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Public Health Profiles Library (FHIR)
    • 1.0.0-ballot
    • Public Health
    • STU
    • US Public Health Pregnancy Status [deprecated]
    • Artifacts Summary
    • Hide

      Several data concepts profiled in the USPHPL (e.g. Disability Status) have been submitted to USCDI and USCDI has approved them at various different levels (e.g.: Disability Status: https://www.healthit.gov/isa/taxonomy/term/3276/level-2). We will update the description of all profiles that represent a data element contained in USCDI with a link to that data element and add language that explains that these are data elements that are currently in USCDI but have not yet been promoted to a USCDI level high enough to be included in US Core.

      We will update the IG to explain that USPHPL will defer as much as possible to US Core and only add constraints / profiles when necessary for public health use.

      If a US Core profile is added that is the same as a USPHPL profile (e.g. due to USCDI promotion) then, as long as there are no additional constraints needed, the USPHPL profile would be retired in favor of the US Core profile.

      If constraints are added to a US Core profile that duplicate constraint(s) in a current USPHPL profile that is based on that US Core profile (e.g. US Public Health Patient profile which is based on the US Core Patient profile) then:

      • either (all US PH constraints duplicated in the US Core profile) the USPHPL profile would be retired in favor of the US Core profile
      • or (some US PH constraints duplicated in the US Core profile) the USPHPL profile would be updated to remove any duplicate constraints.

      Variance processes will work through the PH WG and we will add text to this effect in the IG.

      Show
      Several data concepts profiled in the USPHPL (e.g. Disability Status) have been submitted to USCDI and USCDI has approved them at various different levels (e.g.: Disability Status: https://www.healthit.gov/isa/taxonomy/term/3276/level-2 ). We will update the description of all profiles that represent a data element contained in USCDI with a link to that data element and add language that explains that these are data elements that are currently in USCDI but have not yet been promoted to a USCDI level high enough to be included in US Core. We will update the IG to explain that USPHPL will defer as much as possible to US Core and only add constraints / profiles when necessary for public health use. If a US Core profile is added that is the same as a USPHPL profile (e.g. due to USCDI promotion) then, as long as there are no additional constraints needed, the USPHPL profile would be retired in favor of the US Core profile. If constraints are added to a US Core profile that duplicate constraint(s) in a current USPHPL profile that is based on that US Core profile (e.g. US Public Health Patient profile which is based on the US Core Patient profile) then: either (all US PH constraints duplicated in the US Core profile) the USPHPL profile would be retired in favor of the US Core profile or (some US PH constraints duplicated in the US Core profile) the USPHPL profile would be updated to remove any duplicate constraints. Variance processes will work through the PH WG and we will add text to this effect in the IG.
    • Sarah Gaunt / Erin Holt : 24-0-1
    • Clarification
    • Non-substantive

    Description

      To ensure compatibility with US Core, data element/profile must point to the USCDI v3 "Pregnancy Status" element, and may conflict with future iterations of US Core. Justification should be provided for why a non-USCDI element is necessary.

      Attachments

        Activity

          People

            minigrrl Sarah Gaunt
            kathleen.tully@hhs.gov Kathleen Tully
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: