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

Require US Core Server to support the Simple Observation profile for simple assessments

    XMLWordPrintableJSON

Details

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

      Decision

      1. Clarify in the US Core Observation Simple Observation Profile section that clinical Judgements may be recorded as conditions instead of observations, and thus the Condition profile is used instead.  

      Systems record clinical judgments such as "Patient X has housing insecurity" using FHIR Conditions, FHIR Observations, or both. Systems that record clinical judgments as Observations SHALL use the US Core Simple Observation Profile to represent them. These observations can contribute to the identification of future problems or health concerns and support service requests and procedures. In addition, Simple Observations and Problem or Health Concern Conditions SHOULD reference associated US Core Observation Screening and Assessments Observations when they are based on them.

      # Update the Profile conformance expectations in the capability statement to be logically consistent.

      Background

      Because systems MAY record clinical Judgements as Conditions instead of Observations, they MAY not need to support the Simple Observation profile for Assessments and Screenings.  The US Core CapabilityStatement states:

      The US Core Server SHALL:

      1. Support the US Core Patient resource profile.
      2. Support at least one additional resource profile from the list of US Core Profiles.

      We agree the cascading conformance expectations need to be clarified.

      US Core is silent on whether Screening and Assessment SHALL result in a Simple Observation, Screening and Assessment Observation(s), or both.  That is the result of clinical workflow. However, the use case for recording a clinician or even a patient’s assertion is documented here: http://hl7.org/fhir/us/core/2023Jan/screening-and-assessments.html#us-core-observation-simple-observation-profile

      and on the profile page.

       

       

      Show
      Decision Clarify in the US Core Observation Simple Observation Profile section that clinical Judgements may be recorded as conditions instead of observations, and thus the Condition profile is used instead.   Systems record clinical judgments such as "Patient X has housing insecurity" using FHIR Conditions, FHIR Observations, or both. Systems that record clinical judgments as Observations  SHALL  use the  US Core Simple Observation Profile  to represent them. These observations can contribute to the identification of future problems or health concerns and support service requests and procedures. In addition, Simple Observations and Problem or Health Concern Conditions  SHOULD  reference associated  US Core Observation Screening and Assessments Observations  when they are based on them. # Update the Profile conformance expectations in the capability statement to be logically consistent. Background Because systems MAY record clinical Judgements as Conditions instead of Observations, they MAY not need to support the Simple Observation profile for Assessments and Screenings.  The US Core CapabilityStatement states: The US Core Server  SHALL : Support the US Core Patient resource profile. Support at least one additional resource profile from the list of US Core Profiles. We agree the cascading conformance expectations need to be clarified. US Core is silent on whether Screening and Assessment SHALL result in a Simple Observation, Screening and Assessment Observation(s), or both.  That is the result of clinical workflow. However, the use case for recording a clinician or even a patient’s assertion is documented here: http://hl7.org/fhir/us/core/2023Jan/screening-and-assessments.html#us-core-observation-simple-observation-profile and on the profile page.    
    • Eric Haas / Brett Marquard : 18-0-0
    • Clarification
    • Non-substantive

    Description

      Section 3.6.2.2 states “US Core Servers MAY support this [Simple Observation] profile.” The US Core Server CapabilityStatement says that servers SHALL support this profile. Regardless of whether this profile is misnamed or the scope not fully described (See FHIR-39940), this profile should be required for US Core Server for the assessments use case. The Observation Screening Assessment is required for recording screening assessments on US Core Servers. These simple assessments are no less important. Making this a MAY means that the only assessments that have to be captured are those that use some sort of screening or assessment tool and that a clinician or even a patient’s assertion (e.g. about being homeless) would not be required to be captured and therefore critical data would be missing. I do not believe this would meet the intent of USCDI.

      Attachments

        Activity

          People

            ehaas Eric Haas
            corey_spears Corey Spears
            Corey Spears
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: