For many family practices in BC, OSCAR is not simply the software where the chart lives. Over years of use, it becomes part of how the clinic operates.
Templates have been refined. Billing routines have become familiar. Staff know which inbox to check, which status means something needs another look, and where a physician tends to leave information for an MOA. Someone knows that a particular referral should stay visible until the specialist office responds, even if that expectation exists partly as a clinic habit rather than a formal workflow.
Some of those habits are efficient. Others are compensations.
That is what makes choosing an OSCAR alternative different from choosing an EMR for a new clinic. An existing practice is not starting with a blank slate. It has years of patient data, schedules, templates, billing routines, open referrals, pending results, reminders, reports, and staff knowledge tied to the way it currently uses OSCAR.
The question is not simply, “Is there a better EMR than OSCAR?”
It is: Would another system support the way our clinic needs to work now better than the combination of OSCAR and the habits we have built around it?
For a BC family practice seriously considering switching from OSCAR, that is the comparison worth making.
Why clinics start looking for an OSCAR alternative
A clinic does not necessarily start looking because its current EMR has suddenly stopped working.
Often, the friction accumulates gradually.
The practice grows. More physicians join. Staff responsibilities shift. Referral volume increases. A process that worked when two experienced people understood the clinic’s conventions becomes harder when a locum or new MOA needs to pick it up.
At the same time, small workarounds can become permanent.
A physician leaves a result in a particular inbox state because patient follow-up still needs to happen. An MOA maintains another way of tracking referrals that have been sent but not yet acknowledged. A clinic manager asks several people what is outstanding because the answer is distributed across individual queues, reminders, notes, and memory.
None of this means every OSCAR clinic should switch. Many practices have built workflows around OSCAR that serve them well, and familiarity has real value. So do templates that genuinely save time, billing processes staff can execute efficiently, and routines the whole team understands.
But familiarity also makes it easy to normalize friction.
Before evaluating an OSCAR EMR alternative, a clinic should separate two things that can look very similar after years of use:
Workflows worth preserving are routines that make the clinic better at its work.
Compensations worth questioning are routines that exist because someone has to make up for something the system does not make clear enough.
That distinction should shape the entire comparison.
Do not compare only features. Compare what your clinic has built around OSCAR.
An existing OSCAR clinic already knows it needs documentation, billing, referrals, results, tasks, messaging, and reporting. The more useful question is what the clinic has built around those functions over time.
Which templates are genuinely useful, and which are simply inherited?
Which billing routines are efficient, and which only feel efficient because staff have repeated them for years?
Which inbox habits are doing double duty as reminders?
Which reports does the clinic actually depend on?
Which processes would staff be frustrated to lose?
And which ones should not be recreated in a new EMR because they exist only to compensate for the current setup?
A feature proves that something can be done. It does not tell you how well the clinic can understand what happens afterward.
That matters most for work that spans several steps: a referral that has been sent but not accepted, a result that has been reviewed but still requires a patient call, or a task that another staff member needs to pick up next week.
The strongest OSCAR alternative is not necessarily the system that reproduces every existing workflow. Sometimes reproducing everything means migrating the clinic’s workarounds along with its records.
Use the ten-item test before you compare vendors
One practical exercise can make an EMR evaluation much more revealing.
Call it the ten-item test.
Before a demo, take ten real pieces of unresolved work from your clinic. Do not invent ideal scenarios. Use the awkward, ordinary things your team is actually carrying right now.
For example:
a specialist referral sent two weeks ago with no acknowledgement yet
a referral returned because more information is required
a result that has been reviewed but still requires a patient appointment
a callback assigned to an MOA who will be away tomorrow
a form waiting for information from the patient
a task the physician needs to complete after another team member acts
a reminder whose meaning is obvious to one experienced staff member but not to anyone else
an item being kept in an inbox because removing it would also remove the reminder to follow up
a billing issue that still needs correction
a piece of work that appears finished in the chart but that staff know is not actually finished
Then ask the prospective vendor to show you exactly where each item would live in the new system.
Do not accept “we have tasks” or “we support referrals” as the answer. Follow the work through.
Who would see it? How would they know its current state? Could another staff member cover it? What happens while the clinic waits for an outside response? What makes the item disappear? Can a manager find it without knowing who to ask?
Then use one question repeatedly:
“If I opened the system tomorrow with no prior context, how would I know these things were still open?”
This test shifts the demo away from polished feature tours and toward the operational reality your clinic is actually considering changing.
Compare how open referrals and pending results are represented
Referrals and results are particularly useful comparison points because the first recorded action rarely tells the whole story.
A referral can be sent while the clinic still needs to know whether it was received, accepted, declined, delayed, redirected, or returned for more information.
When evaluating an OSCAR alternative, ask the vendor to show what those different states look like in practice.
Can staff see why a referral is waiting? Is there a clear next step? Can responsibility move between people without losing context? If nothing has happened for several weeks, how does the clinic know that silence now requires attention?
Apply the same test to results.
Reviewing a result and completing the work created by that result are not always the same thing. A physician may review a result and decide the patient needs an appointment, another test, or a phone call. The clinical review is complete, but there is still work to do.
If your current OSCAR workflow uses an inbox state, note, reminder, task, or staff convention to keep that follow-up visible, show the vendor exactly how you do it today. Then ask what replaces that behaviour.
The useful comparison is not whether both systems can receive and review results. It is whether the follow-up created by the result remains understandable until it is completed.
Compare ownership and staff coverage without local knowledge
Long-standing staff can make almost any workflow look more obvious than it really is.
An experienced MOA may know that one physician uses a particular inbox in a particular way, that a certain note means “check again Thursday,” or that an item assigned to one person is actually waiting for somebody else.
Then that person takes vacation. Or a new MOA starts. Or a locum arrives on Monday morning.
When comparing a family practice EMR, remove that local knowledge from the scenario.
Can another staff member tell who owns the next action and see enough context to cover it? Can they distinguish something intentionally waiting from something nobody has touched?
This is also where a clinic manager should test visibility. Ask the vendor to show how a manager would answer a practical question such as: What work has been waiting the longest, and why?
The goal is not to monitor every action. It is to reduce the number of situations where the only way to understand the work is to find the person who already knows the story.
Compare BC billing and documentation by testing what you already do
For an existing OSCAR clinic, the billing and documentation question is not simply whether a prospective BC EMR supports billing or templates.
The clinic already has workflows in both areas. The useful comparison is which ones are worth carrying forward.
Start with documentation.
Make a list of the templates clinicians actually use. Which ones save meaningful time? Which contain information or structure the clinic would want to preserve? Which have accumulated fields or steps nobody would choose if building them today?
Do the same with billing.
Ask staff to identify their most common billing workflows, the exceptions that take the most time, the reports they depend on, and the routines they use to catch or correct unfinished work. Then have vendors demonstrate those scenarios rather than a generic billing sequence.
A useful set of questions is:
Which current routines are truly efficient?
Which ones are merely familiar?
Which workflows would staff be frustrated to lose?
And which should not be rebuilt because their only purpose is to work around the current setup?
A clinic should not discover after launch that a workflow staff used 40 times a day technically still exists, but now takes twice as many steps or depends on a workaround nobody anticipated.
Switching EMRs should not require a clinic to abandon every practice it has refined over the years. But neither should migration become an exercise in faithfully recreating every workaround.
For an EMR serving a BC family practice, local workflow fit should be demonstrated with the clinic’s real billing, reporting, and documentation requirements rather than assumed from a feature checklist.
Compare usability when the clinic is busy
An EMR demonstration is usually calm. A family practice usually is not.
The useful usability questions are therefore mundane.
An MOA is interrupted while working on a referral. Can they return and understand where they left off?
A physician reviews a result between appointments. Can they create or hand off the next action without turning the result itself into a reminder?
Someone covers another employee’s desk over lunch. Can they understand what requires action without opening several screens or asking the usual owner?
A locum starts the day. Can they distinguish work requiring their attention from items that are simply present in an inbox?
Pay particular attention to tasks staff perform repeatedly. Small friction repeated 30 or 40 times in a day may matter more than an impressive feature used twice a year.
The question is not whether the new interface looks cleaner. It is whether the clinic day becomes easier to understand when attention is divided.
Compare migration of active work, not just historical records
Migration is where an existing OSCAR clinic has a fundamentally different problem from a new practice choosing its first EMR.
The clinic is not only moving charts.
It may also need to account for schedules, templates, billing information, reports, open referrals, pending results, reminders, partially completed tasks, and work entered during the transition itself.
Doctors of BC describes EMR migration as a complex process and recommends early planning with vendors around data preparation, timelines, testing, potential effects on operating hours, and post-migration support. Its accompanying conversion checklist specifically recommends clarifying what data can be converted, testing how data will appear in the new system, planning for items that will not migrate, identifying reports that should be retained, and addressing financial information and periods when the EMR may be unavailable.
For clinics planning a switch, the relevant resources are Doctors of BC’s How to Prepare for an EMR Data Migration and EMR Data Conversion Checklist.
For an OSCAR clinic, use that planning process to ask a more operational question: what will happen to the work that is open on the day we switch?
Pick several real examples.
A referral was sent ten days before migration and is still awaiting a response. Where will it appear afterward?
A result has been reviewed but the patient has not yet been reached. How will the remaining follow-up be identified?
An appointment has already been scheduled. A billing issue still needs correction. A reminder exists because somebody needs to check something in three weeks.
Do not assume that because historical chart data transfers, the meaning attached to these open items will transfer with it.
Ask both the current and prospective vendors what will migrate, what will not, what may look different, what requires manual reconciliation, and how the clinic will validate the result before normal operations resume.
Migration should preserve records. A safe operational transition also requires knowing what unfinished work must be deliberately carried across.
The strongest questions to ask before switching from OSCAR
Instead of bringing a long feature checklist to demos, group your questions around the parts of your current clinic that are hardest to reproduce.
Open work and follow-through
Using our ten-item test, show us exactly where each unresolved item would live and how we would know it still needs attention.
How are referrals and results represented when the first action is complete but follow-up is not?
What causes an item to be considered finished or removed from view?
Ownership and coverage
Can another physician or MOA understand and cover someone else’s open work without knowing our local conventions?
Can a clinic manager see what is waiting, who owns it, and where work is getting stuck without asking several people?
BC workflow fit
Show us our common billing, documentation, template, and reporting workflows—not generic examples. Which parts would change?
Which of our existing templates and routines can be preserved, and which should we reconsider rather than recreate?
Migration and compensation
What happens to schedules, billing information, templates, historical records, open referrals, pending results, tasks, and reminders during migration?
After switching, which of our current spreadsheets, inbox habits, paper lists, or manual checks should no longer be necessary?
That final question is particularly revealing.
Every clinic will still have exceptions, judgment calls, and processes that sit outside an EMR. The goal is not to eliminate every workaround.
But if a new system leaves the clinic maintaining the same side lists, remembering the same handoffs, and using the same inbox states as improvised reminders, the team should be clear about what operational problem the switch is actually solving.
What makes an OSCAR alternative “best” for a family practice?
There is no universally best OSCAR alternative for every BC family practice.
One clinic may have an OSCAR setup that continues to serve it well. Another may value its current templates and billing routines but find coordination harder as the team grows. Another may accept more migration work because referrals, results, and staff coverage have become increasingly dependent on informal tracking.
The useful comparison starts with the clinic you already have.
Document what works well enough that you would be disappointed to lose it.
Then document what people have to do around the EMR: the extra lists, inbox signals, repeated checks, explanations to new staff, and manual handoffs.
At Aeon, this is the evaluation standard we keep returning to: the clinic should be able to see what patient work still needs attention, who is responsible for the next step, and what has actually been resolved.
A new system does not have to reproduce OSCAR perfectly to be a better fit. It has to preserve what matters while making enough of the compensating work unnecessary to justify the disruption of changing.
The best alternative is the one the clinic can trust during ordinary work
Switching from OSCAR is a significant operational decision. Familiar templates need to be accounted for. Staff need training. Billing and documentation routines need to be tested. Active patient work needs a transition plan. Years of clinic habits cannot be reproduced overnight.
That disruption is a legitimate reason to be cautious.
But staying has a cost too if the clinic increasingly depends on routines nobody would deliberately choose today.
So when comparing an OSCAR EMR alternative, do not ask only whether the new system can do everything your current system does.
Ask what your clinic will no longer have to do around it.
Which tracking list can disappear? Which inbox signal no longer has to act as a reminder? Which handoff becomes understandable to a new MOA? Which referral can be followed without someone remembering the clinic’s unwritten rule for checking it again?
Those answers help determine whether switching is worth the disruption.
The best alternative is not the one that recreates everything your OSCAR clinic does today. It is the one that preserves the workflows worth keeping, reduces the compensations your team has had to build around the EMR, and makes patient work easier to see, share, resume, and carry to a real endpoint.
