Reference(Any) is too broad

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • STU
    • Encounter
    • Hide

      (This is a duplicate of 8372, 8184, 7906, 7613, 7304 and 7660)

      The reason property has been constrained to Condition and Diagnosis.

      The discharge diagnosis property is contrained to be Condition.

      Show
      (This is a duplicate of 8372, 8184, 7906, 7613, 7304 and 7660) The reason property has been constrained to Condition and Diagnosis. The discharge diagnosis property is contrained to be Condition.
    • Brian/Alexandra:5-0-0
    • Clarification
    • Non-compatible
    • DSTU1 [deprecated]

      For both Encounter.indication and Encounter.hospitalization.dischargeDiagnosis, you've got Reference(Any). There's no reason to be this open. It's going to result in inconsistency. For discharge diagnosis, I don't think anything other than Observation and Condition makes sense and you ought to be able to limit to Condition. For indication, Condition, Observation are all that really make sense either. If you have a ReferralRequest, ProcedureRequest or DiagnosticRequest, those should be linked in "fulfils", not "indication".

      As well, look at taking "reason" and "indication" and combining them into a choice unless you have strong use-cases for supporting both.

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: