This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CMHAFF call, Thursday, Oct 5"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
*Review of first draft of '''"cMHAFF Label,"''' a visual summary of key facts about an app and its conformance to cMHAFF (David) | *Review of first draft of '''"cMHAFF Label,"''' a visual summary of key facts about an app and its conformance to cMHAFF (David) | ||
**Review of '''Label format and "consumer friendly language"''' descriptions (new Section 2.2 in cMHAFF document) | **Review of '''Label format and "consumer friendly language"''' descriptions (new Section 2.2 in cMHAFF document) | ||
| − | **Work through two sections as examplars: '''Product Information''' and '''User Authorization (Consent) for Data Collection and Use''', to | + | **Work through two sections as examplars: '''Product Information''' and '''User Authorization (Consent) for Data Collection and Use''', to explore how the label score (green/yellow/red) might be determined by conformance statements, and who would decide (self-attestation vs inspection vs test vs ____?). |
**Notes from previous discussion (Sept 21st): some information would be provided by self-declaration, but other parts might come from testing or certification. Adamu suggested a simple visual approach, such as "red, yellow, green" lights, possibly combined with symbols. We looked through several cMHAFF sections, envisioning how they might be summarized on this label. Unlike a food or drug label, it does not have to fit on a physical "box," so we expect that it will be a tabular/graphical representation, not to exceed one page. | **Notes from previous discussion (Sept 21st): some information would be provided by self-declaration, but other parts might come from testing or certification. Adamu suggested a simple visual approach, such as "red, yellow, green" lights, possibly combined with symbols. We looked through several cMHAFF sections, envisioning how they might be summarized on this label. Unlike a food or drug label, it does not have to fit on a physical "box," so we expect that it will be a tabular/graphical representation, not to exceed one page. | ||
*Placeholder: Resolution of specific open comments in cMHAFF document, time permitting | *Placeholder: Resolution of specific open comments in cMHAFF document, time permitting | ||
**No specific comments slated for this week, as there will probably not be time. | **No specific comments slated for this week, as there will probably not be time. | ||
Revision as of 23:12, 4 October 2017
ATTENDEES:
AGENDA:
- Review of U.K. PAS277 Guidelines (new document recommended in San Diego) -- Adamu Haruna
- Review short descriptions (most are new) of each section at the Heading 3 level (e.g., 3.4.1 User Authentication, 3.4.2 User Authorizations...)
- Review of first draft of "cMHAFF Label," a visual summary of key facts about an app and its conformance to cMHAFF (David)
- Review of Label format and "consumer friendly language" descriptions (new Section 2.2 in cMHAFF document)
- Work through two sections as examplars: Product Information and User Authorization (Consent) for Data Collection and Use, to explore how the label score (green/yellow/red) might be determined by conformance statements, and who would decide (self-attestation vs inspection vs test vs ____?).
- Notes from previous discussion (Sept 21st): some information would be provided by self-declaration, but other parts might come from testing or certification. Adamu suggested a simple visual approach, such as "red, yellow, green" lights, possibly combined with symbols. We looked through several cMHAFF sections, envisioning how they might be summarized on this label. Unlike a food or drug label, it does not have to fit on a physical "box," so we expect that it will be a tabular/graphical representation, not to exceed one page.
- Placeholder: Resolution of specific open comments in cMHAFF document, time permitting
- No specific comments slated for this week, as there will probably not be time.
