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

Consider managing resource “domain” category slices with a common pattern

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • US Core Condition Problems and Health Concerns Profile
      US Core Observation Screening Assessment Profile
      US Core ServiceRequest Profile
      US Core Simple Observation Profile
    • Hide

      Update category slicing on Condition as proposed

      Show
      Update category slicing on Condition as proposed
    • Eric Haas / Brett Marquard : 18-0-0
    • Enhancement
    • Compatible, substantive

    Description

      The US Core Observation Screening Assessment and Simple Observation and ServiceRequest profiles have an Observation.category slice names us-core that includes domain category options (including sdoh, functional status, etc.). The US Core Condition Problems and Health Concerns Profile defines a specific slice for the singular sdoh domain. It does not have the similar “domain” category. It seems a Condition should just as easily have similar domain categories (functional status, cognitive status. Etc.).

      These are different patterns without an obviously clear reason as to why this is. Please consider instrumenting a similar pattern.

      (One note is that the current slicing of Condition requires that systems must support a sdoh repetition. Changing to a domain level slice with a VS binding, would not require systems support a sdoh repetition unless otherwise specified. This should be taken into consideration.)

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: