Table 4.
Site electronic health record access.
| Description | Respondent | |
|---|---|---|
| CRC | CRIO | |
| Is the EHR at your site FHIR-enabled, i.e., is the EHR capable of sending data to and receiving data from other institutions for routine clinical care/treatment purposes? | ||
| Yes (in use now) | 8(42) | |
| No, but in development now | 4(21) | |
| Does your institution use FHIR to exchange patient data with other organizations for routine clinical care/treatment purposes? | ||
| Yes (in use now) | 4(21) | |
| No, but in development now | 6(32) | |
| Which method do you use to provide access to source data? We print paper copies of the EHR data | 6(27) | |
| We provide a guest / temporary log-in to the EHR with read-only access | 17(77) | |
| We provide “over the shoulder access” to the EHR | 6(27) | |
| We provide access to a shadow chart | 4(18) | |
| We do not provide any access to source data in the EHR/chart | 0(0) | |
| Where would software that requests data from the EHR FHIR server need to be installed to comply with your institution’s policies? | ||
| Our policies require that such software be installed behind our institution’s firewall | 8(42) | |
| Our policies allow such software to be hosted by the Sponsor for the study | 1(5) | |
| Our policies allow such software to be hosted by a third-party for the study (i.e., a data coordinating center; not the Sponsor or the site) | 1(5) | |
| All of the above would comply with our institution’s policies | 9(47) | |
CRC, clinical research coordinator; CRIO, chief research information officer; EHR, electronic health record; FHIR®, Fast Healthcare Interoperability Resources.
Cells values are n (%).