E-government has at least two big problems, and the author faced both of those. First, the users need to be authenticated, as in you are the person you claim t

E-government has at least two big problems, and the author faced both of those. First, the users need to be authenticated, as in you are the person you claim to be authenticated. Almost no other web service actually needs to know that. Banks are an other exception and for example here in Finland they provide authentication for other private and government web services. Finland also has those secure chip ID cards the author briefly mentioned. The problem with those is that, at least here in Finland, nobody has them. And most of those who have one, don't own a reader needed to use the chip. The second problem is about logging and archiving. Governments are subject to very strict laws and regulations about how certain cases need to be handled. The are processes to follow. Who did which step when has to be recorded. When the case is finally closed, every piece of paper about the case needs to be archived. Was something denied because a letter from the applicant did not have the necessary information? That letter needs to be archived. All this is manageable when the case is handled in paper. If the case is handled using a web service, things get more complicated. The system has to log all actions done in the case. It has to archive documents in proper ways. That's not impossible. But it is harder than stamping and signing papers for those whose jobs have been about stamping and signing papers for years. It's also harder for those implementing the web service, as most of the strict regulations don't apply in other projects. All this means that big money needs to used for creating something that adds complexity and is not strictly necessary, and oh boy the government likes to skimp on those kind of projects.