Skip to content
Demo with synthetic sample data. “Prairie State HIE” and every hospital shown are fictional. No real patient data, no PHI.

Regier HealthIT · Assessment demo

ENS Alert Health Check: Lights On for your alert pipeline.

Did the right alert reach the right care coordinator, on time? Most HIEs can’t say for sure.

An encounter notification can fail quietly at five places between the hospital’s ADT feed and the care coordinator’s worklist. A feed goes silent over a weekend. A discharge sits in an MPI review queue. A Direct address bounces. Nobody gets paged, and nobody knows until a patient is readmitted without a follow-up call.

You promised your hospitals compliance. Can you prove it? Many HIEs send the encounter notifications their member hospitals rely on for the CMS e-notification Condition of Participation, and HIEs are expected to meet 21st Century Cures Act information-blocking expectations. Few can show the evidence. The Health Check produces dated timing and delivery evidence behind that promise.

● Demo · synthetic data for a fictional HIE

The blind spot

Engines report “running.” They don’t report “delivered.”

Interface monitoring tells you a channel is up. It doesn’t tell you whether a discharge from a rural hospital at 11:40 PM on a Saturday reached the right primary care practice before Monday.

Silent feeds

A hospital interface stops sending A03 discharges after a weekend change. Volume drops to zero, but nothing errors, so nothing alarms.

Stuck matches

Missing MRNs or demographic drift push messages into MPI manual review. The alert waits in a queue, or never fires.

Unproven delivery

Portal, EHR and Direct deliveries go out without confirmation tracking. Stale Direct addresses bounce and nobody is told.

You promised your hospitals compliance. Can you prove it? When an HIE sends notifications on a hospital’s behalf, the hospital’s CMS e-notification CoP evidence depends on the HIE’s pipeline. Undelivered or late alerts may also raise information-blocking questions. The Health Check gives you dated, per-hospital evidence instead of assumptions. (This is operational evidence, not a legal determination.)

Why now

HIEs are moving from connectivity to provable data quality.

In “Health Data Quality Across Three HIEs Nationwide” (Civitas Networks for Health case study, published as “Measuring What Matters,” November 16, 2026), three member HIEs describe the same shift:

From manual review to continuous monitoring

Site-level scorecards, dashboards, data traffic monitoring, and automated validation against HL7 and C-CDA specifications, with feedback sent straight to participants.

Standards-based quality rubrics

Measures aligned to USCDI, PIQI, HEDIS, Medicaid quality programs and NCQA’s Data Aggregator Validation (DAV) program.

Governance and accountability

Quality councils and committees that set onboarding thresholds by care setting, so data quality becomes an operational discipline, not a side project.

Patient identity as the foundation

Reducing EMPI duplicates and strengthening matching, because duplicate records point to wider downstream problems.

Much of that work is being designed and built in-house, over years. The ENS Alert Health Check is a turnkey, ENS-focused way to get there: continuous monitoring, scorecards and evidence for the alert pipeline, starting with a two-week baseline instead of a multi-year build.

Summary of a public case study. Civitas Networks for Health has not reviewed or endorsed this service.

Where the ENS Alert Health Check fits Three overlapping circles: engine and interface health, feed data-quality scoring, and ENS alert operations and CMS evidence. The ENS Alert Health Check sits in the center where all three overlap. ENGINE & INTERFACE HEALTH Is the pipe running? FEED DATA-QUALITY SCORING Is the content good? Interface engine monitors Channel and queue alerts Uptime dashboards Message-quality scoring HIE site scorecards USCDI / PIQI / DAV rubrics Periodic compliance reports Monthly ADT audits ENS ALERT OPERATIONS & CMS EVIDENCE Did the right alert reach the right person on time? ENS Alert Health Check
Categories based on a public-source market review, November 2026. Each circle is well served on its own. The center, where all three meet, is where alerts are actually proven.

Still open in the center

What the Health Check adds

  • Event-to-alert latency, checkpoint by checkpoint, against the CMS “at the time of” expectation
  • Panel match: did the matched patient hit a subscriber roster?
  • Delivery confirmation across EHR, portal and Direct / DirectTrust
  • Silent-feed alarms against each feed’s normal rhythm
  • Geo/demographic MPI testing with cohorts that reflect your state’s populations
  • Consent and opt-out enforcement tested end to end
  • Cross-HIE benchmarks with anonymized peers

How it works

Six checkpoints, timed end to end.

Each test follows one alert through the whole pipeline and records when it passed each checkpoint, and where it stopped.

  1. Hospital ADT

    Admit, discharge and update events leave the hospital EHR.

    A01A03A08

    Checks: arrival time, A03 coverage, PV1-36

  2. HIE engine

    Messages are parsed, routed and filtered.

    MirthOpen Integration Engine

    Checks: errors, filters, queue time

  3. MPI match

    The patient is linked to the right person in the master patient index.

    Auto-matchReview queue

    Checks: match rate, review delay

  4. Panel match

    The matched patient is checked against each subscriber’s attributed roster.

    Care teamPayer panel

    Checks: roster hit, suppression

  5. Delivery

    The alert goes out to the subscriber’s channel.

    EHR inboxDirect / DirectTrustPortal

    Checks: sent, bounced, delivery time

  6. Ack and open

    The receiving system confirms receipt, and a coordinator opens it.

    ACK / MDNOpened

    Checks: confirmation, time to open

Synthetic sentinel patients

Clearly tagged test patients are enrolled on a test panel. On a schedule, the Health Check injects A01, A03 and A08 messages for them through each hospital’s feed and times every checkpoint.

  • Different times of day, so you see the noon discharge rush, overnight batch windows and weekends, not just one snapshot.
  • Low volume: a handful of test patients per feed per hour. It measures the real load without adding to it.
  • No PHI and no BAA for the sentinel method. Test patients are fictional and tagged so they never reach a real worklist.
  • Optional aggregate metrics from real traffic (match rates, field completeness) can run inside the HIE’s environment.

A sample sentinel schedule

Each filled hour is a test run for one hospital feed. Denser coverage during the discharge rush and the overnight batch window.

12 AM6 AM12 PM6 PM11 PM

Interactive sample dashboard

Prairie State HIE: Network Health

Every number here is generated from a seeded random model of a fictional HIE with 12 fictional hospitals. Change the filters and the charts recompute.

Sample report · fictional HIEPrairie State HIE

Where the time goes

Median and 95th-percentile minutes at each checkpoint, sentinel runs.

End-to-end latency by hour and day

Median minutes from hospital event to confirmed delivery. Hover or tap a cell.

Hospital scorecard

Sort by any column. Select a hospital to see its field completeness and top issues.

Hospital scorecard, fictional sample data

Silent-feed detection

Hourly inbound ADT volume against the feed’s normal rhythm.

Expected rangeObserved messages per hourSilent-feed alarm

Peer benchmark

Prairie State HIE against anonymized peer HIEs A–F (sample).

Sample data only. Hospital names, peer HIEs and every value are fictional and generated in your browser from a fixed seed.

Sample findings

What a readout looks like.

A Full Assessment ends with findings your board can read and a fix list your interface team can work.

Top 10 remediation list (sample)

    Packages and pricing

    Start with a baseline. Keep the lights on.

    Starting-at prices and typical ranges. Final scope depends on the number of hospital feeds, delivery channels and networks.

    Pilot Baseline

    ~$10k one time

    Two weeks of sentinel tests on 5–10 hospital feeds.

    • Time-of-day latency heat map
    • Silent-feed and MPI findings
    • Top-10 fix list
    • One readout session
    Most common

    Full Assessment

    $15k–$25k one time

    Every hospital feed, end to end.

    • Checkpoint-by-checkpoint speed profile: hospital → MPI → panel → delivery
    • MPI match-rate findings
    • Scorecard for each hospital
    • CoP timing evidence by hospital
    • Leadership or board readout

    Health Check Subscription

    $2k–$4k per month

    Continuous monitoring after the baseline.

    • Scheduled sentinel tests
    • Silent-feed alarms
    • Direct delivery monitoring
    • Monthly hospital scorecards
    • Peer benchmarks across participating HIEs

    Add-ons

    Direct Secure Messaging / DirectTrust CoP delivery$5k–$12k setupValidates subscriber Direct addresses against the DirectTrust directory, tracks delivery confirmations, catches bounces and stale addresses, and produces CMS e-notification CoP evidence for each hospital whose alerts go by Direct. Ongoing monitoring is included in the subscription.
    Remediation sprints$5k–$15k eachHands-on work with the hospitals behind the worst feeds: PV1-36, missing A03s, MRN and demographic problems.
    CMS CoP compliance packet$3k–$8k per hospitalDated timing and delivery evidence for each hospital, ready for surveyors and boards. Can be sold through the HIE.
    Mirth 4.5.2 to Open Integration Engine migration$25k–$75kMove off an end-of-life engine to the open-source fork, with Health Check channels built in.
    MPI tuning readout$8k–$15kGeo/demographic-aware testing tailored to your state’s populations: synthetic sentinel cohorts built on local naming conventions, match and false-negative rates by cohort, and tuning recommendations handed to your MPI vendor’s team.
    National network check$5k–$12kCarequality, eHealth Exchange and TEFCA: query response time, document completeness, cross-network match rate and notification timing.
    Public Health Reporting Check$8k–$15kSyndromic surveillance (NSSP) timeliness and completeness, eCR (eICR/RR) delivery, ELR to the state, and Promoting Interoperability public-health measure evidence. Can also be folded into the subscription.
    Consent & Opt-Out Assurance$10k–$20kSentinel patients with opt-out, restricted and Part 2 flags verify that data is sequestered from queries, alerts follow policy, opt-outs take effect on time across the MPI, panels, national networks and Direct, and an audit trail exists. Built for markets with consent rules stricter than HIPAA.
    Annual Network Health Report$5kBoard-ready report for funding renewals and grant applications.
    Fractional ENS program advisor$3k–$6k per monthSenior help on rule changes, procurements and vendor management.

    Prices are starting points and typical ranges, not quotes. Travel, if any, is billed separately.

    Next step

    Want to see your own pipeline this way?

    Tell me how many hospital feeds you run, which engine and MPI you use, and how alerts reach subscribers. I’ll come back with a scoped Pilot Baseline.

    nickregier@gmail.com