Opian Technologies

Link — Multi-Facility EMR

A modular clinical operations platform where vitals, consultation, lab, imaging, pharmacy, and other tools plug into one shared patient-visit context.

.NETASP.NET CoreReactViteSQL ServerHealthcare IT

What it does

  • Shared patient-visit context used by interchangeable clinical modules
  • Facility-controlled tool enablement, role visibility, and workflow placement
  • Vitals, consultation, lab, imaging, and pharmacy tools built around the same visit model
  • Planned clinician-controlled tool suggestions informed by usage patterns
  • Interoperable patient records
  • Low-bandwidth optimization
  • Role-based workflows spanning reception, triage, doctor, cashier, lab, imaging, pharmacy, inpatient, logistics, and super-admin operations
  • Layered architecture with Link.Api, Link.Application, Link.Domain, and Link.Infrastructure boundaries
  • Facility-scoped operations, seeded environments, endpoint maps, and Playwright-backed workflow coverage
  • Queue, reporting, and workflow contract stabilization across frontend and backend subsystems
Li

Inside the build

Problem, constraints, decisions, and outcome.

What changed and why

01

Problem

Clinical software becomes difficult to adapt when every workflow is hard-coded into one application, even though every tool operates on the same patient visit.

02

Constraint

Facilities need different clinical tools, role access, and screen placement while preserving one visit record, low-bandwidth operation, and consistent contracts across the frontend and backend.

03

My contribution

My primary contribution was shaping and implementing Link as a modular clinical platform: one shared visit context with interchangeable tools for vitals, consultation, lab, imaging, pharmacy, and future workflows, plus facility-level controls for enablement, visibility, and placement.

04

Technical decision

Treat each clinical capability as a module attached to a shared visit context, keep facility configuration outside module code, and reserve usage-based suggestions for a clinician-controlled recommendation layer.

05

Outcome

Established a platform direction where facilities can compose clinical workflows without rebuilding the application, while retaining Link's role-based queues, reporting, testing, and multi-facility operational scope.

More Work

Other projects from the same portfolio.