Should I learn SQL programming before applying for Analyst job?

My cousin is the CTO (chief technology officer) at a major hospital here in Seattle. Her and I were just discussing the qualifications for analysts the other day, as she was encouraging me to move into that area of nursing when I graduate next year. I have 7 years experience at a big software company (guess which one??). It's as a program manager, not software programming. She said with a nursing degree, some familiarity with software, and project management experience, I should have a fairly easy time finding an analyst job. She said that they want people who can bridge the software/nursing world, but specific software experience wasn't so important - that training generally comes on the job.

The big bummer for me is that I can't work as an analyst at her hospital, as she doesn't want any appearance of nepotism.

Would it be beneficial to start learning SQL or other types of programming in the meantime? Thank you for your responses!

Yes, it would be beneficial to learn SQL, but it really depends on the software your hospital uses; some vendors close the reporting piece (which uses SQL) and they only make it available to the database/reports person; other vendors give access to the database to those who ask.

For one of my jobs, I was able to troubleshoot SQL reports, or write my own for clients; for another vendor, I was denied access to the reports because I was not the reports analyst.

If you have the time to learn SQL, it is definitely a nice skill to have; even if you don't use it, it helps to know it as it makes it easier to communicate your requirements with your reports analyst, and it could also help you troubleshoot specific problems---again, depending on the vendor you use.

As far as programming...maybe if you have the time to take a class, but SQL would be my first priority.

If you have the time to learn SQL, it is definitely a nice skill to have; even if you don't use it, it helps to know it as it makes it easier to communicate your requirements with your reports analyst, and it could also help you troubleshoot specific problems---again, depending on the vendor you use.

I doubt there is an expectation to know SQL as as nurse informaticist, sure nice to have. But overall try to understand how DB's work, implemented, designed, so you can have a useful exchange with your programmers. Nothing was worse that when a non IT person would dictate requirements to the moon and not understand the feasibility, or more accurately non feasibility.

I doubt there is an expectation to know SQL as as nurse informaticist, sure nice to have. But overall try to understand how DB's work, implemented, designed, so you can have a useful exchange with your programmers. Nothing was worse that when a non IT person would dictate requirements to the moon and not understand the feasibility, or more accurately non feasibility.

To be more specific, probably best to say, take an introduction to database class. That's the class that teaches you as eleectrosaurus says, how databases work, how they are implemented, designed, etc, and they also give you an introduction to SQL. Then again, most colleges don't allow you to take an SQL course without first taking the intro to DB class. And even if you try to teach yourself SQL via a book, most books tend to have a nice intro to databases.