Difference between revisions of "How does Updox help MU Certification"

From Updox API
Jump to: navigation, search
(→‎Receive 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR))
Line 11: Line 11:
 
* API call (polling): /MessageList or <code>/MessageListSince</code> or <code>/MessageFetch</code> + <code>/MessageRetreive</code>
 
* API call (polling): /MessageList or <code>/MessageListSince</code> or <code>/MessageFetch</code> + <code>/MessageRetreive</code>
 
* UpdoxUI: Provider Portal
 
* UpdoxUI: Provider Portal
−
* Other: Updox calls partner-side API upon Direct message receipt, partner calls <code>/MessageRetreive</code> with provided MsgId
+
* Other: Updox calls partner-side API upon Direct message receipt + partner calls <code>/MessageRetreive</code> with provided MsgId
−
 
+
  
 
=== Display 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR) ===
 
=== Display 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR) ===

Revision as of 11:06, 19 June 2014

Contents

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

Send Direct Messages (D1-D16)

  • 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

Send Direct Messages (D1-D16)

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


Create Patient Encounter/Summary of Care as Ambulatory/Inpatient

  • Within EHR only


Send Created CCDA to TTT

  • API: /DirectMessageSend
  • UpdoxUI from within EHR: /MessageCompose



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

Prerequisite: Transmit CCDA to Patient Portal from EHR

  • API: /PortalRecordSend


NTP

  • Within EHR
  • UpdoxUI: Updox demos


View CCDA as Patient, as Authorized Representative

  • UpdoxUI PatientPortal + “View”


Download and View Local

  • UpdoxUI PatientPortal + “Download Text”/“Download Data”


Transmit CCDA to TTT

  • UpdoxUI PatientPortal + “Transmit”


Display Activity Audit Log

  • UpdoxUI “Display Audit Trail”


WCAG Compliance

  • Updox attestation forms
Retrieved from "http://updoxqa.com/wiki/index.php?title=How_does_Updox_help_MU_Certification&oldid=2883"