Our friends at Chamber Cardio have recently published a case study regarding their product build. This follows closely after securing a seed round of funding from General Catalyst and other investors (congratulations!). We've had a great experience working with Chamber and we want to emphasize a few transferable insights from Chamber's technological and product successes from our viewpoint as engineers.

Watch a video overview of the platform and stack:

https://www.youtube.com/watch?v=8bsrKe6VmUs

Read the full case study to dive into some of the specifics of Chamber's product.

Our highlights:

Medplum: It’s no secret that we love MedPlum. You can read about one of our previous projects with them here. We believe that MedPlum makes building healthcare applications based on FHIR accessible (and we believe you generally should build with FHIR as a default). In particular, MedPlum made it easy and convenient to build multiple portals with granular access controls, and MedPlum's subscriptions make synchronizing and updating data from a FHIR server a breeze. The MedPlum team has created an excellent developer experience, which matters quite a bit when you have a tiny team with no time to waste.

Retool: We were incredibly impressed with Retool's capabilities on this project. It allowed a very small team to create a huge amount of product value very quickly and in short iterations. Crucially, we were able to incorporate custom code into Retool easily, calling MedPlum's APIs and our custom lambda functions directly. We were also able to embed custom code for use client-side, packaged up as libraries that could also be used in our custom frontend. In other words, we were able to use the standard tools and best practices of software development within Retool. This is important because it reduces the risk of lock-in and of a truly brutal migration away from Retool (partially or entirely) down the road. While there absolutely was a learning curve to get from zero to these more advanced uses of Retool, we feel the time we invested was extremely worthwhile.

BonFHIR: Chamber was one of the key projects for which we developed BonFHIR, our open source toolkit. We used BonFHIR to build custom UI, but we also used it as an intermediary layer for querying MedPlum's FHIR APIs from within Retool. This particular usage within Retool and outside of it allowed us to test out some of the modularity within BonFHIR itself and make it more than a UI project.

We think Chamber's success serves as an excellent example of what can be achieved with a modern, lean, and developer-friendly healthcare stack. We're excited to build more products that take advantage of both open standards and cutting-edge low-code platforms for remarkable productivity.

Interested in building with us? Get in touch!