This week's introduction

As we mentioned last week, there are two main approaches to protecting data in HIFIS 4.

The first approach is by controlling what goes in to our database. We started to talk about this with regards to consent last week.

This week, we're focusing on controlling who has access to that information. Again, we can divide this into two chunks:

• controlling who has access to a given client file at all, and,
• controlling who has access to exactly what pieces of information are within the client file.

Term 2 is going to focus a lot on what information will be in a client file and who will need access to which information in order to do their job. This week, however, we're still going to be focusing on the real fundamentals. When a client exists in HIFIS, who can access the file at all?

Reference Materials

• HIFIS 4 Implementation Guide, Section 2.4