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

Requirements: PDS.4 Customer/Technical Support (Function)

Official URL: http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-PDS.4 Version: 2.0.1
Standards status: Informative Computable Name: PDS_4_Customer_Technical_Support
  1. Information as to how to access customer support, and channels of support (e.g., voice, email, PDS.4 NC text, Twitter) SHALL clearly be stated within the app's Terms of Use and as a feature accessible from within the app.
Criteria N:
PDS.4#01 SHALL

The system SHALL clearly state how to access customer support and the available support channels, such as voice, email, text, or social media, within its Terms of Use and as a feature accessible from within the system.

PDS.4#02 SHALL

The system SHALL make customer support accessible prior to the establishment of a user account, so that a user can raise questions about the Privacy Policy or Terms of Use before deciding to use the system.

PDS.4#03 SHALL

The system SHALL provide customer support in the language(s) in which it is published.

PDS.4#04 SHALL

The system SHALL give attribution to any open source code library or copyrighted code used in its development, within its Terms of Use or in documentation available from within the system.

PDS.4#05 SHALL conditional

IF a support request involves accessing, disclosing, or changing customer data THEN the system SHALL verify the identity of the customer and the customer's data access rights before any customer data is disclosed or changed.

PDS.4#06 SHOULD

The system SHOULD provide responses to customer support queries that directly address the stated problem or issue within two business days. An acknowledgement that a query has been received, without further action, is not sufficient.

PDS.4#07 SHALL conditional

IF the system uses AI functionality THEN the system SHALL provide consumers with a clear mechanism to report suspected inaccurate, harmful, biased, misleading, or privacy-impacting AI output, and the system SHALL route reports into a documented investigation and remediation process.

PDS.4#08 SHOULD conditional

IF the system uses AI functionality that can influence a high-impact health or safety decision THEN the system SHOULD provide an expedited path to human support or an appropriate safety resource when a consumer reports a potentially serious AI-related issue.

PDS.4#09 SHOULD

The system SHOULD provide consumers with aggregated satisfaction ratings relevant to the customer support terms and conditions, as appropriate.

PDS.4#10 SHOULD

The system SHOULD provide a frequently asked questions (FAQ) resource where users can find answers to common questions.

Notes:

https://www.markdownguide.org/extended-syntax/#footnotes