Will the EHR system be able to import Outlook or BCM data? If not, migration
may not be easy. I would first find out what format the main EHR systems
can import and plan from there. You don't want to spend hours creating the
records in Outlook only to discover you can't import them into the EHR
system.

BCM data is not accessible from OWA.

See http://msdn.microsoft.com/en-us/library/ee693018.aspx for info on
customizing OWA forms. It's not as simple as customizing an Outlook form and
having it available in OWA. It's actually a lot of effort - definitely more
effort than its worth for 6 months use. You could probably put something
together in Access with a SQL backend (SQL Express if your SBS doesn't
include it) that can be accessed using either Access or Infopath.

If it comes down to hiring someone to develop a system for you, you're
probably better off putting the funds into EHR (dev work can be pricey).
With just basic knowledge of Access and the desire to learn, you could do a
database yourself fairly easily. It won't be fancy, but it will store the
data. If your office version doesn't have Access (or Infopath), I wouldn't
buy it - save the money for the EHR and use sharepoint. It can be accessed
over the web (although you need to be sure its secure and in compliance with
HIPPA).


--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Do you sync your mailbox with a smartphone or pda?
http://forums.slipstick.com/showthread.php?t=39473



"Jim Robertson" wrote in message
...
On 3/21/10 9:52 AM, in article
, "Diane Poremsky [MVP]"
wrote:

I would not recommend BCM for this - I don't think I would even suggest
Outlook for it. I'd use Access or Infopath against SQL. Sharepoint is an
option too.

I'm looking at this as a VERY temporary solution (months to less than two
years) for a small LAN consisting of a an SBS 2008 server, 4 docs who work
with laptops on and off the domain, and 5 office staff with workstations
permanently on the domain. We're on a limited budget, and my idea was to
use
the tools we now have (MS Office Outlook for some staffers, Outlook Web
Access for others) to get patient and referring physician information into
a
contact form that would be usable now but capable of being migrated to a
commercial electronic health record once we purchased one.

Adding a second server box and upgrading our SBS license to premium and
buying BCM licenses for our office staff just to make our lives a little
bit
easier now and migration easier later (especially since after the
migration
we'd have no use for BCM) probably doesn't make sense.

I know nothing about InfoPath. I've peeked at its product page, which
suggest it can be used to design forms that can be opened in Outlook. I
also
haven't begun exploring SharePoint yet (I'm a Mac guy doing this in my
spare
time).

Is InfoPath a tool that I could use to modify the basic Outlook contacts
template so that users on our SBS domain using the full Outlook client or
OWA could open a contact form for patients that would contain the
additional
data elements (referring physician, Social Security Number, and yes/no
status fields for which a checkbox would be the interface element (active
patient, deceased, dialysis, and transplant would be examples)? Or would
we
need the SQL server?

Sorry to ask such basic questions. I'm taking baby steps here :-)

Jim Robertson