advanced

Getting
Started

Founding
Members

Participating
Members

Receive Updates

Feedback

 

 

 

 

 
transaction scheduled
Security workgroup
Data Issues Workgroup
Communications Workgroup


Security/Connectivity Workgroup

The Security and Connectivity Workgroup helps you connect to your trading partner securely and effectively for HIPAA compliant transactions.

Our tools include:

  • A list of the security and connectivity methods that your trading partners support.
  • Guidance on transaction packaging methods for Collaboration members and the market in general.

Work Products

(Some of these documents are .pdf files; you will need Adobe® Acrobat® Reader, a free utility, to view. If you do not have Adobe® Acrobat® Reader, please click here to download.)

 

Preferred Connectivity Glossary of Terms

Minnesota HIPAA Collaborative Member

Recommended Connectivity Methods

Allina Hospitals & Clinics

Virtual Private Network

PGP encrypted FTP

Frame Relay Private Circuit

Point to Point

Blue Cross and Blue Shield of Minnesota
an independent licensee of the Blue Cross and Blue Shield Association

FTP over SSH

HTTPS

Fairview Health Services

PGP encrypted FTP

FTP over VPN

Frame Relay Private Circuit

HealthPartners

PGP encrypted FTP

Mayo Clinic

PGP encrypted FTP

Medica

Connectivity Methods not yet available

Minnesota Department of Human Services

Connectivity Methods not yet available

Park Nicollet Health Services

FTP over VPN

PGP encrypted FTP

PreferredOne

PGP encrypted FTP

Recommendations

 

Recommendations for File Size Limitations

Some of the ASC X12N Implementation Guides contain recommendations relative to maximum file sizes per transaction type. The Collaborative supports these recommendations until either ASC X12N or DHHS publishes further file size limitations.

 

Recommendations for File Naming Conventions

HIPAA regulations, the ASC X12N implementation guides and Minnesota regulations are relatively silent on the subject of naming standards for the generation and transmission of HIPAA-compliant transactions. In the absence of any such purported standard, the Collaborative felt it was valuable to propose a file naming convention that seems logical, intuitive and easy to execute.

 

 

 

 

Privacy Statement