Communication basedOn(any) seems too broad - shouldn't it be limited to CommunicationRequest? - 2016-09 core #538

XMLWordPrintableJSON

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

      Communications can occur as a result of other orders. For example a ReferralRequest, DiagnosticRequest or even MedicationOrder could result in the patient being given educational material. Request and event resources don't necessarily exist in neat pairs.

      Show
      Communications can occur as a result of other orders. For example a ReferralRequest, DiagnosticRequest or even MedicationOrder could result in the patient being given educational material. Request and event resources don't necessarily exist in neat pairs.
    • Russ/Elaine: 4-0-2
    • Clarification

      Comment:

      Communication basedOn(any) seems too broad - shouldn't it be limited to CommunicationRequest?

      Summary:

      Communication basedOn(any) seems too broad - shouldn't it be limited to CommunicationRequest?

            Assignee:
            Unassigned
            Reporter:
            Paul Knapp
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: