01
State programs
Medicaid agencies and public programs deciding how encounter notification, a procurement, or a health data utility should work in practice.
Healthcare interoperability advisory
Strategy, agreements, and follow-through for the organizations that have to live with the result.
I work with state Medicaid programs, health information exchanges, payers, providers, and health IT companies on the decisions that determine whether clinical information actually moves.
Lakeville, MinnesotaUpper MidwestNational engagements
01
Medicaid agencies and public programs deciding how encounter notification, a procurement, or a health data utility should work in practice.
02
HIEs and health data utilities sorting participation, TEFCA, governance, and the operating model after the strategy is announced.
03
Health plans, health systems, and care-coordination teams that depend on ADT, encounter alerts, and a feed someone will act on.
04
Vendors entering state and HIE markets, and consulting firms that need senior interoperability capacity on a workstream.
Services
Scoped to the decision in front of you. Most of the work falls into one of these.
New · Interactive demoENS Alert Health CheckProof that encounter alerts reach the right care coordinator on time, with CMS e-notification evidence for every hospital. Explore the sample dashboard →01
TEFCA and QHIN readiness, network strategy, and the choice between a state HIE and a health data utility. I help a leadership team decide what to join, what to build, what to ask of a vendor, and what the operating model has to be once the kickoff is over.
02
Advisory work with Medicaid and other government health programs. Encounter notification, program design, procurement and RFP support, and Rural Health Transformation Program work. The policy, the solicitation, and the exchange that has to follow are one engagement.
03
ADT and encounter notifications, care-coordination workflows, and EMS data moving into a health system, an HIE, or a health plan. We name who sends, who receives, under what agreement, and what the receiving side does differently because the data arrived.
04
For health IT companies entering state and HIE markets. Positioning, a stakeholder map, and the commercial conversations with Medicaid agencies, exchanges, health systems, and plans. I have led this kind of market development across seven Upper Midwest states. This is that work, offered directly.
05
Senior interoperability leadership for a defined season, or subcontracted capacity for a consulting firm that needs a practitioner on a state, HIE, or vendor workstream. You get me in the work. There is no bench of junior consultants behind this site.
About Nick
I am a healthcare IT and interoperability advisor. Regier HealthIT LLC is my practice, a Minnesota single-member firm based in Lakeville. The point of view is an Upper Midwest one: practical, relationship-heavy, and close to the operational detail. The work itself is national.
From 2024 to 2026 I was Market Director for the Upper Midwest at a national post-acute and care-coordination health IT company. I led market development and strategic relationships across Minnesota, Iowa, Nebraska, Kansas, Oklahoma, South Dakota, and North Dakota, with state Medicaid programs, health information exchanges, health systems, payers, and technology partners, spanning acute and payer markets and senior care.
A meaningful part of that chapter, and of the years just before it, was Minnesota’s statewide Encounter Alert Service. As engagement manager at Audacious Inquiry from 2019 to 2024, and then in the market director role, I helped build and expand the service from an early footprint of two or three participating hospitals and two subscribers into a statewide clinical event notification network. It supports care coordination and transitions for about 3.5 million lives. The relationships around it included the Minnesota Department of Human Services, hospitals, health systems, and payers.
Before that I led interoperability delivery at ImageTrend in Lakeville, from 2012 to 2019. The work was the Health Information Hub: connecting EMS clinical data with hospitals and HIEs, including co-authoring specifications to translate NEMSIS data into HL7. That delivery reached CRISP and initiatives in Rhode Island and Iowa.
I started in the technical work at Cerner in Kansas City. From 1999 to 2009 I was an HL7 interface engineer, supporting Millennium implementations and the interfaces that connected those systems to the rest of a health system. From 2009 to 2012 I was a senior operations leader in global business development and sales, where the interface background stayed useful in complex engagements.
I hold a B.S. in Information Systems from Emporia State University.
2024–2026
A national post-acute and care-coordination health IT company
Market development and strategic relationships across seven Midwest states, with Medicaid programs, HIEs, health systems, payers, and technology partners.
2019–2024
Audacious Inquiry
Minnesota HIE engagement. Helped build the Encounter Alert Service from a small hospital footprint into a statewide notification network.
2012–2019
ImageTrend, Lakeville
Interoperability delivery for the Health Information Hub, integrating EMS data into hospitals and health information exchanges.
2009–2012
Cerner, Kansas City
Operational leadership on enterprise healthcare technology engagements, alongside commercial and delivery teams.
1999–2009
Cerner, Kansas City
More than a decade of technical project work: Millennium implementations, HL7 interfaces, and clinical data exchange.
Approach
You work with me. Engagements are fixed-scope or fractional, and I subcontract to consulting firms that need senior interoperability capacity without adding a layer of account management.
01
What has to be true in six months, and who is accountable if it is not. Architecture diagrams come after that sentence is clear.
02
Program staff, counsel, clinical operations, the vendor, and the person who owns the feed. Most of the delay lives between them, not inside a standard.
03
A recommendation should survive a participation agreement, a statement of work, or an RFP response. If it cannot be signed, it is not finished.
04
I came up through interface engineering and technical project work, then spent years on the market side. I am useful while the feed is being built, not only in the workshop where it is described.
Perspectives
Three short views, in my voice, on problems I keep seeing. They are drafts for review: a considered reading of a document or a design choice, written to be edited before anyone treats them as published advice.
Draft for Nick’s review
CMS says clinical super intelligence cannot scale without trusted data exchange. In the roadmap I read, that data foundation never names TEFCA or a health information exchange.
Read the note: Trusted exchange, left out of the sentence that requires itDraft for Nick’s review
OCR’s HIPAA final rule on coordinated care is effective January 18, 2027, with compliance due July 17, 2027. For an HIE, a Medicaid agency, or a health plan, the work is in the workflow and the agreement.
Read the note: The coordinated-care rule is a feed problemDraft for Nick’s review
States are being asked to choose between the health information exchange they have and the health data utility they might become. The name is the easy part. Coverage, governance, and the alert are the work.
Read the note: Call it a utility when it does the job of oneContact
Tell me the organizations involved, the question you have to answer, and the date it is due. I read every note. There is no form and no phone on this site.