Close

2.4 Exemplary Use Cases

As noted in the Introduction, consumer mobile heath apps take many forms, and as such, conformance statements in section 3 of this standard must allow for variation based on multiple factors, including data sensitivity, the nature of conditions addressed by the app (e.g., wellness, chronic illness), and whether/how app data connect to other data sources.

In this section, three archetypal use cases are introduced. While most consumer mobile health apps will not precisely fit any of these models, the models are meant to demonstrate a continuum of issues which may be applied to any app. Use Case A covers the least sensitive example of a health app that collects user information, while Use Case B builds off of Case A with the inclusion of an external system through which personal data is synchronized with the device. Use Case C is the most sophisticated and generates the most requirements. Its description includes examples of the risk factors that should be considered by developers and users.

Section 3 (Conformance Criteria) includes discussion of considerations as to how subsets of conformance criteria can be addressed in different manners, referencing the use cases in this section as a way to provide directional, rather than pinpoint, guidance.

HL7 CMHAFF Standard Overview and Use Cases

Nathan E Botts
/ Categories: Sources

European Committee for Standardization (CEN)

Quality & reliability for health and wellness apps

From the eHealth Standards EU website:

A new CEN Technical Specification for ‘Quality and Reliability of Health and Wellness Apps’ is being developed at the request and with the support of the European Commission. It is due to be completed in 2020. It will help to establish a common framework across Europe for the evaluation of these apps, giving users and health professionals confidence that the apps are fit for purpose, and providing app developers easier access to European markets.

Europe is experiencing a fast growing market for Health and Wellness Apps. At the same time, concerns about the quality and reliability of apps have risen. Many Health and Wellness Apps are being published without there being a clear way for users to establish which ones are reliable and provide evidence to support claimed benefits.

This Technical Specification addresses the specific needs of the developers of Health and Wellness Apps:

  • App developers are a disruptive community, with many members who are entering the Health and Wellness IT market without prior experience in a Health Informatics context. These developers will not have experienced a transfer of health informatics knowledge and good practice from co-workers and broader corporate memory. The specification will compensate for this by providing a set of requirements that have been through a rigorous standards development process.
  • This community does not expect to have to read multiple documents, and map generic standards into their context of use. Apps are typically developed to deliver a small piece of functionality, building on an existing platform – often with a small team doing the work. The specification will directly address the needs and concerns of app developers.
  • Apps run on platforms, and are made available through distinct channels such as app stores and libraries. These platforms and channels provide potential points of control where quality and reliability of apps can be influenced, and this will be taken into account during the development of the specification.
  • There is a need for a specification to establish a consistent set of criteria for among the controlled channels being maintained as trustworthy sources of health and wellness apps in the many national health initiatives within the EU.

The Technical Specification is being developed by the European standardisation committee CEN/TC 251 Health Informatics in collaboration with experts from the standardisation organisations

ISO and IEC, to ensure that it is consistent with international standards. The project team includes members from the following CEN member countries: Belgium (NBN), France (AFNOR), United Kingdom (BSI), Germany (DIN), Netherlands (NEN), Sweden (SIS), Finland (SFS) and Italy (UNI). Quoting the project leader Charles McCay: “Initial work for this standard has already been done in the United Kingdom with the publication by BSI of the publicly available specification PAS 277. This project will expand that work to meet the wider European requirements and ensure compatibility with the world health informatics standards from ISO and IEC.”

Print
8230 Rate this article:
No rating
0Upvote 0Downvote

Leave a comment

This form collects your name, email, IP address and content so that we can keep track of the comments placed on the website. For more info check our Privacy Policy and Terms Of Use where you will get more info on where, how and why we store your data.
Add comment
Terms Of UsePrivacy StatementCopyright 2024 by HL7 International
Back To Top