Difference between revisions of "How can Updox help with MU Certification"
From Updox API
(→Description) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 2: | Line 2: | ||
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 more ways in which the test can be passed using some component of Updox technology. | 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 more ways in which the test can be passed using some component of Updox technology. | ||
| + | |||
| + | |||
| + | |||
== §170.314(b)(1) Receive, Display, Incorporate == | == §170.314(b)(1) Receive, Display, Incorporate == | ||
| Line 16: | Line 19: | ||
* 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) === | ||
| Line 49: | Line 53: | ||
* API: <code>/DirectMessageSend</code> | * API: <code>/DirectMessageSend</code> | ||
* UpdoxUI from within EHR: <code>/MessageCompose</code> | * UpdoxUI from within EHR: <code>/MessageCompose</code> | ||
| + | |||
| + | |||
Latest revision as of 09:52, 26 June 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 more 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+ (/DirectSimpleSendor/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
/MessageListSinceor/MessageFetch+/MessageRetreive - UpdoxUI: Provider Portal
- Other: Updox calls partner-side API upon Direct message receipt + partner calls
/MessageRetreivewith 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+ (/DirectSimpleSendor/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
