Medicus.IA
A health operating system.
Longitudinal records, medication safety and a deterministic clinical engine with FHIR R4 interoperability.
MEDICINE + ENGINEERING + JUDGEMENT
I’m Dr. Ixequi Luna. Physician and AI architect. I turn critical workflows into traceable software, from clinical decisions to business operations.
PUEBLA, MEXICO · GLOBAL COLLABORATION
Figures reported in my 2026 CV; they span different projects and stages, and are not live measurements.
01 / SELECTED WORK
Healthcare, business operations and interoperability. Architecture and code written by me.
No projects match that search.
Medicus.IA
Longitudinal records, medication safety and a deterministic clinical engine with FHIR R4 interoperability.
PuestoYa
HR and payroll for a four-company group. Labour calculations, frozen billing periods and an immutable audit log.
health-interop-lab
One clinical workflow across five languages: HL7 v2, Kafka, FHIR R4, gRPC and EDI X12, instrumented with OpenTelemetry.
Explore the scope of each project.
Booking audits, customer service, CRM and commercial operations. Engine 01 in production and three Engine 02 surfaces live.
Orchestration with typed signals, boundary validation and one synthesis authority. Under support and maintenance.
Multi-company executive CRM integrated with Odoo: quotes, receivables, multi-currency reconciliation and WhatsApp orders.
Tasks, boards, invitations and reports. Five roles with workspace isolation and activity auditing.
A digital experience for handcrafted Tuscan perfumery: a bespoke storefront and Medusa v2 commerce engine.
Habit plans, progress tracking and e-commerce in one experience.
Predictive AI for agriculture and contract analysis. Products in development, with staged scope and validation.
Adaptive learning, real-estate analytics and marketing automation within the Firmus.IA portfolio.
Status and metrics from the 2026 CV. ¹ SOC 2 controls expressed as tests; they do not constitute SOC 2 certification or an audit report.
Grace, Viñedos El Sueño, IA Mundial and the Firmus.IA and Medicus.IA web experiences. The CV covers the full portfolio.
02 / HOW I THINK
I start with the domain: who decides, what evidence they need and what harm an error could cause.
I separate language tasks from critical decisions. An output should be traceable to its rule and source.
Incomplete data and missing context should lead to explicit abstention, not a persuasive answer.
Data contracts, least privilege, regression tests, traceability and reversible deployments.
CASE / MEDICUS.IA
In Pilot 0, as reported in the CV, documentation time fell from 60 to 15 minutes per patient across 100 consultations. This is a pilot result, not a guarantee of clinical outcomes.
−75 % documentation time
Source: 2026 CV · Pilot 0 · n = 100 consultations
03 / THE PERSON BEHIND THE CODE

Clinical practice taught me to listen, recognise uncertainty and take responsibility for a decision. Those same principles guide my engineering.
I hold a medical degree from BUAP, lead Firmus.IA as CEO and CTO, and architect Medicus.IA. I maintain a clinical practice and write the core of my systems in Python, TypeScript and Go.
Technology leadership, architecture and sovereign AI development for critical industries.
PuestoYa, Viajare, Pakal and EmpoweringBiz; product, architecture and security review for Yaan Technology.
Private and occupational practice in Val’Quirico. Co-founding an ambulatory surgery network and leading research.
Medical degree. Internship at Hospital General del Sur and research service at the Biomolecular Detection Center.
Python · TypeScript · Go · Java · Kotlin · C#
FHIR R4 · HL7 v2 · gRPC · Kafka · EDI X12
FastAPI · Next.js · PostgreSQL · AWS · Docker
CI/CD · Playwright · OpenTelemetry · RBAC · SHA-256
04 / RESEARCH & LEARNING
Scientific evidence and continuous learning are part of the way I build.
Luna-Mendoza I, Torres-Rasgado E, Cerón-Morales JA.
DOI 10.7759/cureus.93350
PMID 41158905 · PMCID PMC12558430
CONTINUOUS LEARNING
05 / WORK TOGETHER
From discovery to system: domain, contracts, implementation, validation and operations.
Discuss scopeProduct, security, data integrity and delivery reviews. Prioritised findings and a remediation path.
Discuss scopeDecision support, documentation and FHIR/HL7 workflows, with professional oversight and use-case validation.
Discuss scopeFractional CTO, product strategy, mentoring and engineering governance for teams ready to move forward.
Discuss scopeRates previously published on this site. Scope, availability, taxes and terms are confirmed in a proposal before engagement.
Initial call: 30 minutes, no charge. Previous project payment references: 40% upfront, 30% at milestone and 30% at delivery; retainers monthly in advance. Healthcare projects require a scoped validation and regulatory budget.
The earlier AI subscription plans have no verified signup and payment service on this site. Ask about availability before subscribing.
In love with the intelligence, delivery speed, and quality of the AI architecture he built for my company.
A genius. It's incredible how easily he programs and delivers results better than the biggest AIs on the market.
I've been at MIT working with top-tier AI engineers. Ixequi is 10x more efficient, skilled, and innovative.
His products are gold. Literally gold in code. His AIs are complex, incredibly complete, and truly revolutionary.
Ixequi is a machine. He's beyond my level and speed. He revolutionized my family business with his mentoring and consulting.
I've been coding for 20 years and contributed to the WHO. He surpassed me in just one week. His approach to coding is revolutionary.
A STARTING POINT
Prepare a brief for our first conversation. It is organised in your browser: no AI, no invented return on investment and no automatic submission.
Describe the process without including patient data, passwords or confidential information.
Opening email only prepares a draft. You decide whether to send it.
06 / THINKING IN PUBLIC
Archive articles, March–April 2026. Their figures describe that stage; the CV covers subsequent progress.
BEFORE WE TALK
Yes. Based in Puebla, Mexico, I collaborate remotely or in a hybrid arrangement. I work in Spanish and English; scope and time zones are agreed upfront.
No. I evaluate the problem first. A clear rule, a better integration or a simpler workflow may be the better solution.
No. In my approach, the system suggests and documents; the professional retains judgement and signs the decision. Validation depends on the use case.
With a 30-minute conversation about the process, available evidence and desired outcome. We then define scope, deliverables, risks and budget.

THE NEXT SYSTEM STARTS WITH A CONVERSATION
Architecture, technology leadership or a second look at a critical system. Tell me what you need to solve.
Scheduling opens on Calendly, an external service.