Personal health record

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

A personal health record, or PHR, is a health record where health data and information related to the care of a patient is maintained by the patient.[1] This stands in contrast to the more widely used electronic medical record, which is operated by institutions (such as hospitals) and contains data entered by clinicians or billing data to support insurance claims. The intention of a PHR is to provide a complete and accurate summary of an individual's medical history which is accessible online. The health data on a PHR might include patient-reported outcome data, lab results, data from devices such as wireless electronic weighing scales or collected passively from a smartphone.

Definition

The term “personal health record” is not new. The earliest mention of the term was in an article indexed by PubMed dated June 1978,[2] and even earlier in 1956 reference is made to a personal health log.[3] However, most scientific articles written about PHRs have been published since 2000.

The term "PHR" has been applied to both paper-based and computerized systems; current usage usually implies an electronic application used to collect and store health data. In recent years, several formal definitions of the term have been proposed by various organizations.[4][5][6]

It is important to note that PHRs are not the same as electronic health records (EHRs). The latter are software systems designed for use by health care providers. Like the data recorded in paper-based medical records, the data in EHRs are legally mandated notes on the care provided by clinicians to patients. There is no legal mandate that compels a consumer or patient to store her personal health information in a PHR.

PHRs can contain a diverse range of data, including but not limited to:

There are two methods by which data can arrive in a PHR.[1] A patient may enter it directly, either by typing into fields or uploading/transmitting data from a file or another website. The second is when the PHR is tethered to an electronic health record, which automatically updates the PHR. Not all PHRs have the same capabilities, and individual PHRs may support one or all of these methods.[1]

In addition to storing an individual's personal health information, some PHRs provide added-value services such as drug-drug interaction checking, electronic messaging between patients and providers, managing appointments, and reminders.[7]

Benefits

PHRs grant patients access to a wide range of health information sources, best medical practices and health knowledge. All of an individual’s medical records are stored in one place instead of paper-based files in various doctors’ offices. Upon encountering a medical condition, a patient’s health information is only a few clicks away.

Moreover, PHRs can benefit clinicians. PHRs offer patients the opportunity to submit their data to their clinicians' EHRs. This helps clinicians make better treatment decisions by providing more continuous data.[1]

PHRs have the potential to help analyze an individual’s health profile and identify health threats and improvement opportunities based on an analysis of drug interaction, current best medical practices, gaps in current medical care plans, and identification of medical errors. Patient illnesses can be tracked in conjunction with healthcare providers and early interventions can be promoted upon encountering deviation of health status. PHRs also make it easier for clinicians to care for their patients by facilitating continuous communication as opposed to episodic. Eliminating communication barriers and allowing documentation flow between patients and clinicians in a timely fashion can save time consumed by face-to-face meetings and telephone communication. Improved communication can also ease the process for patients and caregivers to ask questions, to set up appointments, to request refills and referrals, and to report problems. Additionally, in the case of an emergency a PHR can quickly provide critical information to proper diagnosis or treatment.

Architecture

Like other health information technology, PHR architecture of has three main components:

Data
The information collected, stored, analyzed, and exchanged by the PHR.
Examples: medical history, laboratory results, imaging studies, medications
Infrastructure
The platform that handles data storage, processing, and exchange.
Examples: stand-alone software programs or websites, provider- or payer-connected (tethered) websites
Applications
The information exchange, data analysis, and content delivery capabilities of the system.
Examples: scheduling appointments, medication refill or renewal, decision aids, and patient education materials.[8]

Various architectural models have different costs and benefits. Likewise, stand-alone, provider-tethered, and payer-tethered PHRs have different advantages and disadvantages for patients related to their individual circumstances. Such differences are among the priority areas in PHR research.[8] As PHRs may play key role in advancing health information exchange, interoperability with other health IT systems is an important consideration for PHR architecture.[8] If PHRs serve only as a repository for an individual’s health information, it is unlikely that individuals who are not highly motivated will maintain their health records and find PHRs to be useful.[citation needed]

Delivery platforms

One of the principal distinguishing features of a PHR is the platform by which it is delivered. The types of platforms include: paper, electronic device, and web.

Paper

Personal health information is recorded and stored in paper format. Printed laboratory reports, copies of clinic notes, and health histories created by the individual may be parts of a paper-based PHR. This method is low cost, reliable, and accessible without the need for a computer or any other hardware. Probably the most successful paper PHR is the hand-held pregnancy record, developed in Milton Keynes in the mid-1980s[9] and now in use throughout the United Kingdom. These include the Scottish Woman-Held Maternity Record,[10] All Wales Maternity Record,[11] and Perinatal Institute notes.[12]

Paper-based PHRs may be difficult to locate, update, and share with others. Paper-based PHRs are subject to physical loss and damage, such as can occur during a natural disaster. Paper records can also be printed from most electronic PHRs. However, Fawdry et al. have shown that paper records are extremely flexible and do have distinct advantages over rigid electronic systems.[13]

Electronic devices

Personal health information is recorded and stored in personal computer-based software that may have the capability to print, backup, encrypt, and import data from other sources such as a hospital laboratory. The most basic form of a PC-based PHR would be a health history created in a word-processing program. The health history created in this way can be printed, copied, and shared with anyone with a compatible word processor.

PHR software can provide more sophisticated features such as data encryption, data importation, and data sharing with health care providers. Some PHR products allow the copying of health records to a mass-storage device such as a CD-ROM, DVD, smart card,[14] or USB flash drive.[15][16]

PC-based PHRs are subject to physical loss and damage of the personal computer and the data that it contains. Some other methods of device solution may entail cards with embedded chips containing health information that may or may not be linked to a personal computer application or a web solution.

Web applications

Web-based PHR solutions are essentially the same as electronic device PHR solutions, however, web-based solutions have the advantage of being easily integrated with other services. For example, some solutions allow for import of medical data from external sources. Solutions including HealthVault, and PatientsLikeMe allow for data to be shared with other applications or specific people. Mobile solutions often integrate themselves with web solutions and use the web-based solution as the platform.

A large number of companies have emerged to provide consumers the opportunity to develop online PHRs. Some have been developed by non-profit organizations, while others have been developed by commercial ventures. These web-based applications allow users to directly enter their information such as diagnosis, medications, laboratory tests, immunizations and other data associated with their health. They generate records that can be displayed for review or transmitted to authorized receivers.

Despite the need for PHRs and the availability of various online PHR providers, there has not been wide adoption of PHR services. In fact, Google, being among the most innovative companies in the world, discontinued its PHR service called Google Health on January 12, 2012. The reason cited for shutting down Google Health was that the service did not translate from its limited usage into widespread usage in the daily health routines of millions of people.[17]

An emerging standard from HL7, Fast Healthcare Interoperability Resources (FHIR), is designed to make it easier for developers of personal health record applications to access relevant medical records.[18]

EHRs, PHRs, patient portals and UHRs

The terms electronic health records, personal health records, and patient portals are not always used correctly. The generally agreed upon definition of these terms relates mainly to the ownership of the data. Once data is in a PHR it usually owned and controlled by the patient. Most EHRs, however, are the property of the provider, although the content can be co-created by both the provider and patient. A patient has a legal right in most states to request their healthcare data and under recent USA legislation those providers using a certified EHR will be required to provide an electronic copy as well. In the UK, according to the governments's information strategy for the NHS every primary care practice in England will have to offer patients online access to their care records by 2015.[19] In 2012, only 1% did so.[20] Electronic health records and electronic medical records contain clinical data created by and for health professionals in the course of providing care. The data is about the patient but the data resides in a health care provider's system. The patient portal is typically defined as a view into the electronic medical records. In addition, ancillary functions that support a health care provider's interaction with a patient are also found in those systems e.g. prescription refill requests, appointment requests, electronic case management, etc. Finally, PHRs are data that resides with the patient, in a system of the patient's choosing. This data may have been exported directly from an EMR, but the point is it now resides in a location of the patient's choosing. Access to that information is controlled entirely by the patient.

A new concept being discussed is the UHR or "universal health record",[21] which would be a patient-centered and patient-controlled body of information that could be shared in a granular way with particular health care providers at the patient's discretion in support of the patient's work with health care providers. This project would enlist open source contributions and enhancements from developers, with particular emphasis on supporting patient expectations of privacy and responsible patient control of private health information (PHI). It is anticipated that effective implementation of one or more "open source" approaches to the UHR would benefit both providers and patients, including providing more cost-effective solutions to currently difficult problems including entry/verification/update of personal health data, enabling responsible patient-controlled granular release of PHI, and supporting interoperability and effective collaboration of patients and physicians across disparate EHR/PHR platforms.[citation needed]

While PHRs can help patients keep track of their personal health information, the value of PHRs to healthcare organizations is still unclear.[22]

In public health

PHRs have the ability to benefit the public health sector by providing health monitoring, outbreak monitoring, empowerment, linking to services, and research. PHRs can give consumers the potential to play a large role in protecting and promoting the public's health.[23]

Barriers to adoption

Barriers to the adoption of PHRs include economic, technological, behavioral, and organizational issues, and barriers exist at both the environmental and individual levels.[1] Limited access to computers and Internet access among low-income populations, known as the digital divide, is one such barrier.[24]

Functional limitations

Despite the need to centralize patient information, PHR adoption has been very low. A study was carried out in an effort to assess the functionality and utility of online PHRs. An abstraction from real-life case of a patient suffering from a thyroid condition was utilized to create various online PHRs. The outputs generated were examined for accuracy and completeness of clinical information. A team of researchers identified 19 websites offering different versions of PHRs. To evaluate the PHRs, researchers identified criteria based on their promotional advertisements. Ideally, centralized PHRs should help patients relate accurate history during clinical encounters, check for drug interactions, eliminate unnecessary duplication of laboratory tests and diagnostic studies, and serve as an information hub for patients’ health management.[25] An analysis of web-based PHR applications showed that most websites did provide access to personal medical information, however each demonstrated limited capacity in a different way:

From the 19 sites examined, four were found to be specific to certain diseases only and were therefore excluded from the study. Another four were excluded for reasons such as recurrent technical problems or connections to a specific hospital’s information system. The remaining 11 sites did not provide patients with sufficient guidance as to how they should enter personal data. Some of the sites allowed patients to select medical conditions from categorized lists which did not cover the patients’ complete health condition while others allowed free text entry. To formulate medication history, sites that required patients to choose medication from lists requested them to enter a wide range of descriptive information for each medication such as prescribed dose, administration frequency, start date, name of pharmacy that issued the medication and name of provider that prescribed the medication. With respect to laboratory tests, only two allowed patients to import results from outside sources. From these two sites, only one was functional. Not every site allowed patients to enter insurance coverage information. Majority of the sites required patients to enter date and results of diagnostic tests.[25]

Most people do not keep record of minute details of their healthcare experiences and therefore find it difficult to make use of web-based PHRs. Overall, the sites selected for evaluation offered limited functionality to the general public. Low adoption of web-based PHRs can be a direct result of limitations in these applications’ data entry, validation and information display methods. PHR development should be guided by ample patient-oriented research in future.

Promotion

There are instances where the use of a PHR would be beneficial to patients and may, therefore, override privacy concerns. Stage 1 of meaningful use of certified EHR systems requires that practices provide at least 50 percent of their patients with a copy of their health records upon request. While this can be accomplished through a patient portal, this function can also be part of a larger system such as Kaiser Permanente's My Health Manager—a PHR that is integrated into the health system's patient portal. By June 2012, 3.9 million Kaiser members were enrolled in this program. For the first half of 2012, members viewed 2.5 million lab results, sent 1 million e-mails to physicians, and scheduled 230,000 appointments monthly, demonstrating ease of use and convenience.[26]

Privacy and security

One of the most controversial issues for PHRs is how the technology could threaten the privacy of patient information. Network computer break-ins are becoming more common,[27] thus storing medical information online can cause fear of the exposure of health information to unauthorized individuals. In addition to height, weight, blood pressure and other quantitative information about a patient's physical body, medical records can reveal very sensitive information, including fertility, surgical procedures, emotional and psychological disorders, and diseases, etc. Various threats exist to patient information confidentiality, some of which are listed below:

  • Accidental disclosure: During multiple electronic transfers of data to various entities, medical personnel can make innocent mistakes to cause disclosure of data.
  • Insider curiosity: Medical personnel may misuse their access to patient information out of curiosity or for another purpose.
  • Insider subordination: Medical personnel may leak out personal medical information for spite, profit, revenge, or other purposes.
  • Uncontrolled secondary usage: Those who are granted access to patient information solely for the purpose of supporting primary care can exploit that permission for reasons not listed in the contract, such as research.
  • Outsider intrusion: Former employees, network intruders, hackers, or others may access information, damage systems or disrupt operations

Unlike paper-based records that require manual control, digital health records are secured by technological tools.[28] identifies three general classes of technological interventions that can improve system security:

  • Deterrents – These depend on the ethical behavior of people and include controls such as alerts, reminders, and education of users. Another useful form of deterrents has been Audit Trails. The system records identity, times, and circumstances of users accessing information. If system users are aware of such a record keeping system, it will discourage them from taking ethically inappropriate actions
  • Technological obstacles – These directly control the ability of a user to access information and ensure that users only access information they need to know according to their job requirements. Examples of technological obstacles include authorization, authentication, encryption, firewalls, and more.
  • System management precautions – This involves proactively examining the information system to ensure that known sources of vulnerability are eliminated. Examples of this would be the use of encryption or installing antivirus software in the system

Information security concerns surrounding PHRs extend beyond technological issues. There are also ethical issues affecting the transfer of personally identifiable information in the treatment process. Only gradually are architectural requirements and information use policies becoming available such as the Privacy Rule under the U.S. Health Insurance Portability and Accountability Act (HIPAA).

See also

References

  1. 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  4. Connecting for Health. The Personal Health Working Group Final Report. July 1, 2003.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. UK Department of Health (1993). Changing Childbirth. Part II: Survey of good communications practice in maternity services, pp25-26. London: HMSO. ISBN 0-11-321623-8
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. "Healthcare Data Breaches Growing More Frequent, Highlighting Need For Strong Authentication", press release, Sept. 24, 2014, Entrust,
  28. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

Lua error in package.lua at line 80: module 'strict' not found.

Books

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.

Journal Articles

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  4. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  14. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  15. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  27. Lua error in package.lua at line 80: module 'strict' not found. open access publication - free to read
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lafky DB, Tulu B, Horan TA. A user-driven approach to personal health records. Communications of the Association for Information Systems. Jun 2006. 17(46).
  31. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  34. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found. open access publication - free to read
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.

Conference Proceedings

  1. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  2. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  3. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  4. Lua error in package.lua at line 80: module 'strict' not found.

Other

  1. America’s Health Insurance Plans. Consumer and provider focus groups on PHR. Unpublished. Jan 2005.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Canedy JT. SimplyWell PHR. AHIC Consumer Empowerment Workgroup Meeting 7/23/06. Jul 2006.
  5. Connecting for Health. Connecting Americans to Their Health Care: A Common Framework for Networked Personal Health Information. Dec 2006.
  6. Detmer D, Steen E. Learning from abroad: lessons and questions on personal health records for national policy. AARP. Mar 2006.
  7. Haslmaier EF. Health care information technology – getting the policy right. Web Memo – Heritage Foundation. Jun 2006. No. 1131.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Skewes JL. Shared Health, Inc. AHIC Consumer Empowerment Workgroup Meeting 7/23/06. Jul 2006.
  10. The benefits of an internet-based personal health record versus a paper-based personal health record is expected to grow rapidly within the next three years. See interview with CEO, Glen Tullman of Allscripts http://www.ehrtv.com/allscripts-glen-tullman-mar-2010/

External links