User bio

I'm currently a Solutions Architect on the Sales Engineering team at InterSystems, helping clients unlock the full potential of data-driven platforms. With a background in Developer Advocacy and a passion for open source, I thrive on bridging deep technical concepts with clear, impactful communication.

Originally from southern India and now based in Boston, I'm also a dedicated community builder, having led initiatives like GDG Houston and GDG Seattle. And when I'm not architecting solutions, you'll likely find me in the kitchen crafting recipes with the same precision and creativity I bring to my code.

Show all
Member since Jun 20, 2024
Posts:
Replies:

@David Hockenbroch Yes, that seems to be the right approach! Just a small correction to your condition:

AND ((TOURFIND.TNR = TNRHead.TNR) OR (TOURFIND.TNR IS NULL AND SGNRFIND.TNR = TNRHead.TNR))

(You had `TNRHead.TNR = TNRHead.TNR` twice at the end)

performance could be significantly better than NVL as NVL forces a full table scan and OR condition allows index usage so the optimizer can use indexes on both `TOURFIND.TNR` and `SGNRFIND.TNR` 

Great demo, Jesse & Team!!
This kind of longitudinal view definitely makes a difference for rare disease detection.

For the raffle: InterSystems Health Gateway connects to eHealth Exchange, Carequality, and CommonWell Health Alliance.

Certifications & Credly badges:
Vishal has no Certifications & Credly badges yet.
Followers:
Following: