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

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

From HL7Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
 
'''AGENDA:'''
 
'''AGENDA:'''
 
*Review/Approve specific content changes
 
*Review/Approve specific content changes
**DKT4  New decision tree -- is this a good basis?
+
**DKT4  New decision tree -- is this a good basis? -- Yes, the format of the diagram is good. Will be redrawn to point to cMHAFF categories. Add a branch to triage, up front, applications that are in or out of scope. Limit the number of branches.  
**DKT11 Any recommendation on a "secure coding" reference?
+
**DKT15  Should Usability conformance criteria be consolidated? -- No, they were left as is, but Accessibility will be called out
**DKT15  Should Usability conformance criteria be consolidated?
+
**DKT32  Is automatic timeout justified as SHALL? -- Changed to SHALL[IF]
**DKT32  Is automatic timeout justified as SHALL?
+
**DKT36-37  "syncing" data and "pairing" of devices: should they be within the same section? -- Yes, OK
**DKT36-37  "syncing" data and "pairing" of devices: should they be within the same section?
+
**DKT40-42  new "Interoperability" section: should more be said? -- yes, also deal with context of discrete data; unstructured data.
**DKT39  decision on what to do with provenance discussion
 
**DKT40-42  new "Interoperability" section: should more be said?
 
**DKT48  revisit "Conditions and Agreements" and how it differs from "Informing Consumers/Users"
 
**DKT54  Is there a good starting point or reference for a Glossary? Should we have our own?
 
**DKT55  Should Windows platform considerations be included or not?
 
*San Diego September HL7 WGM considerations
 
**Review preliminary cMHAFF presentation for September (San Diego) HL7 WGM
 
**Plan which topics are most in need of discussion for face-to-face time in San Diego
 
  
 
'''NEXT WEEK'''
 
'''NEXT WEEK'''
 
*Nathan agreed to recommend which (if any) criteria from Finland should be added to cMHAFF. This will be done on August 31st.  
 
*Nathan agreed to recommend which (if any) criteria from Finland should be added to cMHAFF. This will be done on August 31st.  
 
**'''[[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: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)

Latest revision as of 18:58, 31 August 2017

ATTENDEES: Adamu Haruna, Gary Dickinson, David Tao

AGENDA:

  • Review/Approve specific content changes
    • DKT4 New decision tree -- is this a good basis? -- Yes, the format of the diagram is good. Will be redrawn to point to cMHAFF categories. Add a branch to triage, up front, applications that are in or out of scope. Limit the number of branches.
    • DKT15 Should Usability conformance criteria be consolidated? -- No, they were left as is, but Accessibility will be called out
    • DKT32 Is automatic timeout justified as SHALL? -- Changed to SHALL[IF]
    • DKT36-37 "syncing" data and "pairing" of devices: should they be within the same section? -- Yes, OK
    • DKT40-42 new "Interoperability" section: should more be said? -- yes, also deal with context of discrete data; unstructured data.

NEXT WEEK