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

Provide further guidance on use of US Core vs other domain specific IGs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • STU
    • Screening and Assessments
    • Hide

      Will add guidance the section 3.6.2.1US Core Observation Screening an Assessments Profile:

      Implementers SHOULD consider more constrained, domain-specific profiles derived from this profile to meet the needs of their respective use cases.

      Show
      Will add guidance the section 3.6.2.1US Core Observation Screening an Assessments Profile: Implementers SHOULD consider more constrained, domain-specific profiles derived from this profile to meet the needs of their respective use cases.
    • Eric Haas / Brett Marquard : 18-0-0
    • Clarification
    • Non-substantive

    Description

      The specification states “Since screenings and assessments are not unique to social needs, US Core 6.0.0+ Profiles and the FHIR RESTful interactions documented below span across use cases and thus are less constrained and form the backbone for the Clinical Care Profiles. They provide a general framework for all domains which use screenings are assessments” and lists a few classes including SDOH, function status, etc. It is appropriate that US Core is providing the base line across use cases, however, this can cause confusion if there are profiles in US Core and profiles in other IGs that cover similar spaces. Implementers might not know when to use which one, and since US Core is so well known, implementers may just default to it. US Core should suggest when it is proper to use the US Core profiles versus using a specialized IG like Gravity. There should be a statement that the use of the more constrained domain specific profiles should be considered to meet the needs of their respective use cases.

      Attachments

        Activity

          People

            Unassigned Unassigned
            corey_spears Corey Spears
            Corey Spears
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: