Skip to main content

Advertisement

Log in

A standard-based model for the sharing of patient-generated health information with electronic health records

  • Original Article
  • Published:
Personal and Ubiquitous Computing Aims and scope Submit manuscript

Abstract

This paper proposes a standard-based model for the automated collection of patient data using personal health devices and the secure sharing of these data with authorized providers’ electronic health records (EHRs). The model addresses a number of important requirements for the practical collection and exchange of such data between patients and providers. The technical elements of the model are based on the features of personal health devices, health data repositories, and interoperability standards that already exist. For the automated collection of data from patients’ personal health devices (such as wireless glucometers or smartphone-based applications), the model suggests a set of content standards developed by the Continua Alliance and already implemented in a number of commercial products. For the sharing of collected data with providers’ EHRs, the model specifies a secure transport layer based on the DIRECT Project’s secure email standards and an application data layer based on HL7 v2.5.1 query-response messages combined with the clinical document architecture Release 2.0 personal healthcare monitoring report implementation guide. All of these standards have been implemented and are in current use, although they have not yet been combined to meet the specific use case of sharing patient-generated health information with providers EHRs. The proposed standard-based model constitutes a “straw man” intended to foster thought, discussions, and refinement through pilot implementations and improvements.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8

Similar content being viewed by others

Notes

  1. Because providers (and/or background processes acting on their behalf) initiate the retrieval of PGHI, providers can customize their data-retrieval patterns to match their organizational capabilities for evaluating and acting on the incoming data. As such, this model can accommodate a wide range of preferences regarding how often PGHI is retrieved and evaluated, from infrequent access (e.g., ad hoc querying of PGHI or retrieval of PGHI in preparation for a specific patient visit) to frequent automated “polling” for PGHI and rule-based processing of it such as an Accountable Care Organization might use for case management.

  2. Simple Mail Transport Protocol.

  3. Public Key Infrastructure (PKI) and S/MIME (Secure Multipurpose Internet Mail Extensions).

  4. For example, a number of vendors now offer web-based email programs that can send and receive DIRECT messages and attachments.

  5. Rather than immediately returning an error response when the patient has not already authorized the PGHI repository to respond to queries from the provider’s DIRECT address, an alternative approach would be for the PGHI repository to prompt the patient about whether the request should be granted at the time the request is received. In this variation, the PGHI repository would wait a predetermined amount of time before rejecting the request if the patient does not authorize it.

References

  1. Office of the National Coordinator for Health Information Technology, HIT Policy Committee (2012) Request for Comment Regarding the Stage 3 Definition of Meaningful Use of Electronic Health Records (EHRs). http://www.healthit.gov/sites/default/files/hitpc_stage3_rfc_final.pdf. Accessed June 11, 2014

  2. Brennan PF, Downs S, Casper G (2010) Project healthdesign: rethinking the power and potential of personal health records. J Biomed Inf 43(5):3–5. doi:10.1016/j.jbi.2010.09.001

    Article  Google Scholar 

  3. Project HealthDesign Estrellita (formerly FitBaby). http://www.projecthealthdesign.org/projects/current_projects/estrellita. Accessed June 11, 2014

  4. Microsoft Corporation (2013) HealthVault: How It Works. https://www.healthvault.com/us/en/howitworks. Accessed June 11, 2014

  5. Office of the National Coordinator for Health Information Technology (2012) Health Information Technology: Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology, 2014 Edition; Revisions to the Permanent Certification Program for Health Information Technology. 45 CFR Part 170 §314(b) and 202(a)

  6. IDEAL LIFE (2013) Products: Consumer-Inspired Products for Better Health & Wellness. http://www.ideallifeonline.com/products/. Accessed June 11, 2014

  7. TheCarrot.com (2013) TheCarrot.com: Track Your Life. http://thecarrot.com/. Accessed June 11, 2014

  8. Microsoft Corporation (2013) HealthVault: Apps & Devices. https://account.healthvault.com/us/en-US/Directory. Accessed June 11, 2014

  9. Continua Health Alliance (2013) About the Alliance.http://www.continuaalliance.org/about-continua. Accessed June 11, 2014

  10. Adams J (2011) Delivering Health Information across the Continua Architecture. http://www.hl7.org/events/ihic2011/papers/friday/F_Q2_1_IHL7IC_May2011_Adams_Final.pdf. Accessed June 11, 2014

  11. Various (2013) ISO/IEEE 11073 Personal Health Data (PHD) Standards. http://en.wikipedia.org/wiki/ISO/IEEE_11073_Personal_Health_Data_(PHD)_Standards. Accessed June 11, 2014

  12. Various (2013) ZigBee. http://en.wikipedia.org/wiki/ZigBee. Accessed June 11, 2014

  13. Continua Health Alliance (2013) Product Showcase. http://www.continuaalliance.org/products/product-showcase. Accessed June 11, 2014

  14. Integrating the Healthcare Enterprise (2013) IHE Technical Frameworks. http://www.ihe.net/Technical_Framework/index.cfm#pcd. Accessed June 11, 2014

  15. Office of the National Coordinator for Health Information Technology (2013) What is the Direct Project? http://www.healthit.gov/providers-professionals/faqs/what-direct-project. Accessed June 11, 2014

  16. The Direct Project (2010) The Direct Project Overview. http://wiki.directproject.org/file/view/DirectProjectOverview.pdf. Accessed June 11, 2014

  17. Madan U, Nolan S, Malec A (2012) Applicability Statement for Secure Health Transport, Version 1.1. http://wiki.directproject.org/file/view/Applicability%20Statement%20for%20Secure%20Health%20Transport%20v1.1.pdf/353270730/Applicability%20Statement%20for%20Secure%20Health%20Transport%20v1.1.pdf. Accessed June 11, 2014

  18. Malec A, Witting K, Petychev V, Tao D, Lewis V, Grantham B, Gunaratne C, Dragon (2011) XDR and XDM for Direct Messaging Specification. http://wiki.directproject.org/file/view/2011-03-09%20PDF%20-%20XDR%20and%20XDM%20for%20Direct%20Messaging%20Specification_FINAL.pdf. Accessed June 11, 2014

  19. DirectTrust.org (2013) DirectTrust.org Home Page. http://www.directtrust.org/. Accessed June 11, 2014

  20. Health Level 7 (HL7) (2007) HL7 Messaging Standard Version 2.5.1, Chapter 5: Query, Section 5.4.1. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=185. Accessed June 16, 2014

  21. Health Level 7 (HL7) (2010) HL7 Implementation Guide for CDA® R2-Personal Healthcare Monitoring Report. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=33. Accessed June 16, 2014

  22. Palme J, Hopman A, Shelness N (1999) Request for Comments (RFC) 2557: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML). Internet Engineering Task Force. http://www.ietf.org/rfc/rfc2557.txt. Accessed June 11, 2014

  23. Health Level 7 (HL7) (2007) HL7/ASTM Implementation Guide for CDA® R2-Continuity of Care Document (CCD®) Release 1. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=6. Accessed September 13, 2013

  24. Health Level 7 (HL7) (2013) HL7 Version 3 Standard: Infrastructure Management; Control Act, Query and Transmission, Release 1.1. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=293. Accessed September 13, 2013

  25. Health Level 7 (HL7) (2010) HL7 Clinical Document Architecture, Release 2 (reaffirmation of ANSI/HL7 CDA, R2-2005) 6/24/2010. Section 3: CDA Document Exchange in HL7 Messages

  26. Health Level 7 (HL7) (2012) HL7 Implementation Guide for CDA® Release 2: IHE Health Story Consolidation, Release 1.1—US Realm. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258. Accessed September 13, 2013

  27. Office of the National Coordinator for Health Information Technology (2012) Health Information Technology: Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology, 2014 Edition; Revisions to the Permanent Certification Program for Health Information Technology. 45 CFR Part 170 §205 and 299

Download references

Acknowledgments

This work was supported by a grant from the Robert Wood Johnson Foundation through Project HealthDesign (http://www.projecthealthdesign.org). We would like to thank the following individuals for their assistance in our research and preparation of this publication: Liora Alschuler, Lantana Group, Keith Boone, GE Healthcare, Patricia Brennan, University of Wisconsin School of Nursing and College of Engineering, Gail Casper, University of Wisconsin School of Nursing, Bob Dolin, Lantana Group, Steven Downs, Robert Wood Johnson Foundation, Igor Gejdos, Roche Diagnostics Corp., Gillian Hayes, University of California, Irvine, Sen Hirano, University of California, Irvine, Sean Nolan, Microsoft, Inc., Martin Rosner, Philips N.A. Corp., Steve Wheeler, IDEAL LIFE, Inc.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Walter Sujansky.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Sujansky, W., Kunz, D. A standard-based model for the sharing of patient-generated health information with electronic health records. Pers Ubiquit Comput 19, 9–25 (2015). https://doi.org/10.1007/s00779-014-0806-z

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00779-014-0806-z

Keywords

Navigation