| EHR | Cloud or On-prem | General Process | Fees required | Additional forms that need to be completed? | Data Landing Frequency |
| Nextech | Cloud | Practices will need to create a ticket with NT support to ask them to add their data to the DataDerm feed. Practices will have to sign a form giving consent. | None | Form will be accessed via contacting Nextech support | Weekly |
| Nextech | On-prem | Practices will be able to use the PULL client. | None | Technical questionnaire + Nextech credentials request | Weekly |
| eClinical Works | Cloud | New practices will need to pay an initial database setup fee of $3K and then an annual fees/per provider fee of $300 and contracts. Practices will need to also complete the PHA Adaptor form and provide their eCW APU ID. This process will trigger eCW to begin transferring data to DataDerm. | One time database setup fee = $3,000 + Annual eCW fee of $300 per clinician | PHA Adaptor Form | Weekly |
| eClinical Works | On-prem | Practices will be able to use the PULL client. | None | Technical questionnaire | Weekly |
| Encite | On-prem only | New Encite users will be required to complete registration with Encite every year as well as the Annual fee of $125 per clinician. Practices will be able to use the PULL client. If the practice allows Encite to manage their data, Encite will set up the PULL client. If the practice hosts/manages their own data server, the practice will be responsible for setting up the PULL client. |
Encite required annual fee of $125 per clinician which will be obtained at the time of the MIPS module purchase. | None | Weekly |
| Nextgen | Cloud or on-prem | Practices will be able to use the PULL client. | None | Technical questionnaire | Weekly |
| Allscripts/Veradigm | Cloud or on-prem | Data will need to be sent via the API. Specific details still TBD. Fees apply for the registration and use of the API on the user side. | Fees apply but unsure of what they are. Working to confirm with Veradigm. | TBD | TBD |
| CGM (Aprima, eMDs) | On-prem | Practices will be able to use the PULL client. | None | Technical questionnaire | Weekly |
| Medent | Cloud | Practices will need to inform Medent that they want their data to be sent to DataDerm. Medent will then be responsible for pushing QRDA files to DataDerm. | None | No form, but need to request this from Medent support. | Daily |
| ModMed | Cloud | Automatic monthly data dumps via the API feed after practice/clinician authorizes the sharing of their data to DataDerm. | None | No form but need to follow instructions in email to authorize data sharing with DataDerm. | Monthly - TBD |
| Epic | Cloud only | Practices will need to set up a push data feed to push data based on the DataDerm specification. | Depends on institute/practice | Need to develop push queries for Epic - piloting with several sites. | Depends on institute/practice - preference is monthly. |
| Other EHRs | On prem | Practices will be able to use the PULL client. | None | Technical questionnaire | Weekly |
| Other EHRs | Cloud | Push data to DataDerm per the specifications outlined in the Data Push specification document which can be provided at request. Please contact dataderm@aad.org for additional information. | Depends on EHR's policy | Depends on EHR's policy or whether practice will be responsible for sending the files | Monthly - TBD |