Question · DSI Source Attributes
What are the 31 source attributes required for predictive DSI under HTI-1?
Certified EHRs must let users see plain-language source attributes for the decision support tools they supply: 13 for evidence-based tools and 31 for predictive (AI or other model-based) tools, covering purpose, training data, fairness, external validation, performance and ongoing monitoring.
01 / The answer
The short answer
They are 31 items in nine groups at 45 CFR 170.315(b)(11)(iv)(B) that certified health IT must support for each predictive decision support intervention the developer supplies: details and output (4), purpose (4), cautioned out-of-scope use (2), development details and input features (4), fairness approach (2), external validation (4), quantitative performance (5), ongoing maintenance and local monitoring (4), and update and revalidation schedule (2). They cover who built the model, what it outputs, its training data, fairness, validation and monitoring. HTI-5, proposed in December 2025, would delete them; it was not final as of October 2026.
02 / The rule
What DSI Source Attributes requires
Certified EHRs must let users see plain-language source attributes for the decision support tools they supply: 13 for evidence-based tools and 31 for predictive (AI or other model-based) tools, covering purpose, training data, fairness, external validation, performance and ongoing monitoring. It is the main US federal rule that forces disclosure of how a clinical prediction model was built and tested, though a pending proposal would remove it.
- 01Support all 31 source attributes for each predictive DSI and 13 for each evidence-based DSI the developer supplies.
- 02Give a limited set of identified users complete, up-to-date plain-language access to those attributes.
- 03Show when validation, local performance or update-schedule information is not available for a predictive DSI.
- 04Let identified users record, change and access source attributes, including extra attributes for predictive DSIs.
03 / Records
Records to keep
- 01Source attribute record for each supplied predictive and evidence-based DSI
- 02External validation and fairness test results by demographic group
- 03Intervention risk management analysis and mitigation log
- 04Dated review history showing attributes kept current
Optional evidence · where Planisphere fits
Keep a record anyone can check
When your team meets a duty, Planisphere can seal the event it reports as a receipt.
A disclosure shown, a review signed, a model change approved: the event your system reports.
The event becomes a sealed receipt, dated and attributed to whoever is signed in.
Paste the receipt into Verify. No account or key.
A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.
SOURCES
Go back to the source
Federal Register (ASTP/ONC)
RELATED
Related: DSI Source Attributes: the full guide · Do I have to keep HTI-1 source attributes updated, and how often?