The aim of the OOP is to simplify interaction with public services and contribute to administrative burden reduction. The Once-Only Principle (OOP) holds that public administrations ideally collect data from citizens and businesses only once to share this information, within regulatory limits, with other administrative bodies and across Member States. The architecture is not built from scratch, but re-uses and enhances already available building blocks in order to seamlessly preserve interoperability and to comply with regulations and existing technical standards, leaving at the same time enough space for vendors and open source developers to propose their compliant solutions, whatever is their business model. The case study, stemming from the EU-funded Once-Only Principle project (TOOP) highlights the challenges faced by the architecture team when developing the Reference Architecture that tackles the Once-Only Principle across different countries and policy domains. This paper presents the development of a Reference Architecture for the Once-Only Principle in Europe. So far, many European countries have started to implement the Once-Only Principle at national level, but its cross-border implementation is still fragmented and limited. ![]() The Once-Only Principle states that citizens and businesses provide data only once in contact with public administrations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |