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.2 | Version: 2.0.1 | ||||
| Standards status: Informative | Computable Name: PDS_2_Product_Risk_Assessment_and_Mitigation | ||||
This category deals with process steps for risk assessment and mitigation for those who are developing a new app, or an upgrade to an app, prior to its being deployed to consumers.
Exception parsing generated Narrative (see /tmp/liquid-83cf6f2a-3ac4-43fc-9d75-ce15b071a40b.html): unable to parse character reference ' Infrastructure, The Mobile Threat Catalogue (USA) https://nccoe.nist.gov/sites/default/files/library/mtc-nistir-8144-draft.pdf (context and background information) https://pages.nist.gov/mobile-threat-catalogue/application.html#vulnerable-applications (actual catalog of threats, specifically the “Vulnerable Application” category, which is the part ofthe threat catalog closest to cMHAFF) • Open Web Application Security Project (OWASP) Top 10 Mobile Security Risks: https://www.owasp.org/index.php/Mobile_Top_10_2016-Top_10 This is focused on appdevelopers, so most of it is pertinent to cMHAFF, and for each risk, there are suggested mitigations. • OWASP Secure Coding Practices Quick Reference Guide: https://owasp.org/www-project-secure-coding-practices-quick- reference-guide/ - This provides resources for developers that can assist in implementing secure coding practices. It is recommended that developers adopt secure coding practices so that applications are developed with an emphasis on security vs having to apply security measures to protect the application. Example: While later sections in this standard include specific security and privacy controls to be applied to consumer mobile health apps, all products addressing health issues, regardless of their type, must be subjected to an overall risk analysis. This risk analysis may uncover the need for additional security controls over-and-above the conformance statements included in this document. As such, a risk analysis provides an additional layer of considerations such that conformance statements are not misused as a simple checklist in which it is assumed all security risks have been addressed if an app is in compliance with the conformance statements in this standard. For an app/product, the risk analysis should be conducted for the target environment(s) where the app will actually be used by consumers. Because of the diversity of consumers, such a risk analysis is wider ranging and more challenging than a risk analysis for the development organization’s own environment.'' (last text = ' ' at line 45 column 53
While mobile computing environments may introduce some specific threats not present in non-mobilecomputing, the principles of risk management are the same across environments, so some standards and regulations are cited, even though they are not mobile-centric. Documents (listed alphabetically below) were sources of some cMHAFF criteria for risk assessment. Other useful references on risk assessment are listed in the Appendix. While some are realm-specific, they have much material that is applicable beyond their countries. Realms are listed in parentheses, if not explicit in the title.
While later sections in this standard include specific security and privacy controls to be applied to consumer mobile health apps, all products addressing health issues, regardless of their type, must be subjected to an overall risk analysis. This risk analysis may uncover the need for additional security controls over-and-above the conformance statements included in this document. As such, a risk analysis provides an additional layer of considerations such that conformance statements are not misused as a simple checklist in which it is assumed all security risks have been addressed if an app is in compliance with the conformance statements in this standard. For an app/product, the risk analysis should be conducted for the target environment(s) where the app will actually be used by consumers. Because of the diversity of consumers, such a risk analysis is wider ranging and more challenging than a risk analysis for the development organization’s own environment.