Privacy Policy

DATE:                                   January 1, 2013                                   

SUBJECT:                            HMIS Privacy and Confidentiality

APPROVAL LEVEL:          Agency Board of Directors

REASONS FOR POLICY:

 

  1. To protect to privacy of agency clients
  2. To comply applicable laws and regulations
  3. To insure fair information practices as to:
    1. Openness
    2. Accountability
    3. Collection limitations
    4. Purpose and use limitations
    5. Access and correction
    6. Data Quality
    7. Security

 

 

STATEMENT OF POLICY:

 

  • Compliance Agency privacy practices will comply with all applicable laws governing HMIS client privacy/confidentiality. Applicable standards include, but are not limited to the following.
    1. Federal Register Vol. 69, No. 146 (HMIS FR 4848-N-02) – Federal statute governing HMIS information.
    2. HIPAA – the Health Insurance Portability Act.
    3. 42 CFR Part 2. – Federal statute governing drug and alcohol treatment.
    4. MSHMIS – Michigan Statewide HMIS Policy and Procedures)
    5. Negotiated QSOBAA(s) – Inter-agency sharing agreement(s).

 

NOTE: HIPAA statutes are more restrictive than the HMIS FR 4848-N-02 standards and in cases where both apply, HIPAA over-rides the HMIS FR 4848-N-02 standards.  In cases where an agency already has a confidentiality policy designed around the HIPAA standards, that policy can be modified to include the HMIS data collection, or can be amended to create one set of standards for clients covered under HIPAA, and a second set of standards for those covered only under HMIS FR 4848-N-02. Agencies should indicate in their Privacy Notice which standards apply to their situation.

 

 

  • Use of Information PPI (protected personal information , that is information which can be used to identify a specific client) can be used only for the following purposes:
    1. To provide or coordinate services to a client.
    2. For functions related to payment or reimbursement for services.
    3. To carry out administrative functions such as legal, audit, personnel, planning, oversight and management functions.
    4. For creating de-personalized client identification for unduplicated counting.
    5. Where disclosure is required by law.
    6. To prevent or lessen a serious and imminent threat to the health or safety of an individual or the public.
    7. To report abuse, neglect, or domestic violence as required or allowed by law.
    8. Contractual research where privacy conditions are met (including a written agreement).
    9. To report criminal activity on agency premises.
    10. For law enforcement purposes in response to a properly authorized request for information from a properly authorized source.

 

NOTE:  HMIS FR 4848-N-02 standards list items a-d above as allowable reasons for disclosing PPI but make provisions for additional uses to meet individual agency obligations In some cases these uses (e-j above) have additional conditions, and HMIS FR 4848-N-02 4.1.3 should be consulted if any of these optional items are to be included in an agency’s policy . It also states that “except for first party access to information and required disclosures for oversight and compliance auditing, all uses and disclosures are permissive and not mandatory.”

 

NOTE:  if a client refuses to release PPI, and such information is needed/required in order to provide services, the client’s refusal may necessitate denial of service. Agencies may choose to make provisions for such denial of services in their policy.

 

 

  • Collection and Notification Information will be collected only by fair and lawful means with the knowledge or consent of the client.
    1. PPI will be collected only for the purposes listed above.
    2. Clients will be made aware that personal information is being collected and recorded.
    3. A written sign will be posted in locations where PPI is collected. This written notice will read:

 

“We collect personal information directly from you for reasons that are discussed in our privacy statement.  We may be required to collect some personal information by law or by organizations that give us money to operate this program.  Other personal information that we collect is important to run our programs, to improve services for homeless persons, and to better understand the needs of homeless persons.  We only collect information that we consider to be appropriate.”

 

“The collection and use of all personal information is guided by strict standards of confidentiality.  Our Privacy Notice is posted.  A copy of our Privacy Notice is available to all clients upon request.

 

  1. This sign will be explained in cases where the client is unable to read and/or understand it.

 

NOTE: Under HMIS FR 4848-N-02, agencies are permitted to require a client to express consent to collect PPI verbally or in writing, however this is optional and not a requirement of the statute.

 

  • Data Quality   PPI data will be accurate, complete, timely, and relevant.
    1. All PPI collected will be relevant to the purposes for which it is to be used.
    2. Identifiers will be removed from data that is not in current use after 7 years (from date of creation or last edit) unless other requirements mandate longer retention.
    3. Data will be entered in a consistent manner by authorized users.
    4. Data will be entered in as close to real-time data entry as possible.
    5. Measures will be developed to monitor data for accuracy and completeness and for the correction of errors.
      1. The agency runs reports and queries monthly to help identify incomplete or inaccurate information.
      2. The agency monitors the correction of incomplete or inaccurate information.
  • By the 15th of the following month all monitoring reports will reflect corrected data.
  1. Data quality is subject to routine audit by System Administrators who have administrate responsibilities for the database.

 

 

  • Privacy Notice, Purpose Specification and Use Limitations The purposes for collecting PPI data, as well as it uses and disclosures will be specified and limited.
    1. The purposes, uses, disclosures, policies, and practices relative to PPI data will be outlined in an agency Privacy Notice (copy attached).
    2. The agency Privacy Notice will comply with all applicable regulatory and contractual limitations.
    3. The agency Privacy Notice will be made available to agency clients, or their representative, upon request and explained/interpreted as needed.
    4. Reasonable accommodations will be made with regards to the Privacy Notice for persons with disabilities and non-English speaking clients as required by law.
    5. PPI will be used and disclosed only as specified in the Privacy Notice, and only for the purposes specified therein,
    6. Uses and disclosures not specified in the Privacy Notice can be made only with the consent of the client.
    7. The Privacy Notice will be posted on the agency web site.
    8. The Privacy Notice will reviewed and amended as needed.
    9. Amendments to or revisions of the Privacy Notice will address the retroactivity of any changes.
    10. Permanent documentation will be maintained of all Privacy Notice amendments/revisions.
    11. All access to, and editing of PPI data will be tracked by an automated audit trail, and will be monitored for violations use/disclosure limitations.

 

NOTE: Items above are required by HMIS FR 4848-N-02, and/or  MSHMIS policy, but agencies can restrict and limit the use of PPI data further by requiring express client consent for various types of uses/disclosures, and/or by putting restriction or limits on various kinds of  uses/disclosures.

 

  • Record Access and Correction Provisions will be maintained for the access to and corrections of  PPI records.
    1. Clients will be allowed to review their MSHMIS record within 5 working days of a request to do so.
    2. During a client review of their record, an agency staff person must be available to explain any entries the client does not understand.
    3. The client may request to have their record corrected so that information is up-to-date and accurate to ensure fairness in its use.
    4. When a correction is requested by a client, the request will be documented and the staff make a corrective entry if the request is valid.
    5. A client may be denied access to their personal information for the following reasons:
      1. Information is compiled in reasonable anticipation of litigation or comparable proceedings;
      2. Information about another individual other than the agency staff would be disclosed,
  • Information was obtained under a promise of confidentiality other than a promise from this provider and disclosure would reveal the source of the information
  1. Information, the disclosure of which would be reasonably likely to endanger the life or physical safety of any individual.
  1. A client may be denied access to their personal information in the case of repeated or harassing requests for access or correction. However, if denied, documentation will be provided regarding the request and reason for denial to the individual and be made a part of the client’s record.
  2. A grievance process may be initiated if a client feels that their confidentiality rights have been violated, if access has been denied to their personal records, or if they have been put at personal risk, or harmed.
  3. Any client grievances relative to HMIS will be processed/resolved according to agency grievance policy.
  4. A copy of any client grievances relative to HMIS data or other privacy/confidentiality issues and agency response are forwarded to MiCAH.

 

  • Accountability Processes will be maintained to insure that the privacy and confidentiality of client information is protected and staff is properly prepared and accountable to carry out agency policies and procedure that govern the use of PPI data.
    1. Grievances may be initiated through the agency grievance process for considering questions or complaints regarding privacy and security policies and practices .All users of the MSHMIS must sign a Users Agreement that specifies each staff persons obligations with regard to protecting the privacy of PPI and indicates that they have received a copy of the agency’s Privacy Notice and that they will comply with its guidelines.
    2. All users of the MSHMIS must complete formal privacy training.
    3. A process will be maintained to document and verify completion of training requirements.
    4. A process will be maintained to monitor and audit compliance with basic privacy requirements including but not limited to auditing clients entered against signed MSHMIS Releases.
    5. A copy of any staff grievances initiated relative to privacy, confidentiality, or MSHMIS data will be forwarded to MiCAH.
    6. Regular user meetings will be held and issues concerning data security, client confidentiality, and information privacy will be discussed and solutions will be developed. Minutes of user meetings will be forwarded to MiCAH as required by the MSHMIS participation agreement.

 

  • Sharing of Information Client data may be shared with partnering agencies only with client approval
    1. All routine data sharing practices with partnering agencies will be documented and governed by a Qualified Service Organization Business Associate Agreement, (QSOBAA) that defines the agency-determined sharing practice.
    2. Agency defaults within the MSHMIS system will be set to “closed,” open for planned exception guided by sharing agreements negotiated between agencies (QSOBAAs).
    3. A completed MSHMIS Client Release of Information (ROI) Form is need before information may shared electronically according to QSOBAA(s).
      1. The MSHMIS release is customized to inform the client about what is shared and with whom it is shared. The customization reflects the agency’s QSOBAA(s).
      2. The client accepts or rejects the sharing plan.
  • If the client rejects the sharing plan, staff click the Security Button, which closes the record.
  1. Clients will be informed about and understand the benefits, risks, and available alternatives to sharing your information prior to signing an ROI, and their decision to sign or not sign shall be voluntary.
  2. Clients who choose not to authorize sharing of information cannot be denied services for which they would otherwise be eligible.
  3. All Client Authorization for ROI forms related to the MSHMIS will be placed in a file to be located on premises and will be made available to the MCAH for periodic audits.
  4. MSHMIS-related Authorization for ROI forms will be retained for a period of 7 years, after which time the forms will be discarded in a manner that ensures client confidentiality is not compromised.
  5. No confidential/restricted information received from the MSHMIS will be shared with any organization or individual without proper written consent by the client, unless otherwise permitted by applicable regulations or laws.
  6. Restricted information, including progress notes and psychotherapy notes, about the diagnosis, treatment, or referrals related to a mental health disorder, drug or alcohol disorder, HIV/AIDS, and domestic violence concerns shall not be shared with other participating Agencies without the client’s written, informed consent as documented on the Agency-modified Authorization for Release of Confidential Form.
    1. Sharing of restricted information is not covered under the general MSHMIS Client ROI.
    2. Sharing of restricted information must also be planned and documented through a fully executed QSOBAA.
  • If a field that normally contain non-confidential information discloses confidential information.
    • The staff completes an Authorization to release Confidential Information.
    • If the client refuses to authorize the release, the staff closes the Assessment/Screen by clicking the lock on the screen and removing any exceptions.
  1. If a client has previously given permission to share information with multiple agencies, beyond basic identifying information and non-restricted service transactions, and then chooses to revoke that permission with regard to one or more of these agencies, the effected agency/ agencies will be contacted accordingly, and those portions of the record, impacted by the revocation, to will be locked from further sharing.
  2. All client ROI forms will include an expiration date, and once a Client ROI expires, any new information entered will be closed to sharing.

 

  • System Security System security provisions will apply to all systems where PPI is stored, agency’s networks, desktops, laptops, mini-computers, mainframes and servers.
    1. Password Access:
      1. Only individuals who have completed Privacy and System Training may be given access to the MSHMIS through User IDs and Passwords.
      2. Temporary/default passwords will be changed on first use.
  • Access to PPI requires a user name and password at least 8 characters long and using at least one number and one letter.
  1. Passwords will not use or include the users name or the vendor name, and will not consist entirely of any word found in the common dictionary or any of the above words spelled backwards.
  2. User Name and password may not be stored or displayed in any publicly accessible location
  3. Passwords must be changed routinely.
  • Users must not be able to log onto more than one workstation or location at a time.
  • Individuals with User IDs and Passwords will not give or share assigned User ID and Passwords to access the MSHMIS with any other organization, governmental entity, business, or individual.
  1. Virus Protection and Firewalls:
    1. Commercial virus protection software will be maintained to protect HMIS system from virus attack.
    2. Virus protection will include automated scanning of files as they are access by users..
  • Virus Definitions will be updated regularly.
  1. All workstations will be protected by a firewall either through a workstation firewall or a server firewall.
  1. Physical Access to Systems where HMIS Data is Stored
    1. Computers stationed in public places must be secured when workstations are not in use and staff are not present.
    2. After a short period of time a pass word protected screen saver will be activated during time that the system is temporarily not in use.
  • For extended absence, staff must log off the computer
  1. Stored Data Security and Disposal:
    1. All HMIS data downloaded onto a data storage medium must be maintained and stored in a secure location.
    2. Data downloaded for purposes of statistical analysis will exclude PPI whenever possible.
  • HMIS data downloaded onto a data storage medium must be disposed of by reformatting as opposed to erasing or deleting.
  1. A data storage medium will be reformatted a second time before the medium is reused or disposed of.
  1. System Monitoring
    1. User access to the MSHMIS Live Web Site will be monitored using the computer access logs located on each computer’s explorer “history” button, or via a central server report.
  2. Hard Copy Security:
    1. Any paper or other hard copy containing PPI that is either generated by or for HMIS, including, but not limited to report, data entry forms and signed consent forms will be secured.
    2. Agency staff will supervise at all time hard copy with identifying information generated by or for the HMIS when the hard copy is in a public area. If the staff leaves the area, the hard copy must be secured in areas not accessible by the public.
  • All written information pertaining to the user name and password must not be stored or displayed in any publicly accessible location.

 

