[bearjaws]

Epic on FHIR is missing a ton of data that is present in Epic, for example if I want to react to a dispensing event, that has to be custom built as far as I know. Even then, you're long polling an endpoint hoping you find work you need to react to.

At times it feels like it would be better to just get data straight from the database, as custom Epic implementation times are insanely long and costly.

[nradov]

I don't know about dispensing events specifically, but Epic supports CDS Hooks to allow for triggering custom code in response to certain events.

Getting data straight from an EHR's underlying database is risky. The vendors generally don't document or support this, and the schema could change at any time.

[nimish]

Well, you don't end up having to query their DB directly, you can do it via standardized IHE ITI XDS/XCA over a network like CareQuality. There are startups like Particle that can do it as a SaaS.

[bearjaws]

Have you used Particle? I find the concept really interesting and could help me in the future. Would love a end user opinion.

[nimish]

Full disclosure, I was an early employee and wrote the first integrations, so I'm likely not the right person to ask. https://www.particlehealth.com/ should have details.

[abrichr]

Thanks for sharing. Can you please suggest some resources for further reading? Is particle.io the startup you mentioned?

[nimish]

https://www.particlehealth.com/ -- full disclosure, I was an early employee