Governing through Architecture Generative Architectures

Transcription

1 Governing through Architecture Generative Architectures Ole Hanseth Department of Informatics University of Oslo, Norway

2 Strategic Architecting Morris and Ferguson: Architectures win technology wars! Architectural control points Platform centric ecologies Morroring Product producer Product users Innovation and generativity

3 The beginning 1987: Fürst s lab report transfer solution 1988: Telenor (Telemedicine in Northern Norway) Lab report transfer solutions Standardizing Statskonsult s Infrastructure programme: EDI Physicians invoices CEN TC/251, KITH Consensus: EDI

4 90-ies: The continuation Lab reports & orders, prescriptions, physicians and outpatient clinics invoices, admission and discharge letters,.. 00-ies: Lab reports & orders, prescriptions, physicians and outpatient clinics invoices, admission and discharge letters,.. ELIN projects The message effort (meldingsløftet) eprescription Status: Modest successes, coordination problems, always someone not doing as promised

5 The EDI Paradigm Information flow ICT architecture Project organization GP offices Hospitals GPs EPR Hospital systems Vendors of GPs EPR Vendors of hospital syst. NAV Pharmacies Labs NAV systems Pharmacy systems Lab systems NAV s dev. org. Vendor of the Pharmacies system Vendors of Lab systems

6 eprescription MyPresciptions Information on medicins in use eprescriptions information Prescription information EPJ- Systems Prescription Recall Hand-over message Deleted prescription Reply from Medicine Agency eprescriptions Exchange Request for expedition Prescription information Hand-over message Pharmacysystem Consent information Reference number Request for assessment by Gvt Medicine Agency Application NAV Prescription and expedition information Notification Application to of Medicine Agency hand-over Reply on application GP information Refund request Refunds and control (NAV) Reply on Refund request FEST (Gvt Medicine Agency) Application (Gvt Medicine Agency) Prescription and expedition information

7 Drifting Architecture Delays => Generic module for Profdoc users => Pharmacies => DIPS users Disagreements!

8 A few other projects Fürst Lab report transfer solution, 1987, 3 man weeks + 1 evening Lab ordering solution Edimed, Northern Norwegian Health Network Well/Dips Interactor Interactive admission letters BlueFox, Prescription register MyJournal

9 An alternative architecture GP office GP s computer GP s EPR system GP GP computer Client module Communication system/network Server module Project org. Lab/hospital Lab system Lab/hospital ICT architecture Project organization

10 Two architectures Non-communicating applications INA Architecture SPA Architecture

11 Two architectures 1. Application Centric/Institutional Interface Architecture (AC/INA) 2. Communication System Centric/Service Provider Architecture (CSC/SPA)

12 The SPA Paradigm Information flow ICT architecture Project organization GP offices Hospitals GPs EPR Hospital systems Vendors of GPs EPR Vendors of hospital systems Services ASP Project ASP National Welfare Agency Pharmacies Labs Welfare Agency Systems Pharmacy systems Lab systems Welfare Agencyde vel. org. Vendors Pharmacy system Vendors of Lab systems

13 Summary Care Record Systems Scotland: 3 MGBP (4M Euros, 4 M USD) Denmark: Official, top-down 10 M Euros, Faded out after about 4 years, officially cancelled after 8 Unofficial, bottom-up Great success Norway (eprescription) UK 500 MNOK, currently piloted in one GP office Started 2004, early adoption 2007, further deployment is frozen Spent 240 MGBP

14 Mirroring: Discussion Product producer!! Product user: Different prespectives INA: network of autonomus organizations SPA: Service providers consumers NNHN: Architecture supporting netw. Mgnt Architectural control points: eprescription Platform centric eco: Interactor, MyJournal INA: Appliances SPA: Generative

15 Discussion 2 INA/AC Complex technical solution Inflexible, cannot be maintained Very complex project organization Top-down Escalating complexity (destabilizing) Stabilizing (freezing) user practices Failure SPA/CSC Simple technical solution Flexible, easy to maintain Very simple project organization Bottom-up, evolutionary Stable complexity Destabilizing user practices (stimulating organizational innovation) Success

16 Conclusion: Generative Architecture?.. A technology s overall capacity to produce unprompted change driven by large, varied, and uncoordinated audiences. Capacity for leverage Adaptability Ease of mastery Accessibility Development, maintenance, evolution/extension/scaling/growth (users, functionality,.), adoption

17 Generative Architecture flexible and adaptable to new requirements as the II matures and scales. relate carefully to the structure of the organizations that are developing it, and with the user community. not contain any architectural control points that allow individual actors to take control over the whole infrastructure. extensible, to allow for new innovations extending the information infrastructure. self-generating or bootstrapable.

18 Strategic Health II Architecting Who? Ministry, RHF, Service provider, Software/communication service provider? Actors taking responsibility for health care Generative architectures Simple solutions Simple organizations Generative platforms

19 Top-down All stakeholders involved Each has separate requirements The more stakeholders involved, the more new requirements will be generated Each change: all stakeholders have their requirements.. Aims at stability generates destabilizing processes

20 Thank you!