Mani
On 11/6/05, Dave Wolf <[EMAIL PROTECTED]> wrote:
>> and all they look for is speed, clarity and
ease of use.
And that's all as users they should care about! I'm not sure that
makes healthcare users any different from every other user. All the
more reason to focus on the user experience first, and use your
engineering experience to implement a performant back-end. The RIA
world gives you a lot more flexability to do that.
On the healthcare side here in the U.S. HIPAA is a huge issue to keep
in mind in terms of security and privacy. We did a lot with LifeCoach
to manage security and privacy in a HIPAA world.
--
Dave Wolf
Cynergy Systems, Inc.
Macromedia Flex Alliance Partner
http://www.cynergysystems.com
Email: [EMAIL PROTECTED]
Office: 866-CYNERGY
--- In [email protected], Aldo Bucchi <[EMAIL PROTECTED]> wrote:
>
> I built a dental clinic diagnose and image/mmedia management
software once.
> the only things I could really say are quite obvious:
>
> - get to know the biz and the users. you will have to learn the
> processes involved to a good detail if you want to be a valid
> interlocutor. there's lots of new words...
> - release early and gather feedback ( go and get it, don't expect a
> written summary from a doctor )
> - don't take feedback as-is, try to guide and educate users into
> accepting your ideas. health related professionals are quite hard
> headed and have been taught to do things in a very particular way ( I
> used to [almost] be one ), but if you get them to see the advantage
> they will understand... and all they look for is speed, clarity and
> ease of use. this might sound similar to dealing with eingeneering or
> business pros, but I must emphasize the "particular way" part. they
> are really different! most of them don't have a solid eingeneering
> foundation and miss some concepts that are obvious to most of us. so
> don't be afraid to presume that they don't know what they are talking
> about when they come and propose a database schema or some UI changes
> for the app.
> OTOH, they have strong communicational skills, so you can easily
> gather valuable use case stories if you know how to question them...
> - try and work with female, young nurses. I'm not sure why, but work
> becomes more fun.
>
> dont know if it helped but you sure brought back some memories.
>
> best,
> aldo
>
> On 11/6/05, JesterXL <[EMAIL PROTECTED]> wrote:
> >
> > My learned lesson: plan for an alpha/beta site early. Building
an internet deployed app is stupid if only 5% of hospitals in the
country have internet access, and that 5% will not compensate for your
development costs.
> >
> > Also, you can get away with things that are fluff; although the
nurses who typically use healthcare like it for about a day, and then
ask for it out of their way, they aren't the ones going to HIMMS, and
writing the million dollar checks to purchase software. When
competing with the likes of Kaiser Permente and others; many have the
same functionality. To stand apart, you have to differentiate
yourself, and Flex/Flash allows you to do that.
> >
> > It's easier to get the "harmless Flash Player" installed on a 6
month-to-build-client-box for a hospital than it is for the likes of
.NET runtime, where you're likely be told to f'off. Use that to your
advantage.> --
> >
> >
> >
> > ----- Original Message -----
> > From: Manuel Saint-Victor
> > To: [email protected]
> > Sent: Saturday, November 05, 2005 9:26 PM
> > Subject: [flexcoders] Requesting feedback from Flex developers
with experience building healthcare applications
> >
> > Good evening,
> >
> > I'm looking for some feedback from some of the developers here.
I'm curious about some of the ways that you have seen Flex used thus
far in the development of applications for use in healthcare. I'm
aware that UNC Chapel Hill has a Flex based application but am not
aware of the details of what functionality it provides.
> >
> > I am in the process of writing a proposal for one of my
attendings to suggest Flex as the tool for the development of a
virtual clinic environment.
> > The part that has me nervous is that although I have ideas and
see the many ways that Flex can be used in the delivery of remote
care I have no hardcore experience or anecdotes of what hurdles
developers have come across in implementing true healthcare delivery
tools.
> >
> > Any stories of successes or failed attempts or known specific
pitfalls would really help.
> >
> > Thanks,
> >
> > Mani
> >
> >
> >
> > --
> > Flexcoders Mailing List
> > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> > Search Archives:
http://www.mail-archive.com/flexcoders%40yahoogroups.com
> >
> >
> >
> >
> > SPONSORED LINKS
> > Web site design development
Software design and development
Macromedia flex
> > Software development best practice
> >
> > ________________________________
> YAHOO! GROUPS LINKS
> >
> >
> > Visit your group "flexcoders" on the web.
> >
> > To unsubscribe from this group, send an email to:
> > [EMAIL PROTECTED]
> >
> > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
> >
> > ________________________________
>
>
>
>
> ::::: Aldo Bucchi :::::
> mobile (56) 8 429 8300
>
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service .
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
