References in Text
Section 300jj–12(b)(2)(B) of this title, referred to in subsec. (b)(1), related to areas of health information technology required to be considered by the HIT Policy Committee and was repealed by [Pub. L. 114–255, div. A, title IV, § 4003(e)(1)], Dec. 13, 2016, [130 Stat. 1168].
Amendments
2016—Subsec. (a)(2)(B). [Pub. L. 114–255, § 4003(e)(2)(A)(i)], substituted “HIT Advisory Committee” for “HIT Standards Committee”.
Subsec. (b)(3). [Pub. L. 114–255, § 4003(e)(2)(D)], substituted “300jj–12(b)(4)” for “300jj–13(b)(2)”.
Subsec. (c). [Pub. L. 114–255, § 4003(d)], added subsec. (c).
Leveraging Electronic Health Records To Improve Patient Care
[Pub. L. 114–255, div. A, title IV, § 4005], Dec. 13, 2016, [130 Stat. 1180], provided that:“(a)
Requirement Relating to Registries.—
“(1)
In general.—
To be certified in accordance with title XXX of the Public Health Service Act (
42 U.S.C. 300jj et seq.), electronic health records shall be capable of transmitting to, and where applicable, receiving and accepting data from, registries in accordance with standards recognized by the Office of the National Coordinator for Health Information Technology, including clinician-led clinical data registries, that are also certified to be technically capable of receiving and accepting from, and where applicable, transmitting data to certified electronic health record technology in accordance with such standards.
“(2)
Rule of construction.—
Nothing in this subsection shall be construed to require the certification of registries beyond the technical capability to exchange data in accordance with applicable recognized standards.
“(b)
Definition.—
For purposes of this Act [see Tables for classification], the term ‘clinician-led clinical data registry’ means a clinical data repository—
“(1)
that is established and operated by a clinician-led or controlled, tax-exempt (pursuant to section 501(c) of the Internal Revenue Code of 1986 [
26 U.S.C. 501(c)]), professional society or other similar clinician-led or -controlled organization, or such organization’s controlled affiliate, devoted to the care of a population defined by a particular disease, condition, exposure or therapy;
“(2)
that is designed to collect detailed, standardized data on an ongoing basis for medical procedures, services, or therapies for particular diseases, conditions, or exposures;
“(3)
that provides feedback to participants who submit reports to the repository;
“(4)
that meets standards for data quality including—
“(A)
systematically collecting clinical and other health care data, using standardized data elements and having procedures in place to verify the completeness and validity of those data; and
“(B)
being subject to regular data checks or audits to verify completeness and validity; and
“(5)
that provides ongoing participant training and support.
“(c)
Treatment of Health Information Technology Developers With Respect to Patient Safety Organizations.—
“(1)
In general.—
In applying part C of title IX of the Public Health Service Act (
42 U.S.C. 299b–21 et seq.), a health information technology developer shall be treated as a provider (as defined in section 921 of such Act [
42 U.S.C. 299b–21]) for purposes of reporting and conducting patient safety activities concerning improving clinical care through the use of health information technology that could result in improved patient safety, health care quality, or health care outcomes.
“(2)
Report.—
Not later than 4 years after the date of enactment of this Act [Dec. 13, 2016], the Secretary of Health and Human Services shall submit to the Committee on Health, Education, Labor, and Pensions of the Senate and the Committee on Energy and Commerce of the House of Representatives, a report concerning best practices and current trends voluntarily provided, without identifying individual providers or disclosing or using protected health information or individually identifiable information, by patient safety organizations to improve the integration of health information technology into clinical practice.”