Hello! Medplum seems awesome. I work w Rhapsody/Mirth and looked at Medplum as a potential replacement. However, the more I look into this engine the more I see how limited it is compared to Mirth/Rhapsody. I'd mostly work with HL7v2(not FHIR) and I would need complex parsing, nested logic, DB Queries, routing, etc. Can someone correct me, are there those limitations or does Medplum have all those capabilities as well?

Hi @ElNiño121 - Thanks for the great questions and for checking out Medplum! It's awesome to hear you're exploring us as a potential Rhapsody/Mirth replacement. You've hit on some key differences in how Medplum operates. We're built as a foundational healthcare developer platform, offering powerful, lower-level primitives. This means immense flexibility, though sometimes it requires a bit more explicit coding compared to highly declarative tools like Mirth. Let's dive into your points: HL7v2 Complex Parsing: We have robust low-level parsing utilities that handle complex HL7v2 structures. Check out our Medplum HL7v2 Mapper demo (https://github.com/medplum/medplum-hl7-mapper-demo) for an interactive look at real-time transformations and granular message control. If you have specific complex parsing scenarios, we'd love to hear them! DB Queries: You're right, Mirth has more built-in database query capabilities. For Medplum, querying external databases currently involves custom dependencies within your Medplum Bots or new connection types. We're actively enhancing this. Our work on Fission.io is a big step towards broader external system integration and more powerful Bots. You can follow the discussion here: https://github.com/medplum/medplum/discussions/6832 and see the PR: https://github.com/medplum/medplum/pull/6830. Routing: Medplum is fully capable here, but the implementation differs. Mirth's "channel" model bakes in declarative routing. With Medplum, you'd send the HL7 message to a Bot, and then use the Bot's JavaScript/TypeScript logic to perform routing. This provides ultimate programmatic control and flexibility for highly customized routing that's often harder to achieve declaratively. In short, Medplum's tools are lower-level and more programmatic. You absolutely can achieve complex parsing, intricate logic, and routing. It's just not always packaged in the same declarative way as Mirth for certain integration patterns. Our strength is providing an extensible platform where developers build highly customized solutions using modern web technologies. We're always evolving, and your feedback is super valuable. Does this help clarify things? Happy to dig deeper!