Making Hospital Data Extracts Visible, Reliable, and Downtime-Ready

1. A guided tour of Insight Pipeline

Welcome to Insight Pipeline. In this walkthrough, we'll connect to a database, configure an SFTP destination, generate a Clinical Summary document, and deliver a census extract. All patient information shown is synthetic demonstration data. The Dashboard brings schedules and execution history together. Operators can see what's enabled, what's due next, and the recorded result of each run. Delivery verification adds another signal alongside execution status.

Insight Resilience provides purpose-built clinical documents for downtime planning. We'll use Clinical Summary, which organizes patient and encounter information into a readable PDF. Connections is where we define reusable database sources and SFTP destinations.

Alerting provides recipient configuration and an alert audit. Email transport is ready in this demonstration; recipients would be configured before relying on notifications. Deployment brings together operational status, access management, and approved export locations. Overview provides a broader picture of execution activity and trends. Together, these tabs help teams manage recurring delivery from one application.

2. Create a database connection

Let's begin with the source connection. We give it a recognizable name, select SQL Server, and enter the server, port, database, and default schema. The hospital's database administrator determines the approved account and its permissions.

The form also identifies the credential references used by the application. Temporary test credentials let us check connectivity before saving. Passwords remain masked during entry.

We test the connection, then save it to the source list. This configuration can now be reused by our schedules. A successful connection test establishes connectivity; reviewing the selected source view and the resulting extract remains part of setting up the workflow.

3. Configure an SFTP destination

Next, we create an SFTP destination. We enter a descriptive name, the server address and port, and the remote folder. The expected host-key fingerprint should come from a trusted source. It lets the application check the server's identity rather than simply trusting an unfamiliar endpoint.

We enter the dedicated account credentials and save the destination. A test upload checks the configured delivery path using a small synthetic file.

Once it finishes, we review the verification result. Testing and enabling are separate steps: a passed test does not automatically enable the destination. The destination must also be enabled before it can be used for scheduled delivery, as it is in our later census example.

4. Schedule a Clinical Summary PDF

In Insight Resilience, we select Clinical Summary and open its schedule. The document lists the source fields it requires. We choose our SQL Server connection and the matching Clinical Summary view.

This schedule produces a PDF. We review the filename and choose an existing approved folder. The folder browser selects a server-side destination; the underlying folder permissions must already allow access.

We review the cadence and timezone, then save the schedule. Run Now starts an immediate execution without waiting for the next scheduled time.

Here is the generated Clinical Summary. Patient information is organized into a readable document, with encounter details, contacts, clinical alerts, and other information supplied by the source view. This can support downtime preparation when the hospital has confirmed the content, refresh interval, and how authorized staff will reach the documents during an outage.

Back in the application, we review the recorded outcome and delivery verification for the run.

5. Deliver a census extract by SFTP

Now we create a separate data-extract schedule from the Dashboard. We name it Current Census, SFTP Delivery, choose the SQL Server connection, and select the census view. We configure a pipe-delimited text file and select our SFTP destination. This demonstration keeps the default daily cadence. For a hospital workflow, the time, timezone, file format, and delivery requirements would be agreed before recurring execution.

After saving, we use Run Now to execute the schedule immediately. In the receiving SFTP folder, we can see the delivered file. Opening the synthetic extract lets us inspect its contents. Successful transfer and correct file contents are separate checks.

Back in job history, the census run shows success, verified delivery, and one hundred twenty rows. Opening the schedule's own history narrows the view to its recorded executions. The Rerun action is also available from the application, without manually changing a query or its parameters. A rerun queries the source again using the retained run's parameters, so results can differ when the source data changes.

6. From configuration to a visible result

We've followed two workflows: a Clinical Summary PDF delivered to an approved folder, and a census extract delivered through SFTP. Insight Pipeline brings configuration, scheduling, and execution history together so teams can see what ran and investigate the result. The next step is to choose one hospital-approved workflow and review its output with the people who will use it. Contact EHR Data Solutions to discuss a demonstration or a scoped pilot.