What does a Clinical Architect Need to Know?
I have been asked a question by a colleague at the regional health authority where I have been consulting. Effectively, this question boiled down to:
What should I learn to become a Clinical Architect?
This is a tricky question, especially as the job descriptions for “Clinical Architect” are so variable, if they exist in organizations at all. Let’s use this brief job description:
The Clinical Architect will provide design leadership of major clinical information systems. Design leadership scope will include assessment and transformation of clinical processes, CIS functionality, clinical content modelling, CIS interoperability, and evaluation. Clinical domains would span all areas within the organization as well as major interfaces with other organizations (local, regional, or jurisdictional).
The clinical architect supports and mentors leadership (project and operations) on topics of informatics related to the choice, design, implementation, and refinement / adaption of clinical information systems over time. Is involved in the planning process, at an organizational level and project level. Assists in the development of standardized development / configuration processes within the organization.
I see the clinical architect a leadership role, with a small design team working with him or her. The one that I have recommended for the health authority looks like the diagram. While in this diagram everyone is an “architect”, those are just names. This is a design team that can span many areas of clinical information system needs.
Here are some of my initial suggestions for topics to cover if one is to be a Clinical Architect:
- General Enterprise Architecture
- Software Lifecycle and Design Methodologies
- Requirements Design / Engineering
- Modelling Notations
- Information / Data Modelling
- Health Information / Data Standards
- Standardized Nomenclatures
- User Centred Design / User Experience
- Privacy and Security Principles
- Evaluation and Benefits Realization
I will work to pull together additional posts on some of the topics over the coming weeks with some links.
I’m curious as to other’s thoughts as to what should be included in a curriculum for clinicians looking to lead the selection / design / customization / implementation of information systems. Please feel free to post a comment.
Related posts:
- Clinical Architect: General Enterprise Architecture NOTE: This post is a follow up from the overall...
- Clinical Architect: Requirements Engineering. NOTE: This post is a follow up from the overall...
- Clinical Architect and Software Lifecycles and Design Methodologies NOTE: This post is a follow up from the overall...
- Clinical Architect: Modelling Notations NOTE: This post is a follow up from the overall...
Related posts brought to you by Yet Another Related Posts Plugin.
