Consumer Mobile Health Application Functional Framework, Release 2
2.0.1 - CI build International flag

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

Requirements: APU.5 Data Authenticity, Provenance, and Associated Metadata (Header)

Page standards status: Informative
Statement N:

This category is about providing assurance that consumer data is secure when it is moved between the consumer’s device(s) and other locations. This category is about the attribution of sources of data (provenance) and assurance of data authenticity.

Criteria N:
APU.5#89 SHALL

Apps conform to Best Practices for Data Authenticity, Provenance, and Associated Metadata.

APU.5#90 SHALL

[App itself originates data <see ISO 21089 definition of “originate”>] Customer has review option which includes the option to irreversibly destroy, reject or discard data.

APU.5#91 SHALL

[App itself only receives data as a “pass through” and cannot store data] Customer has a review option to display the data prior to executing the pass-through which includes the option to irreversibly stop and block the pass-through.

APU.5#92 SHOULD

[App itself receives data and stores it] Customer has a review option that permits only appending data and/or free text comments to received data as author while preserving the original received data intact with original provenance. User may comment that data are erroneous, but does not have the option to delete the original data.

Notes:

The following are examples of standards for data provenance. Even though they are specific to the FHIR and CDA standards respectively, the principles and data elements – for recording entities and processes involved in producing or delivering a resource (data) – may be applicable.