Cerner Millennium Integration Specialist (APIs)

About the Role We're building an AI-powered clinical documentation and decision-support application that integrates directly into Cerner Millennium (Desktop) for physicians at major hospital systems. We've already proven the core workflow - launching our application from within Cerner with patient/encounter context, and writing structured clinical data back via HL7 - but we've hit the limits of what HL7-based integration can do for user experience and data fidelity. We're looking for a Cerner integration specialist who has done this before and can take us from "it technically works" to a production-grade, physician-friendly integration. What We've Built So Far - Launching our web application from inside Cerner into a new browser window/tab, carrying over the relevant Cerner context (patient, encounter, provider) - Pushing data back into Cerner using HL7 interfaces What's Not Working - User experience: Opening in a separate browser window breaks the clinical workflow. We need our application embedded directly inside the Cerner interface. - Data fidelity: HL7 is too limited and rigid for what we need. We're struggling to land formatted text and codified data cleanly into the correct discrete fields in Cerner. What You'll Do - Design and implement a way to embed our web application inside Cerner Millennium (e.g., via AMP pages, MPage/SMART on FHIR, or other Cerner-native embedding mechanisms) so physicians never have to leave Cerner - Build the integration to pull patient/encounter context and clinical data out of Cerner via FHIR APIs - Build the integration to push data back into Cerner via FHIR APIs, including: - Free-text fields: chief complaint, duration of illness, history of present illness, physical examination - Codified/discrete data: diagnoses, orders, allergies, medications - Advise on and resolve any Cerner-specific constraints around document signing status, write-back permissions, and data validation - Work closely with our engineering team to replace or supplement the existing HL7 pipeline with FHIR-based read/write workflows Required Experience - Multiple years of hands-on experience implementing on Cerner Millennium (not just consuming Cerner data - actual implementation/build experience) - Proven track record embedding third-party web applications inside Cerner, using AMP pages, CCL scripts, MPage, and/or SMART on FHIR - Deep, practical experience with Cerner FHIR APIs - both fetching data from Cerner and writing data back into Cerner - Demonstrated experience pushing codified clinical data into Cerner - specifically diagnoses, orders, allergies, and/or medications via API (not just HL7 feeds) - Solid understanding of Cerner Millennium's data model and how it maps to FHIR resources (e.g., Condition, MedicationRequest, AllergyIntolerance, ServiceRequest, DocumentReference) - Comfortable working with hospital IT/security teams on credentialing, scopes, and compliance for API access Nice to Have - Experience working with Cerner's developer/partner program (Cerner Code/Oracle Health developer portal) - Familiarity with SMART on FHIR app launch sequences (EHR launch vs. standalone launch) - Experience in Middle East or other international healthcare markets - Background in clinical documentation, RCM, or AI-assisted charting products How to Apply Please apply only if you meet the required experience above, and include specific examples of: - A Cerner integration where you embedded a third-party application inside Cerner (AMP pages/CCL/MPage/SMART on FHIR) - A project where you pushed codified data (diagnosis, orders, allergies, or medications) into Cerner via API