Consumer Mobile Health Application Functional Framework, Release 2
2.0.1 - CI build International flag

Consumer Mobile Health Application Functional Framework, Release 2, published by HL7 International / Mobile Health. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cmhaff-ig/ and changes regularly. See the Directory of published versions

: APU.7 Notifications and Alerts (Function)

Page standards status: Informative

Raw json | Download

{
  "resourceType" : "Requirements",
  "id" : "CMHAFFR2-APU.7",
  "meta" : {
    "profile" : [
      🔗 "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n    \n    \n    <div id=\"description\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <p>\nExample:\nIn the realm of alerts and notifications, the following table proposed suggested standardized (generic)terms in the left column, with mappings to the\n leading two platforms in the middle columns, and comments in the right column. The platform-specific definitions have been derived from web\n sources,with preference given to information from the creators of the platforms (Apple, Google). Note: the mapping cannot be made an exact 1:1. In\n some cases, the platform-specific term may be more precise(e.g., subtypes) than the generic term, but we do not require a generic equivalent for\n every platform- specific term. In other cases, there may be substantial similarity of concepts across platforms, but not identical behavior, and\n certainly not identical appearance.\n\n Despite the proposed granularity of these terms, that does not mean that there need to be separatecMHAFF conformance requirements for each\n type, but at least the opportunity is there if the need arises. In particular, there may be different conformance requirements for “alerts” vs other\n types ofnotifications.\n\n Suggested “standardized” Apple (iOS) equivalent Google (Android OS) Comments\n (generic) term for cMHAFF equivalent\n Message Generally refers to Generally used to refer to Message, or Messaging, can\n Any computer to computer or messages within specific messages from one describe cMHAFF’s overarching term\n computer-to-human interface, types of apps, like email, device (or server) to for the data packages that are sent\n whether via visual, aural, haptic, text, IM, Facebook… another. by apps. While we consider\n olfactory, taste, or neural notifications and alerts as special\n mediums. However, when types of messages, the specific term\n discussing interoperability, the “message” is used a lot for messages\n focus is on computer-to- within apps, but not generally used\n computer 3 messaging. Note that when describing alerts and\n the messages can be transmitted notifications. We in HL7 also have\n within the same physical the HIT-specific legacy of structured\n computer, but between different “messaging” formats that include\n software (e.g., APIs). healthcare content and sometimes\n PHI (e.g., HL7 v2 message).\n Notification Notification – generic Notification – generic Generic term that has subtypes.\n A device-specific message term to cover many term to cover many types\n communicated to a user to inform types of notifications. of notifications. While HIT also has “notifications” that\n\nthem of device or app activities may be delivered to an app, not just\nthat are deemed important to the to a human user, cMHAFF uses a\nuser. Some types of notifications common consumer-based definition\nrequire a response from the user,\nwhile others do not.\nAlert Alert Alert Dialog, aka These messages will always be seen\nA type of Notification that is Dialog Notification by the user, except if the device is\ncommunicated to a user and turned off or the user does not look at\nrequires a response before the the device at all (nothing is\nuser can proceed with activity on guaranteed). In general, these are\nthe device. For example, it may considered more “serious” than other\ntake the form of a “modal” pop-up types of notifications. Local or other\ndialog that must be dismissed by policy make have more stringent\nclicking OK or taking some other rules for anything deemed an “alert”\naction. vs a “notification.”\nPersistent Notification Notifications (in Status Notification Android has more than one type of\nA device-specific message Notification Center) notification.\ncommunicated to a user to inform Status Notifications can\nthem of device or app activities Badge (on individual app appear outside the app\nand remain displayed on the icons) window and can be used\ndevice. These remain persistent to attract the user back to\nuntil the user deletes them or the app.\ntakes an action that changes their\nstatus (e.g., checks text\nmessages, checks email)\nTemporary Notification Banner Toast Since these messages fade after a\nA subtype of Notification that short time, it is very possible that\ndoes not remain displayed on the “Lock screen Toasts appear within the they will not be seen at all. In\nscreen more than a short time notifications” look like app window, not outside Android, Toasts appear within the\nperiod. banners but appear on of it app window (not outside the app). In\n the lock screen. iOS, they can appear outside the\n app.\nEmergency Notification iPhone provides options Four types: presidential These are outside the scope of an\nA notification from an external for two types of notifications, imminent app, are not written by MH app\nsource, such as the government, Government Alerts, extreme notifications, developers, but can be configured to\ncommunicating important “AMBER Alerts” and imminent severe alert and display on the device. They are\ninformation about your area (e.g., “Emergency Alerts.” AMBER alert. You can mentioned so that we don’t use the\nemergency, disaster, weather…) turn off every alert except same terms for something else.\n for the presidential alert.\n\n Hierarchy\n\n • Message (overarching term)\n o Content Message (e.g., HL7 v2, C-CDA payload, FHIR resource) – out of the scope for this set of definitions.\n o Notification (overarching term)\n  Alert (requires user action, whereas all other types of notifications do not require it,though they may allow it)\n  Persistent notification\n  Temporary notification\n  Emergency Notification (government, outside app control)</p></div>\n    \n    \n    \n    <div id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></div>\n    <table id=\"statements\" class=\"grid dict\">\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#01\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>The system SHALL require opt-in consent from the account holder before sending notifications and alerts.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#02\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>The system SHALL inform the account holder of both the content and the channel, such as SMS, push notification, or email, of the notification or alert that is consented to.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#03\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>IF an alert, notification, or message is generated or prioritized by AI THEN the system SHALL identify the message as AI-generated or AI-prioritized when that information is material to the user's interpretation or action.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#04\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>The system SHALL provide the account holder with the ability to change consent decisions about notifications and alerts through settings available on the device on which the system was downloaded.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#05\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>The system SHALL provide notifications and alerts that contain the least amount of information necessary for the recipient to take a focused action.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#06\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>IF alerts notify the user of conditions that are abnormal, exceptional, or determined to be out of range THEN the system SHALL document or reference the sources (evidence base) of the formulas and algorithms on which those alerts and notifications are based.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#07\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n            \n            <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>IF an AI-generated alert advises a health or safety action THEN the system SHALL ensure that the alert's triggering logic, evidence basis, validation scope, and safe escalation instructions are documented and appropriate to the system's intended use.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#08\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n            \n            <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>IF permitted by the account holder and agreed to by the recipients THEN the system SHOULD provide the ability to send notifications and alerts to the account holder and to another person or entity.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#09\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n            \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>The system SHOULD provide alerts that notify the user of potential faults that could cause inconvenience or harm, such as low battery alerts.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#10\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n            \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>The system SHOULD notify the user in the case of external interruptions or delays, such as loss of network connection, a database problem, or a lengthy operation.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#11\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n            \n            <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>IF the system can detect AI uncertainty, out-of-distribution input, or unavailable supporting data THEN the system SHOULD suppress, downgrade, or qualify the AI-generated alert when the risk assessment indicates that the underlying output may be unreliable.</p>\n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            APU.7#12\n            </td>\n            <td style=\"padding-left: 4px;\">\n            MAY\n            \n            \n            <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <p>IF the system uses AI to personalize notification timing or content THEN the system MAY allow the account holder to control the personalization settings and the categories of data used for personalization.</p>\n\n                \n            </td>\n        </tr>\n        \n    </table>\n    \n</div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "mobile"
    }
  ],
  "url" : "http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-APU.7",
  "version" : "2.0.1",
  "name" : "APU_7_Notifications_and_Alerts",
  "title" : "APU.7 Notifications and Alerts (Function)",
  "status" : "active",
  "date" : "2026-11-18T11:24:54+00:00",
  "publisher" : "HL7 International / Mobile Health",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/mobile"
        }
      ]
    }
  ],
  "description" : "This category applies only if an app exchanges data with other devices, health apps, and/or HIT systems. If so, there are applicable\n standards for data format, vocabulary, and transport, to increase interoperability and ease of connection.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "\nExample:\nIn the realm of alerts and notifications, the following table proposed suggested standardized (generic)terms in the left column, with mappings to the\n leading two platforms in the middle columns, and comments in the right column. The platform-specific definitions have been derived from web\n sources,with preference given to information from the creators of the platforms (Apple, Google). Note: the mapping cannot be made an exact 1:1. In\n some cases, the platform-specific term may be more precise(e.g., subtypes) than the generic term, but we do not require a generic equivalent for\n every platform- specific term. In other cases, there may be substantial similarity of concepts across platforms, but not identical behavior, and\n certainly not identical appearance.\n\n Despite the proposed granularity of these terms, that does not mean that there need to be separatecMHAFF conformance requirements for each\n type, but at least the opportunity is there if the need arises. In particular, there may be different conformance requirements for “alerts” vs other\n types ofnotifications.\n\n Suggested “standardized” Apple (iOS) equivalent Google (Android OS) Comments\n (generic) term for cMHAFF equivalent\n Message Generally refers to Generally used to refer to Message, or Messaging, can\n Any computer to computer or messages within specific messages from one describe cMHAFF’s overarching term\n computer-to-human interface, types of apps, like email, device (or server) to for the data packages that are sent\n whether via visual, aural, haptic, text, IM, Facebook… another. by apps. While we consider\n olfactory, taste, or neural notifications and alerts as special\n mediums. However, when types of messages, the specific term\n discussing interoperability, the “message” is used a lot for messages\n focus is on computer-to- within apps, but not generally used\n computer 3 messaging. Note that when describing alerts and\n the messages can be transmitted notifications. We in HL7 also have\n within the same physical the HIT-specific legacy of structured\n computer, but between different “messaging” formats that include\n software (e.g., APIs). healthcare content and sometimes\n PHI (e.g., HL7 v2 message).\n Notification Notification – generic Notification – generic Generic term that has subtypes.\n A device-specific message term to cover many term to cover many types\n communicated to a user to inform types of notifications. of notifications. While HIT also has “notifications” that\n\nthem of device or app activities may be delivered to an app, not just\nthat are deemed important to the to a human user, cMHAFF uses a\nuser. Some types of notifications common consumer-based definition\nrequire a response from the user,\nwhile others do not.\nAlert Alert Alert Dialog, aka These messages will always be seen\nA type of Notification that is Dialog Notification by the user, except if the device is\ncommunicated to a user and turned off or the user does not look at\nrequires a response before the the device at all (nothing is\nuser can proceed with activity on guaranteed). In general, these are\nthe device. For example, it may considered more “serious” than other\ntake the form of a “modal” pop-up types of notifications. Local or other\ndialog that must be dismissed by policy make have more stringent\nclicking OK or taking some other rules for anything deemed an “alert”\naction. vs a “notification.”\nPersistent Notification Notifications (in Status Notification Android has more than one type of\nA device-specific message Notification Center) notification.\ncommunicated to a user to inform Status Notifications can\nthem of device or app activities Badge (on individual app appear outside the app\nand remain displayed on the icons) window and can be used\ndevice. These remain persistent to attract the user back to\nuntil the user deletes them or the app.\ntakes an action that changes their\nstatus (e.g., checks text\nmessages, checks email)\nTemporary Notification Banner Toast Since these messages fade after a\nA subtype of Notification that short time, it is very possible that\ndoes not remain displayed on the “Lock screen Toasts appear within the they will not be seen at all. In\nscreen more than a short time notifications” look like app window, not outside Android, Toasts appear within the\nperiod. banners but appear on of it app window (not outside the app). In\n the lock screen. iOS, they can appear outside the\n app.\nEmergency Notification iPhone provides options Four types: presidential These are outside the scope of an\nA notification from an external for two types of notifications, imminent app, are not written by MH app\nsource, such as the government, Government Alerts, extreme notifications, developers, but can be configured to\ncommunicating important “AMBER Alerts” and imminent severe alert and display on the device. They are\ninformation about your area (e.g., “Emergency Alerts.” AMBER alert. You can mentioned so that we don’t use the\nemergency, disaster, weather…) turn off every alert except same terms for something else.\n for the presidential alert.\n\n Hierarchy\n\n • Message (overarching term)\n o Content Message (e.g., HL7 v2, C-CDA payload, FHIR resource) – out of the scope for this set of definitions.\n o Notification (overarching term)\n  Alert (requires user action, whereas all other types of notifications do not require it,though they may allow it)\n  Persistent notification\n  Temporary notification\n  Emergency Notification (government, outside app control)",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-01",
      "label" : "APU.7#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL require opt-in consent from the account holder before sending notifications and alerts."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-02",
      "label" : "APU.7#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL inform the account holder of both the content and the channel, such as SMS, push notification, or email, of the notification or alert that is consented to."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-03",
      "label" : "APU.7#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : true,
      "requirement" : "IF an alert, notification, or message is generated or prioritized by AI THEN the system SHALL identify the message as AI-generated or AI-prioritized when that information is material to the user's interpretation or action."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-04",
      "label" : "APU.7#04",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the account holder with the ability to change consent decisions about notifications and alerts through settings available on the device on which the system was downloaded."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-05",
      "label" : "APU.7#05",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide notifications and alerts that contain the least amount of information necessary for the recipient to take a focused action."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-06",
      "label" : "APU.7#06",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : true,
      "requirement" : "IF alerts notify the user of conditions that are abnormal, exceptional, or determined to be out of range THEN the system SHALL document or reference the sources (evidence base) of the formulas and algorithms on which those alerts and notifications are based."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-07",
      "label" : "APU.7#07",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : true,
      "requirement" : "IF an AI-generated alert advises a health or safety action THEN the system SHALL ensure that the alert's triggering logic, evidence basis, validation scope, and safe escalation instructions are documented and appropriate to the system's intended use."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-08",
      "label" : "APU.7#08",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : true,
      "requirement" : "IF permitted by the account holder and agreed to by the recipients THEN the system SHOULD provide the ability to send notifications and alerts to the account holder and to another person or entity."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-09",
      "label" : "APU.7#09",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide alerts that notify the user of potential faults that could cause inconvenience or harm, such as low battery alerts."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-10",
      "label" : "APU.7#10",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD notify the user in the case of external interruptions or delays, such as loss of network connection, a database problem, or a lengthy operation."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-11",
      "label" : "APU.7#11",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : true,
      "requirement" : "IF the system can detect AI uncertainty, out-of-distribution input, or unavailable supporting data THEN the system SHOULD suppress, downgrade, or qualify the AI-generated alert when the risk assessment indicates that the underlying output may be unreliable."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "CMHAFFR2-APU.7-12",
      "label" : "APU.7#12",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : true,
      "requirement" : "IF the system uses AI to personalize notification timing or content THEN the system MAY allow the account holder to control the personalization settings and the categories of data used for personalization."
    }
  ]
}