Care IQ / In development
Trust starts
at the boundary.
A healthcare operations platform for independent practices.
A small first workflow, with a deliberate foundation.
ContextIndependent medical practices
FocusArchitecture & implementation
StageFirst working vertical slice
The starting point
Shared infrastructure.
Separate practices.
The first slice connects authentication, patient records, and appointment scheduling. Practices can share the platform, but the data boundary between them has to be explicit.
Follow a request
From identity to integrity.
Follow the practice context through the system.
Clerk / Authentication
Establish identity.
The request begins with an authenticated identity and an active organization. Identity answers who is making the request.
An illustrated request path. No patient data.
The tradeoffs
Good choices
have costs.
Architecture becomes more useful when the tradeoffs are visible. These are the consequences of the structure in the current implementation.
A versioned interface keeps data access and practice resolution in one place. It asks for separate deployment, cross-origin configuration, and care around contracts between the web app and API.
Tenant policy sits alongside the data, with the practice included in patient–appointment relationships. It asks for correct database roles, consistent transaction context, and tests for denied and cross-practice access.
A connected path through UI, identity, API, and database comes before the platform grows wider. It asks for restraint: features beyond the first patient and appointment slice remain future work.
What exists today
One complete workflow first.
- Authenticated patient creation and listing
- Appointment creation and listing
- Practice context and database row-level security
- Patient–appointment relationships scoped to the practice
- Version-controlled schema migrations
Active development. Operational outcomes will be added when available.
The tools
Next.js · React · TypeScript
Express · PostgreSQL · Drizzle · Clerk