For the incoming MSHI cohort

You are about to spend two years in a programme that assumes you care about health systems and will tolerate a steep technical ramp. If you came from nursing, pharmacy, medicine, or public health, you are not behind. You are differently prepared, and the difference shows up in different weeks.

Week zero: orient before you optimise

Before you buy textbooks or install seventeen tools, do three things:

1. Read your programme's degree map. Identify which courses are methods-heavy, which are technical, and where the capstone or practicum lands. You cannot plan a term you have not mapped.
2. Find out what EHR your placement site runs. Epic, Cerner, Meditech, something else: the name determines which vendor-specific skills are worth your time and which are noise.
3. Locate one person one year ahead of you. Not the star of the cohort; the honest one. Ask what they wish they had done in term one. The answer is rarely "more Coursera."

First term: vocabulary before velocity

The comp sci cohort will look faster in the first lab. They are. That gap is real for roughly two terms and irrelevant by year two. Your job in term one is not to win the syntax race. It is to build a bilingual dictionary between clinical concepts and informatics concepts.

Prioritise learning that translates across employers:

• Data modelling basics: what is a relational table, what is a primary key, why duplicates break things. One afternoon of focused study closes most of the foreign-key anxiety.
• One query language, slowly: SQL or Python with pandas, pick whichever your programme emphasises. Learn to select, filter, join, and count. Stop there until the assignments demand more.
• Interoperability vocabulary: HL7 v2, FHIR, API, interface engine. You do not need to implement any of them; you need to recognise them in meetings.
• Your programme's research methods sequence. Boring until you need to read a paper for a stakeholder who cites one. Then it pays rent.

Defer, unless a course forces it:

• Vendor reporting tools (Epic Reporting Workbench, etc.)
• Cloud certification prep
• Building a portfolio app nobody asked for

How to use clinical background without leading with it

You have operational knowledge the syllabus cannot replicate. Use it strategically, not constantly.

Do: when a lecture describes a workflow that would never survive a busy shift, say so once, specifically. "This assumes the nurse has time to document before leaving the room" is useful. "In my experience nurses are busy" is not.

Do: volunteer for assignments that connect to settings you know, then hold yourself to the same evidence standard as everyone else. Clinical intuition is a hypothesis, not a citation.

Do not: answer every discussion prompt with a ward story. Your classmates will stop listening, and fair enough.

Do not: treat technical struggle as proof you do not belong. Treat it as a skill gap with a finite study cost.

Practicum and networking: the non-coursework work

Most MSHI value is front-loaded into relationships and placements. First term moves:

• Attend one informatics meeting at your placement site, even as a fly on the wall. Hear how projects are named, who owns decisions, what "go-live" means in that org.
• Keep a running glossary. When someone says "ADT feed" or "Clarity," write it down the same day. Review weekly. Vocabulary is the fastest-closing gap you have.
• Set a weekly office-hours visit with one instructor whose work interests you. Not to impress; to calibrate your reading list.

What "done" looks like at the end of term one

You are on track if you can:

• Explain what an API is to a clinician without using the word "endpoint" until the second sentence.
• Write a query or script that answers a simple counting question from a dataset your course provides.
• Read an abstract and locate sample, setting, and primary outcome without panic.
• Name one informatics problem at your site that is actually a workflow problem dressed in software.

You are not expected to ship production code, pass a vendor certification, or have a LinkedIn thought leadership arc.

Common first-term failure modes

Tool collecting: installing FHIR servers, BI platforms, and note-taking apps instead of finishing problem sets. Tools feel like progress. They are often procrastination with better branding.

Comparison spirals: measuring yourself against the CS grad who built an app in high school. They have a head start on syntax. You have a head start on knowing which problems matter. The job market wants both, in the same person, eventually.

Hiding clinical expertise: performing ignorance of the ward to seem "technical enough." The programme admitted you for the combination. Hiding half your CV helps nobody.

Ignoring writing: informatics is memos, requirements, slide decks, and emails that survive forwarding. If your programme offers a technical writing or policy course, take it early.

A blunt note on imposter feelings

The feeling that everyone else already speaks the language arrives in week one, usually in a computer lab. It fades slower than the actual knowledge gap closes. By the second year, the conversation often inverts: your classmates ask you what actually happens on a unit at 3 a.m., because the syllabus never covered it and it turns out to matter more than anyone admitted.

Learn the syntax. Keep the instinct. The programme is not trying to turn you into someone else. It is trying to give the person you already are a larger toolbox and a credential that opens doors.

That is the whole job for year one.