Industries · Healthcare
Clinics, medical groups, allied health practices and digital health teams come to us for booking, intake, patient portals and practice management integrations that hold up under real clinic load and real privacy obligations.
You own the code and IP Weekly demos Reply within one business day
Availability - November
Live312
Bookings this month
1.8%
No-show rate after optimisation
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds software for clinics, medical groups, allied health practices and digital health products.The work usually covers online booking, patient intake and forms, patient portals, virtual care and integration with EMR or practice management systems. Privacy sits in the design from the first sprint, with data handling shaped around PIPEDA, the applicable provincial health privacy law such as PHIPA in Ontario, and HIPAA where a US covered entity or business associate is involved. That is design practice, and it does not replace advice from your own privacy counsel. Every build is tested against WCAG 2.2 AA so patients using assistive technology can book, complete forms and read their results.
Key facts
Healthcare
The problems we are asked to solve most often — and how.
Practice management and EMR platforms vary widely in what they expose. Some offer documented APIs, some offer scheduled flat file exports, some offer nothing supported at all. The integration plan has to follow what the vendor actually supports, not what the brochure implies.
A clinic in British Columbia, a group with Ontario locations and a product serving US patients can sit under three different privacy regimes at once. Data residency, consent wording, audit logging and breach response all change with the answer, so the rules get settled before the schema does.
Paper intake gets retyped, PDFs get emailed unencrypted and patients repeat themselves at the front desk anyway. Digital intake only works when it saves progress, handles a substitute decision maker, and lands in the chart in a shape the clinical team can actually use.
Provider availability, room and equipment constraints, appointment types with different durations, buffer time, waitlists and no show policies all interact. A booking screen that ignores any one of them creates work for reception instead of removing it.
Patients with low vision, tremor, low literacy or limited English are exactly the people most likely to need care. Keyboard paths, contrast, focus order, error messages and plain language get tested against WCAG 2.2 AA rather than assumed to be fine.
Regulated health professionals answer to colleges with rules on claims, testimonials, before and after imagery and comparative language. Campaign copy, landing pages and review requests have to be written so the practice can defend every line if asked.
Process
Discovery and privacy mapping
We agree scope, clinical workflows, the systems in play and the privacy obligations that apply to your locations and your patients.
Architecture and integration plan
We choose the stack, confirm hosting and data residency, and prove the EMR or practice management connection with a small working slice.
Design and accessibility review
Screens are designed for both patients and staff, reviewed for plain language, and checked against WCAG 2.2 AA before build starts.
Build with weekly demos
One accountable team ships to a staging environment every week, so clinical and administrative staff can react while changes are still cheap.
Launch and aftercare
We migrate data, train staff, watch the first weeks closely, and hand over every account, repository and credential. You own all of it.
How we work
We map what personal health information the product touches, where it lives, who can see it and how long it stays, before any screen is built. Roles, audit logging and retention become part of the schema rather than a later hardening pass.
We test the vendor connection early with a narrow slice of realistic data, so the schedule reflects what the EMR or practice management platform will actually return instead of what the documentation promises.
We sit with reception and clinical staff, follow the current process end to end, and design screens around how the day really runs rather than an idealised path that only works when nobody is late.
Keyboard, screen reader and contrast checks run against WCAG 2.2 AA throughout the build, with plain language content and bilingual EN and FR versions where a practice serves both languages.
Video visits, secure messaging and document exchange are built to keep working on older devices and weak connections, with an obvious fallback when a call drops mid appointment.
Search, content and paid campaigns are written within professional advertising standards, and measurement is configured so patient identifiers stay out of analytics and ad platforms.
Recommended
WCAG 2.2 AA
Accessibility standard tested on every build
Weekly
Working demo cadence on healthcare projects
1 business day
Reply time on new healthcare enquiries
FAQ
Usually yes, and the honest answer depends on what your vendor exposes. Some platforms offer documented APIs or HL7 v2 and FHIR interfaces, others offer scheduled exports, and a few offer nothing supported. We check that first, test a narrow slice of realistic data early, and tell you plainly if a workaround is the only route.
We map the personal health information the product touches before building, then set hosting, access roles, audit logging and retention to match. Canadian projects are commonly designed around PIPEDA and the applicable provincial health privacy law, such as PHIPA in Ontario or the Personal Information Protection Act in British Columbia, with Canadian data residency where you need it. Work involving a US covered entity is scoped with HIPAA in mind. This is design practice, not legal advice, and your privacy counsel should confirm what applies.
Yes. Portals typically cover booking, forms, documents, secure messaging and results access, with role based permissions for patients, caregivers and staff. Virtual care can include video visits, waiting room states and file exchange. We build these to keep working on older devices and weak connections, with a clear path back to a phone call when the video fails.
Yes. Our performance marketing work for regulated practices is written to the standards your college sets, which usually restrict testimonials, comparative claims and outcome promises. We also configure measurement so patient identifiers and condition specific signals stay out of analytics and ad platforms, and we ask your compliance lead to approve the claims before anything runs.
We watch the current process before designing the new one, including the workarounds people have invented. Reception, nursing and administrative staff see a working demo every week, so their feedback lands while it is still cheap to act on. Training and a short written guide are part of launch, not an afterthought.
Yes. The studio is in Vancouver, British Columbia, and we work with clinics and health teams across Canada and the United States remotely, with video calls scheduled in your time zone and on site visits when the work calls for it, such as observing intake at the front desk or testing hardware in an exam room.
You do. Clients own all code, designs, accounts and intellectual property from day one, including hosting, repositories, analytics and any third party services set up on your behalf. We document the architecture and hand over credentials at launch, so another team could pick up the work without calling us. Request a quote to talk through scope.
Let’s connect
We’ll reply within one business day with next steps and a tailored quote — no obligation.