Calling programmers

[_Stretchie_]

Just an idea.

It would be good for me and where I work if I could write a programme on the mobile Android platform. Only problem is last time I wrote code was on my Spectrum 128k and it made funny coloured squares bounce around the screen and that was about 22 years ago.

Obviously not planning to become a master programmer overnight or anything but how would you suggest I could go about it and set off on the right foot.

An example of what I mean.
I work for the NHS, and in the persuit of innovation and making things easier / cheaper for us and our staff it would be good if I could write something to speak to an SQL databse written by our DBA team on site so that clinical staff could download some case files to their device (Android phone) that contains the data required to consult with the patient, go and see patients and fill in forms on the device and then when they get back home or to the office they can upload the information securley back into the database to update the information held. And then the information could be reported on.

The stock answer of 'Do a course' is a good one but what course?

Looking into Android developer courses they seems to say that as a pre-req you want to have:
Java skills
An understanding of Java technologies
and the J2ME and experience with Eclipse would be useful

Also being able to self teach would be an advantage as it would be cheaper for the organisation.

Ideas on a postcard...

It's not a small undertaking, if you have no programming background.

Check your local university and see what sort of "continuing education" courses they may offer for non-traditional students who want to learn about, for example, computer programming. You may find an introductory JAVA course there, and you may even be able to do it all online. This should familiarize you with the fundamentals of the language.

An alternative might be a private school running a course on JAVA, at an introductory, intermediate or advanced level.

Once you know some basics, you should be able to use the Eclipse IDE and ANT for your coursework, and subsequent development projects.

Then have a look at Android and how to incorporate that into your project.

Finally, get your hands on some books such as "The Pragmatic Programmer" by Andrew Hunt, so you can get into some good habits.

Good luck!

[timwilky]

Java is easy to learn as a core language. Next you then need to think about object orientated design. Again easy once you understand the concepts (Many don't).

what is hard is the different technologies floating about, different frameworks, etc. There is a solution out there most most things. good design patterns are published.

Most of my stuff is java stuff struts, servlets, ldap, database integration, J2EE. I however tend to "prototype" and then let other industrialise, whilst I play with the next interesting thing.

Oh and to above, learn XML

[TSM]

Java in Android is aparently stripped down from the normal versions on most mobile platforms.

Set yourself up with Eclipse IDE, there should be some plugins to assist android development.

[Vindaloo]

^^^ What they said.

A lot of standard programming courses are likely to be in the Java language anyway, so there's quite a good chance of that. If you've got a fair idea and have programmed before, then perhaps reading a 'Teach yourself Java in 21 days' might suffice ... depends on your aptitude, etc. The basic fundamentals of Java will be the same (looping, variable use, etc.) but you'll be calling different functions (and some won't exist)

The only thing I'd add is to point out any security issues with patient data going missing ... should the software would have to be locked to work only on particular phones that are hospital property, etc.

Though I think most of that data can be freely gained from laptops kindly left on trains.

Adrian

I'd also look into seeing whether you'd be allowed to do that, as well as whether its possible - I'm sure you know how paranoid they are about access to patient information.

Technically though, its as TSM said: Eclipse is the weapon of choice, and the database connection side is covered in the API documentation (all here)

[SoulKiss]

Its a big job (the actual app, not the Android stuff)

As TSM said, Eclipse can be set up for Android - I know, I am looking at Android Dev myself.

The actual App is doomed to fail - there are all sorts of Data Protection issues that will need to be considered - what happens then a phone that has downloaded records on it goes missing for example...

You would really need to be working with the guys that created the system, as they will have the overview of how the system you are trying to tap into works, as well as the security and privacy issues.

Its probably FAR too much work to be developed under "Skunkworks" conditions...

I agree with many of the comments, it's a very big task. If I had to pick something which I was knowledgable about, Java would be near the top of the list, much of my work involves it & I've been using it for around 10 years now.

However I don't think it's the fact it's Java especially, the main thing is just how much background experience and knowledge you might find useful (if not strictly *needed*). Having and using that knowledge is the difference between a good programmer and a bad programmer. The kind of things I'm referring to are design principles, that sort of thing. Stuff that's lower level than design patterns which were mentioned above...and if you have to learn all that, so you can do it right as opposed to just doing it? It's a mammoth task IMO...it's very easy to program badly, there are probably 10 bad programmers for every 1 good programmer (IME).

[_Stretchie_]

Cheers for the responses fellas. Security wise it would be no different to having a laptop (which I hasten to add we do not keep patient data on) It is all encrypted up and the encryption software also covers things like external drives.

If the device cannot be encrypted then it would not be used. That is the reason I mentioned downloading the casenotes only for the particular cases that will be seen that day and there would be some sort of ID key so that the devices know which patient the information would be for and the clinician would know who they are seeing so that would all mnatch up. Also the idea of uploading/downloading the data directly to the computer over a secure NHS connection would be in place instead of transmitting over the airwaves. We don't even really use wireless connection for that very reason in the buildings.

We have wireless but it's only used for non patient activities

This could be a minefield for someone with no recent programming knowledge.

You mention downloading case files. These would then need uploaded back to the system once you've made your changes. If someone else makes a change to these files - whose changes take precedence?

I do want to put you off.

I think you need to discuss this with people their hands on the purse strings and either get someone more techncal in-house to do it or hire a developer that has worked within the NHS-confines before.

If you were doing a small app to get familiar with the basics of programming that would be one thing - but to jump in with this, I think it's gonig to be too much. You'll need to know more than just the basics of Database Design & implementation, Object Orientated Programming, project manangement and how this will work within the parameters set down by the NHS.