Table 1.

EHR vendor survey responses (N=6)

Question	Answer	Number (%)
Does your EHR allow for PGHD to be ingested? (N=6)	Yes No	5 (83) 1 (17)
n=5 below
Do you allow for a bring your own device (BYOD) model?	Yes No	4 (80) 1 (20)
To process and manage PGHD does your EHR require custom-built or pre-built functionality, or both?	Both	5 (100)
Is PGHD inclusion part of the original contract with clients or an add-on?	Original contract Add-on	3 (60) 2 (40)
Can PGHD be received outside of the patient portal?	Yes No	3 (60) 2 (40)
Is PGHD accessible by providers/health system to intervene?	Yes No	4 (80) 1 (20)
Does your EHR have functionality to notify providers regarding PGHD (e.g., exists, needs action, or is out of range)?	Yes No	3 (60) 2 (40)
Does your EHR have functionality to notify patients regarding PGHD (e.g., exists, needs action, or is out of range)?	Yes No	3 (60) 2 (40)
Does your EHR have the capability to send patient data from the EHR to mobile health apps?	Yes No	5 (100) 0 (0)
Does your EHR allow for the push/active or pull/passive transfer of PGHD?	Push, active and pull Passive	4 (80) 5 (100)
What technical approach to PGHD integration does your EHR support?	HL7 FHIR Standardized APIs Web services	4 (80) 4 (80) 3 (60) 4 (80)
Does your EHR use design schemas such as Open mHealth? (OmH; IEEE P1752 standards process)?	Yes Not sure No	0 (0) 4 (60) 2 (40)
What platforms does your EHR partner with to integrate PGHD?	iOS HealthKit Android Google Fit Other	5 (100) 2 (40) 3 (66)
Does your EHR have the ability to translate PGHD in different languages?	Yes Not sure No	1 (20) 1 (20) 3 (60)
Does your EHR have the ability to consume PGHD in different languages?	Yes Not sure No	1 (20) 1 (20) 3 (60)
Are there readily available resources through your patient portal for patients about PGHD?	Yes Not sure No	3 (60) 1 (20) 1 (20)
Patients have the ability to easily connect to supported devices without practice assistance or tech support Patients require a clinic to activate prescribed devices	Yes Yes	3 (60) 3 (60)