本技术报告定义了个人健康记录（PHR）。这一定义旨在帮助澄清 这类记录应被称为PHRs，因为该术语的定义缺乏一致性 目前正在使用。本技术报告从个人信息的角度考虑PHR 包含在it中，以及管理此信息所需的核心服务。 PHR不是单一实体；这个概念包括一系列可能的信息存储库 以及满足与定义一致的不同目的的服务。因此，本技术报告也 讨论了PHR的范围，即PHR可以通过的一系列维度 进行分类，并与同等PHR产品进行比较。它还包括一个维度来分类 医疗机构提供的协作护理PHR。 本技术报告还考虑了个人参与项目管理的更广泛背景 他们自己的健康和医疗保健，因为这种参与是目前的主要驱动力- PHR的日生长 国际系统和服务。 本技术报告包括: -PHR的定义； -短语的语用多维分类； -概述了个人参与管理工作的可能方式 健康和医疗保健对PHR潜在作用的影响，包括协作护理的场景 在个人和医疗机构之间。 可以实现并用于交付PHR系统功能的多种最终用户应用程序 不在本技术报告的范围内。

This Technical Report defines a personal health record (PHR). This definition is intended to help clarify the kinds of records that should be called PHRs, in recognition of the lack of consistency in how this term is presently used. This Technical Report considers the PHR from the perspective of the personal information contained within it and the core services needed to manage this information. A PHR is not a singular entity; the concept encompasses a spectrum of possible information repositories and services that meet different purposes consistent with the definition. This Technical Report therefore also discusses the scope of the PHR in terms of this spectrum as a series of dimensions by which a PHR may be classified and equivalent PHR products compared. It also includes one dimension to classify the kinds of collaborative care PHRs provided by healthcare organizations. This Technical Report also considers the wider context of engagement of individuals in the management of their own health and healthcare, since this engagement is the primary driver for present-day growth of PHR systems and services internationally. This Technical Report includes: — a definition of a PHR; — a pragmatic multidimensional classification of PHRs; — an overview of the possible ways in which the inclusion and engagement of individuals in managing their health and healthcare impacts on the potential roles of the PHR, including scenarios for collaborative care between individuals and healthcare organizations. The many kinds of end-user application that might be implemented and used to deliver PHR system functionality are outside the scope of this Technical Report.