Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-28250

Modify Encounter.reason to allow DocumentReference and Bundle

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • Encounter
    • Hide

      We think using the workflow-supportingInfo extension is the best option here.  The document itself isn't really the reason for the encounter (unless you got a papercut).  Instead, you'd have Encounter.reason pointing to a Condition or some other resource that represents the reason being documented in the document.  Often the related resource would have the supportingInfo content, but if those aren't available, then you can use workflow-supportingInfo.

      Note that we are working on refactoring Encounter.reason, and that work is documented in https://confluence.hl7.org/pages/viewpage.action?pageId=51223352.  

      FHIR-35850 has been created for FHIR-I to expand/clarify the context of use for that extension to include Encounter.

      Show
      We think using the workflow-supportingInfo extension is the best option here.  The document itself isn't really the reason for the encounter (unless you got a papercut).  Instead, you'd have Encounter.reason pointing to a Condition or some other resource that represents the reason being documented in the document.  Often the related resource would have the supportingInfo content, but if those aren't available, then you can use workflow-supportingInfo. Note that we are working on refactoring Encounter.reason, and that work is documented in  https://confluence.hl7.org/pages/viewpage.action?pageId=51223352.    FHIR-35850  has been created for FHIR-I to expand/clarify the context of use for that extension to include Encounter.
    • Cooper Thompson / Line Saele: 7-0-1

    Description

      There is substantial use of a "Reason for Visit" section in clinical documents, so it should be valid to reference either a DocumentReference resource or a Bundle where Bundle.type=document as a reason for an encounter. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            rgeimer Rick Geimer
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: