Feedback on ClinicalImpression - 2016-09 core #363

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Care
    • ClinicalImpression
    • 9.6.1
    • Hide

      No changes needed.

      •When is an existing clinical impression revised, rather than a new one created (that references the existing one)? Riki's comment didn't advocate strongly one way or the other, so this remains an open question where we are seeking input.


      •Should prognosis be represented, and if so, how much structure should it have? *Patient Care wants to keep the flexibility of using *either a CodeableConcept and/or a RiskAssessment, so we will keep the prognosis elements.

      Show
      No changes needed. • When is an existing clinical impression revised, rather than a new one created (that references the existing one)? Riki's comment didn't advocate strongly one way or the other, so this remains an open question where we are seeking input. • Should prognosis be represented, and if so, how much structure should it have? *Patient Care wants to keep the flexibility of using *either a CodeableConcept and/or a RiskAssessment, so we will keep the prognosis elements.
    • Rob/Stephen: 5-0-0
    • Clarification

      Comment:

      depends what the need is to capture changes to the Impression over time (if changes over time are important, then may need specific rules about when a new resource is created that links to the superseded version) - would need clear guidance when "draft" is appropriate vs. "completed" as well as at what time one or more conditions (diagnosis) is being added (if draft, then must be working type?).

      Since there is a reference to risk assessment, don't think prognosis is needed.

      Summary:

      Feedback on ClinicalImpression

            Assignee:
            Unassigned
            Reporter:
            Ulrike Merrick
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: