US Core: Encounter.diagnosis shouldn't be must support

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • STU3
    • US Realm Task Force [deprecated]
    • STU
    • Encounter [deprecated]
    • Profiles and Extensions
    • Hide

      Proposal:
      - Remove diagnosis, diagnosis.condition and diagnosis.rank as Must Support

      Add guidance to both the Condition profile and the Encounter profile on how to search for encounter diagnosis

      Add to Quick Start SHOULD searches.

      Show
      Proposal: - Remove diagnosis, diagnosis.condition and diagnosis.rank as Must Support Add guidance to both the Condition profile and the Encounter profile on how to search for encounter diagnosis Add to Quick Start SHOULD searches.
    • Eric Haas/Brett Marquard: 21-0-1
    • Enhancement
    • Non-substantive

      Encounter.diagnosis is currently marked as Must Support, but this causes us issues since our system has diagnoses, but we don't support it in the Encounter API due to versioning concerns. Specifically, in our EHR, the Encounter.diagnosis.use and Encounter.diagnosis.rank are managed as attributes of the condition (not the Encounter). Thus, changes to the condition don't update the encounter's meta.lastUpdated date or versionId.

      Proposal: remove diagnosis, diagnosis.condition and diagnosis.rank as Must Support

            Assignee:
            Unassigned
            Reporter:
            Michelle Miller
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: