Your cart is currently empty!
PRIVACY POLICY
Who we are:
This is a gathering place for supporters of the System Speak podcast and its community.
Our website address is: https://systemspeakcommunity.com
This website does not collect or retain your data.
Comments
We recommend you utilize basic cyber safety when participating in online discussions and communities, including not disclosing identifying information to people you do not know or do not feel safe with, and we recommend you not disclose personal details that would enable anyone to access your internal system or geographic location.
When visitors leave comments on the site, we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection. This is not used for other purposes, aside from site safety and protection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Media
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Cookies
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
We highly recommend crispy chocolate chip oatmeal cookies (no raisins). You can make them crispier if you tap them with a spatula as soon as they come out of the oven.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Who we share your data with:
No one.
However, if you request a password reset, your IP address will be included in the reset email.
If you opt-in to newsletters or email services, your information is retained for that purpose according to standard security processes.
If you order things from the shops, your contact information is retained only for shipping purposes, in accordance with established third party sites providing drop-shipping services.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where your data is sent
Visitor comments may be checked through an established automated spam detection service.
NOTICE OF PRIVACY PRACTICE PRACTICES
for PROTECTED HEALTH INFORMATION
[45 CFR 164.520]
Background
The HIPAA Privacy Rule gives individuals a fundamental new right to be informed of the privacy practices of their health plans and of most of their health care providers, as well as to be informed of their privacy rights with respect to their personal health information. Health plans and covered health care providers are required to develop and distribute a notice that provides a clear explanation of these rights and practices. The notice is intended to focus individuals on privacy issues and concerns, and to prompt them to have discussions with their health plans and health care providers and exercise their rights.
How the Rule Works
General Rule. The Privacy Rule provides that an individual has a right to adequate notice of how a covered entity may use and disclose protected health information about the individual, as well as his or her rights and the covered entity’s obligations with respect to that information.
Most covered entities must develop and provide individuals with this notice of their privacy practices.
The Privacy Rule does not require the following covered entities to develop a notice:
C | Health care clearinghouses, if the only protected health information they create or receive is as a business associate of another covered entity. See 45 CFR 164.500(b)(1). |
C | A correctional institution that is a covered entity (e.g., that has a covered health care provider component). |
C | A group health plan that provides benefits only through one or more contracts of insurance with health insurance issuers or HMOs, and that does not create or receive protected health information other than summary health information or enrollment or disenrollment information. |
See 45 CFR 164.520(a).
Content of the Notice. Covered entities are required to provide a notice in plain language
that describes:
OCR HIPAA Privacy December 3, 2002 Revised April 3, 2003 | |
C | How the covered entity may use and disclose protected health information about an individual. |
C | The individual’s rights with respect to the information and how the individual may exercise these rights, including how the individual may complain to the covered entity. |
C | The covered entity’s legal duties with respect to the information, including a statement that the covered entity is required by law to maintain the privacy of protected health information. |
C | Whom individuals can contact for further information about the covered entity’s privacy policies. |
The notice must include an effective date. See 45 CFR 164.520(b) for the specific requirements for developing the content of the notice.
A covered entity is required to promptly revise and distribute its notice whenever it makes material changes to any of its privacy practices. See 45 CFR 164.520(b)(3), 164.520(c)(1)(i)(C) for health plans, and 164.520(c)(2)(iv) for covered health care providers with direct treatment relationships with individuals.
Providing the Notice.
C A covered entity must make its notice available to any person who asks for it.
C A covered entity must prominently post and make available its notice on any web site it maintains that provides information about its customer services or benefits.
C Health Plans must also:
< Provide the notice to individuals then covered by the plan no later than April 14, 2003 (April 14, 2004, for small health plans) and to new enrollees at the time of enrollment.
< Provide a revised notice to individuals then covered by the plan within 60 days of a material revision.
< Notify individuals then covered by the plan of the availability of and how to obtain the notice at least once every three years.
C Covered Direct Treatment Providers must also:
< Provide the notice to the individual no later than the date of first service delivery (after the April 14, 2003 compliance date of the Privacy Rule) and, except in an emergency treatment situation, make a good faith effort to obtain the individual’s written acknowledgment of receipt of the notice. If an acknowledgment cannot be obtained, the provider must document his or her efforts to obtain the acknowledgment and the reason why it was not obtained.
< When first service delivery to an individual is provided over the Internet, through e-mail, or otherwise electronically, the provider must send an electronic notice automatically and contemporaneously in response to the individual’s first request for service. The provider must make a good faith effort to obtain a return receipt or other transmission from the individual in response to receiving the notice.
< In an emergency treatment situation, provide the notice as soon as it is reasonably practicable to do so after the emergency situation has ended. In these situations, providers are not required to make a good faith effort to obtain a written acknowledgment from individuals.
< Make the latest notice (i.e., the one that reflects any changes in privacy policies) available at the provider’s office or facility for individuals to request to take with them, and post it in a clear and prominent location at the facility.
C A covered entity may e-mail the notice to an individual if the individual agrees to receive an electronic notice.
See 45 CFR 164.520(c) for the specific requirements for providing the notice. Organizational Options.
C Any covered entity, including a hybrid entity or an affiliated covered entity, may choose to develop more than one notice, such as when an entity performs different types of covered functions (i.e., the functions that make it a health plan, a health care provider, or a health care clearinghouse) and there are variations in its privacy practices among these covered functions. Covered entities are encouraged to provide individuals with the most specific notice possible.
C Covered entities that participate in an organized health care arrangement may choose to produce a single, joint notice if certain requirements are met. For example, the joint notice must describe the covered entities and the service
delivery sites to which it applies. If any one of the participating covered entities provides the joint notice to an individual, the notice distribution requirement with respect to that individual is met for all of the covered entities. See 45 CFR 164.520(d).
Frequently Asked Questions
To see Privacy Rule FAQs, click the desired link below:
FAQs on Notice of Privacy Practices
FAQs on ALL Privacy Rule Topics
(You can also go to http://answers.hhs.gov/cgi-bin/hhs.cfg/php/enduser/std_alp.php, then select “Privacy of Health Information/HIPAA” from the Category drop down list and click the Search button.)