Operational infrastructure for HIPAA compliance

The operational layer for work that touches protected health information. Structure, control and trace every record, without replacing the systems you already run.

We take HIPAA Database Compliance seriously

Data Security is at Kohezion's core

Business Associate Agreement

Breach Mitigation

Fully Managed Firewall

Unique HIPPA User IDs

handshake_2_icon
branch mitigation_2_icon
handshake_2_icon-Recovered
barcode_2_icon

User Audit Logs

High-Security Infrastructure

Fully Encrypted Backups

Encrypted Storage

user_audit_2_icon
padlock_icon_2
backup_icon_2
storage_icon_2

Your EHR and practice management system stay where they are

Most organizations handling PHI already run a solid system of record. What usually sits outside it is the work in between: the intake that lives in a shared folder, the case tracked in a spreadsheet, the release-of-information log someone keeps by hand. That work carries PHI too, and it is rarely held to the same standard as the record system.

Kohezion holds that work, with the same structure, control and traceability you expect of a record system, and connects out to the platforms you already depend on. Nothing gets ripped out, and nothing gets migrated that does not need to move.

clark
yale
harvard
marine mammal
university of san francisco
iniversity of illinois

Dedicated HIPAA support team

The dedicated Kohezion HIPAA compliance team provides priority support and 10 hours of free consulting to get you started. But it doesn’t stop there, a Kohezion expert is always available to assist with new projects.

A large shield outline at the center with a medical cross inside

HIPAA Compliant Software

The Health Insurance Portability and Accountability Act (HIPAA) was enacted with the goal of improving the efficiency and effectiveness of the health care system, as well as maintaining consistency and security around the exchange of electronic protected health information (PHI).

HIPAA covers many entities, including health care providers that are required to follow the 3 primary rules to ensure patient data security.

HIPAA impacts healthcare workers in several different ways, regardless of the size of the practice. Let’s use a medical clinic as an example. When treating a patient, sharing records with other physicians, and processing payments, PHI must remain confidential and is only authorized to be disclosed for very specific purposes or situations. A medical practice must also ensure that they are storing all their patient data in a way that is HIPAA compliant. Often this means limiting employee access to PHI, encrypting data, and being proactively prepared with a breach mitigation strategy.

Adopting technologies that allow healthcare providers to grow while maintaining HIPAA compliance is extremely important, as we are continuing to see significant numbers of HIPAA violation in the medical sector.  Healthcare providers must make informed decisions when selecting healthcare software to manage their PHI data to ensure it meets HIPAA requirements now, and in the future.

HIPAA Compliant Healthcare

What Does Kohezion's HIPAA Compliant Database Software cover?

Privacy

Kohezion is committed to safeguarding Patient Health Information data by encrypting storage and monitoring system access to maintain compliance for end-users.

Disclosure

Full event disclosure for security incidents that affect client data. In the event of any incident affecting your data, your account administrator will be notified immediately.

Security

Kohezion has a risk management plan to mitigate, and proactively protect against data breaches. Access to Kohezion servers is restricted to specific individuals who are closely monitored and audited to maintain compliance

Business Associate Agreement

Before handling Patient Health Information data, Kohezion requires both parties to sign a Business Associate Agreement, which is covered by law under the Health Insurance Portability and Accountability Act.

Kohezion Database Builder Software

Build custom, secure, HIPAA compliant applications to store your PHI data.

Structured, controlled and traceable from the first record, not from the first audit.

How a Kohezion application holds PHI

You describe what the record has to hold. The fields, the links between records, the rules that check an entry and the permissions that govern who sees each field become a working Kohezion application, built to the standards set by the US Department of Health and Human Services.

STRUCTURED. Every record carries the same fields, the same required entries and the same links to the records around it, so nothing gets saved half finished.

CONTROLLED. Access is set by role, by user group, by application and by individual field, and revoked the moment someone leaves.

TRACED. Every change to a field, every version of a record and every time someone opened it is kept, with the name and the timestamp attached.

FAST. A first application goes live in hours rather than months, and your own team changes it afterward without programming, with video training and support from Kohezion consultants.

AWS HIPAA-Compliant Servers

HIPAA Compliant AWS Servers

Kohezion's IT cloud infrastructure complies with the best standards and practices in the industry for a HIPAA Compliant Database Software.

HIPAA Definition

HIPAA is an acronym for the “Health Insurance Portability and Accountability Act.” It is an Act that was passed by Congress in 1996.

A few of the main reasons for the passing of the Act include:

  • Modernizing the PHI flow: revamping the way patient information is stored, shared, and utilized.
  • Laying out PHI security ground rules: ensuring the protection of data maintained by the health industry from fraud and theft.
  • Addressing constraints in healthcare insurance coverage: making sure workers and their families are always covered. It applies even though they may be employed, unemployed, or between jobs at the time.

Overall, HIPAA is meant to protect patients' privacy by stating the essential requirements for the secure storage and access of their health data. This is how the need for HIPAA Compliance Software begins.

HIPAA Compliance Act US Congress

Protected Health Information (PHI)

It covers data on the health status, received healthcare, payments made for treatments, or any related data that you can trace back to an individual patient. Examples of such data include names, financial information, contact details (digital or otherwise), account numbers, and biometric or identifying media files.

Primary Rules of HIPAA

HIPAA regulation consists of 3 primary rules that keep patient’s health information safe and make the foundation for any database software to be  a HIPAA compliant database software:

The Security Rule

Safeguards that covered entities and business associates must implement to protect the confidentiality, integrity, and availability of protected health information. When it comes to electronically stored protected health information (ePHI), this security rule lays down three security safeguards – Administrative, Physical, and Technical – that must be adhered to in full in order to comply with HIPAA.

The safeguards have the following goals:

Administrative: To create policies and procedures that clearly show covered entities and business associates how they need to comply with the Act.
Physical: to control the physical access of data storage devices and areas (server rooms, for example) to protect against unauthorized access
Technical: to protect health information data packets as they are in transit over open communication networks

The Privacy Rule

Sets the national standards that outline when PHI can be used or disclosed without the patients’ authorization; on the other hand, the HIPAA privacy rule also outlines patients’ rights over their own personal health information and includes their right to access, copy, or edit their records (in case of errors).

The Breach Notification Rule

It states that – within 60 days – covered entities must notify any affected patients about a leak or loss of their PHI; they also need to contact the U.S. Department of Health & Human Services (HHS) and might even need to handle press releases to the media and the public in general.

In 2013, the HIPAA Omnibus Rule was added which resulted in the final version of the HIPAA Privacy Policy and Security Rule. It also laid out the final rules for the enforcement, data breach notification, and the Genetic Information Nondiscrimination Act (GINA).

Deploy your HIPAA compliant application, fast

Bring the work that currently sits in spreadsheets, shared folders and email threads onto one platform. A first application is deployed in hours rather than months. What takes the time is agreeing what the record has to contain, not the build.

HIPAA Compliant Software FAQ

Scroll to Top