Consumer Mobile Health Application Functional Framework, Release 2
2.0.1 - CI build
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
| Official URL: http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-APU.8 | Version: 2.0.1 | ||||
| Standards status: Informative | Computable Name: APU_8_Product_Upgrades | ||||
| APU.8#01 | SHALL |
The system SHALL respect operating system level permissions concerning automatic product updates. |
| APU.8#02 | SHALL conditional |
IF an updated version of the system includes updated Terms of Use THEN the system SHALL present the updated Terms of Use to the account holder for acceptance before the updated version may be used. Significant changes to the terms and conditions are highlighted, and a link to the full set of updated Terms of Use is available. |
| APU.8#03 | SHALL conditional |
IF automatic updates are not enabled THEN the system SHALL prompt the user when a new version is available. |
| APU.8#04 | SHALL conditional |
IF an account holder elects not to install a new version THEN the system SHALL inform the user of the consequences of not installing it, including information about support limitations for the older version. |
| APU.8#05 | SHALL conditional |
IF a new version increases what information is exposed by alerts THEN the system SHALL require the user to consent to the information being exposed, and SHALL clearly highlight the changes to the exposed information when that consent is given. |
| APU.8#06 | SHALL conditional |
IF the system uses AI functionality THEN the system SHALL treat a material change to an AI model, prompt, retrieval source, training data, inference service, or decision threshold as a controlled product change and SHALL document the change, risk assessment, validation, approval, and rollback plan before deployment. |
| APU.8#07 | SHALL conditional |
IF an AI change materially affects data use, intended use, performance, or consumer-facing risk THEN the system SHALL notify affected users before or at deployment, explain the material change in understandable terms, and obtain updated permission when the change expands personal-data use or another consent-relevant practice. |
| APU.8#08 | SHOULD conditional |
IF the system uses AI functionality THEN the system SHOULD maintain the ability to suspend or roll back an AI component without requiring removal of unrelated App functionality when a material safety, privacy, or performance issue is detected. |