Inspiration
In the modern healthcare landscape, data is often siloed or too complex for immediate clinical use. We were inspired to build CliniqBridge to solve the "Last Mile" problem: turning raw FHIR (Fast Healthcare Interoperability Resources) data into actionable, summarized intelligence that a doctor can use in seconds, not minutes.
What it does
CliniqBridge is a robust Model Context Protocol (MCP) server that acts as a secure gateway to clinical data.
Real-time Summarization: It pulls complex JSON data for conditions and medications and presents them in a human-readable format.
Smart Interoperability: It understands and parses clinical data for specific patients (like our demo case, James Chen).
SHARP Integration: It utilizes the SHARP context extension to ensure that the AI Agent always knows which patient it is discussing without compromising security.
How we built it
We utilized a modern, scalable tech stack to ensure CliniqBridge is "production-ready":
Backend: Built with Python and FastAPI for high-performance asynchronous communication.
Protocol: Implemented the MCP JSON-RPC 2.0 standard to ensure native compatibility with the Prompt Opinion ecosystem.
Data Integration: Connected to HAPI FHIR R4 servers to fetch authentic clinical data.
Deployment: Hosted on Render to provide a live, reachable cloud service.
Challenges we ran into
One of the primary challenges was mastering the SHARP context propagation. Ensuring that the fhir_context and patient IDs passed correctly from the Marketplace to our MCP server required deep technical dives into the SHARP specifications. We also spent significant time optimizing our JSON-RPC handlers to handle large FHIR bundles efficiently without timing out.
Accomplishments that we're proud of
We are proud to have moved beyond "local code." CliniqBridge is a live service that proves AI can be successfully integrated into established healthcare standards. Successfully implementing the SHARP extension—the "secret sauce" of this hackathon—is a major milestone for our team.
What we learned
We gained a deep understanding of the Model Context Protocol and how A2A (Agent-to-Agent) communication will define the next generation of healthcare software. We also learned the importance of "Conversational Interoperability"—it's not just about moving data; it's about making that data useful for the clinician at the point of care.
What's next for CliniqBridge
Our next phase involves expanding CliniqBridge to support LOINC for lab results and SNOMED CT for more granular clinical coding. We aim to list more specialized agents in the Prompt Opinion Marketplace to support specific medical specialties like Cardiology and Oncology.
Log in or sign up for Devpost to join the conversation.