> Markdown version of [/jobs/ext/4743883-clinical-systems-ai-lead](https://www.wearedevelopers.com/jobs/ext/4743883-clinical-systems-ai-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Clinical Systems & AI Lead - **Company:** MEDMATCH INC - **Location:** Novi, MI, United States - **Experience:** Expert - **Salary:** $70,000 - $95,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Backup Devices, Custom Software, Systems Integration - **Published:** November 16, 2026 - **Apply:** https://www.juju.com/job/15_fa1dd3942 ## About the Role * Demonstrated EHR administration or advanced super-user work: show what you personally configured, improved and taught. * Direct APRIMA experience is strongly preferred; comparable ambulatory EHR expertise is considered. * Nursing, MA or other hands-on clinical experience is valuable, but strong clinical-workflow understanding can also be demonstrated through implementation and training work. * We value calm troubleshooting, clear documentation, respectful teaching, discretion and completion of practical projects. * AI implementation, reporting, revenue-cycle or interoperability experience is a plus-not a requirement to be expert in all of them. ## Description * Manage day-to-day EHR configuration, task routing, templates, reporting, user onboarding and role-appropriate access. Improve referral intake, scheduling, documentation, orders, results and follow-up workflows. Observe both office and field work, teach users patiently, maintain clear procedures, and coordinate vendor escalation. Measure whether changes reduce rework, improve follow-through and save staff time. Responsible AI and automation: * Lead focused pilots for documentation assistance, document handling, communications and other approved workflows. * Evaluate privacy, clinical accuracy and user experience before broader deployment. * AI-generated clinical content remains subject to clinician review and authentication; automation must not independently diagnose, prescribe or make unreviewed clinical decisions. * Use approved systems, documented permissions and appropriate contractual/privacy safeguards. A realistic technical boundary: * You are the internal owner of clinical applications and workflow, not the sole infrastructure engineer, cybersecurity specialist or custom software developer. * Coordinate networking, backups, security and complex integrations with qualified IT and vendor specialists. * Work with practice leadership on priorities and approvals; clinical policy remains with licensed clinicians.