Enterprise architect
Enterprise architects give the organization a joined-up view of its services, information, applications, and technology, and use it to turn health and care strategy into a coherent plan for change. They set architecture principles, standards, and roadmaps, guide investment decisions, and make sure digital change supports safe, joined-up care for patients across organizations.
- Family
- Architecture
- UK GDaD PCF role
- Enterprise architect (Architecture)
- ESCO occupations
- enterprise architect (ISCO-08 2511)
- On GitHub
- Role document · Role data
Levels
| Band | Role level | UK GDaD PCF level | Civil Service grades | Job evaluation points |
|---|---|---|---|---|
| 8a | Enterprise architect | Enterprise architect | HEO/SEO | 560 |
| 8b | Senior enterprise architect | Senior enterprise architect | SEO/G7 | 622 |
| 8c | Lead enterprise architect | Lead enterprise architect | G7/G6 | 658 |
| 8d | Principal enterprise architect | Principal enterprise architect | G6 | 703 |
In a digital health care organization
- Care pathways cross many organizations and systems, so the architecture must support sharing of records, results, and referrals across boundaries.
- The estate often includes long-lived clinical systems, medical devices, and supplier contracts that are hard to change, so roadmaps must plan transitions carefully.
- Architecture decisions affect patient safety, privacy, and the resilience of services that run around the clock.
- Open standards such as HL7 FHIR, SNOMED CT, and IHE profiles are key to avoiding lock-in and enabling interoperability.
- Funding is constrained and closely scrutinised, so architects must show value for money and reuse of shared platforms where they exist.
UK GDaD PCF role description
Enterprise architects are leaders working across different levels within an organisation to translate the business strategy into business change and technical delivery.
In this role, you will:
- identify priorities for change to enable delivery at pace
- lead and influence the delivery of cross-cutting capabilities that enable change
- own the enterprise architecture vision, strategy and roadmaps from a business, technology and data perspective, including ‘as is’, ‘to be’ and transitional states
- consult and support collaboration across the business
- understand the organisation’s ecosystem and its interdependencies, including reference architectures
- take a strategic view across all architectural domains, portfolios and programmes
- guide the organisation to make appropriate business, technology and data decisions by recommending reuse, sustainability and scalability, to achieve value for money and reduce risk
- establish architectural principles, policies and standards
- collaborate and consult with stakeholders to assure business, technology and data decisions are aligned with enterprise architecture strategy
- develop the architecture community
- carry out horizon scanning across industry, identifying emerging trends and their potential impact and opportunity for the organisation
ESCO occupations and skills
ESCO lists the skills and knowledge that employers usually need (essential) or may need (optional) for each occupation. Use them as a checklist for development conversations.
enterprise architect
Enterprise architects balance technological opportunities with business requirements. They also maintain a holistic view of the organisation's strategy, processes, information and ICT assets and link the business mission, strategy and processes to the ICT strategy.
Essential skills and knowledge (23)
Skills and competences
- align software with system architectures
- apply ICT system usage policies
- collect customer feedback on applications
- define software architecture
- design enterprise architecture
- design information system
- execute feasibility study
- identify processes for re-engineering
- implement ICT security policies
- keep up with the latest information systems solutions
- manage ICT data architecture
- perform project management
- perform risk analysis
- provide ICT consulting advice
- review development process of an organisation
- use an application-specific interface
Knowledge
Optional skills and knowledge (68)
Skills and competences
- analyse business requirements
- apply conflict management
- apply information security policies
- apply systemic design thinking
- build business relationships
- coordinate technological activities
- manage cloud data and storage
- manage staff
- monitor technology trends
- optimise choice of ICT solution
- provide cost benefit analysis reports
- use different communication channels
Knowledge
- ABAP
- AJAX
- APL
- ASP.NET
- Agile development
- Agile project management
- Assembly (computer programming)
- C#
- C++
- COBOL
- CoffeeScript
- Common Lisp
- DevOps
- Erlang
- Groovy
- Haskell
- Java (computer programming)
- JavaScript
- Lisp
- MATLAB
- ML (computer programming)
- Microsoft Visual C++
- Objective-C
- OpenEdge Advanced Business Language
- PHP
- Pascal (computer programming)
- Perl
- Process-based management
- Prolog (computer programming)
- Prototyping development
- Python (computer programming)
- R
- Rapid application development
- Ruby (computer programming)
- SAP R3
- SAS language
- Scala
- Scratch (computer programming)
- Smalltalk (computer programming)
- Spiral development
- Swift (computer programming)
- TypeScript
- VBScript
- Visual Basic
- Waterfall development
- business process modelling
- business requirements techniques
- computer programming
- emergent technologies
- incremental development
- iterative development
- lean project management
- software architecture models
- software design methodologies
- system design
- unified modelling language
Contains ESCO v1.2.1 data (https://esco.ec.europa.eu/). © European Union. Reuse authorised under Commission Decision 2011/833/EU.