{"id":22350,"date":"2026-09-10T11:42:23","date_gmt":"2026-09-09T23:42:23","guid":{"rendered":"https:\/\/medtechglobal.com\/nz\/?p=22350"},"modified":"2026-09-11T11:43:28","modified_gmt":"2026-09-10T23:43:28","slug":"from-curiosity-to-capability-medtech-globals-first-ai-hackathon-2","status":"publish","type":"post","link":"https:\/\/medtechglobal.com\/nz\/from-curiosity-to-capability-medtech-globals-first-ai-hackathon-2\/","title":{"rendered":"Medtech Hackathon Part 2: Meet the Teams Behind Medtech\u2019s Hackathon Winning Ideas"},"content":{"rendered":"
\n
\n
\n

By Mari Taylor \u00b7 Medtech Global<\/p>\n

Putting customers at the forefront<\/h3>\n<\/div>\n<\/div>\n
\n
\n
\n

In Part 1<\/a> of our Medtech Hackathon series, we shared how teams from across the business came together to explore new ideas, experiment with AI and transform everyday challenges into working prototypes.<\/p>\n

The Hackathon invited teams to respond to four briefs: Ships Monday<\/strong>, Best Customer or Patient Outcome<\/strong>, Biggest Internal Impact<\/strong> and Biggest Leap<\/strong>. Each category encouraged a different kind of thinking, from practical ideas that could quickly deliver value to ambitious concepts that could help shape Medtech\u2019s future.<\/p>\n

While the teams responded to different briefs, they all began in the same place: with our customers at the forefront.<\/p>\n

At Medtech, our vision is to enable connected technology for healthcare by listening to our customers, understanding the challenges they face, and creating technology that makes a meaningful difference. That purpose was central to the Hackathon. Each winning solution addresses a real problem affecting healthcare clinics, clinicians, patients or the Medtech teams supporting them.<\/p>\n

For Part 2, we are putting the spotlight on the teams that delivered exactly to the brief. We asked them about the customer challenge that inspired their idea, the solution they developed, and the difference it could make for our users.<\/p>\n

Supporting Clinicians Through Responsible and Secure Innovation<\/h3>\n

Biggest Leap<\/strong><\/p>\n

Team name: <\/strong>TeamMCP (Model Context Protocol)<\/p>\n

Prototype name: <\/strong>MCP Server<\/p>\n

Team members: <\/strong>Ging Ming Chan, Prashanth Koval and Chieh-Ting Chan<\/p>\n

The Biggest Leap <\/strong>category encouraged teams to think beyond immediate improvements and explore ideas that could help shape the future of healthcare technology.<\/p>\n

Team MCP <\/strong>responded with an ambitious concept examining how Medtech\u2019s existing platforms could support safe and governed AI-enabled experiences.<\/p>\n

The team began by considering the everyday experience of clinicians. Important information may be available, but finding, reviewing and making sense of what is relevant can take valuable time that clinicians would rather spend focused on their patients.<\/p>\n

One insight helped shape the team\u2019s thinking:<\/p>\n

\u201cConnecting data isn\u2019t the same as making sense of it.\u201d – Team MCP<\/strong><\/p>\n

Before looking at what the team built, it helps to understand the technology that makes it possible: MCP stands for Model Context Protocol.<\/p>\n

An MCP server is the piece of software that lets an AI assistant talk to Medtech ALEX\u00ae<\/a> using MCP\u00a0the shared “language” AI tools use to discover and call tools. The MCP server itself doesn’t hold the security, business rules, or clinical data logic\u00a0that all already lives in ALEX\u00ae. What the MCP server does is translate a plain-language AI request into the correct ALEX\u00ae API call, and pass the response back. It never talks to the Medtech Evolution database directly every request goes through ALEX\u00ae, which means every existing control, authentication, auditing, permissions\u00a0is enforced exactly as it is today.<\/p>\n

Prashanth Koval Senior Product Manager (Integrations) at Medtech, summed this up perfectly:<\/p>\n

“Think of ALEX\u00ae as the vault that already holds the security, rules, and controls around Medtech Evolution<\/a>. The MCP server is the translator standing at the door it takes a plain-language request from an AI assistant, turns it into the exact ALEX\u00ae API call needed, and hands back the answer. It never opens the vault itself or reaches past ALEX\u00ae to the database. Every request still goes through ALEX\u00ae’s existing checks, so nothing changes about who’s allowed to see or do what.”<\/p>\n

Their MCP server prototype explored how clinicians could interact more naturally with approved information while maintaining the security, permissions and governance expected within healthcare.<\/p>\n

Rather than focusing only on what AI could do, the team considered how it could responsibly support clinicians and healthcare clinics. Keeping people in control and protecting access to information were central to the idea.<\/p>\n

\u201cThe vision is simple: make every Medtech clinic AI-ready without ever giving AI direct database access.\u201d – Team MCP<\/strong><\/p>\n

The concept was designed to make technology easier for clinicians to use. The team imagined a future where a clinician could ask a straightforward question and receive useful information without needing to understand the complexity behind the experience.<\/p>\n

\u201cA GP could ask a simple question about their own patients without ever needing to think in code.\u201d – Team MCP<\/strong><\/p>\n

The project impressed the judges because it combined ambitious thinking with a clear focus on the needs of clinicians and clinics.<\/p>\n

It demonstrated how responsible innovation could help reduce administrative effort, make important information more accessible, and give clinicians more time to focus on delivering care.<\/p>\n

\n
\n
\n
\"Article<\/div>\n<\/div>
Medtech Hackathon Team: Team MCP<\/figcaption><\/figure>\n<\/div>\n

<\/h3>\n

Making Support Easier to Access<\/h3>\n

Biggest Internal Impact<\/strong><\/p>\n

Team name: <\/strong>Hack to the Future<\/p>\n

Prototype name:\u00a0<\/strong>Chatterbox<\/p>\n

Team members:<\/strong> Dabby Quizo<\/a>, Heimona Potoru<\/a>, Charlotte Corbett<\/a>, Barbara MacLean<\/a>, Meg Tyre<\/a> and Mel Nepomuceno<\/a><\/p>\n

The Biggest Internal Impact <\/strong>category celebrated an idea with the potential to improve the everyday experience of both Medtech customers and employees.<\/p>\n

Team Hack to the Future<\/strong> won with Chatterbox<\/strong>, a concept exploring how trusted knowledge could be made easier to find and use, saving both clinicians and internal support members time.<\/p>\n

The team considered what happens when a customer needs help. In many cases, the information required to answer their question already exists but finding it can take time. This can leave customers waiting while consultants repeatedly search through documentation for the right answer.<\/p>\n

As the team explained:<\/p>\n

\u201cThe right answer usually already existed; it just wasn\u2019t standing next to the person who needed it. That’s the idea that unlocked the whole design.” – <\/em>Team Hack to the Future<\/strong><\/p>\n

Chatterbox explored how customers could access useful information sooner while supporting Medtech consultants to work more efficiently.<\/p>\n

The team developed the concept around two connected AI chatbot experiences: Ava, <\/strong>designed to help customers get quick answers to frequently asked questions, and Milo<\/strong>, designed to support Medtech consultants both utilising one knowledge base.<\/p>\n

Instead of treating customer self-service and consultant support as two separate challenges, the team brought them together around a shared source of trusted knowledge.<\/p>\n

\u201cSame brain, two conversations.\u201d – <\/em>Team Hack to the Future<\/strong><\/p>\n

The customer remained at the centre of the idea. Faster access to trusted information could reduce unnecessary waiting and create a smoother support experience. At the same time, consultants could spend less time answering repetitive questions and more time helping customers with issues that require human experience and judgment.<\/p>\n

\u201cEvery minute saved on a question someone\u2019s already answered is a minute back for the problem nobody\u2019s solved yet.\u201d – <\/em>Team Hack to the Future<\/strong><\/p>\n

The concept is not about removing people from customer support. It is about enabling Medtech teams to use their time where it can make the greatest difference.<\/p>\n

The team\u2019s vision was a more responsive experience for customers and a more focused experience for consultants.<\/p>\n

\u201cCustomers can get answers to frequently asked questions instantly instead of a ticket number and a wait time. Consultants get their time back for the cases that actually need judgment, not just a search bar.\u201d – <\/em>Team Hack to the Future<\/strong><\/p>\n

Chatterbox stood out because it considered the full support journey. By making trusted knowledge easier to access, the concept could help customers receive support sooner while enabling Medtech employees to deliver more meaningful assistance.<\/p>\n

\n
\n
\n
\"Article<\/div>\n<\/div>
Medtech Hackathon Team: Biggest Internal Impact<\/figcaption><\/figure>\n<\/div>\n

<\/h3>\n

Turning insights into answers<\/h3>\n

Best Customer or Patient Outcome<\/strong><\/p>\n

Team name: CodeBlue<\/strong><\/p>\n

Prototype name: <\/strong>FinPulse<\/p>\n

Team members: <\/strong>Abhiram Bourisetty<\/a>, John Zhao, Mary Tenny, Pranitha Thumma<\/a>, Sheron Kumar<\/a>, Vinay Gusain<\/a><\/p>\n

For Best Customer or Patient Outcome, the challenge was to stop and really sit with what a clinic, a clinician or a patient needs, not what’s interesting to build. Judges were looking for genuine relief from an everyday frustration: a faster answer, an easier day, a manual step finally gone.<\/p>\n

The team that stood out was CodeBlue, who looked at the common queries and support tickets that kept recurring, and did something simple but not always easy: they truly stepped into the shoes of the clinician, the practice manager, the patient on the other end of that call, and worked backwards from what would genuinely resolve it for them.<\/p>\n

CodeBlue,\u00a0looked at the common queries and support tickets that land with Medtech every day: is capitation reconciling correctly, which consults are actually profitable, how much revenue last month’s no-shows really cost, how to pull together a report for the accountant. None of these questions had a home inside Medtech. Practice managers were solving them in a spreadsheet, over the phone with support, or not at all.<\/p>\n

As the team explained:<\/p>\n

“Every piece of it maps to a real operational task a clinic does today with no proper tool.”<\/em> – Team CodeBlue<\/strong><\/p>\n

The insight that shaped their thinking came directly from listening to their own support calls. Customers would ring in frustrated, be walked through every screen, report and workaround available, and still leave without an answer they could act on.<\/p>\n

“Giving someone more options isn’t the same as giving them an answer they can act on.”<\/em> – Team CodeBlue<\/strong><\/p>\n

That reframed the problem for the team. The gap wasn’t a missing feature or a missing report inside Medtech Evolution. The data needed to answer these financial questions was already there. What was missing was the interpretation, a step that normally required accounting expertise or hours of manual work most clinics simply don’t have.<\/p>\n

FinPulse explored how an AI layer could do that interpretation instantly, turning a plain question into a correct, reliable answer, without a practice manager needing accounting training or a call to the help desk.<\/p>\n

“With FinPulse, that same question gets answered correctly and instantly, every time, by anyone in the clinic.”<\/em> – Team CodeBlue<\/strong><\/p>\n

For the team, the value wasn’t only the time given back to clinics every month-end. It was what it proved about what Medtech could become.<\/p>\n

“Right now we’re a practice management system that stores data and shows it back. If this works, we’ve shown we can build an AI layer that reasons over that data and gives a real answer.”<\/em> – Team CodeBlue<\/strong><\/p>\n

FinPulse reflected the intent of the Best Customer or Patient Outcome brief precisely: it began with a frustration clinics were already living with every day, and turned it into a genuine, immediate answer.<\/p>\n

\n
\n
\n
\"Article<\/div>\n<\/div>
Medtech Hackathon Team: CodeBlue<\/figcaption><\/figure>\n<\/div>\n

<\/h3>\n

Helping Clinics Access the Right Support Sooner<\/h3>\n

Ships Monday<\/strong><\/p>\n

Team name: <\/strong>7,000 RPM<\/p>\n

Prototype name: <\/strong>PracticeConnect<\/p>\n

Team members:<\/strong> Prashant Kumar<\/a>, Tyson Somerville<\/a>, James Portz<\/a> and Claire Ge<\/a><\/p>\n

The Ships Monday <\/strong>category recognised a practical prototype that addressed a genuine challenge and demonstrated the potential to begin delivering value quickly.<\/p>\n

Team 7,000 RPM <\/strong>won the category with PracticeConnect, an idea focused on helping Medtech identify and connect with healthcare clinics that may benefit from additional tools and support that Medtech can offer.<\/p>\n

The team began by considering the experience of clinics that might not yet know about the solutions available to them. These clinics could be working without tools that might make everyday tasks easier for their teams and improve the experience of their patients.<\/p>\n

As the team explained:<\/p>\n

“By pulling together information that was already out there we could see clearly which clinics weren’t yet using the modern tools already available within the Medtech ecosystem. That let us connect the right Medtech consultant with the clinics who’d benefit most, so the right kind of help finds them sooner.” <\/em>– Team <\/em><\/strong>7,000 RPM<\/strong><\/p>\n

The team recognised that valuable information was available but bringing it together could involve considerable manual research and time. This took time away from speaking directly with clinics, learning about their needs, and helping them find the right support.<\/p>\n

Their idea was grounded in a straightforward insight:<\/p>\n

\u201cInstead of searching all over the place, bring all the information together onto one dashboard.\u201d <\/em>– Team <\/em><\/strong>7,000 RPM<\/strong><\/p>\n

PracticeConnect explores how Medtech teams could develop a clearer understanding of where support may be valuable, helping the right Medtech consultant connect with the right clinic sooner.<\/p>\n

The purpose was not simply to improve the internal process. It was to create a more proactive and relevant experience for customers.<\/p>\n

By reducing the time spent searching for information, Medtech teams could spend more time having genuine conversations with clinics and understanding the challenges they are trying to solve.<\/p>\n

\u201cIt means our team gets to spend their time on what matters. Real conversations with the clinics who need us.\u201d – Team <\/em><\/strong>7,000 RPM<\/strong><\/p>\n

The team captured the customer-focused purpose behind PracticeConnect in one sentence:<\/p>\n

\u201cWe built PracticeConnect so the clinics who need us most don\u2019t have to wait to be found and so our team gets to spend their time actually helping, not searching.\u201d – Team <\/em><\/strong>7,000 RPM<\/strong><\/p>\n

PracticeConnect reflected the intent of the Ships Monday brief: begin with a real customer need, create a focused response, and demonstrate how the idea could deliver practical value for both Medtech and the clinics we support.<\/p>\n

CodeBlue, PracticeConnect, Chatterbox and the MCP Server addressed very different challenges, but each team followed the same important principle: start with the problem experienced by the customer and find a solution.<\/p>\n

\n
\n
\n
\"Article<\/div>\n<\/div>
Medtech Hackathon Team: PracticeConnect<\/figcaption><\/figure>\n<\/div>\n

 <\/p>\n

PracticeConnect considered how Medtech could connect clinics with relevant support sooner. Chatterbox explores how customers could access trusted answers more easily. MCP looked further ahead, considering how technology could help clinicians interact with information more naturally and responsibly.<\/p>\n

None of the teams began with technology for technology\u2019s sake. They began by asking:<\/p>\n