Lysander C.

Healthcare software rarely fails in development. It fails at the interface layer and at the point of clinical adoption, the HL7 feed that drops segments, the FHIR mapping that doesn't match the source EHR, the workflow providers quietly work around by week three. I'm a healthcare technology consultant working at that seam: clinical workflow on one side, integration architecture on the other. I help digital health companies, MedTech startups, and provider organizations scope, integrate, and ship systems that hold up in live clinical environments. Clinical domains I work in: ambulatory and multi-specialty practices, telehealth, remote patient monitoring, revenue cycle and prior authorization, care coordination, and practice management. I've worked directly with practice managers, hospital IT stakeholders, and clinical operators, through go-live, not just requirements. 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗱𝗲𝗽𝘁𝗵:   • Interoperability - HL7 v2 (ADT, ORM, ORU, SIU), FHIR R4, SMART on FHIR, CDS Hooks, C-CDA, X12 (837/835/270/271)   • EHR platforms - Epic (App Orchard/Vendor Services), Cerner/Oracle Health, Athenahealth, eClinicalWorks, and integration middleware patterns   • Compliance & security - HIPAA, PHI data flow mapping, BAA scope, audit logging, SOC 2 readiness   • AI in clinical settings - ambient documentation, clinical decision support, triage and intake automation, scoped against real provider workflow, not demo conditions   • Product - discovery workshops, MVP scoping, technical requirements, integration architecture, roadmap validation 𝗛𝗼𝘄 𝘄𝗲 𝘄𝗼𝗿𝗸: Anonymized engagement + measurable outcome 𝗛𝗼𝘄 𝗲𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁𝘀 𝘁𝘆𝗽𝗶𝗰𝗮𝗹𝗹𝘆 𝗿𝘂𝗻:   • Discovery first, clinical workflows, data flows, and integration constraints mapped before a single requirement is written. Then technical requirements and integration architecture. Then build guidance or delivery, depending on what you need. I can bring an engineering team behind the strategy when a project needs execution rather than advice.   • What clients value: I can sit in a clinical stakeholder meeting and a technical architecture review on the same day and translate accurately in both directions. That's where most healthcare projects lose time.   • Typical engagements: integration assessments, discovery sprints (2–3 weeks), fractional product strategy. If you're building a digital health platform, integrating with Epic or another EHR, implementing HL7 or FHIR interoperability, or planning AI-enabled clinical tools, send a short note on what you're building and where you're stuck. I'll tell you honestly whether I'm the right fit. Lysander