For hospitals
Patient experience that fits your Epic workflows.
NEPA adds a low-friction patient channel for meal preferences, daily check-ins, and confidential feedback — without adding charting work for your clinical teams.
How the integration works
Standards-based, push-only
We use FHIR R4 and SMART Backend Services (authenticated with private_key_jwt). Patient and encounter context arrives through hospital-authorized ADT and approved FHIR channels — push-only, least-privilege.
No reusable credentials, no new chart burden
NEPA issues its own short-lived sessions and does not retain reusable hospital or Epic tokens for routine workflows. Where appropriate, check-ins write back as a QuestionnaireResponse against an Epic-assigned questionnaire.
Dietary preferences, not diet orders
Your EHR remains the source of truth for clinical diet orders. NEPA captures patient preferences and appetite to support — never override — your dietary workflows.
Staff access you control
Pilot staff use app-managed accounts with mandatory MFA and role-based access. Hospital SAML/OIDC SSO and SCIM are supported enterprise upgrades when you're ready.
Security & compliance posture
- Hosted on HIPAA-targeted AWS infrastructure, encrypted in transit and at rest.
- A Business Associate Agreement (BAA) is signed with every hospital customer.
- Append-only audit logging with database-level role separation.
- Patient data is never sold, used for advertising, or used for unrelated research.
NEPA is an early-stage product. Formal third-party certifications (e.g. SOC 2, HITRUST) are on our roadmap and not yet in place; we're glad to discuss our current controls and timeline.
Inquire
Tell us about your hospital and EHR environment. We'll follow up to talk through a pilot.