EzMR gives EMS teams real-time, HIPAA- and HIE-compliant access to critical patient data so they can make life-saving decisions under pressure.
- Why EzMR
- What It Does
- Key Features
- Architecture
- Tech Stack
- Setup
- Usage Walkthrough
- Security & Compliance
- Screens & Visuals
- Challenges & Learnings
- Roadmap
- Contributing
- License
In emergencies, seconds matter. Paramedics often treat without context on allergies, implants, meds, and history due to fragmented HIE rules and strict “minimum necessary” HIPAA sharing. EzMR acts as the compliant bridge between hospitals and EMS, unlocking only what each state and role permits.
- Compliance Filter: Dynamically exposes permitted patient fields by state HIE + HIPAA rules.
- Unified EMR View: Normalizes records across common EMR systems into a clean, queryable schema.
- Fast Decision Support: AI-powered search and 3D medical visualization reduce cognitive load in the field.
- AI Clinical Search — Pull allergies, meds, vitals, and conditions from messy notes in seconds.
- 3D Medical Diagramming — React Three Fiber models with skeleton overlays + clickable body regions.
- Medical Imaging — DICOM/X-ray upload & viewing with window/level, zoom, and multi-slice.
- Secure Uploads — Cloudinary pipelines for sensitive docs & imaging.
- Audit & RBAC — Fine-grained, role-based permissions with full read audit trails.
- Multi-Tenant SaaS — Hospital/agency separation, break-glass access, and comprehensive logging.
- Real-Time UI — Debounced APIs, optimistic updates, robust error handling.
- 25+ Prisma models:
Patient,Allergies,Medications,Problems,ClinicalNotes, etc. - Multi-tenant schema with role-based access and full audit logging.
- AI pipeline maps 800+ medical terms for injury/body-part identification.
- Frontend: Next.js + React + TypeScript, Tailwind, Radix UI, Shadcn, Framer Motion
- 3D/Graphics: Three.js, React Three Fiber, Drei
- Backend/APIs: Next.js API routes, Vercel AI SDK
- AI: Google Gemini 2.0 Flash via Maestra Agent Framework (structured output schemas)
- Database: PostgreSQL (Neon) + Prisma
- Auth: NextAuth.js (magic links via Resend), break-glass emergency access
- Files/Imaging: Cloudinary, JSZip, dicom-parser
- Compliance: HIPAA/HIE policy filters, field-level permissions, exhaustive auditing
Prereqs: Node 18+, PNPM/NPM, PostgreSQL (Neon URL), Cloudinary creds, NextAuth secrets.
# 1) Install
pnpm install
# 2) Env
cp .env.example .env.local
# fill in: DATABASE_URL, NEXTAUTH_SECRET, CLOUDINARY_*, GEMINI_API_KEY, RESEND_API_KEY
# 3) DB & Prisma
pnpm prisma migrate deploy
pnpm prisma generate
# 4) Dev
pnpm dev- Sign In via magic link (NextAuth + Resend).
- Onboard Tenant (hospital/EMS agency), create roles, assign field-level permissions.
- Import/Sync Records from EMR or upload DICOM/X-ray; metadata normalized in Prisma.
- Use AI Clinical Search to surface allergies/meds/vitals and structured summaries.
- Visualize patient issues with 3D anatomical model overlays (clickable regions).
- Audit every access — reads/writes logged automatically for compliance.
- Minimum Necessary: Policy engine reveals only what each role/state permits.
- RBAC + Field-Level Controls: Admins toggle fields per role; UI renders any combination cleanly.
- Audit Trails: Every read/write captured with actor, timestamp, and context.
- Break-Glass: Emergency access with mandatory post-hoc review.
Drop screenshots or short clips here when you’ve deployed the app (UI dashboard, DICOM viewer, 3D model view, AI search results).
- DICOM viewer showing window/level & multi-slice
- 3D model with body-part highlights
- AI search panel extracting allergies/meds
- Role editor (field-level toggles)
- Audit trail explorer
- AI Note Structuring: Reliable, schema-bound outputs required multi-step prompts + Maestra structured schemas.
- 3D Model Tradeoffs: Pure prisms lacked clarity; pure skeleton was heavy. Hybrid model delivered responsiveness and readability.
- Security Design: “Blanket filters” broke workflows. Field-level configurability + dashboard redesign solved it.
- Scale HIE Integrations across states and major EMRs
- Enterprise Partnerships for production pilots
- Global Access with offline-first kits for low-connectivity regions
- Analytics: outcomes dashboards & cohort insights
- EMS UX: voice-first flows, faster field data capture