Set up Hospital Patient Lifecycle
Import the inactive workflow kit and run its supplied synthetic example. Enter API credentials directly in your client-owned n8n Credentials vault, never in Aria's form.
What your client supplies
- Hospital-approved HMS/EMR/CRM APIs or documented human handoffs
- Approved scheduling, messaging, and AI providers
- Security, privacy, and clinical-stakeholder review
- Named workflow owners and signed production scope
Product-specific provider and API checklist
HMS/EMR/CRM and scheduling — Required for the scoped production use
Supplies approved administrative status and available slot values.
- Vendor APIs, sandbox docs/credentials, scope approval, source-of-truth owner
Credential destination: Client-controlled n8n Credentials vault only.
- Review all synthetic safety paths.
- Connect an approved sandbox API or keep a staff handoff.
Messaging/AI provider — Optional
Optional administrative drafts and consented messages.
- Approved provider, supported features, consent and facility security/privacy approval
Credential destination: Credential vault only; not Aria’s form.
- Add provider credentials in client n8n.
- Keep clinical, write, and send actions under facility approval.
Installation and API connection are separately quoted
Ask Aria to contact you for installation, provider API wiring or a managed usage-cost quote. Purchasing a kit does not activate integrations, calls, broadcasts or schedules.