×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 

Consumer Mobile Health Application Functional Framework

Basics

Consumer Mobile Health Application Functional Framework

1182
Ballot - STU to Normative


Functional Profile

Create New Standard, Supplement to a Current Standard

Details

This project will define security, privacy and data standards for secure mobile health applications (apps). The intent is to provide industry guidance and common methods to enable the development of mobile health smartphone apps targeted to consumers/citizens that use protected health information (PHI) and personally identifiable information (PII). These standards will not address the content of such apps, but will provide a framework for security, privacy and trusted integration of data generated from apps into Personal Health Record (PHR) and Electronic Health Record (EHR) systems as well as into other types of data repositories (e.g., personal data stores, population care systems). This project will reuse conformance criteria already available within the HL7 PHR-S and EHR-S Functional Models, augmenting with new conformance criteria specific to mobile platforms (e.g., use of geolocation services, accelerometers, cameras, microphones). In particular, standards will address the following areas: - Privacy policy, terms of use, and in-app disclaimers - User, device, and cross-system authentication - Authorization to content and features - Proxy designations - Use of location services, camera, accelerometers and other smartphone services - Security of data at rest (local and cloud) - Security of data in transit (wired and wireless) - Minimum data standards for device generated and device transmitted information - Record system reliability; record authenticity (it is what it represents to be) - Data provenance - Audit - Standards related to discontinuation of use of an app


Industry is in need of privacy and data standards in order to create consumer smartphone health apps which are secure, private, and that allow for data generated from and through these apps to be used in other health care contexts (e.g., personal data tracking, integration into a person's record of care, clinical decision making). While the HL7 PHR-S FM expresses many of these functional requirements, it is not possible to use the PHR-S FM as-is to create mobile application standards. Mobile apps are generally not comprehensive in scope and, as such, mobile app standards cannot be extracted as PHR system profiles as it is impossible for most apps to adhere to all the SHALL statements within the PHR-S FM.



Submit Framework for Comment Only Ballot(First Ballot Cycle) - Actual: 2016 Jan Ballot Complete consideration of comments - Actual: 2016 Sept WGM Submit for DSTU or Informative Ballot (1) - Target: 2017 May Ballot DSTU Period - 12 months; complete reconciliation of comments - Target: 2017 Sept WGM Submit for Normative Ballot - Target: ??? Complete Normative Reconciliation - Target: ??? Submit Publication Request - Target: ??? Receive ANSI Approval - Target: ??? Project End Date (all objectives have been met)* *consideration will be given to beginning new project for V2 of the framework dependent on the continued evolution of consumer mobile devices and applications - Target: ???


TBD

Assuming 30% to 50% of material will be derivative from existing conformance criteria from the PHR-S FM and EHR-S FM

None

Payors, Other (specify in Misc. Notes below),Healthcare Institutions (hospitals, long term care, home care, mental health),EHR, PHR; Health Care IT

1) Nathan Botts / HITEQ / Health eServices 2) Frank Ploeg / Diabetes App Pilot for Glucose Monitoring 3) Maqbool Hussain (maqbool110 at gmail.com) - Sejong University South Korea 4) Jose Costa Teixera - Consultant with App Vendors (Gora contact) 5) Anita Walden (Univ Arkansas Medical Science) 6) Gora Datta / CAL2CAL / mH4all

No external drivers are known at this time.

Mobile Health Framework; Consumer Health Mobile Framework

While this is a new product, it will draw conformance criteria from both the EHR-S FM Release 2 and the PHR-S FM Release 1.


N/A

No

2026 September: Normative notification submitted 2026 March: TSC approved an STU Extension Request HL7 consumer Mobile Health Application Functional Framework (cMHAFF) Release 1, STU Release 2 2025 April: TSC approved STU Extension Request for HL7 consumer Mobile Health Application Functional Framework (cMHAFF) Release 1, STU Release 2 for 6 months 2025 Jan WGM: GDatta/MGraham: Targeting to ballot 2025 Sept. PMO: Since the project has been stagnant for years, MH WG should create a new PSS in Jira so as to provide updated information. Once the new PSS is created in Jira, it will be tied back to PID 1182, as that is what the ballot system connects to for CMHAFF STU. PID 1452 can be closed/archived as 1182 will be the PID tracking this specification going forward. Additionally, the STU (from PID 1182) ends in April 2025, so MH WG should request an extension prior to the Normative ballot. 2020 July: M. Grahame: preparing for STU2 ballot May 2021 2020 May: TSC approved STU Extension Request for HL7 Consumer Mobile Health Application Functional Framework (cMHAFF), Release 1 for 24 months. 2025 Jan: PMO emailed MH WG asking them to submit an STU extension request. 2023 March: TSC approved STU Publication Request for Consumer Mobile Health Application Functional Framework 2018 June: The TSC approved the STU Publication Request for HL7 Consumer Mobile Health Application Functional Framework (cMHAFF), Release 1 at TSC Tracker 17290 thru June 26, 2019 2016 October:D. Tao: Updated target dates
Organization & Realm

Universal

People

Tim McKay



Mobile Health Work Group

Electronic Health Records Work Group

Status & Dates

Active

STU - Test Period/Accepting Comments

04/10/2015

09/15/2027

2027 Sept WGM/Ballot

01/01/2027

2027 Jan WGM/Ballot

2021 Sept Ballot Cycle Info: STU Ballot results: Met basic vote requirements. 9 Negatives to reconcile Document Name: HL7 Consumer Mobile Health Application Functional Framework, Release 1 (See Jira Ballot Dashboard) 2021 May Ballot Cycle Info: STU Ballot Results: Postponed Document Name: HL7 Consumer Mobile Health Application Functional Framework, Release 1 2021 Jan Ballot Cycle Info: STU Ballot Results: Postponed Document Name: HL7 Consumer Mobile Health Application Functional Framework, Release 1 2018 Jan Ballot Cycle Info: STU Ballot results: Met basic vote requirements. 2 Negatives to reconcile Document Name: HL7 Mobile Health Application Functional Framework; Consumer MHaFF, Release 1; Requesting alternate ballot title 'HL7 Consumer Mobile Health Application Functional Framework, Release 1' 2017 May Ballot Cycle Info: INFORMATIVE Ballot results: Postponed Document Name: HL7 Mobile Health Application Functional Framework; Consumer MHaFF, Release 1 2016 Jan Ballot Cycle Info: COMMENT ONLY Ballot results: Met basic vote requirements. 30 Negatives to reconcile Document Name: HL7 Mobile Health Application Functional Framework; Consumer MHaFF, Release
Approvals

09/22/2015


Not Needed


Not Needed




System Info





09/11/2026

Anne Wizauer