Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build
Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-01-31 |
| PH.3.5.4#01 | SHALL |
The system SHALL present the PHR Account Holder with reminders of scheduled events. |
| PH.3.5.4#02 | SHALL |
The system SHALL manage timely reminders from PHR Account Holder provider(s) to include notifications for services, tests or actions that are due or overdue. |
| PH.3.5.4#03 | SHOULD |
The system SHOULD provide the ability to capture a history of notifications. |
| PH.3.5.4#04 | MAY |
The system MAY provide the ability to manage the PHR Account Holder’s response(s) to notifications and/or reminders. |
| PH.3.5.4#05 | MAY |
The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding a notification and/or reminder. |
| PH.3.5.4#06 | MAY |
The system MAY provide the ability to transmit to the sender of a notification and/or reminder the PHR Account Holder's response to that notification and/or reminder. |
| PH.3.5.4#07 | SHOULD |
The system SHOULD provide the ability to track PHR Account Holder-configured notifications and/or reminders. |
| PH.3.5.4#08 | SHOULD |
The system SHOULD provide the ability to manage PHR Account Holder notifications and/or reminders based on configuration options (e.g., repetitions or timing of the activity). |
| PH.3.5.4#09 | MAY |
The system MAY provide the ability to present options for the PHR Account Holder to configure preferences for notifications and/or reminders (e.g., posting on the PHR summary screen, e-mail, or text messages to another e-mail account or device). |
| PH.3.5.4#10 | SHOULD |
The system SHOULD provide the ability to update the content of notifications, guidelines, reminders, and associated reference materials. |
| PH.3.5.4#11 | SHOULD |
The system SHOULD provide the ability to receive and update content of notifications, guidelines, reminders, and associated reference materials from the PHR Account Holder’s provider(s). |
| PH.3.5.4#12 | MAY |
The system MAY provide the ability to manage the lifecycle of the states of the notifications and/or reminders. |
| PH.3.5.4#13 | SHOULD |
The system SHOULD provide the ability to update the established criteria that trigger the reminders. |
| PH.3.5.4#14 | SHALL |
IF indications for specific preventive services and accompanying reminders were previously captured, THEN the system SHALL present reminders to the PHR Account Holder of all specific preventive services (e.g., a follow up examination that is scheduled in the coming week). |
| PH.3.5.4#15 | SHOULD |
The system SHOULD provide the ability to receive secure messages of reminders or notifications from the PHR Account Holder's provider(s) to remind the PHR Account Holder of tests or actions that are due or overdue. |
| PH.3.5.4#16 | SHOULD |
The system SHOULD provide the ability to update a repetitive reminder by dismissing the reminder. |
| PH.3.5.4#17 | SHOULD |
The system SHOULD provide the ability to transmit a notification to the PHR Account Holder or the PHR Account Holder's designated representative that a reminder was not acknowledged. |