Solutions · IT and clinical informatics
Standard interfaces, least privilege and changes you can review
Aurifex connects through standard Epic interfaces, signs people in through your identity provider and files nothing without a person's approval. Model and prompt changes are reviewed, versioned and can be rolled back.
Integration at a glance
| Data in | HL7 v2 ADT feed for admit, transfer and discharge events; FHIR R4 APIs for encounters, conditions, observations, medication orders, coverage and clinical notes |
|---|---|
| Where results appear | Case-management worklist columns, the Discharge Planning activity in the chart, pended orders and a review worklist your Epic analyst builds |
| Write-back | Only after a named person approves: pended orders signed by a physician, notes and packets filed or sent by the case manager |
| Sign-in | Single sign-on with SAML 2.0 or OpenID Connect |
| Epic versions | Epic 2023 and later; build: 3 worklist columns, 1 review activity, 1 report and 1 SmartText |
| Environments | Built and tested in your non-production environment, then silent mode on live data before go-live |
Security and access
- Business associate. Aurifex works under a BAA signed before any patient data is shared.
- Least privilege. Each part of the system runs under its own service identity and requests only the data its task needs.
- Role-based access. Mapped to your existing roles, with single sign-on.
- Encryption. In transit with TLS 1.2 or higher and at rest with AES-256, in US data centers.
- Language model. Reached through a HIPAA-eligible cloud service with zero data retention. Your data never trains models for other hospitals.
- Audit trail. Every read, draft, edit, approval and rejection, available to your compliance team.
The full IT and security review, including IT hours for a pilot
Change control
Changing a model or a prompt changes what clinicians see, so it's treated like any other clinical system change.
- Every model and prompt change is versioned, with a written reason.
- It's tested offline against an evaluation set and must pass the launch gates.
- A named reviewer approves it, and you're notified before release.
- It can be rolled back to the previous version at any time.
Nothing changes automatically in production because of real-time feedback. Feedback is reviewed first.
In testing
Security review
We sign a business associate agreement with each hospital before any patient data is shared. A completed security questionnaire and an architecture review with your security team are available on request.
See Aurifex on your own discharge workflow
We'll walk through your worklist, a drafted referral and how a pilot would be measured on your units.