ui.launchactivity should only do a UI action of launching an activity

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • SMART Web Messaging (FHIR)
    • 0.1.0
    • FHIR Infrastructure
    • Home
    • Hide

      Perhaps there is confusion about what is expected to happen in the cited example with the problem condition.  The "problem" attribute is meant to be used by the EHR to pre-populate values in the problem-add form - the practitioner in control of the EHR remains the one responsible for adding the problem through some other action.  The pre-populated values just make that job easier.

      Show
      Perhaps there is confusion about what is expected to happen in the cited example with the problem condition.  The "problem" attribute is meant to be used by the EHR to pre-populate values in the problem-add form - the practitioner in control of the EHR remains the one responsible for adding the problem through some other action.  The pre-populated values just make that job easier.
    • Matt Varghese / Josh Bagley: 8-0-0
    • Correction
    • Non-compatible

      ui.launchactivity should only do a UI action of launching an activity. In the way the spec is written now, it can be leveraged as a clinical action for example with a problem-add activity to add a Condition resource to a patient. That is bad practice and mixing up concepts that should not be mixed together.

            Assignee:
            Unassigned
            Reporter:
            m_varghese
            m_varghese
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: