Getting discharge events into RemedyRite
Send patient discharge events three ways — manual upload, scheduled SFTP, or a real-time stream.
Choose a delivery method
Each organization picks how it delivers discharge events in Settings → Data ingestion: Manual file upload, a scheduled SFTP drop-off we poll on a cron, or a near-real-time stream (e.g. a Kafka bridge) posted to our secure webhook. You can run more than one source at once.
Field mapping
Clients who use their own column or field names don't have to reformat. Add a JSON field mapping on the source to translate their names to our canonical format (for example patient_phone → mobile).
Metrics & resiliency
Every run is recorded with throughput, duplicates, and error counts, plus source health (last run, next poll). Bad rows are flagged for self-service fixing and never block the good ones; the pipeline de-duplicates and is safe to re-send. See the Pipeline health panel on the Imports page.
See it in action
Open the interactive demo at /demo/imports to watch a discharge event flow through validation, de-duplication, and survey scheduling for each delivery method. It's replayable and writes no data.