Rajinder M.

I build the software that sits around an EHR for US practices and healthtech teams. That means integrations, billing and eligibility, patient intake, and automations that take repetitive work off front-desk and billing staff. Most of this comes from a clinical operations platform for a multi-office US outpatient practice. It’s live and used every day. I was the main engineer on a team of three, and I own billing, scheduling, patient intake, medications and refills, and the EHR sync. EHR and third-party integrations: two-way sync with DrChrono over REST, OAuth2 and webhooks, including reconciliation when both systems accept writes and drift apart. Also X12 270/271 eligibility through Stedi, e-prescribing through WENO, e-signature consent through DocuSeal, and outbound fax for lab, imaging, referral and DME orders. Workflow automation: patient intake, billing prep and claim follow-up workflows in n8n or custom Python. IVR call flows for appointment confirmations and refill requests. Inbound fax and email processing with OCR, classification, field extraction and a staff review queue, so nothing gets filed without someone checking it. Clinical AI: dictation turned into templated notes the provider reviews, and ICD and problem-list extraction that only uses what’s written in the note. In a clinic, a confident wrong answer is worse than no answer, so every output has a review step. PHI handling: role-based access down to in-page actions, MFA, audit logs, presigned document links, and error reporting that strips identifiers. I’ll tell you what’s actually in place rather than calling something “HIPAA compliant.” Underneath it all is Python (FastAPI, Flask, Django), PostgreSQL and AWS, and I deploy and support what I build. I’ve done 70+ projects and 5,500+ hours on Upwork. I work with a small team, so larger scopes aren’t a problem. If you’re stuck on an EHR integration, or your staff still handle something by hand every day, send me the details and I’ll tell you how I’d approach it.