Condition.category - can be used to specify granular type code?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • STU
    • Condition
    • Hide

      During the Sept WGM PA/PC quarter, https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=20483 has been resolved - no change. These properties (Encounter.diagnosis.use) that already exist on encounter will remain there, and not denormalize into the condition.

      Show
      During the Sept WGM PA/PC quarter, https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=20483 has been resolved - no change. These properties (Encounter.diagnosis.use) that already exist on encounter will remain there, and not denormalize into the condition.
    • Jay/Rob: 8-0-0
    • Clarification

      Can it be clarified for Condition.category that we can use this 0...* attribute to specify information such as – this is a visit diagnosis vs. a billing diagnosis, + professional billing diagnosis vs. facility billing diagnosis, + present-on-admission diagnosis vs. discharge diagnosis? This is available to some extent under Encounter, but often we only care about these conditions outside of the context of the encounter.

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Claude Nanjo (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: