What is Juno EMR?

The short answer

Juno EMR is a cloud-hosted electronic medical record used by Canadian clinics, family practice among them. It is a branch of OSCAR, the open-source EMR released by McMaster University, maintained with a focus on stability, cloud hosting, and third-party integrations. Juno EMR Services hosts and supports it, and the product now sits within WELL Health.

Being externally hosted means you do not run a server, patch anything, or arrange your own backups. It is also why Juno leans harder on integrations than the older OSCAR variants: the platform is maintained centrally, so connecting things to it is a supported activity rather than a favour.

If you want the wider picture, the OSCAR guide maps how Juno relates to OSCAR Pro, Avaros, Open OSP, and the original McMaster release.

What “integrates with your EMR” is worth asking about

Juno’s pitch is integrations, and clinics on Juno tend to have already connected a booking tool, a lab feed, or an eForm library. So you have probably heard a vendor say they integrate with your EMR. It is worth knowing what that sentence usually means.

Most clinical tools integrate one way. They take something from the visit, produce an output, and write it back. A scribe records the encounter and pushes a note into your progress note. That is a real integration and it saves you typing, but the tool never reads your chart, so it cannot know what is already on the problem list, which medication you renewed in March, or what the last clinician flagged for follow-up.

Two-way is the harder version. The tool reads the chart, uses what is there, and writes structured data back into the right places. That is what decides whether a suggestion is grounded in your patient or generated from the last twenty minutes of conversation.

When a vendor says they integrate with Juno, the question is which of those two they mean.

Where the work actually piles up

Juno inherits the OSCAR chart model, and it shapes the day more than any interface choice.

The encounter note is a single free-text progress note in one box, with no separate Subjective, Objective, Assessment, and Plan fields to fill. Writing the note is quick.

The standing record sits apart from the note, in the Cumulative Patient Profile: Ongoing Concerns, Medical History, Social History, Family History, Reminders, and Risk Factors. Oscar’s own documentation is explicit that encounter notes do not belong there. Each CPP section is maintained by hand, one overlay at a time, and none of it is filled by a scribe that only writes notes.

So a one-way integration solves the fast part of documentation and leaves the slow part alone.

What Medulla does with the same connection

Medulla reads the visit and the chart together, then proposes the updates the visit calls for: new diagnoses, medication changes, care plan items, follow-ups. Each is a checkbox you accept or discard, and the accepted ones go into the chart in one click. A dozen overlays become a single review.

Nothing reaches the record on its own, and you can discard all of it. Because Medulla reads the chart as well as writing to it, billing and diagnostic code suggestions come from what is in the record rather than from the conversation alone.

If you already run a scribe alongside Juno, this is the work it leaves you. It writes the note and stops, and the CPP is still yours to fill one overlay at a time.

The gap is widest on a first visit with a new patient, where nearly everything said belongs in the CPP rather than the note. Medulla turns that forty minute meet and greet into a fifteen minute one, and it does it through the same connection your other integrations use, reading the chart rather than only writing to it.

Where Medulla fits

Medulla runs inside the encounter you already have open, on Med Access and Oscar-based EMRs including Juno, Oscar Pro, Oscar 19, Open OSP, and Avaros. No separate tab, and no copy and paste between a scribe and your chart.

See it on your own charts. The trial is free for a month with no credit card required.