Client Scheduling and management app

[Bellamy]

Hey everyone,

I get my Adam this week (I hope). My girlfriend is an acupuncturist and is looking to get a tablet. However, at looking at the options available for both the iPad and Android apps, there's nothing she would find useful.

Specifically, she wants more than simple scheduling as she wants to includes notes on treatments performed, basic patient health information, etc.

At the same time, she doesn't need something as advanced as the PM software available for medical doctors.

So after talking with her about what she needs and would like in a tablet application, I have an idea for an Android tablet application (Adam first!). The target customers would be professional massage therapists, acupuncturists, and other client-based service providers. The focus is on speed of record access, creation, and updating. Is there anyone else out there that would be interested in using it?

I'm a crappy programmer (in fact, I haven't programmed in 10 years; I mostly work in documentation now), so if there is anyone who would like to assist me in the development of this project, please send me a private message or respond here!

Cheers!

[davidk]

Some of us are working on a notetaking and observation gathering app now for the Adam, check out the thread here:

http://www.notionaddicts.com/forums/...n-app-for-Adam

It's evolved quite a bit from where I thought it would be at first, and the first thing that we are working on is to have user defined form creation. So once that is ready, it maybe would meet your girlfriend's needs? The app will sync the data between the Adam tablet and a server at Google, then ultimate with desktop databases (Access, etc).

At the very minimum, maybe there is some source code you can reuse if the app is not otherwise a good match?

[MATrickett]

Yeah, the Reasonspace concept should be able to handle that easily, e.g. patient notes and the medieval profession was one of the original workflows/wishlists for the project.

[Bellamy]

Read what you guys are doing with the Reasonspace concept, and it seems like it will be a very versatile tool. I'll use the Adam mockup images you guys created fro Reasonspace and do some of my UI mockups (warning - I'm a very crappy artist!). I'll post them here when they're ready. If you think Reasonspace could handle it, that's great! But Reasonspace does seem a bit different in some key ways from what I have in mind.

1. What she needs is a tablet-only solution. She's not a power user, and will only get WiFi only to cut costs, so no regular synching with a server or cloud. The tablet software has to do everything she needs.
2. Data entry needs to be quick. She travels from house to house visiting patients, so can't spend a lot of time on the tablet. The UI has to be as few touches/gestures as possible.

And if things go well, I might even be able to implement record printing so client records can be printed via a USB printer. That is assuming the Adam recognizes printers over USB? Haven't heard any details yet. *Note to self, check it out.

One of the key functions the software needs to provide is two-way lookups. By that I mean users can browse the calendar to find past and current scheduling information and access patient/client information that way, or browse/search the client list and get details and scheduling information that way. The Adam is pretty powerful, and huge spreadsheets or graphing of information isn't needed. The Tegra2 should be able to handle notes, scheduling, and contact information pretty easily. Probably going to set an artificial limit of 100 or 150 clients just to prevent the DB from from getting too large too quickly.

Do plan to add PC synching eventually to create backups, but can for the moment just have the client DB loaded off a SD Card.

Anyway, time to call it a day. Will start on the UI mockups tomorrow.

And still looking for someone to assist in programming! I know you two are working on Reasonspace, but anyone else reading this is welcome to help.

[MATrickett]

Not wanting to hijack the thread or anything, but in response to these points...

1. What she needs is a tablet-only solution. She's not a power user, and will only get WiFi only to cut costs, so no regular synching with a server or cloud. The tablet software has to do everything she needs.

I can definitely agree with you on this. Ultimately the information is going to be resident on the tablet and the just where you "backup" to should be user-selectable. I'm not sure that I would be overtly keen on the sole use of the cloud, especially for sensitive data, given that it is susceptible to hacking.

2. Data entry needs to be quick. She travels from house to house visiting patients, so can't spend a lot of time on the tablet. The UI has to be as few touches/gestures as possible.

It was my understanding that this was one of the reasons for the desktop element--to design an individual workflow for your own needs and, after that, it's only used for backup/etc. I might have the wrong end of the stick, of course, but with the form design elements etc. that davidk is working on this should make it relatively easy than working purely with a database and having to get down and dirty with the SQL. The radical menu concept was there to allow further customisation, i.e. you select what you want to appear based upon what you do on a day-to-day basis. Of course, it's early days yet.

(Also, looking forward to seeing your UI concepts in that other thread.)

And if things go well, I might even be able to implement record printing so client records can be printed via a USB printer. That is assuming the Adam recognizes printers over USB? Haven't heard any details yet. *Note to self, check it out.

That sounds like something that would be useful in general, so certainly let people know how you get on with that.

One of the key functions the software needs to provide is two-way lookups. By that I mean users can browse the calendar to find past and current scheduling information and access patient/client information that way, or browse/search the client list and get details and scheduling information that way.

This ultimately seems to be an extension of the "tags" and how you query the database, or basically davidk's really big piece of paper.

Do plan to add PC synching eventually to create backups, but can for the moment just have the client DB loaded off a SD Card.

It certainly sounds that your project might crossover with the Reasonspace one, so that should help both projects along.

And still looking for someone to assist in programming! I know you two are working on Reasonspace, but anyone else reading this is welcome to help.

And I'll stop with the thread-derailment right now.