14.11.2014 Views

JR - Health Care Compliance Association

JR - Health Care Compliance Association

JR - Health Care Compliance Association

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

many tasks forces as they deemed<br />

appropriate. It was in their best interest<br />

to participate in this process so that<br />

their organizational structures and opinions<br />

on how to implement HIPAA at<br />

the School of Medicine would be taken<br />

into consideration. The main goals were<br />

to identify the use and disclosure of<br />

protected health information at the<br />

University, identify potential areas of<br />

risk, and to provide training and guidance<br />

to the practice plans. Unlike the<br />

hospitals affiliated with the School of<br />

Medicine, many practice plans did not<br />

have the manpower or resources in<br />

which to develop a HIPAA compliance<br />

begin with a blank canvas. As a result,<br />

flow chart templates for each task force<br />

were developed to allow the task force<br />

members to react to a base model<br />

rather than brainstorming on a blank<br />

sheet of paper. These templates were<br />

developed from flow charts from other<br />

organizations and from the experiences<br />

of our staff who have worked in physician<br />

practices. In addition to these task<br />

force meetings, the Office of <strong>Compliance</strong><br />

Services also convened meetings<br />

with the specific practice plans in order<br />

to provide a more detailed inventory<br />

of protected health information use,<br />

disclosure, and storage.<br />

similar to the need to know basis, and<br />

safeguards were essentially policies and<br />

procedures. This explanation was necessary<br />

in order to allow those who had<br />

not participated in the initial HIPAA<br />

process to understand the goals of the<br />

privacy and security regulations enough<br />

to assist the administrators in the assessment<br />

process. Simplifying this process<br />

will hopefully allow each work force<br />

member to assess the privacy and security<br />

risks present in their own areas.<br />

Training<br />

The next area of concern involved training.<br />

Pursuant to Section 164.530(b)(1),<br />

program alone. Therefore, guidance<br />

from the School of Medicine was necessary.<br />

Additionally, to mimic the structure<br />

developed for the <strong>Compliance</strong><br />

Program at the School of Medicine,<br />

each practice plan would be required to<br />

have a HIPAA compliance program that<br />

would need to be consistent with the<br />

yet to be finalized requirements of the<br />

School of Medicine’s HIPAA<br />

<strong>Compliance</strong> Program.<br />

The main charge for these task forces<br />

Assessments<br />

Identifying the use, disclosure, and storage<br />

of protected health information was<br />

only half the battle. The other half<br />

involved determining whether sufficient<br />

safeguards were in place. If these safeguards<br />

were not in place, what guidance<br />

would the School of Medicine need to<br />

provide to the practice plans to allow<br />

them to assess their current risks and to<br />

prioritize the privacy and security issues<br />

that needed to be addressed?<br />

covered entities must train all members<br />

of its work force as necessary and<br />

appropriate. However, in an academic<br />

medical setting, it is extremely difficult<br />

to keep track of who has met this training<br />

requirement. Many work force<br />

members wear several hats and go in<br />

and out of the several covered entities<br />

on campus on a daily basis. So, who has<br />

a responsibility of providing this training?<br />

Therefore, the various affiliates of<br />

the School of Medicine decided that a<br />

reciprocal training program had to be<br />

was to develop a flow chart of how protected<br />

health information was used, disclosed,<br />

and stored within their practices.<br />

Based on these findings, a checklist was<br />

developed to assist with the assessment<br />

of the uses, disclosures, and storage of<br />

protected health information. The purpose<br />

of the flow charts was not to identify<br />

every detailed use, disclosure, and<br />

storage of protected health information,<br />

but the main concern was to identify<br />

the more common processes that were<br />

likely to occur among the various practice<br />

plans. In an effort to make their<br />

time more valuable and efficient, it was<br />

imperative that the task forces did not<br />

Clearly, the administrator of each practice<br />

plan alone could not accomplish<br />

this process. One of the main themes<br />

that the Office of <strong>Compliance</strong> Services<br />

wanted to get across during its initial<br />

training for HIPAA awareness was that<br />

the confidentiality of patient information,<br />

now known as protected health<br />

information, was not a new phenomenon.<br />

Therefore, part of the training<br />

would entail reintroducing a familiar<br />

topic in the health care industry under<br />

different names. Protected health information<br />

was simply confidential patient<br />

information, minimum necessary was<br />

developed. Open training schedules<br />

were advertised and any member of the<br />

work force from any of the covered<br />

entities at the medical center were permitted<br />

to attend any training session.<br />

Uniform attendance sheets were developed<br />

so that the information could be<br />

consistently tracked.<br />

Perhaps one of the greatest hurdles to<br />

overcome in the HIPAA implementation<br />

process was the development of<br />

policies and procedures that are consistent<br />

among the various covered entities<br />

at the medical center. Initially, develop-<br />

Continued on page 24<br />

23<br />

August 2002

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!