Question

1.15 Patient-generated health data Subdomain L.E.1 Validate data from secondary sources including personal health records sources to include in the patient's record eh Ci The physician you work for is concerned about incorporating patient gen erated health data employs into his EHR. Help him design a policy that not only addresses his concerns biu sound data stewardship principles as well. 1. For the purpose of this exercise,formulate a list of the topics that should be covered 2. Create a policy. References AHIMA. 2015. Including Patient-Generated Health Data in Electronic Health Records. Journal of AHIMA 86(2): 54-57 LeBlanc, M.M. Human Resources Management. Chapter 23 in Health Information Management: Concepts, Principles, and Practice, 5th ed. Oachs, P. and A. Watters, eds, Chicago: AHIMA

Answer 1

*The physician who works for is concerned about incorporating patient-generated health data into his EHR.Help him design a policy that not only addresses his concerns but employs sound data stewardship principle as well?

Patient-generated health data (PGHD) are health-related data created, recorded, or gathered by or from patients (or family members or other caregivers) to help address a health concern.

PGHD is health data produced by the patient and can include data from mHealth apps, wearable devices, and other remote patient monitoring systems. PGHD can also include patient and family health histories and other data patients can recall and enter into the patient portal.

Test Method : (2015 Edition)

The Test Method provides the structure for evaluating conformance of the Health IT Module to the certification criteria defined in 45 CFR Part 170 Subpart II of the 2015 Edition Health Information Technology (Health IT) Certification Criteria, 2015 Edition Base Electronic Health Record (EHR) Definition, and ONC Health IT Certification Program Modifications final rule as published in the Federal Register on October 16, 2015. The 2015 Edition Test Method includes Test Procedures, Test Tools and Test Data and is listed below by certification criterion number.

Test Procedures

The test procedures offer objective guidance to ONC-Authorized Testing Laboratories (ONC-ATLs) as they conduct Health IT module testing in the Program, to provide traceability from the certification criterion or criteria to testing activities, and to ensure consistency throughout the certification process. The new Test Procedures format includes a grid of testing components that the ONC-ATLs would use as the test approach for that particular criterion.

*Gap: Indicates that a Health IT module is eligible to receive gap certification if previously certified to the 2014 Edition criterion.

* Documentation: is an approved method to demonstrate conformance. This may include documents from the health IT developer or third-party that demonstrate/attest to the compliance with the criterion.

*Visual inspection: is an approved method to demonstrate conformance. Most commonly, this will be accomplished via a live demonstration of functionality that meets the criterion.

* Test tools: exists and must be used to test a portion or all of a Health IT Module’s conformance to the criterion.

*ONC supplied Test data: Indicates that test data supplied by ONC or as required by the tool(s) must be used during the test.

The topics that should be covered are :

-Computerized provider order entry (CPOE) – medications

-Computerized provider order entry (CPOE) – laboratory

-Computerized provider order entry (CPOE) – diagnostic imaging

-Drug-drug, drug-allergy interaction checks for CPOE

-Demographics

-Problem list

-Medication list

-Medication allergy list

-Clinical decision support (CDS)

-Drug-formulary and preferred drug list checks

-Smoking status

-Family health history

-Patient-specific education resources

-Implantable device list

-Social, psychological, and behavioral data

-Transitions of care

-Clinical information reconciliation and incorporation

Electronic prescribing

Policy:

Benefits to PGHD use and EHR storage include more efficient and accurate diagnoses, patient-centered care, meaningful chronic care management, and reductions in repetitious lab testing.

PGHD embedded in the EHR can also show providers patient wellness status between visits, illustrate patient health and behavior trends over a broad time period, improve patient medication safety, and inform patient-provider communication centered on shared decision-making.

The patient portal, a key part of the EHR technology suite, is essential for PGHD use because it allows patients to upload or modify their own data.

Despite the promise of patient-generated health data, its use is not widespread, the Playbook revealed. Forty percent of smartphone or tablet owners use their devices to track progress on health and wellness goals, and 30 percent use a wearable device such as a fitness tracker or glucose monitor.

PGHD use begins with practice administrators, the Playbook suggested. Administrators should start by discussing with staff how PGHD can improve patient care and practice efficiency.

Next, organization leaders should evaluate what data they are already gathering and what data could be valuable. What provides insights about one patient population may not be relevant to another population, and organizations must be cognization of that.

Organization leaders should next create policies for gathering and reviewing PGHD. Although PGHD can offer valuable insights, it is not usable until expert vets the information.

Finally, organizations must educate patients and family caregivers about the importance of PGHD to motivate them to continue sharing this data.

The Playbook authors recommended organizations start small and make it easy for patients to share their own health data.

The expectations should be set between patients, providers, and other relevant stakeholders (e.g., administrators, reimbursing agencies, and technology vendors) from the very beginning of the process – including identifying and reconciling differences in those expectations. Transparency in this process may be an approach to avoid frustration and confusion. Goals for collecting and using PGHD need to be explicit.

Before implementing a tool, technology vendors are advised to follow best practices for engaging patients and providers in specifying system requirements for flexibility, standardization, visualizations, messaging, data summarization, and integration. Administrators can identify and seek to mitigate workflow barriers such as scheduling, role delegation, and scope of practice. Policymakers should analyze current incentive structures for patients and reimbursement for providers.