User Story Workgroup Endorsements
Jump to navigation
Jump to search
| Company |
Vote (Yes/No) |
Comments |
| Allscripts |
No |
by Rich Elmore. Need to reserve for a possible change in prioritization with an extended implementation timeframe (plus some minor story edits) for "Patient Sends a Message to a Provider". Based on feedback from the Individual Involvement workgroup meeting on 4/29/2010. |
| American Academy of Family Physicians |
Yes |
by Steven Waldren |
| CareSpark |
Yes |
by Susan Torzewski |
| Cerner |
Yes |
by Andy Heeren |
| Clinical Groupware Collaborative |
||
| eClinicalWorks |
||
| Epic |
Yes |
by Peter DeVault |
| FEI.com |
Yes |
by Tony Calice |
| GE |
Yes |
by John Moehrke -- We should be careful to separate the transport requirements from the content and workflow requirements. The main difference in our use-cases is in content being communicated and workflow. |
| HLN Consulting, LLC |
||
| MedAllies |
||
| Medicity |
||
| MedPlus/Quest Diagnostics |
Yes |
by Steve Krsacok, Joannie McHugh |
| Oracle |
No |
Provider to Specialist "The referral reason is described in the message" In both the CCD and the CCR, the purpose is described within the document itself. Any text in the message should be on topics that are not included in sections in the CCR-CCD that are required for standard EHR documentation. |
| Oregon's Strategic Workgroup for the HIT Oversight Council |
||
| RedwoodMedNet |
Yes |
by Will Ross |
| Social Security Administration |
||
| SureScripts |
||
| VA |
||
| VisionShare |
Yes |