I recently came across https://cloud.google.com/healthcare-api, by GCP. We're wondering how it compares to Medplum at a high-level - what are the advantages / disadvantages of using one or the other?

Great Question! At a high level, GCP Health API is primarily tailored towards analytics and data mining use cases, whereas Medplum is optimized to be an application backend. This is reflected in some of the tradeoffs we make: - **Auth**: Medplum supports a variety OAuth2 configs, SCIM, and access policies that can be configured per user type - Performance: Medplum is tuned more for low latency queries for interactive applications, where as GCP is more tunred towards throughput - **UX**: Medplum provides the Medplum App , react components, and an SDK client to speed up the building of Web apps. You typically interact with GCP via the API - Integration: Midland provides the bat primer to connect to third-party API and provide workflow automation Ultimately, GCP and medical can be really good complements to each other, as their tuned to different use cases. We have some users who sync data from Medplum as a source of truth / app backend to GCP as an analytics engine