There's no need to mandate provider EHR workflow in this paragraph - PAS #124

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      This sentence does not mandate anything.  First, it's a lower-case should.  Second, it uses the phrase "appropriate", which would be a decision made by the EHR developer.  The purpose of the sentence is to highlight that there could be multiple relevant locations and that EHRs ought to provide access to this functionality in those locations where it would be useful to providers to access.

      Show
      This sentence does not mandate anything.  First, it's a lower-case should.  Second, it uses the phrase "appropriate", which would be a decision made by the EHR developer.  The purpose of the sentence is to highlight that there could be multiple relevant locations and that EHRs ought to provide access to this functionality in those locations where it would be useful to providers to access.
    • Laurie Burckhardt/Mark Scrimshire: 31-0-0

      Existing Wording: Within an EHR Client, the prior authorization request process should be capable of being evoked anywhere within the clinical and administrative workflow that is appropriate for that system.

      Comment:

      There's no need to mandate provider EHR workflow in this paragraph. This sentence should be removed.

      Summary:

      There's no need to mandate provider EHR workflow in this paragraph

            Assignee:
            Unassigned
            Reporter:
            Isaac Vetter
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: