
Mirth Connect Alternatives for HL7 Interface Engines
Compare Mirth Connect alternatives after the licensing change, from Open Integration Engine and BridgeLink to commercial engines and cloud HL7 and FHIR services
Five AI co-creation models, how to choose one and the governance each needs.

Co-creation means building an AI solution together with the people who will use it, buy it or support it, instead of handing over requirements and waiting for a finished product. There is more than one way to do it, and the right model depends on who holds the knowledge, who carries the risk and who will own the result. This guide describes five common AI co-creation models, when each fits and the governance each needs. For what co-creation means and why it matters, see co-creation and the future of AI innovation; for examples, see case studies in AI co-creation.
| Model | How it works | Best for | Watch out for |
|---|---|---|---|
| Joint delivery team | Client domain experts and partner engineers work as one team on a shared backlog | Custom solutions where domain knowledge sits with the client | Clear decision rights and time commitment from client experts |
| User co-design | End users shape the product through workshops, prototypes and testing in real work | Tools that change daily workflows | Representative users, not only enthusiasts |
| Co-development partnership | Two organizations build a product together and share costs, rights or revenue | New products that need both parties' data, expertise or market access | IP ownership, data rights and exit terms agreed up front |
| Internal business and tech squad | A business unit and an internal AI team share goals and staff | Organizations with in-house AI capability | Shared metrics and funding so priorities do not drift |
| Open innovation | Challenges, hackathons or startup programs invite outside ideas against a defined problem | Exploring many options quickly | A path from winning idea to production |
The benefits and risks of this way of working are covered in benefits and risks of AI co-creation. To see how we co-create AI solutions with clients, visit our AI implementation support page.
AI co-creation can take five main forms: joint delivery teams, user co-design, co-development partnerships, internal squads and open innovation. Choose based on where the knowledge sits, who will use and own the result and how clear the problem is. Every model needs a shared charter, clear decision rights, data and IP terms, a regular cadence and responsible AI checks.
If you want to co-create an AI solution, book a consultation with Ekipa's AI engineers.
A way of building AI together with users, clients or partners, with shared work, decisions and sometimes ownership.
Joint delivery teams, user co-design, co-development partnerships, internal business and tech squads, and open innovation.
It depends on the agreement. Settle ownership of code, models, data and outputs before work starts.
A prototype can be ready in weeks; a production system usually takes several months, depending on scope and data.
It needs more of your team's time, but often reduces rework and improves adoption.

Compare Mirth Connect alternatives after the licensing change, from Open Integration Engine and BridgeLink to commercial engines and cloud HL7 and FHIR services

RAG for clinical documents: ingest FHIR notes, retrieve and cite evidence, protect PHI, and test faithfulness, recall and abstention before release.

How an FDA predetermined change control plan lets AI device updates ship without new submissions: the three parts, modification protocol and release controls.
Connect with our team to explore how AI expertise can transform your business.