HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## Requirements: TI.6 Business Rules Management (Function)

Page standards status: Informative

Statement N:

Manage the ability to create, update, delete, view, and version business rules including institutional preferences. Apply business rules from necessary points within a PHR-S to control system behavior. A PHR-S audits changes made to business rules, as well as compliance to and overrides of applied business rules.

Description I:

PHR-S business rule implementation functions include decision support, diagnostic support, workflow control, and access privileges, as well as system and user defaults and preferences. A PHR-S supports the ability of providers and institutions to customize decision support components such as triggers, rules, or algorithms, as well as the wording of alerts and advice to meet realm specific requirements and preferences.

Actors:
ehr Criteria N:

TI.6#01 | SHALL | The system SHALL provide the ability to manage business rules.
TI.6#02 | SHOULD | The system SHOULD provide the ability to enter, import, or receive business rules to guide system behavior.
TI.6#03 | SHOULD | The system SHOULD provide the ability to maintain business rules and their components.
TI.6#04 | dependent SHOULD | The system SHOULD provide the ability to tag decision support rules as inactive / obsolete or to remove them according to scope of practice, organizational policy, and/or jurisdictional law.
TI.6#05 | SHOULD | The system SHOULD provide the ability to render business rules.
TI.6#06 | dependent SHOULD | The system SHOULD provide the ability to manage diagnostic decision support rules that guide system behavior according to scope of practice, organizational policy, and/or jurisdictional law.
TI.6#07 | dependent SHOULD | The system SHOULD provide the ability to manage workflow control rules that guide system behavior according to scope of practice, organizational policy, and/or jurisdictional law.
TI.6#08 | dependent SHOULD | The system SHOULD provide the ability to manage access privilege rules that guide system behavior according to scope of practice, organizational policy, and/or jurisdictional law.
TI.6#09 | dependent SHOULD | The system SHOULD provide the ability to manage other rules (for example, monitoring rules, user defaults rules and preferences rule) that guide system behavior according to scope of practice, organizational policy, and/or jurisdictional law.
TI.6#10 | SHALL | The system SHALL provide the ability to determine system behavior based upon defined business rules.