I'm struggling with the notion of scratchpad

XMLWordPrintableJSON

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

      I believe there is still justification for the scratchpad message group and mechanism, and the suggested fhir. message group (in 1.8.4) is still not convincingly (IMHO) superior to the standard FHIR REST API.

      Show
      I believe there is still justification for the scratchpad message group and mechanism, and the suggested fhir. message group (in 1.8.4) is still not convincingly (IMHO) superior to the standard FHIR REST API.
    • Clarification

      I'm struggling with the notion of scratchpad.. From the SMART app's perspective, it is just telling the EHR to do something. It's more EHR internal process whether the action will be reviewed in a scratchpad before finalizing, or whether it will be immediately applied etc. Granted, it was myself, Josh, and Isaac who sat down and came up with the scratchpad., but now I'm having second thoughts In fact I'd even say, the messages should be fhir., and a separate fhir. message group described in 1.8.4 doesn't merit implementation.

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

              Created:
              Updated:
              Resolved: