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

Change the title and/or description of the Simple Observation Profile

    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
    • US Core Simple Observation Profile
    • Screening and Assessments
    • Hide

      This profile is meant to capture any sort of “simple” observations that are not otherwise covered by other US Core Observation profiles. Will update the profile description to scope to reflect its true scope.

      Will clarify the definition so as not to imply the intent is only for practitioner observation

      This US Core FHIR Profile is meant to capture any “simple” observations that are not otherwise covered by other US Core Observation profiles. It represents any type of observation that is not classified as vital signs, laboratory, imaging, or other more specific observation types. This profile promotes interoperability and adoption through common implementation by setting minimum expectations for the Observation resource to record, search, and retrieve observations such as a clinical observation or assertion about a patient’s health status or other general observations.   This profile identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific use cases.

       

      Will document its use in the context of US Core Data for Interoperability (USCDI) Assessments. to the Profile specific implementation guidance section.

      ADDED on Mar 23:

      1) will remove the ms on derivedFrom and on the reference to US Core Observation Screening Assessment Profile; and

      2) make element an USCDI requirement to support assessments and

      3) add user note in Profile specific implementation guidance how to reference the source for assessments

      4) Change the derivedFrom Reference from US Core Observation Screening Assessment Profile to Observation.

      Please note that we have used OpenAI's chatCPG to assist in answering this question. We review these responses, and the information provided is based on our experience, implementer feedback, and our design choices for US Core.

      Show
      This profile is meant to capture any sort of “simple” observations that are not otherwise covered by other US Core Observation profiles. Will update the profile description to scope to reflect its true scope. Will clarify the definition so as not to imply the intent is only for practitioner observation This US Core FHIR Profile is meant to capture any “simple” observations that are not otherwise covered by other US Core Observation profiles. It represents any type of observation that is not classified as vital signs, laboratory, imaging, or other more specific observation types. This profile promotes interoperability and adoption through common implementation by setting minimum expectations for the Observation resource to record, search, and retrieve observations such as a clinical observation or assertion about a patient’s health status or other general observations.   This profile identifies which core elements, extensions, vocabularies, and value sets SHALL  be present in the resource when using this profile. It provides the floor for standards development for specific use cases.   Will document its use in the context of US Core Data for Interoperability (USCDI) Assessments. to the Profile specific implementation guidance section. ADDED on Mar 23: 1) will remove the ms on derivedFrom and on the reference to US Core Observation Screening Assessment Profile; and 2) make element an  USCDI requirement to support assessments and 3) add user note in Profile specific implementation guidance how  to reference the source for assessments 4) Change the derivedFrom Reference from US Core Observation Screening Assessment Profile to Observation. Please note that we have used OpenAI's chatCPG to assist in answering this question. We review these responses, and the information provided is based on our experience, implementer feedback, and our design choices for US Core.
    • Eric Haas / Yunwei Wang : 18-0-0
    • Clarification
    • Compatible, substantive

    Description

      The title “Simple Observation” either does not adequately describe the purpose of the profile or the scope of the profile is not adequately described.

       

      The profile intro material states “The US Core Simple Observation Profile meets the requirements of the US Core Data for Interoperability (USCDI) Assessments. This profile promotes interoperability and adoption through common implementation by setting minimum expectations for the Observation resource to record, search, and retrieve observations representing a practitioner’s clinical observation or assertion about a patient’s health status. These observations may or may not be associated with a formal survey, screening, or assessment tool. For example, a social history status such as education or food insecurity or an assessment of the patient’s cognitive, functional, or disability status. This profile identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific use cases.”

       

      1. This seems to indicate that the use of the profile should be assessments.
        1. If this profile is only meant to be for assessments, please rename the profile something like “Simple Assessment Observation”. This will help reduce confusion on the use of the profile and implementers from capturing non-assessment observations with the wrong profile.
        2. If this profile is meant to capture any sort of “simple” observations that are not otherwise covered by other US Core Observation profiles, please describe the scope and use of the profile up front.
          Additionally, change the description on the Screening and Assessments page (http://hl7.org/fhir/us/core/2023Jan/screening-and-assessments.html) section 3.6.1 where the US Core Simple Observation Profile is first mentioned to state something to the effect that simple assessments are captured using the Simple Observation profile. Not stating this could lead to an incorrect that the “Simple Observation” profile is synonymous with the assessment use case, though its scope is actually greater than that.
      2. The profile description states that the profile is about observations representing a “practitioner’s clinical observation”, however, the profile does allow the performer to be a patient. Related person, organization, or care Team (which may include non-practitioners). It seems the intent is that the profile should be able to be used to capture more than a practitioner’s observation and furthermore not just a clinical observation. For domains like SDOH, this may also mean other types of status of a patient than just their health status. Please reword to make this intent clear, perhaps something like “an observation or assertion (such as a practitioner’s clinical observation) about a patient’s status.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: