The resume for a nurse moving into informatics is already in your shifts

Step one: take inventory

Before you touch the resume, get a blank page and list what you do on a shift. Not what the job description says. What you do. Write fast and don't edit.

Then answer these, because they pull out the work people forget:

• When a system changed on your unit, who did people come to with questions?
• Have you ever been named a super-user (a staff nurse trained early on a new system who supports peers)?
• Did you work a go-live, the day a new system or module switches on for real patients?
• Have you reported a problem with a screen, an order set or a device, and followed it to a fix?
• Did you build anything people use to see the unit at a glance: a huddle board, a tracker, a shared sheet?
• Do you teach? New grads, float staff, students, the night shift on the new pumps?
• Do you sit on a practice council or committee that reviews documentation or policy changes?

You now have a messy list. Most of it is clinical, and that is fine. The next step is sorting it into three piles.

Step two: sort it

Every line on your list goes into one of these:

• Keep up top. Already systems work. Super-user roles, go-lives, device rollouts, anything with "build", "test" or "train" in it. These lead each role.
• Translate. Systems work wearing clinical clothes. Precepting, bug reports, the huddle board, committee work. True and useful, but written for the wrong reader right now.
• Shrink. Core nursing that every RN does. Charting, med pass, procedures. It stays on the page, compressed to a line.

Practice on eight common duties before you sort your own.

Keep up top: the super-user and go-live work

This is your strongest material, and nurses tend to write it as a single line near the bottom of a role. "Super-user for Epic." That tells an informatics reader you had a badge. It does not tell them what you can do.

A go-live has stages. Say which ones you touched:

• Before launch. Testing workflows, checking build against how the unit works, flagging gaps.
• Training. Who you taught, how (classroom, one-on-one, quick tip sheets), and on what.
• Go-live support. At-the-elbow support, which means standing next to colleagues while they use the new system on real patients and fixing problems as they come up.
• After. Issues you logged, escalated or helped resolve once the launch crowd went home.

Name the system and the module if you know them. Job posts in this field name specific EHR vendors (Epic, Oracle Health, MEDITECH and others), and a reader scanning for the one they run will stop on it. If you only used the system as an end user, say that plainly rather than implying you built it.

Translate: same work, new reader

Translating doesn't mean inflating. It means describing the part of the task an informatics team does all day. Teaching people to use a system. Spotting where a workflow breaks. Turning raw data into something a charge nurse can read at a glance.

"Steps to reproduce" is the phrase that matters. It means you described the problem well enough that someone who wasn't there could make it happen again. That is a core informatics skill, and you have been doing it on the phone at the nurses' station for years.

A flowsheet is the grid in the EHR where nurses document vitals, assessments and intake. If you have ever argued about which rows belong on it, you have done workflow design.

Shrink: the clinical list

This is the hard one for nurses, because the clinical work is the work. You are not hiding it. You are compressing it so the informatics material has room.

A long list of procedures (IV starts, wound vacs, Foley insertion, telemetry, blood administration) is what a clinical hiring manager scans for. An informatics reader needs to know one thing from it: you understand the care that the software supports. One line does that.

The same goes for charting. Every nurse charts, so "documented care in the EHR" adds nothing. The exception is when you changed how charting works. A template you proposed, a shortcut you taught, a duplicate field you got removed: that moves up to Translate.

Target title and summary

Informatics job titles vary by employer: clinical informatics nurse, nurse informaticist, clinical analyst, clinical applications specialist. Read the posting and mirror its title in your title line, as long as it describes the job you want and you can back it up below.

Keep "RN" visible. Your clinical license is the reason a hospital hires a nurse for this work instead of a general analyst.

"A passion for technology" is a feeling. "Two go-lives as super-user" is a fact a reader can check in an interview. Write the summary in your own voice, from the inventory you made, and keep it to two sentences.

Licenses and certifications

Give them their own short section, high enough to see without scrolling far.

• Your RN license stays. List it as Registered Nurse, the state, and that it is active. If you hold a multistate compact license, say so. The employer verifies the details with the board.
• Clinical certifications compress. BLS, ACLS and your specialty certification fit on one line.
• Informatics certifications exist, and you should know about them. The American Nurses Credentialing Center (ANCC) offers board certification in informatics nursing, and HIMSS (a health IT membership organization) offers health IT credentials. Each has its own eligibility rules. Read them on the certifying body's site before you plan around one.
• List only what you hold. If you are studying for one, say so in the cover letter or the interview, not as a line that reads like a credential.
• Vendor training counts. If you completed EHR vendor training or a certification through your employer, list it with the system name.

Putting it together

Here is the top of a resume for a fictional med-surg nurse after the inventory and the sort. Everything above the first job is informatics-facing. The clinical scope is still there, in one line at the bottom of the role.

Read the first three bullets without the job title above them. They could belong to someone already working in informatics. That is the point. The reader decides what you are from the top of each role, so the top of each role has to be the systems work.

Your turn

Pull out the inventory you made. Circle every Keep and every Translate. Then open the free editor, add an RN title line that names the informatics role you want, and rewrite the first bullet of your current job from the Keep pile. Write it yourself. Your words, not AI; nobody else knows what happened on your unit during that go-live.

If you want a second read once the draft exists, the one-time $2.99 Career Analysis Review looks at the resume you wrote and tells you what is landing and what isn't.