Deprecated: Return type of DrupalCacheArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 362

Deprecated: Return type of DrupalCacheArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 369

Deprecated: Return type of DrupalCacheArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 381

Deprecated: Return type of DrupalCacheArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 388
University of Oklahoma Health Sciences Center

Patient-Generated General Health Data

×

Error message

  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 695 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 696 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 697 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 700 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 702 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 328 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 329 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 337 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 344 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_settings_initialize() (line 819 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_settings_initialize() (line 828 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: session_name(): Session name cannot be changed after headers have already been sent in drupal_settings_initialize() (line 831 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Deprecated function: Return type of DatabaseStatementBase::execute($args = [], $options = []) should either be compatible with PDOStatement::execute(?array $params = null): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2244 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).

Guide to Integrate Patient-Generated Digital Health Data into Electronic Health Records in Ambulatory Care Settings

Author/s: 
Agency for Healthcare Research and Quality

Effective use of PGHD in clinics poses many challenges, including clinician and patient burden, poor usability, workflow integration challenges, and the potential to make health inequities worse.

To promote the collection, integration, and use of PGHD in clinical care, AHRQ has developed a guide that has evidence-based, practical steps for implementation.

The guide is organized into six folios that help ambulatory care practices navigate the many steps from design, to launch, to maintenance of a successful, sustainable PGHD program.

Folio 1: Introduction – What Is PGHD and Why Is It Important?
Folio 2: Assessing Readiness for PGHD program Implementation
Folio 3: Assembling a Team to Manage Change
Folio 4: Making the Right PGHD and Information Technology Decisions for Your Practice
Folio 5: Evaluating the Costs of PGHD Implementation
Folio 6: Steps to Successfully Implement a PGHD Program

Subscribe to Patient-Generated General Health Data