Migrate from Suki to Eclinicalworks.

Suki and eClinicalWorks both produce a drafted clinical note from the ambiently captured visit. A practice on eClinicalWorks can retire the standalone Suki contract by switching to the EHR-family's own ambient scribe, Sunoh.ai: it listens to the patient-provider conversation, categorizes the dialogue into Progress Note (SOAP) sections, and pre-fills coded and uncoded allergies, diagnoses, treatment plans, plus labs, imaging, procedures, medication orders, and follow-ups; the provider reviews and imports directly into the Progress Note inside eClinicalWorks (desktop EHR, eClinicalTouch on iPad, eClinicalMobile). Because the draft lands in the same encounter the EHR already uses for orders and coding, there is no separate Suki login or paste-back. Keep eClinicalWorks; cut the standalone Suki.

Suki suggests visit codes (ICD-10, HCC, CPT, E/M) from the documented encounter; eClinicalWorks does coding natively inside the EHR. A practice on eClinicalWorks can drop Suki's coding by relying on the eCW Clinical Rules Engine (CRE), which automatically suggests/drops the appropriate codes from the clinical documentation as encounters are completed and feeds them into the integrated charge/claim workflow on the same chart; the embedded eva assistant can also be invoked in-context during documentation. Let eClinicalWorks generate and attach the codes at encounter close instead of pulling them from Suki. Keep eClinicalWorks; cut the standalone Suki.