Thanks Reshma. I'll keep you posted. Where are you guys at with sidecare apps that I can use inegtrate with Cerner and Epic etc. Also... by integrate, I actually completey bypass and future proof against their current incumbency and incompetency.

So there are 2 sides to the "sidecar" - technical and policy/governance. Technical: Cerner and Epic support the "G10" ONC criteria (which Medplum also has an implementation) Standardized API for Patient and Population Services (Cures Update). That's a path to get data in and out of the system. Policy: Providers need to enable any app built. We have a advanced security and compliance posture, but it's still some work to get access and go through policies.

Do you mean policy on part of the Cerner / Epic / etc... or other stakeholders in the domain where their software is implemented?

It's actually usually the policy of the organization to whom the Cerner / Epic instance belongs.

Perfect! If I was in an organization that had committed to Cerner and had access to their API as part of the build and happened to be involved in writing the policy and governance for how we are going to use this API, what kind of best practices would you recommend for writing progressive policy. Do you have examples of where this was done well, and where this was done poorly? Assume that I have the same philisophical leanings as you fine people at MedPlum re: open source software, progressive web tech, freeing ourselves from the clutches of the current EHR software landscape.