I was thinking to position the product more as a standalone component of healthcare. As of now, there is no need to access patient data. Administrators can access, add, and update checklists through a web interface, and then deploy new checklists out to all hospital staff who can access checklists through a browser or any iOS device.

As it currently stands, the main implementation of checklists in hospitals consists of nothing more than taping up a sheet of paper onto the OR wall. I want to give hospitals a tool to analyze checklist performance data and refine them for procedural purposes only – no patient data needed, as of now.

What are your thoughts on that?

I've worked on systems that have checklists tied to charging systems where the nurse practitioner is expected to record charges for every procedure as they check it off while caring for a patient. These "charge codes" are standardized across the industry, and multiple subsystems are designed to detect new charge codes and verify errors or insurance related issues as quickly as possible.

The basic lists as you described, are usually tied to charge codes and then applied on a patient by patient basis.

What you've observed is probably a hospital that didn't have such a system in place yet (they are expensive). While you could certainly pitch your product to such a place, they're likely going to ask if you can tie into a billing/charge code system. That's a pretty expensive and time consuming integration with legacy systems to do that.

My advice is to do as much business development as you can before writing any code. See if you can follow a nurse around and understand how the information flows through the system to figure out where you can add value without signing up for a lot of costly integrations.

The issue I see is that the checklist contains information that would be relevant to a malpractice claim. That makes integration important.