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-PDS.3 | Version: 2.0.1 | ||||
| Standards status: Informative | Computable Name: PDS_3_Usability_Accessibility_Assessment | ||||
This category is about the assessment of usability during the product development cycle, for the intended use by a target audience.
Certain accessibility requirements (usability for users with specific disabilities) are recommended, but the list is not exhaustive. Other disabilities not mentioned (e.g., cognitive/learning disabilities) should be considered under the umbrella of conformance criterion #1. Example: The timing of implementation of usability findings can be indicated in functional profiles based on the severity of findings. At a minimum a usability assessment plan includes information about the timeframe under which remediation will occur. These conformance statements apply to any type of app addressed in this standard. However, specific usability measures and remediation plans will differ based on app functionality, intended users, and app platform, and as such this standard does not discuss specific controls; instead, it speaks to a development process which encourages inclusion and end user satisfaction. See Appendix: Reference Documents
| PDS.3#01 | SHALL |
The system SHALL be assessed against an industry-validated usability assessment tool using subjects who are demographically similar to the intended users (target audience). User types may include, for example, those with motor disabilities, visual impairment, or auditory disabilities. |
| PDS.3#02 | SHALL conditional |
IF the system displays AI output to consumers THEN the system SHALL assess, with representative intended users, whether consumers can understand that an output is AI-assisted, the output's intended purpose, its material limitations, and the appropriate next step. |
| PDS.3#03 | SHOULD |
The system SHOULD undergo non-functional usability testing that assesses its user-friendliness, performance reliability, and adherence to end-user expectations for the targeted consumer group. |
| PDS.3#04 | SHOULD |
The system SHOULD have a written usability assessment plan that includes known product usability problems and a mitigation plan. |
| PDS.3#05 | SHOULD |
The system SHOULD follow the design and style guide standards established by the platform provider(s) on which it runs, such as Android or iOS. |
| PDS.3#06 | SHOULD |
The system SHOULD avoid excessive data use, minimize data use as far as practicable, and warn the user when high data usage occurs, such as during downloads and updates. |
| PDS.3#07 | SHOULD |
The system SHOULD be supported by a requirements analysis that describes the use cases (business scenarios) and intended users for its main functions. |
| PDS.3#08 | SHOULD conditional |
IF the system uses AI functionality THEN the system SHOULD assess cognitive burden, health literacy, language accessibility, disability access, and the likelihood that interface design could cause users to over-trust or misunderstand AI output. |
| PDS.3#09 | SHOULD |
The system SHOULD permit adaptation to the user's specific abilities, needs, or requirements. |
| PDS.3#10 | SHOULD |
The system SHOULD provide information about its accessibility characteristics in the product description and in the contextual assistance sections of the system. |
| PDS.3#11 | MAY conditional |
IF the system uses AI functionality THEN the system MAY provide an accessible explanation mode that uses plain language, translated text, visual aids, or other adaptive presentation methods. |
The timing of implementation of usability findings can be indicated in functional profiles based on the severity of findings. At a minimum a usability assessment plan includes information about the timeframe under which remediation will occur.
These conformance statements apply to any type of app addressed in this standard. However, specific usability measures and remediation plans will differ based on app functionality, intended users, and app platform, and as such this standard does not discuss specific controls; instead, it speaks to a development process which encourages inclusion and end user satisfaction.
See Appendix: Reference Documents