Solution architect
Solution architects design how a new or changed service will work end to end, from user needs and clinical workflows to applications, data, integrations, hosting, and security. They make sure each solution fits the organization's architecture, meets its safety, privacy, and interoperability needs, and can be built, run, and supported affordably.
- Family
- Architecture
- UK GDaD PCF role
- Solution architect (Architecture)
- ESCO occupations
- ICT system architect (ISCO-08 2511)
- On GitHub
- Role document · Role data
Levels
| Band | Role level | UK GDaD PCF level | Civil Service grades | Job evaluation points |
|---|---|---|---|---|
| 7 | Associate solution architect | Associate solution architect | HEO/SEO | 483 |
| 8a | Solution architect | Solution architect | SEO/G7 | 560 |
| 8b | Senior solution architect | Senior solution architect | G7 | 604 |
| 8c | Lead solution architect | Lead solution architect | G7/G6 | 655 |
| 8d | Principal solution architect | Principal solution architect | G6 | 699 |
In a digital health care organization
- Solutions often combine bought clinical systems, in-house services, and shared platforms, so architects must design across supplier boundaries.
- Design choices can introduce clinical hazards, such as lost results or wrong patient matching, so solution designs feed into the clinical safety case.
- Every new data flow of patient information needs a lawful basis and a data protection impact assessment, so architects work closely with information governance.
- Interoperability with other health and care organizations, using standards such as HL7 FHIR, is usually a core requirement.
- Some solutions include software that is a medical device, which changes the design, assurance, and supplier requirements.
UK GDaD PCF role description
A solution architect designs solutions for problems that affect the organisation.
In this role, you will:
- ensure a problem and the desired outcomes are properly defined
- ensure the scope of a solution meets the organisation's requirements
- stay up to date on technology trends and approaches
- understand organisational objectives and external drivers, for example, legislation or financial constraints
- work with others to develop business and technical strategies
- work within business and technical constraints
- design and document solutions so they can be implemented by the organisation
- comply with standards and governance
- communicate and work effectively with stakeholders
- manage risks and decisions in a transparent way
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.
ICT system architect
ICT system architects design architecture, components, modules, interfaces, and data for a multi-components system to meet specified requirements.
Essential skills and knowledge (23)
Skills and competences
- acquire system component
- align software with system architectures
- analyse business requirements
- apply ICT systems theory
- assess ICT knowledge
- create data models
- define technical requirements
- design enterprise architecture
- design information system
- implement ICT security policies
- integrate system components
- manage database
- manage system testing
- use an application-specific interface
- use markup languages
Knowledge
Optional skills and knowledge (69)
Skills and competences
- apply technical communication skills
- build business relationships
- design cloud architecture
- design database in the cloud
- design database scheme
- design for organisational complexity
- design process
- develop with cloud services
- manage cloud data and storage
- manage staff
- manage standards for data exchange
- perform resource planning
- plan migration to cloud
- provide cost benefit analysis reports
- solve ICT system problems
- use object-oriented programming
Knowledge
- ABAP
- AJAX
- APL
- ASP.NET
- Agile project management
- Assembly (computer programming)
- C#
- C++
- COBOL
- CoffeeScript
- Common Lisp
- Erlang
- Groovy
- Haskell
- ICT process quality models
- ICT project management methodologies
- ICT security legislation
- ICT system integration
- ICT system programming
- Java (computer programming)
- JavaScript
- Lisp
- MATLAB
- ML (computer programming)
- Microsoft Visual C++
- Objective-C
- OpenEdge Advanced Business Language
- Oracle WebLogic
- PHP
- Pascal (computer programming)
- Perl
- Process-based management
- Prolog (computer programming)
- Python (computer programming)
- R
- Ruby (computer programming)
- SAP R3
- SAS language
- Scala
- Scratch (computer programming)
- Smalltalk (computer programming)
- Swift (computer programming)
- TypeScript
- VBScript
- Visual Basic
- computer programming
- defence standard procedures
- image recognition
- information structure
- lean project management
- model based system engineering
- security engineering
- task algorithmisation
Contains ESCO v1.2.1 data (https://esco.ec.europa.eu/). © European Union. Reuse authorised under Commission Decision 2011/833/EU.