Page tree
Skip to end of metadata
Go to start of metadata

Track description

In this track we will update you on the work of the Mobile Health Working, especially the Consumer Mobile Health Application Functional Framework (cMHAFF), the Mobile Health App Data Exhange project, the School Health Innovation Framework leveraging Technology (SHIFT) project, and the work currently undertaken by CEN/ISO to develop Techincal Specifications for Health Software (ISO/AWI TS 82304-2) Part 2: Health and Wellness apps - Quality criteria across the life cycle - Code of practice. 


Hands on activities: Assessment sheet cMHAFF, Questionaire CEN/ISO TC251 Health and Wellness apps


Presentation: 

Expected level of skill

No sepcific expert level of skill is needed.

level

description

Absolute beginners(thumbs up)
Heroes(thumbs up)


Preparation


Prep

level

Content

DocumentationAll
Downloads
  • All material mentioned above is downloadable
Equipment


Status Track

Geef aan waar de track zich bevindt, is het een nieuwe track, gaan we door op de vorige hackathon , zijn er onderdelen op verschillende levels, enz. Werk dit verder uit in de scenarios

Status

level

Description

NewAbsolute beginners(thumbs up)

Heroes(thumbs up)
SequalAbsolute beginnersN/A

HeroesN/A


Submitting WG / Project / Implementer Group

HL7 Mobile Health Working Group

Justification

The Consumer Mobile Health Application Functional Framework is an HL7 Standard for Trial Use (STU). The primary goals of the Consumer Mobile Health Functional Framework ( cMHAFF ) are to provide a standard against which a mobile app’s foundational characteristics -- including but not limited to security, privacy, data access, data export, and transparency/disclosure of conditions -- can be assessed.

The framework is based on the lifecycle of an app, as experienced by an individual consumer, from first deciding to download an app, to determining what happens with consumer data after the app has been deleted from a smartphone. It is important to note that the Framework does not speak directly to the specific health or clinical functionality of an app but can be extended to do so through the use of profiles (with constraints and/or extensions) developed on top of cMHAFF.

Related Tracks

N/A

Proposed Track Lead(s)

name

Description

Contact Info

Frank PloegCo-Chair MHr.f.ploeg@umcg.nl

Expected Participants

name

Description

Contact Info







Available Roles

Role

Description

App developer
Interested parties, cinsumers of apps

Scenario(s)

#

Scenario

Level

Description

1
AB




H
2....

Testscripts

N/A

Security & Privacy Consideration


  • No labels