HEART Deployment Profiles
A HEART Deployment Profile describes the bounded context in which verification occurs. It prevents a result for one system, version, function, population, or place from becoming a universal claim.
A Deployment Profile can identify
- the system, service, model, process, organization function, or claim;
- material versions and change boundaries;
- intended and reasonably foreseeable uses;
- location, jurisdiction, population, and affected persons;
- interfaces, modalities, autonomy, persistence, and human roles;
- data, providers, dependencies, and third parties;
- relevant Source and Domain Profiles;
- material exclusions and unresolved uncertainty; and
- surveillance, change, and expiry triggers.
Current status
The Deployment Profile family is current architecture. No individual deployment receives HEART status merely by publishing a Profile. Formal conformity requires the separate Scheme, authorized evaluation and decision, and current Registry status.