Difference between revisions of "MHWG Consumer Mobile Health Application Functional Framework,"
Nathan botts (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | '''Project | + | '''Project Co-Leads:''' Nathan Botts and David Tao |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Overview == | == Overview == | ||
| − | This project (Consumer Mobile Health Application Functional Framework, AKA Consumer Mobile App Framework)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 the 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 (Consumer Mobile Health Application Functional Framework, AKA cMHAFF and Consumer Mobile App Framework) will define security, privacy and data standards for secure mobile health applications (apps), as well as guidance pertaining to transparency and consumer protection through the life cycle of such apps (from purchase, download, installation, use, and deletion). 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 the 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). | 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). | ||
| Line 27: | Line 19: | ||
* Data provenance | * Data provenance | ||
* Audit | * Audit | ||
| − | * | + | * Discontinuation of use of an app |
== Project Scope Statement == | == Project Scope Statement == | ||
Revision as of 17:15, 16 August 2016
Project Co-Leads: Nathan Botts and David Tao
Overview
This project (Consumer Mobile Health Application Functional Framework, AKA cMHAFF and Consumer Mobile App Framework) will define security, privacy and data standards for secure mobile health applications (apps), as well as guidance pertaining to transparency and consumer protection through the life cycle of such apps (from purchase, download, installation, use, and deletion). 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 the 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
- Discontinuation of use of an app
Project Scope Statement
File:PSS Consumer Mobile Health App Framework 20150217.pdf
Meetings
Standing meetings are every Monday at 5 PM Eastern
WebEx: https://westat.webex.com/westat/j.php?MTID=mf163da12b3585dd6f6ffa0e66adfb4bf
Phone: +1 770-657-9270 Participant Passcode: 465623
Documents
File:HL7 Consumer Mobile App Conformance Criteria v20150618.docx
File:HL7 Mobile Health App Post Outofcycle v20150504.pptx
File:HL7 MH Out of Cycle intro v20150427.pptx
File:HL7 Consumer Mobile Framework Overview v20150406.pptx
Minutes
File:HL7 Consumer Mobile App Framework Minutes v20150818.docx
File:HL7 Consumer Mobile App Framework Minutes v20150810.docx
File:HL7 Consumer Mobile App Framework Minutes v20150615.docx
File:HL7 Consumer Mobile App Framework Minutes v20150601.docx
File:HL7 Consumer Mobile App Framework Minutes v201500518.docx
File:HL7 Consumer Mobile App Framework Minutes v201500504.docx
File:HL7 Consumer Mobile App Framework Minutes v20150427 28.docx
File:HL7 Consumer Mobile App Framework Minutes v20140413.docx
File:HL7 Consumer Mobile App Framework Minutes v20140406.docx
