Model MedicationStatement.reasonCode as polymorphic element. - STU #33

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Pharmacy
    • MedicationStatement
    • Hide

      Not persausive. We require BOTH the Reason Code and Reason Reference. For example, Reason Code could be nausea with a Reason Reference to a related diagnosis.

      Show
      Not persausive. We require BOTH the Reason Code and Reason Reference. For example, Reason Code could be nausea with a Reason Reference to a related diagnosis.
    • John Hatem/Scott Robertson: 4-0-2
    • Correction

      Comment:

      The reason for a Medication statement should be modeled the same way as an Appointment or Encounter. They are all reasons for the event. They should be a polymorphic element (named the same across all of them) with a choice of codeableConcept or reference to a Condition, Procedure, or Observation

      Summary:

      Model MedicationStatement.reasonCode as polymorphic element.

            Assignee:
            Unassigned
            Reporter:
            corey_spears#1
            corey_spears#1
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: