HIPAA Compliance

Health Insurance Portability and Accountability Act compliance for medical imaging

Important HIPAA Notice

HTJ2K MetaWave codec software operates entirely on your local device and does NOT collect, transmit, or store Protected Health Information (PHI) or medical images. Therefore, for codec usage alone, we are NOT a Business Associate under HIPAA.

However, if you share PHI with us during support interactions or request our cloud services, we will execute a Business Associate Agreement (BAA).

1. HIPAA Overview

The Health Insurance Portability and Accountability Act (HIPAA) establishes national standards for protecting patient health information. Organizations handling Protected Health Information (PHI) must comply with HIPAA Privacy Rule, Security Rule, and Breach Notification Rule.

2. Our HIPAA Posture

2.1 Codec Software (Local Processing)

Not a Business Associate for Codec Usage

The HTJ2K MetaWave codec runs entirely on your device:

Conclusion: Since we do not create, receive, maintain, or transmit PHI during codec usage, we are NOT a Business Associate under 45 CFR § 160.103.

2.2 Support Interactions (BAA Required)

Business Associate Relationship Possible

If you share PHI with us during support:

We will execute a Business Associate Agreement (BAA) before accessing any PHI. Contact legal@htmeta.dev to request a BAA.

2.3 Your Responsibility as Covered Entity

If you are a HIPAA Covered Entity (hospital, clinic, PACS vendor), you remain responsible for:

3. HIPAA Security Rule Considerations

3.1 Technical Safeguards

While the codec itself doesn't handle PHI transmission, consider these implementation best practices:

Access Control

Audit Controls

Integrity Controls

🚨 Transmission Security

3.2 Physical Safeguards

3.3 Administrative Safeguards

4. Business Associate Agreement (BAA)

4.1 When BAA is Required

We will sign a BAA if:

4.2 BAA Key Terms

Our standard BAA includes:

4.3 Requesting a BAA

Need a Business Associate Agreement?

Contact our legal team to execute a BAA. Turnaround time: 5-10 business days.

Email: legal@htmeta.dev
Subject: BAA Request - [Your Organization Name]

5. DICOM and Medical Imaging Considerations

5.1 Metadata Handling

DICOM images contain PHI in metadata tags (patient name, MRN, DOB, etc.). The codec:

5.2 De-Identification

If sending us sample images, use DICOM de-identification per HIPAA Safe Harbor method (45 CFR § 164.514(b)):

6. Breach Notification

6.1 If You Experience a Breach

If PHI processed by our codec is compromised on your systems:

6.2 If We Experience a Breach

In the unlikely event we experience a breach involving your PHI (e.g., during BAA-covered support):

7. Enforcement and Penalties

HIPAA violations can result in significant penalties:

Ensure your implementation complies with all applicable regulations.

8. Compliance Resources

8.1 Documentation We Provide

8.2 External Resources

9. Frequently Asked Questions

Q: Do I need a BAA to use the codec?

A: No. The codec processes images locally and doesn't transmit PHI to us. BAA is only needed if you share PHI during support interactions.

Q: Does the codec log patient information?

A: No. The codec operates on image pixel data and doesn't parse or log DICOM metadata.

Q: Can I use the codec in a HIPAA-compliant PACS?

A: Yes. The codec is a processing component. Ensure your overall system architecture (network, storage, access controls) meets HIPAA requirements.

Q: What if my compliance officer requires a BAA anyway?

A: We're happy to sign a BAA for compliance documentation purposes. Contact legal@htmeta.dev.

Q: Is lossy compression HIPAA-compliant?

A: HIPAA doesn't prohibit lossy compression, but you must ensure it doesn't affect diagnostic quality. Use lossless mode for primary diagnostic images; lossy may be acceptable for secondary viewing or archives (consult your radiologists).

10. Contact Information