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

From Updox API
Jump to: navigation, search
(→‎§170.314(b)(2) Create and Transport)
 
(11 intermediate revisions by one user not shown)
Line 1: Line 1:
−
== 170.314(b)(1) Receive, Display, Incorporate ==
+
== Description ==
 +
 
 +
Following are major test points in the path to Meaningful User Certification for §170.314(b)(1), §170.314(b)(2), and §170.314(e)(1) with which Updox can help.  Following each test point are one or ways in which the test can be passed using some component of Updox technology.
 +
 
 +
 
 +
 
 +
== §170.314(b)(1) Receive, Display, Incorporate ==
  
 
=== Send Direct Messages (D1-D16) ===
 
=== Send Direct Messages (D1-D16) ===
−
* API call: optional /DirectAddressValidate + (/DirectSimpleSend or /DirectMessageSend)
+
* API call: optional <code>/DirectAddressValidate</code> + (<code>/DirectSimpleSend</code> or <code>/DirectMessageSend</code>), or
−
* UpdoxUI from within EHR: /MessageCompose + “Send”
+
* UpdoxUI from within EHR: <code>/MessageCompose</code> + “Send”, or
−
* UpdoxUI from within EHR: /ApplicationOpen + “Compose” + ”Send”
+
* UpdoxUI from within EHR: <code>/ApplicationOpen</code> + “Compose” + ”Send”, or
 
* UpdoxUI-ProviderPortal: Compose + Send
 
* UpdoxUI-ProviderPortal: Compose + Send
  
  
 
=== Receive 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR) ===
 
=== Receive 4 Document Types (CCD/Ambulatory, CCD/Inpatient, C32, CCR) ===
−
* API call (polling): /MessageList or /MessageListSince or /MessageFetch + /MessageRetreive
+
* API call (polling): <code>/MessageListSince</code> or <code>/MessageFetch</code> + <code>/MessageRetreive</code>, or
−
* UpdoxUI: Provider Portal
+
* UpdoxUI: Provider Portal, or
−
* Other: Updox calls partner-side API upon Direct message receipt, partner calls /MessageRetreive 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) ===
−
* UpdoxUI: Provider Portal + Open email + “View Record”
+
* UpdoxUI: Provider Portal + Open email + “View Record”, or
 
* EHR: show within EHR
 
* EHR: show within EHR
  
  
 
=== Incorporate and Reconcile 2 Document Types (CCD/Ambulatory, CCD/Inpatient) ===  
 
=== Incorporate and Reconcile 2 Document Types (CCD/Ambulatory, CCD/Inpatient) ===  
−
* API: /MessageRetrieve + EHR Import
+
* API: <code>/MessageRetrieve</code> + EHR Import, or
−
* UpdoxUI: Provider Portal + Open email + “Import to EHR” + /QueueList + /QueueRetrieve + /QueueUpdate + /QueueDequeue
+
* UpdoxUI: Provider Portal + Open email + “Import to EHR” + <code>/QueueList</code> + <code>/QueueRetrieve</code> + <code>/QueueUpdate</code> + <code>/QueueDequeue</code>
  
  
Line 27: Line 33:
 
* Updox handles all of this automatically
 
* Updox handles all of this automatically
  
−
 
+
== &sect;170.314(b)(2) Create and Transport ==
−
 
+
−
 
+
−
== 170.314(b)(2) Create and Transport ==
+
  
 
=== Send Direct Messages (D1-D16) ===
 
=== Send Direct Messages (D1-D16) ===
−
* API call: optional /DirectAddressValidate + (/DirectSimpleSend or /DirectMessageSend)
+
* API call: optional <code>/DirectAddressValidate</code> + (<code>/DirectSimpleSend</code> or <code>/DirectMessageSend</code>), or
−
* UpdoxUI from within EHR: /MessageCompose + Send
+
* UpdoxUI from within EHR: <code>/MessageCompose</code> + Send, or
−
* UpdoxUI from within EHR: /ApplicationOpen + Compose + Send
+
* UpdoxUI from within EHR: <code>/ApplicationOpen</code> + Compose + Send, or
 
* UpdoxUI-ProviderPortal: Compose + Send
 
* UpdoxUI-ProviderPortal: Compose + Send
  
Line 44: Line 47:
  
 
=== Send Created CCDA to TTT ===
 
=== Send Created CCDA to TTT ===
−
* API: /DirectMessageSend
+
* API: <code>/DirectMessageSend</code>, or
−
* UpdoxUI from within EHR: /MessageCompose
+
* UpdoxUI from within EHR: <code>/MessageCompose</code>
−
 
+
−
 
+
−
 
+
  
−
== 170.314(e)(1) View, Download, and Transmit ==
+
== &sect;170.314(e)(1) View, Download, and Transmit ==
  
−
=== Prereq: transmit CCDA to patient portal from EHR ===
+
=== Prerequisite: Transmit CCDA to Patient Portal from EHR ===
−
* API: /PortalRecordSend
+
* API: <code>/PortalSendRecord</code>
  
  
Line 61: Line 61:
  
  
−
=== View CCDA as patient, as rep ===
+
=== View CCDA as Patient, as Authorized Representative ===
 
* UpdoxUI PatientPortal + “View”
 
* UpdoxUI PatientPortal + “View”
  
  
−
=== Download and view local ===
+
=== Download and View Local ===
−
* UpdoxUI PatientPortal + “Download Text”/“Download Data” ===
+
* UpdoxUI PatientPortal + “Download Text”/“Download Data”
  
  
−
=== Transmit CCDA to TTT
+
=== Transmit CCDA to TTT ===
−
* UpdoxUI PatientPortal + “Transmit” ===
+
* UpdoxUI PatientPortal + “Transmit”
  
  
−
=== Display portal audit log
+
=== Display Activity Audit Log ===
−
* UpdoxUI “Display Audit Trail” ===
+
* UpdoxUI “Display Audit Trail”
  
  
−
=== WCAG+
+
=== WCAG Compliance ===
−
* Updox attestation forms ===
+
* Updox attestation forms

Latest revision as of 11:05, 8 July 2014

Contents

Description

Following are major test points in the path to Meaningful User Certification for §170.314(b)(1), §170.314(b)(2), and §170.314(e)(1) with which Updox can help. Following each test point are one or ways in which the test can be passed using some component of Updox technology.


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

Send Direct Messages (D1-D16)

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


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

  • API call (polling): /MessageListSince or /MessageFetch + /MessageRetreive, or
  • UpdoxUI: Provider Portal, or
  • 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”, or
  • EHR: show within EHR


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

  • API: /MessageRetrieve + EHR Import, or
  • 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), or
  • UpdoxUI from within EHR: /MessageCompose + Send, or
  • UpdoxUI from within EHR: /ApplicationOpen + Compose + Send, or
  • UpdoxUI-ProviderPortal: Compose + Send


Create Patient Encounter/Summary of Care as Ambulatory/Inpatient

  • Within EHR only


Send Created CCDA to TTT

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

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

Prerequisite: Transmit CCDA to Patient Portal from EHR

  • API: /PortalSendRecord


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=2925"