NOTE :Various important aspects of system security are the contracted responsibility of Bowman Systems and are therefore not covered in agency policy.  These involve procedures and protections that take place at the site of the central server and include data backup, disaster recovery, data encryption, binary storage requirements, physical storage security, public access controls, location authentication etc.

 

 

PROCEDURES:

 

NOTE: Procedures and roles relative to this policy should be defined in a procedure section. These  will vary significantly from agency to agency but may include the following.

 

  1. Participating agencies may integrate MSHMIS into the agency’s existing Privacy Notice. If the agency does not have an existing Privacy Notice, agencies may adopt the MSHMIS Privacy Notice Example or use it as a model.  The Privacy Notice must reflect the agency’s privacy policy.
  2. Board approval of your Confidentiality/Privacy Policy is required. Copies of the Participation Agreement, the User Agreement/Code of Ethics, and the Sharing QSOBAA may be attachments to your Policy.  In addition to customizing the sample policy provided above, the agency should describe:
    1. A plan for remote access if staff will be using the MSHMIS System outside of the office such as doing entry from home. Concerns addressed in this plan should include the privacy surrounding the off site entry
    2. Who will have what Access Levels on MSHMIS ServicePoint.
    3. How access to the room(s) where the System is being used will be controlled. 
    4. Procedures for acquiring client consent.
      1. The Agency’s Privacy Notice should be posted.
      2. How the Privacy Notice will be explained (include the basic script – models are provided by MSHMIS for different levels of intervention).
  • How and when the MSHMIS Release will be introduced to clients.
  1. A copy of the second Release required to share restricted information (MSHMIS has provided several models).