Netal Health

FAQ

Operational answers for teams launching Netal Health

Use this page as a quick reference for onboarding, billing, security posture, and deployment readiness.

Where should users sign in?

All users start on netalhealth.com/login/. Account roles route users into the patient or doctor portal after authentication.

Why are patient and doctor portals separate?

Each portal has distinct permissions and workflows. Separation keeps boundaries explicit and reduces accidental role leakage.

Can users access portals without accounts?

No. Portal views require active account sessions and role checks before protected content or actions are available.

How does checkout work?

Pricing actions call backend checkout routes that redirect to Stripe hosted links configured in Render environment variables.

Where does AI run?

AI synthesis runs in backend routes only. Browser clients never contain provider API keys.

What is required for production database setup?

Apply all backend migrations on the production backend service shell using npm run migrate to avoid missing relation errors.

Navigate

Need deeper detail?

Open the page that matches the question type.

Product Questions

Workflow behavior and role-specific journeys.

Open Product

Security Questions

Authentication, consent, audit, and AI boundaries.

Open Security

Billing Questions

Plan comparison, trial windows, and checkout flow.

Open Pricing

Still Have Questions

Send your implementation question directly to our team.