Integration
Standalone by design. Live on eClinicalWorks.
A hospital EMR integration is a multi-quarter project. Because inFormed Consent runs standalone, you can pilot and prove value in weeks, then integrate on your timeline, not ours. On eClinicalWorks, we already read the schedule.
Four steps, at your pace
Standalone
inFormed Consent runs with zero EMR integration. Deploy in days, not quarters, without opening an IT project. The signed consent record downloads as a PDF your team attaches to the chart, and we can bulk-import a patient list to get a practice live quickly.
- No EMR dependency to start
- Signed PDF for the chart
- Bulk patient import
eClinicalWorks schedule sync
Integrated witheClinicalWorksWe read the practice schedule straight from eClinicalWorks through its FHIR APIs, every hour during business hours. Each upcoming visit lands on an Upcoming visits list with the consent we would suggest, read from the visit type and reason, and a check for consents the patient has already signed. Each site carries its own brand, so a new patient gets the right welcome. Staff review and send. Nothing reaches a patient without a staff click. Running now at a multi-site interventional pain practice.
- eCW FHIR R4, read-only
- Hourly schedule sync
- Suggested consent per visit
- Staff approve every send
The consent, back in the chart
Next on eClinicalWorks: open the visit list to every staff member at a practice, fill surgery dates into the patient journey as they are booked, stop reminders when a visit is cancelled, and write the signed consent back into the eCW chart. Beyond eCW, the record moves to PDF/A-3 with embedded FHIR and MRN mapping, so any EMR or document system ingests it as structured data. We build that with the first institutional partner that needs it.
- Signed consent written to the eCW chart
- Surgery dates from the schedule
- PDF/A-3 + embedded FHIR
Deeper integration
SSO, scheduling feeds from other EMRs, and launching inside your EMR workflow are integrations we scope and build with a committed partner. We are a small, senior team, and we ship the integration your rollout actually needs rather than a generic connector nobody uses.
- SSO (SAML / OIDC)
- Other EMR feeds (HL7 / FHIR)
- EMR launch / embed
The integration questions we always get
Do we need to integrate with our EMR to start?
No. inFormed Consent runs standalone. Integration is a roadmap you control, not a prerequisite.
How does the signed consent get into the chart today?
The record downloads as a PDF your team attaches to the chart. For volume, we can bulk-import a patient list so a practice is live quickly.
Do you integrate with eClinicalWorks?
Yes. We read upcoming visits and patient demographics from eClinicalWorks through its FHIR APIs, server to server, with a signed key and no shared passwords. It is live in pilot at a multi-site pain practice today.
What does our eCW practice need to do?
Very little. Your eCW admin enables our app under FHIR APIs, and we map your providers, sites and visit types once at onboarding. Read access needs no extra eCW contract. Writing the signed consent back into the chart is a separate eCW add-on.
Does the eCW sync send anything to patients on its own?
No. The sync only stages visits for your staff to review. Every consent, video or journey goes out because someone on your team chose to send it.
Can the consent record become structured data our systems ingest?
Yes. That is on the roadmap: a machine-readable PDF/A-3 record with embedded FHIR and MRN mapping, so the consent flows in as data rather than a flat file.
What about SSO, other EMRs, or launching inside our EMR?
Those we build with a committed partner, scoped to your stack. We are EMR-agnostic and standalone by design, so we integrate to your environment rather than forcing ours.