Warning: Use of undefined constant curid - assumed 'curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 3

Warning: Use of undefined constant r_curid - assumed 'r_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 29

Warning: Use of undefined constant v_curid - assumed 'v_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 61

Warning: Use of undefined constant f_cur - assumed 'f_cur' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 102

Warning: Use of undefined constant p_curid - assumed 'p_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 118

Warning: Use of undefined constant mp_curid - assumed 'mp_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 152

Warning: Use of undefined constant mps_curid - assumed 'mps_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 226

Warning: Use of undefined constant e_curid - assumed 'e_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 244

Warning: Use of undefined constant up_curid - assumed 'up_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 270

Warning: Use of undefined constant fq_curid - assumed 'fq_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 292

Warning: Use of undefined constant pp_curid - assumed 'pp_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 347

Warning: Use of undefined constant i_curid - assumed 'i_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 355

Warning: Use of undefined constant ln_curid - assumed 'ln_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 368

Warning: Use of undefined constant rsp_curid - assumed 'rsp_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 384

Warning: Use of undefined constant ie_curid - assumed 'ie_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 428

Warning: Use of undefined constant im_curid - assumed 'im_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 442

Warning: Use of undefined constant imp_curid - assumed 'imp_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 476

Warning: Use of undefined constant ic_curid - assumed 'ic_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 512

Warning: Use of undefined constant imkt_curid - assumed 'imkt_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 524

Warning: Use of undefined constant a_curid - assumed 'a_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 536

Warning: Use of undefined constant am_curid - assumed 'am_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 550

Warning: Use of undefined constant ast_curid - assumed 'ast_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 576

Warning: Use of undefined constant ac_curid - assumed 'ac_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 588

Warning: Use of undefined constant amkt_curid - assumed 'amkt_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 600

Warning: Use of undefined constant mng_curid - assumed 'mng_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 614

Warning: Use of undefined constant pet_curid - assumed 'pet_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 678

Warning: Use of undefined constant peta_curid - assumed 'peta_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 697

Warning: Use of undefined constant pnav_curid - assumed 'pnav_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 751

Warning: Use of undefined constant alert_curid - assumed 'alert_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 764

Warning: Use of undefined constant fam_curid - assumed 'fam_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 774

Warning: Use of undefined constant mntl_curid - assumed 'mntl_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 800

Warning: Use of undefined constant diag_curid - assumed 'diag_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 838

Warning: Use of undefined constant sp_curid - assumed 'sp_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 870

Warning: Use of undefined constant xr_curid - assumed 'xr_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 884

Warning: Use of undefined constant agree_curid - assumed 'agree_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 902

Warning: Use of undefined constant butt_curid - assumed 'butt_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/includes/pgVars.php on line 920

