Domain-Level Requirements
Our software transforms fragmented healthcare data into something searchable, accessible, and actionable. At the foundation, we're building three core capabilities: searchable healthcare data for pricing, providers, and procedures; accessible healthcare data with clear, transparent pricing once you've found what you need; and user-friendly authentication with secure login and signup to personalize your experience.
Functional-Level Requirements
Here's how we deliver on those domain goals, from must-haves to should-haves that push the system even further.
Must-Haves
A central search interface moves users from query to results instantly, powered by Azure containers that categorize procedures by location and type. Choose a procedure and see everything: pricing, provider details, and relevant information displayed cleanly. Login and signup pages are protected by Azure tokens and end-to-end HTTPS encryption.
Should-Haves
Upload medical bills or EOBs and let our system process them into structured data, flagging potential overcharges. Refine results by geography for location-specific pricing and availability. Note that document scanning is resource-intensive and may require dedicated GPU processing for AI-driven analysis.
Performance Requirements
Speed and responsiveness aren't optional. They're essential to keeping users engaged. Search delivers results in under 5 seconds, achieved by sorting data into Azure containers by procedure type and location. Our decompiler runs on a schedule to minimize CPU load, processing data updates only when necessary. The React-powered frontend stays snappy, with clear feedback when backend processes or connections slow down.
Environmental Requirements
Built entirely on Microsoft Azure, our infrastructure is secure, scalable, and compliant from the ground up.
Platform and Hosting
Azure App Services with PostgreSQL and Blob Storage for data management. Accessible via standard browsers with no special hardware required.
Development Stack
Backend uses Python (FastAPI) and Node.js. Frontend uses React. Version control and CI/CD through GitHub with automated pipelines.
Security and Compliance
HIPAA and HITECH compliant to protect healthcare data. Azure Active Directory for authentication with token-based role access. TLS 1.2+ for data in transit, AES-256 for data at rest.
Testing and Deployment
Dedicated staging environment separate from production. Continuous integration with unit and functional testing before merge. Production deployment via GitHub Actions for seamless releases.
Development Process
Our development approach prioritized flexibility and momentum, adapting week-to-week based on progress and priorities rather than rigid sprints.
Workflow and Collaboration
The team evaluated current progress and assigned tasks dynamically on a weekly basis, allowing us to pivot quickly as challenges emerged. Primarily remote work supplemented by weekly meetings to sync up, troubleshoot blockers, and align on next steps. Discord served as our primary collaboration hub for quick questions, updates, and coordination.
Version Control Strategy
Separate branches for major components like cloud and frontend allowed parallel development without conflicts. All code versioned and tracked through GitHub, with pull requests for merging feature work.
Deployment Approach
Primary deployment through Bicep templates for consistent, repeatable Azure infrastructure provisioning. For rapid iterations or troubleshooting, manual deployments kept development moving forward.
This adaptive process let us stay responsive to technical challenges while maintaining steady progress toward our goals.