“Patients have the ability to electronically submit patient-generated health information” should be part of Meaningful Use Stage 3. It suggested that PGHD could be submitted through structured or semi-structured questionnaires and secure messaging and, depending on input from the HITSC, possibly through devices.”

Click to access pghd_brief_final122013.pdf

Patient generated health data (PGHD)

• Health history, symptoms, biometric data, treatment history, lifestyle choices, and other information—created, recorded, gathered, or inferred by or from patients or their designees (i.e., care partners or those who assist them) to help address a health concern.

Demographics data: Age, sex,race

Genomics data: Patient rights and ownership of genomic pattern data

Protocol with clinician when capturing PGHD

• Advise that physicians have a patient-clinician agreement and consent form that is discussed with and signed by each patient before engaging in electronic communication

Secured mobile application connection: Data security

• Enforce strong VPN encryption, authentication and granular access policies to ensure that access to data is secure. Secure on-device data with policies to allow or disallow intranet file download, and on-device file share, copy and print.
• ———-

Motherhealth mobile health application is seeking investors, doctors, developers and collaborators to match, monitor and report patient generated health data, includes telemedicine, personalize medicine and more.. Email Connie at motherhealth@gmail.com

Address: Motherhealth at 1708 Hallmark Lane San Jose, CA 95124

WCAG 1.0 consist of 14 guidelines—each of which describes a general principle of accessible design. Each guideline covers a basic theme of web accessibility and is associated with one or more checkpoints that describes how to apply that guideline to particular webpage features.

• Guideline 1: Provide equivalent alternatives to auditory and visual content
• Guideline 2: Don’t rely on colour alone
• Guideline 3: Use markup and style sheets, and do so properly
• Guideline 4: Clarify natural language usage
• Guideline 5: Create tables that transform gracefully
• Guideline 6: Ensure that pages featuring new technologies transform gracefully
• Guideline 7: Ensure user control of time sensitive content changes
• Guideline 8: Ensure direct accessibility of embedded user interfaces
• Guideline 9: Design for device independence
• Guideline 10: User interim solutions
• Guideline 11: Use W3C technologies and guidelines
• Guideline 12: Provide context and orientation information
• Guideline 13: Provide clear navigation mechanisms
• Guideline 14: Ensure that documents are clear and simple

Each of the in total 65 WCAG 1.0 checkpoints has an assigned priority level based on the checkpoint’s impact on accessibility:

• Priority 1: Web developers must satisfy these requirements, otherwise it will be impossible for one or more groups to access the Web content. Conformance to this level is described as A.
• Priority 2: Web developers should satisfy these requirements, otherwise some groups will find it difficult to access the Web content. Conformance to this level is described as AA or Double-A.
• Priority 3: Web developers may satisfy these requirements to make it easier for some groups to access the Web content. Conformance to this level is described asAAA or Triple-A.

Click to access HITJC_PMTF_Presentation_2016-05-17_update_2.pdf

This slideshow requires JavaScript.