Before I worked in health IT, I spent years managing IT operations at Scion, the Crown Research Institute for forestry. On paper, forestry research and primary health care have nothing in common. In practice, the operational lessons translate almost directly. Systems thinking, stakeholder management, and the discipline of running IT for people whose real work has nothing to do with technology.
What You Need to Know
- IT operations at a Crown Research Institute taught foundational lessons about service reliability, stakeholder communication, and managing technology for specialist users who view IT as a tool, not an end in itself.
- Research environments share a key trait with clinical environments: the users are experts in their domain and deeply impatient with technology that gets in the way of their work.
- The transition from research IT to health IT revealed that the core operational challenges - uptime, data integrity, change management, vendor relations - are remarkably consistent across sectors.
What Scion Was Like
Scion sits in Rotorua, focused on forestry research, bioproducts, and wood processing. The research staff included scientists, engineers, and field researchers. My role as IT Operations Manager meant keeping the systems running that supported their work: laboratory information systems, research data repositories, collaboration tools, field data collection platforms, and the standard corporate infrastructure underneath it all.
$50M+
annual investment in NZ Crown Research Institutes' IT infrastructure across all CRIs
Source: Ministry of Business, Innovation & Employment, CRI Investment Report, 2020
The environment was demanding in ways that prepared me for health. Research operates on grant timelines. When a scientist has a funding deadline, the systems need to work. There's no flexibility in the schedule and no patience for downtime. A laboratory instrument that can't connect to the data system doesn't just create an inconvenience - it wastes research time that's funded by the taxpayer and can't be recovered.
That pressure to deliver reliable, uninterrupted service is the same pressure you face in health IT, with higher stakes.
Lessons That Transferred
Your users are not generalists
At Scion, I learned early that researchers don't think about technology the way IT professionals do. They think about their research. The technology is a means to an end, and they have very specific requirements that they articulate in domain language, not IT language.
A forest ecologist describing a data collection requirement doesn't talk about database schemas or API endpoints. She talks about plot measurements, species classifications, and longitudinal data series. My job was to translate that into a technical specification without losing the domain meaning.
In health, it's the same dynamic. A GP doesn't describe a referral workflow in terms of data flows and system integrations. She describes it in terms of patient need, urgency, and clinical pathways. The translation work is identical.
Reliability is non-negotiable
Research environments taught me that system reliability isn't a feature. It's the baseline expectation. At Scion, a system outage during a critical experiment could invalidate weeks of work. The tolerance for downtime was near zero.
Scion taught me that IT operations is not about technology. It's about understanding what your users are trying to achieve and making sure the technology never becomes the reason they can't.
Rikimata Massey
Health CIO Advisory
Health amplified this lesson. In primary care, system downtime doesn't just waste time - it creates clinical risk. A GP who can't access patient records during a consultation is making clinical decisions with incomplete information. The reliability standards I developed at Scion became the foundation for how I approached health IT infrastructure.
Change management is the real project
At Scion, rolling out a new research data management system taught me that the technology is maybe a third of the effort. The rest is change management: understanding how researchers currently work, designing the transition so it doesn't disrupt active projects, training staff in a way that respects their expertise, and supporting the messy period between old system and new.
Every health IT implementation I've been involved in since has confirmed this ratio. The technology works. The question is whether the organisation can absorb the change.
Data is the asset, not the system
Research organisations understand instinctively that their data is more valuable than any system that stores it. Decades of research data represent an irreplaceable institutional asset. Systems come and go. Data persists.
This perspective was invaluable when I moved into health. Patient data spans lifetimes. The system managing it today will be replaced by something else within a decade. The data migration, preservation, and governance practices I learned at Scion applied directly.
What Was Different
The differences between research IT and health IT are real and significant.
Stakes. At Scion, an IT failure cost research time and money. In health, an IT failure can affect patient safety. That changes the risk calculus for every decision.
Regulation. Health IT operates under the Privacy Act, the Health Information Privacy Code, and professional standards that research IT doesn't face. The compliance overhead is substantial and affects every system decision.
Scale of human impact. Research IT serves hundreds of staff. Health IT, even at a single PHO, affects the care of tens of thousands of patients. The downstream impact of every decision is larger.
Cultural complexity. Health IT in New Zealand must account for te Tiriti obligations, Māori data sovereignty, and the diverse health needs of communities that research IT doesn't typically encounter at the same intensity.
Why the Path Matters
I don't think my path from Crown Research to primary health is unusual. Many health IT leaders come from other sectors - telecommunications, banking, government. What matters isn't the sector you came from. It's whether you bring the operational discipline and the willingness to learn the clinical domain.
The best health IT professionals I've worked with aren't the ones with the deepest technical expertise. They're the ones who understand that the technology exists to serve the clinical mission, and who have the operational experience to make sure it does so reliably. That understanding can come from anywhere.