Warning: Use of undefined constant fq_curid - assumed 'fq_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/v-faqs.php on line 8
FAQs for Emergency Contact Data

    Frequently Asked Questions (FAQs)


    • Warning: Use of undefined constant fq_curid - assumed 'fq_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/v-faqs.php on line 134

      Warning: Use of undefined constant fq_curid - assumed 'fq_curid' (this will throw an Error in a future version of PHP) in /home/nba7b25/public_html/v-faqs.php on line 134

      HIPAA Disclaimer

      Health Insurance Portability & Accountability Act (HIPAA) of 1996

      Please refer to Individuals’ Right under HIPAA to Access their Health Information 45 CFR ยง 164.524 at http://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/. “Providing individuals with easy access to their health information empowers them to be more in control of decisions regarding their health and well-being.”

      HIPAA governance only applies to three types of Covered Entities:

      • Healthcare providers who transmit any health information electronically in connection with certain transactions
      • Health plans
      • Healthcare clearinghouses are public or private entities, including a billing services, re-pricing companies, community health management information systems or community health information systems, and “value-added” networks and switches, that does either of the following functions:
        1. Processes or facilitates the processing of health information received from another entity in a nonstandard format or containing nonstandard data content into standard data elements or a standard transaction.
        2. Receives a standard transaction from another entity and processes or facilitates the processing of health information into nonstandard format or nonstandard data content for the receiving entity.

      Emergency Contact Data does not meet the legal / government definition of any of the above Covered Entities. Nor does Emergency Contact Data sell or manage, collect or process any payment(s) relative to any type of healthcare and / or insurance plan.

      Health Insurance Portability & Accountability Act (HIPAA) of 1996; Disclaimer

      Individuals and businesses are encouraged to review the Health Insurance Portability and Accountability Act (HIPAA) that was passed by Congress in 1996.

      HIPAA Privacy Rule

      The United States Department of Health and Human Services (HHS) published a final Privacy Rule in December 2000, which was later modified in August 2002. This Rule set national standards for the protection of individually identifiable health information by three types of COVERED ENTITIES: health plans, health care clearinghouses, and health care providers who conduct the standard health care transactions electronically.

      Emergency Contact Data is not one of the three types of COVERED ENTITIES and is therefore exempt from and not governed by the HIPAA Privacy Rule.

      Protected Health Information (PHI)

      To understand the possible impact of the Privacy Rule on their work, researchers will need to understand what individually, identifiable health information is and is not protected under the Rule. With certain exceptions, the Privacy Rule protects a certain type of individually identifiable health information, created or maintained by COVERED ENTITIES and their business associates acting for the covered entity. This information is known as “protected health information” or PHI.

      • The key to understanding what HIPAA governs is to be clear on the definition of a COVERED ENTITY and the definition of PHI. For information to be PHI it has to be created or maintained by one of the three COVERED ENTITIES. Emergency Contact Data does not create or maintain the information that an individual posts to his account. The individual posts and stores non-PHI information in his account that he manages and controls. Neither the Emergency Contact Data Member nor Emergency Contact Data creates, stores or possesses PHI.
      • The information provided to Emergency Contact Data is owned by an adult who voluntarily posts information to his own account controlled by himself. The posting party voluntarily accesses the blank, Emergency Contact Data templates that he chooses to use. Emergency Contact Data does not direct the posting party to post any information. All information posted to Emergency Contact Data is voluntary. The ownership and management of the information is never transferred to Emergency Contact Data. The information is managed by the Emergency Contact Data member in accordance with the Emergency Contact Data Membership Agreement, which is read and electronically acknowledged prior to an adult becoming an Emergency Contact Data member. The individual entering the information is not a COVERED ENTITY that is governed by the HIPAA Privacy Rule and the information is not Protected Health Information (PHI) and Emergency Contact Data is not a COVERED ENTITY governed by HIPAA.
      • Note: Think of Emergency Contact Data as a blank, paper form for organizing one’s medical history. In this case, the potential Emergency Contact Data member requests and uses the form provided by Emergency Contact Data. The form is provided by Emergency Contact Data. The individual voluntarily creates his or her medical history on the form and then places the form in his account for future utility. The individual creates and / or maintains his information. What the individual does with form and the information is totally under the purview of the individual.

      The Privacy Rule defines PHI as individually identifiable health information, held or maintained by a COVERED ENTITY or its business associates acting for the COVERED ENTITY that is transmitted or maintained in any form or medium (including the individually identifiable health information of non-U.S. citizens). Neither the individual nor Emergency Contact Data is a covered entity.

      Information Management

      Emergency Contact Data is a system of blank templates that an individual will voluntarily post information to. The posted information is known and controlled by the individual. Emergency Contact Data is similar to a paper note an individual would carry in their wallet or purse that has information like their blood type on it that an individual wishes to be known in case of a medical event.

      Emergency Contact Data does not enter or manage the information within an individual’s profile or cause the information to be accessed or transmitted. The individual Emergency Contact Data member is storing his or her information on the templates within their private Emergency Contact Data account. The individual’s information has never left the control of the individual; therefore the individual creates the information, stores the information in his account and then provides his own access points to his own information. The individual causes the information to be accessed and used to manage his or her care.

      Emergency Contact Data Notifications to Medical Personnel

      The note below is the first thing first responders or ER personnel see when visiting the Emergency Contact Data page that will display the member’s data.

      Note to Emergency Responder: A person’s legally protected right to create and publicize their own health data is not subject to HIPAA and PHI guidelines. This individual or this individual’s guardian entered the information presented in their Emergency Profile for its use in treatment rendered by first responders.
      By way of agreement with Emergency Contact Data, this individual or this individual’s guardian gives their permission for the use of this data. This website acts only to facilitate the presentation of information by its enrollees who have sole responsibility for the accuracy of posted information. In the Terms and Conditions Agreement we include HIPAA release language that covers Emergency Contact Data relative to HIPAA governance.

      In Summary the Emergency Contact Data member agrees to have his / her information stored and displayed via the terms of the Membership Agreement. Since Emergency Contact Data only stores information that belongs to an individual, the storage nor the facilitation of data is governed by the HIPAA Privacy Rule, as neither Emergency Contact Data nor the individual is a COVERED ENTITY governed by HIPAA.

      HIPAA does not control or limit an individual’s right as to what an individual can or cannot do with information that is owned and controlled by the individual. If HIPAA could govern what the individual does with his / her own, medical knowledge about himself an individual could not wear a diabetic bracelet or carry a piece of paper in their wallet that displays their blood type. The Emergency Contact Data members are exercising their freedom of speech right under the First Amendment to the Constitution.

      Is speech on the Internet entitled to as much protection as speech in more traditional media?
      Yes, the U.S. Supreme Court ruled in Reno v. ACLU (1997) that speech on the Internet receives the highest level of First Amendment protection. The Supreme Court explained that “our cases provide no basis for qualifying the level of First Amendment scrutiny that should be applied to this medium.”