3.6 Data Authenticity, Provenance and Associated Metadata 3.7 In-app Payments Apps conform to Best Practices for Data Authenticity, Provenance, and Associated 1 Shall In-app payments are not required in order for the app to provide its main functions. 1 SHALL Metadata (This will require an Appendix and a testing reference such as Drummond [App permits in-app payments] The benefits for paying for a service or feature are Group?) Shall 2 clearly stated in a manner which allows an account holder to make an informed decision SHALL [App itself originates data <see draft ISO 21089 definition of originate>] Customer has [IF] 3 about making or declining an in-app payment. [IF} review option which includes the option to irreversibly destroy, reject or discard data. 3 [App itself only receives data as a “pass through” and cannot store data] Customer has a SHALL 4 4 review option to display the data prior to executing the pass-through which includes the [IF} 5 option to irreversibly stop and block the pass-through. Regulations, standards, [App itself and receives implementation data and stores tools it] Customer has a review option that permits only SHALL 5 appending data and/or free text comments to received data as author while preserving [IF] the original received data intact with original provenance. Implementation guidance by use case 6 (Others to follow if not deemed too much of a reach…) 7 Use Case A: Regulations, standards, and implementation tools Use Case B: Use Case C: Implementation guidance by use case Use Case A: Use Case B: Use Case C:
3.6 Data Authenticity, Provenance and Associated Metadata 1 SHALL Apps conform to Best Practices for Data Authenticity, Provenance, and Associated Metadata (This will require an Appendix and a testing reference such as Drummond Group?) 3 SHALL [IF} [App itself originates data <see draft ISO 21089 definition of originate>] Customer has review option which includes the option to irreversibly destroy, reject or discard data. 4 SHALL [IF} [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. 5 SHALL [IF] [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. 6 (Others to follow if not deemed too much of a reach…) 7 Regulations, standards, and implementation tools Implementation guidance by use case Use Case A: Use Case B: Use Case C: 3.7 In-app Payments 1 Shall In-app payments are not required in order for the app to provide its main functions. 2 Shall [IF] [App permits in-app payments] The benefits for paying for a service or feature are clearly stated in a manner which allows an account holder to make an informed decision about making or declining an in-app payment. 3 4 5 Regulations, standards, and implementation tools Implementation guidance by use case Use Case A: Use Case B: Use Case C:
HL7_Consumer_Mobile_App_Framework_Minutes_v20150818.docx