Feedback on "no known problems" - 2016-09 core #252

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Care
    • Condition
    • 9.2.3.4
    • Hide

      http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8749 - added No Known Problem to the valueset-condition-code

      Add to the condition.code value set defintion the "SNOMED 160245001 "No current problems or disability (situation)".

      Show
      http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8749 - added No Known Problem to the valueset-condition-code Add to the condition.code value set defintion the "SNOMED 160245001 "No current problems or disability (situation)".
    • Rob/Stephen: 3-0-1
    • Non-substantive
    • DSTU2

      Existing Wording: STU Note:There are two primary ways of reporting "no known problems" in the current specification: using the CodeableConcept, as described above, or using the List resource with emptyReason. During the STU period, feedback is sought regarding the preferred approach

      Comment:

      Per our prior change request 8749, we support using the CodeableConcept to convey No Known Problems. Additionally, since a Condition could represent both problems and concerns, it seems possible that there could be a situation where there are no known problems (on the provider's problem list), but there are concerns expressed by the patient (e.g. fear of losing a parent), such that a List empty reason is not going to work.

      Summary:

      Feedback on "no known problems"

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

              Created:
              Updated:
              Resolved: