ONC HTI-1 / HTI-2
ONC certification rules adding transparency and risk-management requirements to certified health IT, including AI/predictive DSI.
Definition
HTI-1 (final 2024) introduced the Decision Support Intervention criterion requiring source attributes and intervention risk management for predictive models in certified EHRs. HTI-2/HTI-3 extend transparency, interoperability, and information-blocking requirements. HTI-1 requires certified health IT developers that supply predictive decision support to give users access to source attributes, such as intended use, training data details and performance, and to apply risk management practices. It also set the USCDI v3 standard. HTI-2, finalized in parts in 2024, added public health and payer-related certification criteria. These rules apply to EHR and health IT developers, which can include MedTech companies selling software into hospitals.What this means in practice
Even non-EHR vendors are affected: model 'nutrition labels' are increasingly expected by HDOs procuring AI-enabled tools.Examples
- A developer integrating a diagnostic AI algorithm into a certified EHR must ensure the algorithm's training data, validation metrics, and known biases are clearly documented as source attributes.
- A hospital procuring an AI-powered clinical decision support system requests explicit documentation of its intervention risk management plan, demonstrating compliance with ONC HTI-1 requirements.
- A health IT vendor creates a mechanism within their EHR to display the source attributes of a predictive model whenever a clinician receives a decision support alert.
- •Misconception: These rules only apply to EHR vendors, but any developer whose software integrates with or provides data to certified EHRs may be indirectly affected.
- •A common pitfall is failing to adequately document the 'source attributes' of predictive models, which can lead to non-compliance during certification.
- •Overlooking the necessity of a robust intervention risk management plan for all decision support interventions is a frequent error.
- •Assuming that existing risk management processes are sufficient without specifically addressing the unique risks of AI-driven interventions can lead to gaps.
- •Failure to keep up with subsequent ONC rules, such as potential HTI-2 or HTI-3 updates, could lead to outdated compliance strategies.
Frequently asked questions
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsMore in Software & AI
· Same categoryAAMI Technical Information Report providing guidance on applying Agile software development practices within an IEC 62304-compliant medical device software lifecycle.
Resilience of an ML model to inputs deliberately crafted to cause misclassification.
Medical device that uses artificial intelligence or machine learning to perform its intended use.
Historical FDA AI/ML change-control terminology, now reflected in the PCCP Modification Protocol.
Where this term appears across MedTech Terms.
Latest in MedTech
Sources
3 sourcesSources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.
- 1ONC HTI-1Tier 2 VerifiedONChealthit.gov
- 2FDA - Software as a Medical Device (SaMD)Tier 2 VerifiedFDAfda.gov
- 3FDA - AI/ML-Enabled Medical DevicesTier 2 VerifiedFDAfda.gov
Inline markers like [1] jump to the matching reference above.