Discuss your project
Healthcare

Custom software and app development for healthcare

Daily healthcare work happens between clinical systems: spreadsheets, shared drives, paper forms, small databases. We build applications that close those gaps, connect them to your HIS, EMR or lab system, and support them long term.

Discuss your project How the work is delivered

A good fit if

  • A process affecting patients, flow or reporting lives in spreadsheets, Access or paper.
  • You need an accessible patient portal, form or app, in French where required.
  • You are a digital health company needing a team to build, integrate and support.
  • An existing app is fragile, insecure or undocumented, or IT lacks developers.

Another approach may suit you better if

  • Your clinical system's own module does the job: cheaper, easier to support. We will say so.
  • Nobody owns the app after launch; every system needs a business owner, even with our support.

What is included

  • Discovery: users, workflows, data, integrations, privacy, security, accessibility, language
  • Prototypes tested with clinicians, staff or patients before development
  • Web or mobile app, built and demonstrated release by release
  • Integration with your HIS, EMR, lab and other systems
  • Role-based access, SSO, encryption, logged access to health information
  • WCAG 2.0 AA testing (public web), French interfaces where required

What we build

Clinical systems miss work their vendors will not add. The stopgap tools, often built by someone long gone, hold sensitive data, are unsafe to change and rarely connect.

Clinical and operational tools

Patient flow, referrals, wait lists, specimen and order tracking, infection control, equipment, quality reporting.

Patient portals and forms

Registration, intake, pre-visit questionnaires, appointments, feedback. Accessible, in French where required.

Mobile apps for staff

Clinicians and community care teams: secure sign-in, no health information left on devices.

Digital health products

From first release to a platform customers rely on, integration and security included.

Replacing ageing apps

Inherited code starts with a code audit, so decisions rest on evidence.

Reporting and dashboards

Several systems' data, together for managers and leadership.

Examples by setting
  • Hospitals and health systems: bed and flow boards in spreadsheets, referral trackers in shared mailboxes, equipment logs.
  • Clinics, practices, labs and imaging: intake and referral forms on paper or fax, recall lists, specimen tracking, reports stitched together by hand.
  • Long-term, home and community care: visit scheduling, care coordination, reporting to funders.
  • Also: health agencies, and digital health companies building for all of the above. Each application is built around your workflows and systems, not as another island of data.

Built for healthcare

Connected

HL7 v2 via your interface engine, FHIR or vendor interfaces; tested end to end, including errors.

Private by design

Audit logs of who viewed what, minimal real data outside production; questionnaire, TRA and PIA inputs.

Hosted where you decide

Your infrastructure or a Canadian cloud region, with monitoring, backups and tested recovery.

Supported for years

Warranty, then a support or managed services agreement: monitoring, patching, upgrades, enhancements, end-of-life plans.

Procurement

Hospitals and agencies buy through RFPs, RFQs, supplier qualification or invitational processes; we respond with the privacy and security schedules and terms you require. A short paid discovery can settle scope before the build is procured. Clinics, care providers and companies usually start with a written proposal. Our partner checklist helps compare vendors, us included.

Delivery

How the work is delivered

One path, scaled to each project's size and risk.

  1. Discover

    Workshops with future users, a review of current tools and data, and agreed scope, risks and priorities.

    Output: Discovery report, scope, staged plan.

  2. Design

    User journeys, prototypes and an architecture for hosting, integration, security and privacy, tested with real users.

    Output: Approved designs and architecture.

  3. Build

    Short increments with regular demonstrations, automated tests and security checks in every release.

    Output: Working software, release by release.

  4. Validate

    Acceptance, accessibility and security testing (code, dependencies, running application), then your privacy and security sign-off.

    Output: Test results and go-live approval.

  5. Launch and support

    Go-live within your change and downtime rules, on approved hosting, staff trained to monitor, escalate and restore.

    Output: Live application, runbooks, support agreement.

Scope at a glance

Not included unless agreed

  • Clinical system licences, interface fees, third-party software (supplier-billed)
  • Configuring the clinical system itself (your vendor or IT team)
  • Medical device advice; we flag the question before any build

What we need from you

  • A business owner and leads who decide and test releases
  • Test environments for every system the application connects to
  • Privacy lead's PIA and TRA timelines; your interface work

Before handover

  • Every role completes its main tasks in acceptance testing without workarounds
  • High-risk issues fixed, health-information access logged, WCAG 2.0 AA met
  • Code, documentation and admin guides handed over as the agreement sets

What affects the cost

  • Roles, workflows, screens; number and type of integrations
  • Web, mobile or both; used by patients too
  • Security, privacy, accessibility and French requirements
  • Hosting and environments; support model and length

No package prices: estimates in Canadian dollars from an agreed scope, taxes shown separately.

Questions buyers usually ask

Who owns the code?

Ownership of and access to the source code are set in the agreement. Most healthcare organizations take code and documentation at agreed milestones; we can use escrow instead. Either way, you are never locked out of your own application.

How do you handle personal health information?

We work within the restrictions PHIPA places on service providers, under your written agreement: we use personal health information only to provide the service, never disclose it, and bind our staff the same way. Elsewhere, your province's health privacy law applies. Not legal advice.

Does the application have to meet accessibility standards?

Ontario public hospitals, other designated public sector organizations and organizations with 50 or more Ontario employees must make internet websites and web content, including web apps they control or can modify by contract, meet WCAG 2.0 Level AA. We design, test and document to it.

Could our application count as a medical device?

Software intended to diagnose or treat can fall under Health Canada's medical device regulations. Most workflow tools do not; some clinical tools might. We raise it at discovery so you can get regulatory advice before design is fixed, and we support your adviser.

Have a healthcare workflow that needs its own application?

Tell us the work, who does it and the systems it touches. We'll arrange a conversation and suggest a first step, usually a short discovery.

Discuss a healthcare software project