Applicability Statement for Secure Health Transport - Implementation Group Consensus
Jump to navigation
Jump to search
Implementation Group Call for Consensus: Applicability Statement for Secure Health Transport
Closed, document reached consensus on 2/17/2011
Consensus voting on: Applicability Statement for Secure Health Transport
See the Documentation and Testing workgroup consensus votes here.
| Organization |
Endorsement (Yes or No) |
Comments (If "No," what can be changed to make it a "Yes") |
Disposition |
| Alere |
|||
| Allscripts |
|||
| American Academy of Family Physicians |
|||
| Atlas Development |
|||
| Axolotl |
|||
| CareEvolution, Inc. |
Yes |
||
| CareSpark |
Yes |
||
| Cautious Patient |
Yes |
||
| Cerner Corporation |
Yes |
||
| Christus Health |
|||
| Clinical Groupware Collaborative |
|||
| CMS |
|||
| Covisint |
|||
| CSC |
|||
| DoD |
|||
| eClinicalWorks |
|||
| Emdeon |
|||
| Epic |
Yes |
||
| FEI |
|||
| Health-ISP, a service of Garden State Health Systems |
Yes |
||
| GE |
Yes |
XDM does require more than just the reference to Vol 2b. Vol 1 includes the high level information, and Vol 3 contains necessary information on the metatdata |
|
| Google |
|||
| Greenway Medical Technologies |
|||
| Harris Corporation |
Yes |
||
| High Pine Associates |
Yes |
||
| HLN Consulting, LLC |
Yes |
||
| IBM |
Yes |
||
| ICA |
|||
| Indiana State Department of Health |
|||
| Inpriva |
|||
| Intel |
|||
| Kryptiq |
|||
| LabCorp |
|||
| Massachusetts eHealth Collaborative |
|||
| MedAllies |
|||
| MEDfx |
|||
| Medical Informatics Engineering, Inc./ NoMoreClipboard.com |
|||
| Medical University of SC, South Carolina Research Authority |
|||
| Medicity |
|||
| MedNet |
|||
| MedPATH Networks |
|||
| MedPlus/Quest Diagnostics |
Yes |
||
| Microsoft |
Yes |
||
| Mirth Corporation |
|||
| Misys Open Source Solutions (MOSS) |
|||
| MobileMD |
|||
| NextGen Healthcare Information Systems, Inc. |
|||
| NIH NCI |
|||
| NIST |
|||
| NYC Dept. of Health and Mental Hygiene’s PCIP |
|||
| Oregon HIE Planning Team |
Yes |
||
| Redwood MedNet |
|||
| RelayHealth |
|||
| Rhode Island Quality Institute |
|||
| SAFE-BioPharma |
|||
| SCHIEx - South Carolina Health Information Exchange |
|||
| Secure Exchange Solutions |
|||
| Serendipity Health, LLC |
Yes |
||
| Siemens |
Yes w comment |
In 2.4, it says "STAs MUST support the creation and processing of signed and encrypted MIME entities. That is, they MUST be capable of creating and reading documents that are encrypted as Enveloped Data, as specified by RFC 3851..." But I don't see RFC 3851 listed in the Normative References section 9.1 at the bottom of the spec. |
|
| Surescripts |
|||
| Techsant Technologies |
Yes |
||
| TN State HIE |
Yes |
||
| VA |
|||
| Verizon Business |
|||
| VisionShare |
Yes |