When people hear "Chief Information Officer," they think servers and software. In health, the CIO role is something else entirely. It's about connecting clinical need to operational capability, and making sure the systems that support patient care actually work for the people using them.
What You Need to Know
- The health CIO role sits at the intersection of clinical operations, data governance, and organisational strategy. It's not a technology role that happens to be in health.
- In New Zealand's primary care sector, CIOs rarely have the luxury of dedicated teams. They're often managing vendor relationships, infrastructure, training, and change management simultaneously.
- The most effective health CIOs spend more time with clinicians than with technologists. Understanding clinical workflows is the foundation of every good IT decision.
The Misconception
Most organisations outside health think the CIO is the person who keeps the lights on. Network uptime, server maintenance, helpdesk. That's part of it. But in health, the CIO's primary job is translation.
Clinicians speak in terms of patient outcomes, workflow efficiency, and clinical safety. Boards speak in terms of risk, compliance, and cost. Vendors speak in terms of features, platforms, and roadmaps. The CIO sits in the middle and makes these conversations productive.
67%
of health CIOs report spending more than half their time on strategic alignment rather than technology management
Source: HIMSS, CIO Leadership Survey, 2020
At RAPHS, my role as Information Systems Manager meant I was the person who had to understand what a practice nurse needed from her patient management system, translate that into a specification a vendor could build against, and then explain to the board why the investment was worth making. That translation work is the actual job.
What the Role Looks Like Day to Day
A typical week in health IT leadership doesn't look like what people expect.
Monday might be spent in a practice watching how reception staff manage patient flow, because a new booking system needs to work with their existing process, not replace it. Tuesday is a vendor call about an upgrade that will affect every GP in the network. Wednesday is a governance meeting about data sharing between primary and secondary care. Thursday is training support staff on a system change. Friday is reporting to the board on project status.
None of that is "technology" in the way most people understand it. It's operations, change management, stakeholder communication, and governance. The technology is the tool. The job is making sure it serves the clinical mission.
The Vendor Relationship
One of the least understood parts of the health CIO role is managing vendors. In New Zealand, the primary care IT vendor market is small. A handful of patient management system providers serve the majority of practices. The relationship with those vendors isn't just commercial. It's strategic.
A health CIO who only talks to vendors about features is missing the point. The conversation should be about how the platform supports the clinical model - and whether the vendor understands the model well enough to be a genuine partner.
Rikimata Massey
Health CIO Advisory
A good vendor relationship means honest conversations about what works and what doesn't. It means pushing back on feature roadmaps that don't align with clinical need. And it means accepting that no vendor product will ever perfectly fit your organisation, so your job is to close the gap through configuration, training, and workflow design.
Why It Matters
Health is different from other sectors because the consequences of getting IT wrong are measured in patient outcomes, not just lost revenue. A system outage in retail means lost sales. A system outage in health means delayed diagnoses, missed test results, and clinical risk.
$8.3B
estimated annual cost of health IT-related inefficiencies in Australasia
Source: Deloitte, Digital Health Report, 2020
That's why the CIO role in health can't be purely technical. It requires someone who understands clinical operations well enough to make good judgements about technology decisions. Not which platform has the best features, but which platform will actually be adopted by clinicians under real working conditions.
The organisations that get this right are the ones that treat their CIO as a clinical operations partner, not just the person who manages the IT budget. The ones that get it wrong usually discover the cost when their next implementation fails.