Does Suki Work With MEDITECH Expanse?

In two layers, which is how every real MEDITECH integration is built.

The read layer uses MEDITECH's FHIR APIs, the same US Core FHIR R4 surface that MEDITECH exposes to any developer through Greenfield Workspace. This gives Suki the schedule and patient context so a clinician records against the right encounter. Greenfield is described by MEDITECH as view only and patient authorised, which is enough to build a demo and not enough to put anything into the chart.

The write layer is the Expanse Documentation APIs, and that is the part that required an Alliance relationship and that Suki was first to ship. The note Suki generates is delivered into the Expanse document, where the clinician reviews and signs it in the normal workflow. Suki's dictation works inside Expanse fields, which was part of the 2024 release.

Two things to confirm with Suki and MEDITECH together. First, which Expanse release the Documentation APIs need, because a hospital a release or two behind may have an upgrade in its critical path. Second, who raises the enablement request. If you are on MEDITECH as a Service, MEDITECH runs the environment and the request goes through MEDITECH's queue rather than yours.

• Ambient documentation. Suki records the visit, drafts a specialty specific note and delivers it into the Expanse document for review and signature. This is the July 2025 capability.
• Dictation. Voice to text inside Expanse fields, which is the 2024 capability and the one that gives clinicians an immediate reason to keep the app open.
• Coding suggestions and patient insights. Generated in Suki from the note and the chart; whether they reach Expanse charge workflows is not published.
• Ambient orders and mobile. Announced as coming in the July 2025 release. Treat as roadmap until shown on your instance.

For a community hospital the practical question is how many clicks sit between the Suki draft and a signed Expanse note, and whether edits happen in Expanse or in Suki. The ambient scribe use case page lists the pilot measurements. Because MEDITECH has not shipped a competing in house scribe, Suki on Expanse is being sold into a gap rather than against a bundled incumbent, which is a better position for a buyer than on Oracle Health.

Four approvals, and at a community hospital the constraint is people rather than technology.

• Tenant enablement. Suki's application enabled on your Expanse environment with the API access it needs. On MEDITECH as a Service, MEDITECH performs this on request.
• The Documentation APIs. Confirm your release supports them and whether an upgrade is needed first.
• The business associate agreement. Suki signs one. Start it in week one and settle audio and transcript retention, subprocessors and model training; the HIPAA and AI compliance page lists what to insist on.
• A real security review covering the mobile app, device management, where audio is processed and access logging.

The MEDITECH Alliance includes consulting firms, and using one to carry the integration work is a legitimate answer for a hospital with a two person IT team. Decide that early. Our hospitals page covers what small team resourcing does to an AI programme, and our HIPAA compliant AI scribe checklist keeps the compliance items from being left until the end.

Not published, checked September 2026:

• The minimum Expanse release for the Documentation APIs integration.
• Whether an in context SMART launch inside Expanse is available or whether the Suki app runs alongside.
• Whether ambient order generation and mobile integration, announced as upcoming in July 2025, are live.
• Whether coding suggestions reach Expanse charge workflows.
• Pricing. Suki is a per clinician subscription priced on request; the Suki pricing page records what is public.

On the competitive side, Microsoft's Dragon Copilot has been integrated in Expanse since 2024 and Microsoft is also on the Alliance roster, so on MEDITECH the choice is a real one between two established partners rather than a displacement of a first party product. MEDITECH's own AI work with Google went into chart search and summarisation, not ambient capture. That leaves you comparing Suki and Microsoft on where the note lands, how the app launches, price and audio handling, which is the comparison our AI medical scribe comparison sets up.

1. Which Expanse release do the Documentation APIs need, and does our environment meet it?
2. Show the note landing in the Expanse document on our version, and show a clinician editing it there.
3. Is there an in context launch inside Expanse, and on which releases?
4. Which of ambient orders and mobile integration are live today?
5. Give three Expanse references, including one on MEDITECH as a Service and one at a hospital of our size.
6. Where is audio processed and stored, for how long, and does any of it train shared models?
7. What is the per clinician price, the minimum term, and are any MEDITECH fees passed through?

Our EHR integration questions for AI agents has the full list in procurement ready form.

A comparison between the two established Expanse partners, run on your encounters, and a plan that fits your hosting model and release schedule.

Suki and Microsoft are both Alliance members with production Expanse integrations, and they differ in ways that decide adoption: where the note lands, whether the app is embedded, how dictation behaves, and how each is priced when a Microsoft agreement already exists. A community hospital rarely has the staff to run that comparison properly alongside everything else. Our vendor selection service runs it on your instance with no vendor commission, and the ROI calculator tells you what either option has to deliver to pay for itself.

If you have a date, book a call before it and we will tell you what to put in the contract.