Project HealthDesign - Rethinking the Power and Potential of Personal Health Records

Subscribe Contact Us Site Map Log In

 
Home
About Us
Round 2 Information
Round 1 Projects and Products
Common Platform
Blog ODL Wiki
Home > Common Platform Components - Functional Requirements

Printer Friendly VersionPrinter Friendly Version

 

 

 

Common Platform Components - Functional Requirements

Project HealthDesign (PHD) has worked with a team led by Walter Sujansky of Sujansky & Associates, LLC, along with the project’s nine grantees, to help develop a set of functional requirements and common platform components for PHR applications. The requirements were developed through an in-depth process of needs assessment interviews and analysis of work performed by the grantees in their design and prototyping efforts to date. Through this process, four target components were determined to be an essential subset of common functionality that is required for all of the application domains.

The requirements were derived from the needs of the nine PHD grantee applications, but given the diversity of the teams and their applications, the functional requirements should have broad application across the PHR field. They support functions common to many personal health applications: medication list management, calendaring, observations captured in the course of daily living, and identity management. The program expects the release of the functional requirements will complement and inform existing and future PHR development and related efforts, and that it will stimulate a broader discussion about the standardization and modularization of PHR platform services.

Project HealthDesign invites your comments and feedback below.  We are specifically interested in feedback that addresses the adequacy and form of the functionality with regard to existing, planned or envisioned PHR applications.

We’re particularly interested in comments that identify omissions or inconsistencies in the specifications when they are matched against a wide range of PHR application domains. We’re also looking for feedback on issues that may arise in the integration of PHR applications with sources of information importation or destinations of information transmission – provider information systems and a wide range of other technology platforms such as social networking infrastructures and search engine technologies.

Functional Requirements for PHRs
Click here to view the set of functional requirements and common platform components (pdf).


 

Please provide your comments and feedback in the form below. (all fields are required)
 

E-mail address 
Comments 

 

 

 
Robert Wood Johnson Foundation

HomeAbout Us | Round 2 Info | Round 1 Projects | Common Platform| Blog
Privacy Policy | Terms of Use | Subscribe | Contact Us | Site Map | Log In
Copyright 2010