Recently, the Banking Industry Architecture Network (BIAN) published version 8.0 of its financial industry reference architecture. This provides a comprehensive model of the business capabilities, business scenarios, service domains and business objects used in banking and other financial services.
Like many of technology’s better creations, the IT4IT™ Reference Architecture standard was born out of necessity.
The IT landscape is continually shaped by innovation. Despite that being a cause for celebration for consumers and end-users, the introduction of these new technologies – such as the mainframe, the PC, client servers, the Internet, cloud computing, IoT, etc. – meant that the IT function had, effectively, lost track of what it needed to manage and control.
An open standard architecture-based approach to managing the business of IT was needed. This would have to be a holistic, end-to-end, service-based description of everything the IT function needs, and to be a good steward of all the IT components, solutions, and services within its remit. It was this issue that set in motion the train of events that brought us to where we are today. But there are no grounds for complacency. The work continues.
Even today the complexity and pervasiveness of, and the dependency on, IT systems continues to grow. In many cases, in many organizations today, the management solution is a loose collection of siloed processes. We are still not paying enough attention on how to remain in control. That is why the IT4IT standard is such an important instrument to manage IT, and why we have chosen to document how it came to be.
In this second article, I discuss key ideas and concepts underlying the design of a Reference Architecture for Health. Based upon the principles developed in the first article, these ideas and concepts describe what is needed. Together with the essential capabilities that we will introduce in a third article, they provide the input to how to build and deliver such a Reference Architecture. This document uses the following approach:
– From the large to the small: Start with the outer context, the overall Healthcare system, and refine into individual subject areas and building blocks
– Outside in: Start outside the organization, from the perspective of a customer, and design your organization around the needs of the customer
In this article, I’ll share guiding principles for a reference architecture for the Healthcare industry. The main beneficiaries of this reference architecture are patients, health professionals, and Healthcare organizations. Its main users are planners, managers, and Enterprise Architects. A second article will focus on key design ideas for such a reference architecture, followed by a third article to describe its essential capabilities.
Before describing the future Enterprise Architect, we will reflect on the current Enterprise Architect, one of their customers – a current line of business leader – and the strained relationship between them. For the sake of personalization, we will call the current Enterprise Architect ‘Archie’, and current line of business leader ‘Loretta’.
In the future state of Enterprise Architecture, the relationship between the two evolves towards one that is more productive and trusted. We describe what a future Enterprise Architect might look like and summarize the salient differences.
The Open Group hosted its latest event at the Marriott Riverwalk in the lively city of San Antonio, Texas. On January 27 – 30, we welcomed attendees from across the globe – including decision-makers, Enterprise Architects, Data Scientists, engineers, technologists, and end-users representing many businesses and governments – to explore how organizations can utilize their growing volume of data effectively and securely as part of a digital transformation program.