How does Updox help MU Certification

From Updox API
Revision as of 10:52, 19 June 2014 by Thenate (Talk | contribs)

Jump to: navigation, search

Contents

170.314(b)(1) Receive, Display, Incorporate

Send Direct Messages

- API call: optional /DirectAddressValidate + (/DirectSimpleSend or /DirectMessageSend) - UpdoxUI from within EHR: /MessageCompose + “Send” - UpdoxUI from within EHR: /ApplicationOpen + “Compose” + ”Send” - UpdoxUI-ProviderPortal: Compose + Send


Receive 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR)

- API call (polling): /MessageList or /MessageListSince or /MessageFetch + /MessageRetreive - UpdoxUI: Provider Portal - Other: Updox calls partner-side API upon Direct message receipt, partner calls /MessageRetreive with provided MsgId


Display 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR)

- UpdoxUI: Provider Portal + Open email + “View Record” - EHR: show within EHR


Incorporate and Reconcile 2 Document Types (CCD/Ambulatory, CCD/Inpatient)

- API: /MessageRetrieve + EHR Import - UpdoxUI: Provider Portal + Open email + “Import to EHR” + /QueueList + /QueueRetrieve + /QueueUpdate + /QueueDequeue

Reject Invalid Direct Messages

- Updox handles all of this automatically



170.314(b)(2) Create and Transport

170.314(e)(1) View, Download, and Transmit

Retrieved from "http://updoxqa.com/wiki/index.php?title=How_does_Updox_help_MU_Certification&oldid=2875"