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

Observation.subject explanation isn't logical

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US SDOH Clinical Care (FHIR)
    • 0.1.0 [deprecated]
    • Patient Care
    • SDOHCC Observation ScreeningResponseBase 1 [deprecated]
    • Hide

      will be changing observation.subject to US Core Patient profile (will use US Core Profiles for all references that are mustsupport and where the profiles exist) – remove current note on this element from the guidance.

      Show
      will be changing observation.subject to US Core Patient profile (will use US Core Profiles for all references that are mustsupport and where the profiles exist) – remove current note on this element from the guidance.
    • Bob Dieterle / Jay Lyle : 7-0-1
    • Correction
    • Compatible, substantive

    Description

      The first statement doesn't in any way drive the second statement. Yes, you're not based on a US Core profile. That doesn't mean you can't constrain to US Core Patient. What's the reason you don't want to constrain? If you don't have a good reason, you may as well constrain - because you know that once US Core does have a generic Observation profile, it's going to demand the use of US Core Patient.

      Existing Wording:

      US Core does not offer a generic Observation Profile. For this reason, SDOHCC_Observation_ScreeningResponseBase_1 does not restrict Observation.subject to US Core Patient Profile

      (Comment 120 - imported by: Robert Dieterle)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: