How is Fixxbook modeled after other industry regulations?

We didn’€™t say, “€œWe’™re going to make sure that every service provider in the world is credentialed through Fixxbook and we’€™re going to create this credentialing tool.”€ It was quite the opposite: Our clients were coming to us and saying, “€œWe need more information about these contractors. We need to know more about them; we need to know the answer to this question and that question.”

So what’€™s driving the development of Fixxbook today? The private networks of clients. We realized that other industries had gone down this same path (of credentialing)… where software was created specifically because of an event or series of events:

The first one we saw that we could relate to was the Health Insurance Portability and Accountability Act (HIPAA) laws in 1996. Before it, health insurance and doctors were holding people hostage…  In effect saying, “€œWell, if you don’€™t want to use me as your doctor, we’€™re not going to give you your medical records. You’re going to have to start all over again from the beginning with your tests, because they belong to us.”

That’€™s when the government said “œNo; healthcare information belongs to the individual, and they can take it wherever they want to take it and get service.” And that’€™s when people’€™s private information was all over the place and on the streets.

So in 2003, I think it was, they created some additional policies and procedures as far as information security. One of the pieces of that was that any healthcare facility, whether you’€™re a doctor’€™s office or hospital, you have to have policies and procedures in place to protect people’s information. One of those was that anybody coming on the site – any type of vendor – whether they’re coming there to do work, to bring catering, or work on equipment – that facility is required by law to know who that person is, where they’€™re coming from, background checked, and that they have this information on file… for everyone who’s coming on site.

A company that was already in the software business, in the healthcare business, doing something else probably not much different than ServiceChannel situation, who just happened to be in the industry with another product, created VendorMate, a credentialing software specifically for healthcare vendor credentialing. They didn’€™t create the software ahead of the need. The need was there, created by regulation, and they created the software.

Another example is in 2001, after 9/11: The Dept. of Homeland Security was created via the PATRIOT Act, to protect our infrastructure. And software was developed.

There’s a couple of popular softwares now that are used in office buildings, power plants, refineries, that keep track of all of the credentials of anybody coming on site with the badges and the data and the retinal eye scans. This software was created specifically from the need that came out of the regulations for security and management of the credentials of individuals that are coming into these buildings.

So there’€™s two examples of where companies didn’t just say, “You know, let’€™s make life more difficult. Let’€™s create a software that’s going to require effort on a lot of people to gather information.” It was created as the result of a need for security.

Leave a Reply

Your email address will not be published.