Make element naming and modeling more consistent for Appointment/Encounter reason - STU #27

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Encounter
    • Hide

      Appointment udpate:
      reasonCode codeableConcept
      reasonReference reference(Condition|Procedure|Observation|ImmunRecom)

      Update Encounter to:
      reasonCode codeableConcept
      reasonReference reference(Condition|Procedure|Observation|ImmunRecom)
      diagnosis
      condition reference(condition|procedure) – unchanged
      *use *(renamed from role) ...

      The description of the Encounter.diagnosis.condition property will be updated from "Reason the encounter takes place (resource)"

      to

      "The diagnosis or procedure relevant to the encounter"

      Show
      Appointment udpate: reasonCode codeableConcept reasonReference reference(Condition|Procedure|Observation|ImmunRecom) Update Encounter to: reasonCode codeableConcept reasonReference reference(Condition|Procedure|Observation|ImmunRecom) diagnosis condition reference(condition|procedure) – unchanged *use *(renamed from role) ... The description of the Encounter.diagnosis.condition property will be updated from "Reason the encounter takes place (resource)" to "The diagnosis or procedure relevant to the encounter"
    • Cooper Thompson/Stephen Chu: 14-0-0
    • Correction
    • Non-compatible
    • STU3

      Comment:

      Appointment has an "indication" element that is the reason for appointment which is a reference to a Condition or Procedure). It is unclear as to why the encounter reason does not have the same name and modeling. They both should be "indication" or "reason" and both should be a polymorphic codableConcept or reference to condition, observation, or procedure.

      Summary:

      Make element naming and modeling more consistent for Appointment/Encounter reason

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

              Created:
              Updated:
              Resolved: