This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CMHAFF call, Thursday, August 10"

From HL7Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
Attendees: ____
+
Attendees: David Tao, Adamu Haruna, Gary Dickinson, Nathan Botts, Vanessa Batoon
  
 
AGENDA
 
AGENDA
*Review of recommendations re French Good Practice Guidelines: Reliability (Adamu)
+
*Review of recommendations re French Good Practice Guidelines: Reliability (Adamu) -- Adamu's recommendations were discussed, and dispositions were agreed upon. David will incorporate them into the next draft of cMHAFF.
 
*Review latest draft of cMHAFF: '''[[File:cMHAFF_STU_Ballot_Draft.docx]]'''  
 
*Review latest draft of cMHAFF: '''[[File:cMHAFF_STU_Ballot_Draft.docx]]'''  
**Section 3.3.1.1, Informing Consumers/Users section, review conformance statements. Logically group them, decide upon conformance strength and whether there are too many (currently 24). When trying to add ideas from many sources, cMHAFF grows larger and larger.
+
**Section 3.3.1.1, Informing Consumers/Users section, review conformance statements. Logically group them, decide upon conformance strength and whether there are too many (currently 24). When trying to add ideas from many sources, cMHAFF grows larger and larger. Decision was to consolidate some duplicates that were noticed, and to group them into subcategories (e.g., General Info, Payment, Limitations, Evidence/Credentials, etc.) so there is not just one long undifferentiated list.  
**Specific comment numbers to discuss:
+
**Specific comment numbers discussed:
***DKT4 decision tree
+
***DKT10  narrative introductions for each category? YES, this should be added.
***DKT6 levels of criticality -- if used, need clear definitions so developers can easily classify their apps
+
***DKT20  style/wording decision throughout -- refer to "app," "product," or...?  Explain that they are synonymous, but change wording to consistently use "App" in conformance statements.
***DKT10  narrative introductions for each category?
 
***DKT14  reference for "secure coding practices?"
 
***DKT20  style/wording decision throughout -- refer to "app," "product," or...?
 
***DKT30 granularity vs precision -- are both needed?
 
***DKT39 and DKT40  "syncing" data and "pairing" of devices?
 
***DKT42  decision on what to do with provenance discussion
 
***DKT43  new "Interoperability" section
 
***DKT51  revisit "Conditions and Agreements" and how it differs from "Informing Consumers/Users"
 
***DKT56  Glossary: build it, or refer to external glossary?
 
***DKT46  Should Windows platform considerations be included or not
 
*Check status, set schedule for recommendations from additional European documents. Look for gaps (missing in cMHAFF, but within scope), or contradictions (recommendations that run counter to cMHAFF).
 
**'''[[File:charismha_abr_v.01.1e-20160606 (003)_ENG SHORT VERSION.pdf]] -- GERMAN''' Chances and Risks of Mobile Health Apps" to compare to cMHAFF. (HARRY RHODES)
 
**'''[https://www.gov.uk/government/publications/medical-devices-software-applications-apps UNITED KINGDOM Guidance]''' Guidance for medical device stand-alone software, including apps, from UK Medicines and Healthcare Products Regulatory Agency (MHRA) (ADAMU)
 
**'''[https://appcheck.de/kriterienkatalog GERMAN Assessment Criteria for health-related apps]''' These are mostly intended for developers to use in self-assessment, but the assessments also contain reviews by a third party. (UNASSIGNED)
 
**'''[[File:National authorisation criteria of Finnish PHR v2.2 Nokia Translation.xlsx]]''' -- '''FINNISH''' National Authorisation (Certification) Criteria for PHR (unofficial translation into English)  Contains approximately 80 criteria in 6 categories. (NATHAN BOTTS)
 
**'''[[File:Draft guidelines mhealth apps_not for publication_DTao_Comments.docx]]''' -- Draft mHealth Guidelines from a project not completed in EU (unpublished, not for distribution), with a mandate "to develop guidelines for assessing the validity and reliability of the data that health apps collect and process." While the project was never completed, there was a report on the work (UNASSIGNED)
 
***'''[[File:ReportofmHealthWorkingGroup-June2017cleanpdf.pdf]]''' of which page 6 summarizes 13 categories for assessment that were discussed, of which six had a higher degree of consensus than others.
 
***'''[[File:Assessment Questionnaire.xlsx]]''' -- Assessment Questionnaire from a project not completed in EU (unpublished, not for distribution)
 

Latest revision as of 20:21, 10 August 2017

Attendees: David Tao, Adamu Haruna, Gary Dickinson, Nathan Botts, Vanessa Batoon

AGENDA

  • Review of recommendations re French Good Practice Guidelines: Reliability (Adamu) -- Adamu's recommendations were discussed, and dispositions were agreed upon. David will incorporate them into the next draft of cMHAFF.
  • Review latest draft of cMHAFF: File:CMHAFF STU Ballot Draft.docx
    • Section 3.3.1.1, Informing Consumers/Users section, review conformance statements. Logically group them, decide upon conformance strength and whether there are too many (currently 24). When trying to add ideas from many sources, cMHAFF grows larger and larger. Decision was to consolidate some duplicates that were noticed, and to group them into subcategories (e.g., General Info, Payment, Limitations, Evidence/Credentials, etc.) so there is not just one long undifferentiated list.
    • Specific comment numbers discussed:
      • DKT10 narrative introductions for each category? YES, this should be added.
      • DKT20 style/wording decision throughout -- refer to "app," "product," or...? Explain that they are synonymous, but change wording to consistently use "App" in conformance statements.